Every PR, push to master and manual run: lint, format, tests, build, dependency audit, and Lighthouse on mobile and desktop.
Test: deploys automatically on a push to master, and from any branch with "Deploy to Test". It goes to the Raspberry Pi with nginx; the deploy step refuses folders containing WordPress.
Production: manual only, from release/* branches. It uploads over FTP with TLS to the IIS webhost.
Server config: web.config and both nginx configs are generated from the same security header list (pnpm server-config), and a test fails if they drift.
Repository settings: .gitattributes forces LF line endings, and pnpm is pinned through packageManager.
What this PR run should verify
Not verifiable locally:
Playwright Chromium installs and starts on the linux-arm64 runner
Lighthouse runs in the container (mobile and desktop)
pnpm format:check passes on a fresh checkout (line endings)
A PR run does not deploy. Before merging, set the Actions secrets and variables (see aidlc-docs/features/frontend-shell/operations/deployment/deployment-instructions.md, section 1.1).
When merging, keep the branch. Work on getting the pipeline running continues on feature/frontend-shell.
Completes the front-end shell and adds the CI/CD pipeline.
## Front-end shell
- Footer (brand, socials, contact; e-mail address joined in the browser), back-to-top button, skip link, and four placeholder routes.
- 404 and error pages inside the shell.
- SEO from one page registry: canonical URLs, Open Graph image, JSON-LD, generated `sitemap.xml` and `robots.txt`.
- Theme tokens and recipes instead of repeated styling.
- The hero loads only the active and neighbouring slides. Home download went from 2.6 MB to 1.2 MB.
- Tests: Vitest with property-based tests (fast-check) and axe checks, plus ESLint. 93 tests pass.
## CI/CD (`.gitea/workflows/continuous_integration.yaml`)
- **Every PR, push to `master` and manual run**: lint, format, tests, build, dependency audit, and Lighthouse on mobile and desktop.
- **Test**: deploys automatically on a push to `master`, and from any branch with "Deploy to Test". It goes to the Raspberry Pi with nginx; the deploy step refuses folders containing WordPress.
- **Production**: manual only, from `release/*` branches. It uploads over FTP with TLS to the IIS webhost.
- **Server config**: `web.config` and both nginx configs are generated from the same security header list (`pnpm server-config`), and a test fails if they drift.
- **Repository settings**: `.gitattributes` forces LF line endings, and pnpm is pinned through `packageManager`.
## What this PR run should verify
Not verifiable locally:
- [x] Playwright Chromium installs and starts on the `linux-arm64` runner
- [x] Lighthouse runs in the container (mobile and desktop)
- [x] `pnpm format:check` passes on a fresh checkout (line endings)
A PR run does **not** deploy. Before merging, set the Actions secrets and variables (see `aidlc-docs/features/frontend-shell/operations/deployment/deployment-instructions.md`, section 1.1).
**When merging, keep the branch.** Work on getting the pipeline running continues on `feature/frontend-shell`.
Generated with [Claude Code](https://claude.com/claude-code)
Workspace detection, reverse engineering of web/, requirements with
answered verification questions, the execution plan and the open
application design questions for the frontend-shell feature.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Component boundaries, interfaces, services and dependencies for the
shell: footer, back-to-top, skip link, status pages, page intro,
shared RouterLink, content folder and navigation module. Includes the
answered design questions and the revised site content requirement.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds the footer, back-to-top button, skip link, placeholder routes,
404 and error pages inside the shell, plus per-page SEO from a single
page registry (canonical URLs, Open Graph image, JSON-LD, generated
sitemap.xml and robots.txt).
Theme tokens and recipes replace repeated styling, the hero loads only
the active and neighbouring slides, and the e-mail address is joined
in the browser to keep it out of the HTML and bundle.
Adds Vitest with property-based (fast-check) and axe tests, ESLint,
security headers for dev and preview, Lighthouse CI and a `pnpm check`
script that runs all quality gates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Functional design, NFR requirements, code generation plan and summary,
and build-and-test instructions with results.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pipeline runs lint, format, tests, build, dependency audit and
Lighthouse (mobile and desktop, Playwright Chromium on the arm64 runner)
on every pull request, push to master and manual run.
Pushes to master deploy to test automatically, and any branch can be
deployed to test manually. Test is a Raspberry Pi with nginx next to the
current WordPress site; the deploy refuses folders containing WordPress.
Production deploys are manual and only from release/* branches, over
FTP with TLS to the IIS webhost.
The IIS web.config and both nginx configs are generated from the same
security header list as the Vite servers, with a test that fails when
the generated files drift. Adds .gitattributes for LF line endings and
pins pnpm through packageManager.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first render with axe takes up to 7 s on the Raspberry Pi runner,
above Vitest's 5 s default; the suite now allows 20 s per test. Also
silences the router warning in the test that crashes a page on purpose,
and makes the nginx test config return 404 instead of a redirect loop
(500) while the test folder is still empty.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The echo message contained unquoted parentheses, which cmd.exe accepts
but sh on the CI runner rejects as a syntax error.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The container's /dev/shm is limited to 64 MB, which makes the browser
tab crash on the image-heavy home page. Chrome now uses /tmp instead
via --disable-dev-shm-usage.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lighthouse slows the CPU 4x relative to the measuring machine, so the
Raspberry Pi runner scores performance 30-40 points lower than a PC for
the same build. In CI the performance assertions now only warn;
accessibility, best practices and SEO still block, and performance still
blocks in `pnpm check` on a PC. Mobile and desktop reports go to
separate folders and are attached to every run as an artifact.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sluijsens
scheduled this pull request to auto merge when all checks succeed 2026-10-19 01:24:33 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Completes the front-end shell and adds the CI/CD pipeline.
Front-end shell
sitemap.xmlandrobots.txt.CI/CD (
.gitea/workflows/continuous_integration.yaml)masterand manual run: lint, format, tests, build, dependency audit, and Lighthouse on mobile and desktop.master, and from any branch with "Deploy to Test". It goes to the Raspberry Pi with nginx; the deploy step refuses folders containing WordPress.release/*branches. It uploads over FTP with TLS to the IIS webhost.web.configand both nginx configs are generated from the same security header list (pnpm server-config), and a test fails if they drift..gitattributesforces LF line endings, and pnpm is pinned throughpackageManager.What this PR run should verify
Not verifiable locally:
linux-arm64runnerpnpm format:checkpasses on a fresh checkout (line endings)A PR run does not deploy. Before merging, set the Actions secrets and variables (see
aidlc-docs/features/frontend-shell/operations/deployment/deployment-instructions.md, section 1.1).When merging, keep the branch. Work on getting the pipeline running continues on
feature/frontend-shell.Generated with Claude Code