Skip to content

docs: document the multi-site architecture and how to work on all sites#41

Merged
ronaldtse merged 2 commits into
mainfrom
readme-multi-site-architecture
Jun 18, 2026
Merged

docs: document the multi-site architecture and how to work on all sites#41
ronaldtse merged 2 commits into
mainfrom
readme-multi-site-architecture

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

Expands the README from a 2-line "Sub-sites" bullet list into a full architecture guide for the whole fontist.org family of sites.

What's in it

  • Architecture overview — explains the multi-repo setup: this repo is the GitHub Pages org site that owns the fontist.org custom domain (served at /); each subsite is a separate repo whose own GitHub Pages is served at fontist.org/<repo>/.
  • Mermaid diagram — visual map of the 4 repos → their deployed subpaths, with the cross-site nav links.
  • Site table — repo, URL, default branch (main, or v5 for formulas), and build entrypoint for each site.
  • Local development — how to run this site and each subsite (clone siblings, cd docs/, npm run dev).
  • Deployment — automatic per-repo via build.yml / docs.yml; nothing manual. Includes a per-repo workflow table noting formulas' batched build (4,300+ pages).
  • Shared conventions — the consistency layer across the ecosystem: per-page OG via transformHead, shared og:image PNG, sitemap.xml + robots.txt per site, directory-style URLs (post-build dirify), and cross-site links using target="_self" to avoid the SPA-router client-side 404.
  • "Adding blog posts" updated to mention the auto-generated BlogPosting JSON-LD.
  • See also — links to fontist, fontisan, formulas, and setup-fontist.

Also fixed

  • The deploy badge at the top pointed at deploy-pages.yml, which doesn't exist. Corrected to build.yml (the actual workflow).

Verification

README.md only — no code/build changes. Mermaid diagram uses standard flowchart syntax that renders on GitHub.

Expand the README from a minimal 'Sub-sites' bullet list into a full architecture overview: a Mermaid diagram of the four-repo + custom-domain setup, a site table (repo / URL / default branch / build entrypoint), per-site local-dev and deploy instructions, and the shared conventions (per-page OG, shared og:image, sitemap+robots, directory-style URLs, cross-site link target) that keep the ecosystem consistent.

Also fixes the deploy badge to point at the actual workflow (build.yml, not the non-existent deploy-pages.yml).
@github-actions

Copy link
Copy Markdown

🔗 Link Check Failed

Results

Summary

Status Count
🔍 Total 145
✅ Successful 26
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 118
❓ Unknown 0
🚫 Errors 1
⛔ Unsupported 0

Errors per input

Errors in .vitepress/dist/README/index.html

Full Github Actions output

…im checks it)

lychee runs with include_verbatim=true, so the http://localhost:5173 URL in the code comment was extracted and checked — and failed (connection refused in CI). The comment now just describes the command; npm run dev prints the URL anyway.
@ronaldtse ronaldtse merged commit cb9c4c5 into main Jun 18, 2026
5 checks passed
@ronaldtse ronaldtse deleted the readme-multi-site-architecture branch June 18, 2026 08:13
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