feat(Docs): Build SveltePress site with localized content and content chrome - #50
Conversation
|
Important Review skippedToo many files! This PR contains 136 files, which is 36 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (136)
You can disable this status message by setting the Warning
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Builds the AuthKit SveltePress documentation site with English first localized content (EN + PL), automated locale route generation, and runtime content chrome (ADR + section styling, landing), while fixing content drift against the codebase and modernizing the frontend layer with TypeScript, Tailwind CSS v4, and shared i18n labels.
Documentation Site
npm run sync): content trees, ADR collection, schemas, registry, paraglide, version manifestsContent
Docs/content/en/adr/so EN/PL content trees stay symmetricsrc/:ConnectionStrings:Marten, per pluginPlugins:authkit.devtokensoptions, real ServiceDiscovery keys,DEV_CERT_*env vars, verify endpoint shape (keyrequest,boolresponse, anonymous),Userrole on revoke-rotate, grpcurl--insecure, Swagger dev-only defaultContent Chrome
lib/chrome/(dom, content-hero, section-accents, icons, landing-data, labels) andlib/adr/(registry filter, section match)i18n/messages(chrome + sections slugs) new language adds JSON entries, no code changesFrontend Styling
Sync Pipeline Fixes
content/en/paths and validates the registry against themValidation
npm run syncnpm run buildgit diff --checkResult
Docs ship as a localized, statically prerendered site whose routes, registry, and translations regenerate from content sources on every build. Content matches the codebase, UI copy and section slugs come from i18n messages, and the presentation layer is shared typed modules styled with Tailwind instead of scattered hand-written CSS.