Themes
The order below is a review aid, not a delivery promise. Shipped links resolve to current news entries or the news index.
Current focus
The immediate work is trust and conversion page depth for visitors who need product fit, setup, security, FAQ, policy, and contact clarity.
Website
Complete use cases, security, publishing, company, contact, press, roadmap, FAQ, and legal placeholder routes before the final copy pass.
Guardrail Legal and policy pages remain visibly pre-review until owner-approved text exists.
Review
Audit internal links, CTAs, route labels, metadata, and no-overclaim language across the launch website.
Guardrail The copy pass may remove or soften language if evidence does not support it.
Privacy
Keep website behavior static while routing demo, docs, and email contact actions to explicit external or mailto destinations.
Guardrail No analytics, hosted forms, cookies, auth, runtime personalization, or server adapter behavior is added here.
Near-term themes
The next website work focuses on responsive hardening, performance, automated checks, deployment path evidence, and launch handoff documentation.
Quality
Review desktop, tablet, narrow mobile, keyboard focus, heading scale, wrapping, and footer reachability after all pages exist.
Guardrail This is quality evidence for the static website, not broad product certification.
Performance
Keep static output lean, validate asset sizes, and preserve the existing package-local media registry posture.
Guardrail Media showcase readiness remains claim-scoped to approved website assets.
Checks
Strengthen typecheck, build, static HTML inspection, and no-claim scans before deployment handoff.
Guardrail Passing local gates does not imply live production-hosted validation.
Deploy
Prepare a static deployment route for the public website while keeping server adapters and runtime personalization out of scope.
Guardrail Live deployment claims require separate sanitized evidence after deployment is available.
Later themes
Future product and hosted-service directions need scoped specs, threat models, tests, docs, and owner review before public claims change.
Hosted
Optional hosted storage, analytics, push, public replay, tunnels, or remote access remain future review areas.
Guardrail These are not active hosted-service claims and do not imply account identity or production auditability.
Teams
Role-specific team pages can later connect to stronger collaboration evidence after identity, authorization, consent, and abuse controls exist.
Guardrail War Room federation remains optional and separate from hosted account identity.
Policy
Privacy, terms, and acceptable-use placeholders can become final only after owner/legal review supplies approved copy.
Guardrail Pre-review placeholders are not a substitute for legal approval or acceptance workflows.
Recently shipped
These links point at current non-draft news content. If a matching news entry is not available, the roadmap should link to the news index instead of inventing history.
Astro static output, metadata helpers, sitemap posture, RSS, and publishing routes are in place.
Resolved from an existing news entry, not a roadmap promise.Publishing templates now support featured entries, category groups, related links, and draft-safe validation.
Resolved from the news collection and bounded to editorial readiness.The public website links to a separate demo destination without becoming an app host itself.
Resolved from an existing demo news entry with explicit external-boundary language.Website route depth expanded into use cases, security, publishing, company, contact, and press surfaces.
Resolved from an existing company-style website update.