A static Astro site using shared terminal styling. The CV lives at /, the portfolio at /portfolio/, and project case studies at /portfolio/projects/{slug}/.
Use Node 24 LTS (nvm use if you use nvm), then:
npm ci
npm run devnpm run dev refreshes Astro's development content cache on startup so changes to project metadata and schema defaults are applied to every entry. Starting it again replaces this project's existing dev server. With the dev server running on port 4321, npm run validate:dev checks that the portfolio contains all seven listed projects in the intended order and omits the hidden entries.
npm test builds the site and validates generated pages, portfolio selection and order, internal links, static assets, indexing metadata, analytics and preservation of the original CV content. npm run preview serves the production build locally.
Optional Astro/TypeScript diagnostics can run without adding application dependencies:
npm exec --yes --package=@astrojs/check --package=typescript -- astro-checksrc/content/projects/*.md: project metadata and case-study copy. The filename determines the URL slug. Keep existing filenames stable when changing a display title.src/content.config.ts: project fields and validation.src/assets/projects/: original project screenshots, named by project slug.src/components/CvContent.astro: existing CV content.src/layouts/TerminalLayout.astroandsrc/styles/global.css: shared layout, themes and visual styling.public/: fonts, vendored analytics, robots policy and custom-domain configuration.DESIGN.md: design decisions and remaining editorial questions.
Each project needs a title, summary, context, role, order and at least one link. Collaborators, status, tags, highlights and a featured flag are optional. Keep external resources in frontmatter links, where the template adds analytics consistently. Optional sections may be omitted; do not invent dates, outcomes or metrics to fill the template.
Use order for project sequencing and placement to control the overview: primary (the default) shows a full preview, supporting shows a compact text entry, and personal shows a small link. Set placement: "hidden" to remove an entry from the overview and next-project navigation while keeping its direct case-study URL available. Restore it by changing the placement and setting its desired order.
For a report download, put the PDF in public/reports/ and add a resource link with a root-relative .pdf URL and download: true. The shared template adds the browser's download attribute and click tracking. T.R.I.B.E. uses /reports/tribe-selected-report.pdf; its selection of source pages is recorded in DESIGN.md.
To add or replace a portfolio preview, put the original image in src/assets/projects/ and add this optional frontmatter field to the project's Markdown file. The path is relative to that file; alt must describe the screenshot and cannot be empty.
screenshot:
src: ../../assets/projects/aime.png
alt: AI.M.E. dashboard showing the FTSE 350 AI maturity assessment.Primary project previews appear beneath their summaries on the portfolio overview and link to their case studies. Astro generates responsive WebP images at build time; previews retain their full proportions and load lazily. See Astro images in content collections. The intake folder screenshots/projects/ is ignored by Git; the copies in src/assets/projects/ are the maintained source assets.
All pages carry noindex, nofollow. Crawling is allowed so search engines can read that directive; a blanket Disallow can prevent this. See Google's guidance.
The Validate site workflow builds and validates pushes and pull requests. Every push to main, including a merged pull request, automatically publishes the site after the build and validation pass. Pull requests and pushes to other branches validate without deploying. Manual deployment from main remains available.
On 16 September 2026, GitHub Pages was verified to use GitHub Actions as its publishing source, with the jameswolman.dev custom domain and HTTPS enforcement preserved. The github-pages environment permits deployments from main.
Follow this sequence to publish the Astro migration:
- Open Settings → Pages. Under Build and deployment → Source, confirm GitHub Actions is selected. If it still says Deploy from a branch, switch it before merging the migration. Preserve
jameswolman.devand Enforce HTTPS. Skip the suggested workflow templates; this repository already contains the deployment workflow. - Open the portfolio branch comparison, create a pull request from
feature/portfoliointomain, and merge once its checks pass. - After merging, open Actions → Validate site and select the run triggered by the push to
main. Deployment starts automatically; no manual trigger is needed. - Confirm both jobs finish successfully.
buildcompiles Astro, uploads thedist/artifact and validates the generated site.deploypublishes that artifact to GitHub Pages after validation passes. A skippeddeployjob is expected for pull requests and runs on other branches. If the build or validation fails, deployment is skipped. - Visit the CV and portfolio, then open a project page. Check navigation, images, the custom domain, HTTPS and the expected
noindex, nofollowmetadata.
For subsequent releases, merge verified changes into main, then repeat steps 3–5 to monitor the automatic deployment and check the live site.
To deploy manually, open Actions → Validate site → Run workflow, select main, and click the green Run workflow button. This builds, validates and publishes the selected branch's current revision; deployment is restricted to main.
Official references: Astro on GitHub Pages, GitHub Pages publishing sources.