> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/public-website/docs/archive-docs_public-website/post-launch-backlog.md). # Post-Launch Backlog This backlog captures public website work that was intentionally deferred from the first static launch handoff. Listing an item is not approval to ship it. Status labels: * `deferred` * `needs phase` * `needs owner review` * `needs authorized environment` ## Deferred Website Enhancements | ID | Item | Status | Reason Deferred | Evidence Needed Before Promotion | | ------- | ----------------------------------------------- | ---------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | PLB-001 | Self-hosted brand font pipeline | deferred | First launch uses system fonts and no remote font requests. | Font source, license, byte budget, fallback behavior, privacy review, and build output checks. | | PLB-002 | Social image generation pipeline | deferred | Current launch uses static `og-default.png` fallback. | Deterministic generation command, approved templates, image budget, metadata review, and regression checks. | | PLB-003 | Site search | needs phase | Static first launch does not include search UI, search index, or hosted search service. | Search provider or local index decision, privacy review, no-prompt/no-path policy, accessibility checks, and tests. | | PLB-004 | Blog/news tag archive pages | needs phase | Tag archive routes are not required for launch. | Route contract, metadata, RSS/sitemap behavior, draft exclusion, and checker coverage. | | PLB-005 | CMS or editorial workflow integration | needs phase | First launch uses repository content collections only. | Provider decision, auth model, preview rules, draft isolation, audit trail, retention, and privacy review. | | PLB-006 | Optional analytics adapter | needs owner review | Analytics is disabled by default and not wired. | Umami adapter plan, explicit approval, payload scrub tests, no replay/heatmap/console capture, and docs updates. | | PLB-007 | Cloudflare adapter or server rendering | needs phase | Static Astro output does not need `@astrojs/cloudflare`. | Server-rendered requirement, binding model, caching plan, privacy/security review, and deploy tests. | | PLB-008 | Authorized production deploy and homepage smoke | needs authorized environment | Local launch-review shell lacked Cloudflare credentials and dashboard/domain access. | Successful Pages deploy, sanitized HTTPS homepage smoke, and docs update with exact pass/fail labels. | | PLB-009 | Production domain and dashboard evidence | needs authorized environment | Dashboard/domain access was unavailable locally. | Project/domain status from authorized operator without account ids, tokens, or dashboard dumps in tracked files. | | PLB-010 | Formal legal/privacy approval | needs owner review | Launch review could only record copy and no-claim boundaries. | Owner approval record and approved launch wording. | | PLB-011 | Formal accessibility or VPAT certification | needs owner review | Local automated/manual QA is not certification. | Scope, evaluator, methodology, remediation plan, and certification artifact policy. | | PLB-012 | Physical mobile-device QA matrix | needs owner review | Session QA is local viewport/browser evidence only. | Device/browser matrix, tested hardware, results, and residual risk record. | ## Operational Follow-Ups | ID | Item | Status | Owner Input Needed | | ------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | ----------------------------------------------------- | | OPS-001 | Decide whether launch can proceed after local gates pass but deploy credentials are unavailable locally. | needs owner review | Release owner decision. | | OPS-002 | Run `.github/workflows/public-website-deploy.yml` manually or on `main` from an authorized repository environment. | needs authorized environment | Cloudflare secrets and Pages project access. | | OPS-003 | Run manual Wrangler fallback only if workflow deploy is unavailable or inappropriate. | needs authorized environment | Cloudflare credentials and release operator approval. | | OPS-004 | Capture post-deploy smoke evidence with sanitized status labels only. | needs authorized environment | Live HTTPS target after deploy. | | OPS-005 | Open a later scoped effort for hosted identity, hosted storage, analytics, CMS, search, forms, or server rendering if product scope changes. | needs phase | Product owner decision. | ## Backlog Rules * Do not merge backlog items into routine copy or style work. * Promote one item at a time through a scoped implementation and docs update. * Update source, validation, and docs together. * Keep static privacy checks aligned with any runtime behavior change. * Keep no-claim language until evidence exists. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/public-website/docs/archive-docs_public-website/post-launch-backlog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.