Skip to content

Feat/fshsp 95 deploy pages - #36

Merged
LBU4SH merged 2 commits into
mainfrom
feat/fshsp-95-deploy-pages
Aug 14, 2026
Merged

Feat/fshsp 95 deploy pages#36
LBU4SH merged 2 commits into
mainfrom
feat/fshsp-95-deploy-pages

Conversation

@LBU4SH

@LBU4SH LBU4SH commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator

FSHSP-95 — Deploy the demo app to GitHub Pages alongside Storybook

LBU4SH added 2 commits August 14, 2026 16:06
…ybook

Storybook stays at /starter-angular/, the demo lands on /starter-angular/demo/.
Both builds are merged into one directory before upload-pages-artifact, Pages
accepting a single artifact.

GitHub Pages honours exactly one 404.html, the one at the site root, so it has
to serve both surfaces: it is the demo's SPA shell, guarded by an inline
redirect that sends anything outside /demo/ back to the Storybook home.

Two fixes the deployment made necessary:

- `npm run build` failed on main: ui-motion.demo.ts passed null to
  `motionDuration` (`input<string>()`). Only the AOT build catches it — the PR
  workflow type-checks with `tsc --noEmit`, which ignores Angular templates,
  and no workflow ran `npm run build` until now.
- The favicon was declared before <base> and reached above the deployment
  sub-path (`../assets/favicon.png`), so it resolved outside /demo/.

Cross-links both ways: a topbar entry in the demo, a section on the Storybook
home page.

(cherry picked from commit 3bbe93f684fdabd801c5aecfae78fb17724b7adc)
@LBU4SH
LBU4SH force-pushed the feat/fshsp-95-deploy-pages branch from 72b9747 to 2470731 Compare August 14, 2026 14:06
@LBU4SH
LBU4SH merged commit e11bc23 into main Aug 14, 2026
2 of 3 checks passed
@LBU4SH
LBU4SH deleted the feat/fshsp-95-deploy-pages branch August 14, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant