Website Publication

Static publication surface

The website is a static SvelteKit professional publication surface. It publishes selected public profile, resume, evidence, and machine-readable material without relying on a live application backend.

• Built with SvelteKit static output rather than a server-rendered runtime.
• Public pages render from committed source content and static assets.
• Deployment headers define browser-facing security and cache behaviour.
• Each major human route declares page identity and social preview metadata.
• Generated public files can be served without a dynamic application server.

Public route system

The public site is organized around a small set of intentional entry routes for human readers and machine readers.

• The homepage introduces the profile, public links, resume entry point, highlights entry point, and canonical JSON pointer.
• /resumes lists the active role-specific resume projections.
• Resume detail routes publish the HTML versions for each active projection.
• /highlights lists the public evidence highlight routes.
• Highlight detail routes publish bounded evidence pages, including this Website Publication page.
• /canonical.json, /llms.txt, /sitemap.xml, and robots.txt provide public machine-readable and discovery surfaces.

Resume projection surface

The active resume surface is projection-based. It publishes three reviewed role-specific resume paths from the same public profile and evidence model.

• The three active public projections are IT Support, Technical Operations, and AI / Process Improvement.
• Each projection has a human-readable HTML detail route linked from /resumes.
• Each projection also has a reviewed static PDF artifact under /resumes.
• The resume index opens PDFs in a new tab; resume detail pages expose a Save PDF action using the browser download attribute.
• Unknown or inactive resume projection slugs resolve to a not-found state rather than a generated resume.

Machine-readable surfaces

/canonical.json is the authoritative structured public surface. It is generated from build-time content modules and exposes selected public profile, practice, evidence, resume projection, artifact, and publication-boundary data.

• Machine readers are directed to start with resume_projection_index.
• The canonical payload declares active projection metadata, HTML routes, PDF artifact paths, evidence relationships, and publication boundary notes.
• /llms.txt points machine readers to /canonical.json and summarizes the intended reading path.
• /sitemap.xml lists intentionally exposed public routes and PDF artifacts.
• robots.txt allows crawling and points crawlers to the sitemap and canonical JSON surface.

Portrait entry behaviour

Portrait entry behaviour is visual navigation state. It is not application loading, resume generation, or data fetching.

• Portrait images are attached to selected entry surfaces, including the homepage, resume area, and highlight detail pages.
• The visual fade state is tracked separately from interaction readiness.
• Controls can become available before the portrait fade has fully completed.
• Reduced-motion preference skips the long fade path.
• Resume-area navigation suppresses repeated automatic portrait intros while moving between active resume pages.

Floating actions and accessibility

Floating actions are simple action lists for route navigation, top-of-page actions, and PDF access. They are not clipboard controls or complex menu widgets.

• The Actions trigger opens a grouped list of links or buttons.
• Opening the list moves focus to the first available action.
• Escape closes the list and returns focus to the trigger.
• Button actions close the list after running.
• Link actions close the list and may carry portrait handoff state for supported home navigation.

Publication boundary

This website publishes reviewed public material. It does not expose private development state, old project routes, or runtime resume generation.

• The public model is bounded to selected professional profile, evidence, projection metadata, and artifact data.
• Runtime job-description ingestion and bespoke resume generation are not supported by this site.
• Only reviewed committed PDF artifacts are published from this repository.
• Retired or unknown public links fall back to the current not-found page and active entry points.
• Future generation systems, if used, are separate from this static publication surface.