redesign 00 — foundation: the redesign stack (rails, covers, typographic system) #5
Loading…
Reference in a new issue
No description provided.
Delete branch "redesign/00-foundation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
The redesign foundation lands on
main— the full slice stack merged intoredesign/00-foundation(docs + decided feature set, terminal chrome, typographic system, layout rails, article covers, syndication/perf and a11y sweeps).Highlights of the final slices:
max-w-imagerail (container lives inbase.html, overridablepage_containerblock); custom layouts opt outcoverfield: per-post cover image,cover: falseto disable;thumbnailkeeps feeding listings + og:imageDeploy
Merge triggers the Forgejo Actions deploy pipeline (test → release build → SSG export → rsync to katelyn).
Stack maintenance policy
We always merge slices into
redesign/00-foundationwith rebase-merge (keeps the branch linear).Do NOT rebase the whole stack after each merge. Only the branch we are about to work on next gets updated — rebase it onto the refreshed
redesign/00-foundation(and retarget its PR base if needed) just before starting on it. The remaining stacked branches stay untouched until their turn comes, saving per-merge churn.0313022c8aa1c48cbc1dIntegration log: typography (PR #6) merged into 00 — fast-forward
a1c48cb→af8531d, branch redesign/01-typography deleted.Operational note for future slice merges (hard-won): Forgejo auto-closes the PR above when its base branch is deleted. Order: retarget the dependent PR's base to redesign/00-foundation (API PATCH pulls/{n}) BEFORE deleting the merged branch. PR #7 needed reopen+retarget after the fact.
- 404: $ GET line → kicker (~/{url}, leading slash trimmed in handler, overflow-wrap for long query strings); 404 heading to text-display-1; suggestions copy: check out introduction page, blog or get in touch - contact: rows keep text-blue-950 but hover now actually flips icon+label to blue-500 (fill-current, color on the anchor)Upsert a marker comment (<!-- preview-link -->) via GITHUB_TOKEN after deploy — POST first, PATCH on re-deploys (one comment per PR, no spam). Teardown PATCHes it to 'removed' so closed PRs keep no dead link. Both steps are best-effort (:⚠️: on API failure, never fail the job).🪦 Live preview
removed (PR closed)
WIP: redesign 00 — foundation (docs: decided feature set + DESIGN.md)to redesign 00 — foundation: the redesign stack (rails, covers, typographic system)