# Page Inventory - catalog_id: astrodeck-226-baseline - primitive_class: Page - entry_count: 13 ### page.index - entry_id: page.index - identifier: index - primitive_class: Page - file_ref: apps/website/src/pages/index.astro - functional_role: Homepage entrypoint that sequences the launch hero, product framing, trust, progress, and contact handoff. - default_semantics: Primary marketing route for first-visit orientation and route handoff into product, trust, changelog, and contact. - default_visual_character: bold-visual - tenantatlas_relevance: high - suitability_class: A - markers: [tenantatlas-likely] - notes: The current homepage already reflects the canonical TenantAtlas launch journey and is the main reference page for downstream mapping. ### page.product - entry_id: page.product - identifier: product - primitive_class: Page - file_ref: apps/website/src/pages/product.astro - functional_role: Explains the connected product model before the visitor is asked to trust or contact the team. - default_semantics: Product explainer route that combines hero framing, feature clusters, narrative callouts, and downstream CTAs. - default_visual_character: enterprise-neutral - tenantatlas_relevance: high - suitability_class: A - markers: [tenantatlas-likely, product-explainer-candidate] - notes: Strong direct-fit route for rebuild planning because it already anchors the product explanation in current release truth. ### page.trust - entry_id: page.trust - identifier: trust - primitive_class: Page - file_ref: apps/website/src/pages/trust.astro - functional_role: Dedicated trust posture route for operator safeguards, isolation boundaries, and credibility framing. - default_semantics: Trust-first supporting page with one explicit proof surface and a clear contact handoff. - default_visual_character: enterprise-neutral - tenantatlas_relevance: high - suitability_class: A - markers: [tenantatlas-likely, trust-candidate] - notes: This is the canonical trust route and should remain explicit in any AstroDeck rebuild plan. ### page.changelog - entry_id: page.changelog - identifier: changelog - primitive_class: Page - file_ref: apps/website/src/pages/changelog.astro - functional_role: Publishes dated product progress so visitors can verify motion without relying on vague marketing claims. - default_semantics: Content-led route with a hero, chronologically ordered update cards, and a closing CTA back into evaluation. - default_visual_character: content-heavy - tenantatlas_relevance: high - suitability_class: A - markers: [tenantatlas-likely, changelog-candidate] - notes: The route is already aligned with the visible-progress requirement in the active website strategy. ### page.contact - entry_id: page.contact - identifier: contact - primitive_class: Page - file_ref: apps/website/src/pages/contact.astro - functional_role: Qualifies outreach and shows what a serious first conversation should contain before anyone shares sensitive detail. - default_semantics: Contact and demo-prep route with guidance cards, a static message preview, legal reassurance, and a CTA handoff. - default_visual_character: utility-dense - tenantatlas_relevance: high - suitability_class: A - markers: [tenantatlas-likely, contact-candidate] - notes: Strong fit for rebuild planning because it already combines contact intent, legal reassurance, and route continuity. ### page.solutions - entry_id: page.solutions - identifier: solutions - primitive_class: Page - file_ref: apps/website/src/pages/solutions.astro - functional_role: Shows audience fit and operating-model resonance for deeper evaluators without owning the primary journey. - default_semantics: Supporting audience-fit route with hero framing, audience cards, supporting signals, and a closing CTA. - default_visual_character: enterprise-neutral - tenantatlas_relevance: medium - suitability_class: B - markers: [tenantatlas-likely] - notes: Reusable with limited copy and information-architecture changes, but it should stay subordinate to the primary route set. ### page.integrations - entry_id: page.integrations - identifier: integrations - primitive_class: Page - file_ref: apps/website/src/pages/integrations.astro - functional_role: Documents ecosystem fit and integration direction without pretending broad platform coverage is already launch truth. - default_semantics: Supporting ecosystem route with badges, rule cards, and a handoff back into product or contact. - default_visual_character: enterprise-neutral - tenantatlas_relevance: medium - suitability_class: B - markers: [tenantatlas-likely] - notes: Structurally reusable, but its value depends on keeping ecosystem claims concrete and bounded. ### page.privacy - entry_id: page.privacy - identifier: privacy - primitive_class: Page - file_ref: apps/website/src/pages/privacy.astro - functional_role: Explains the narrow public-site privacy posture and the bounds of inquiry handling. - default_semantics: Legal text route with an opening hero, reading-width rich text, and a simple next-step CTA. - default_visual_character: content-heavy - tenantatlas_relevance: medium - suitability_class: B - markers: [tenantatlas-likely] - notes: Good structural fit for the rebuild, but the content remains jurisdiction- and policy-dependent. ### page.terms - entry_id: page.terms - identifier: terms - primitive_class: Page - file_ref: apps/website/src/pages/terms.astro - functional_role: States the website terms and clarifies that public marketing pages do not replace commercial agreements. - default_semantics: Legal text route built from hero, reading-width prose cards, and a closing CTA. - default_visual_character: content-heavy - tenantatlas_relevance: medium - suitability_class: B - markers: [tenantatlas-likely] - notes: Directly reusable for the legal baseline, with expected copy and jurisdiction updates only. ### page.imprint - entry_id: page.imprint - identifier: imprint - primitive_class: Page - file_ref: apps/website/src/pages/imprint.astro - functional_role: Publishes the public legal-notice baseline for publisher identity and jurisdiction-specific disclosure. - default_semantics: Legal notice route with a hero, reading-width legal content, and a return CTA into trust or contact. - default_visual_character: content-heavy - tenantatlas_relevance: low - suitability_class: B - markers: [tenantatlas-likely] - notes: Useful for the retained legal baseline, but the content remains highly dependent on jurisdiction and publication details. ### page.legal - entry_id: page.legal - identifier: legal - primitive_class: Page - file_ref: apps/website/src/pages/legal.astro - functional_role: Aggregates trust, privacy, terms, and imprint into one retained legal hub route. - default_semantics: Secondary legal index page that duplicates links to leaf legal routes and adds a short notice section. - default_visual_character: content-heavy - tenantatlas_relevance: low - suitability_class: C - markers: [needs-heavy-adaptation, semantic-risk] - notes: The hub risks adding route ambiguity because the leaf legal pages already exist; keep only if the rebuild still needs a legal index. ### page.security-trust - entry_id: page.security-trust - identifier: security-trust - primitive_class: Page - file_ref: apps/website/src/pages/security-trust.astro - functional_role: Preserves a legacy alias by redirecting `/security-trust` to `/trust`. - default_semantics: Redirect-only route with no user-facing content surface. - default_visual_character: minimal - tenantatlas_relevance: low - suitability_class: D - markers: [] - notes: Inventory it for route completeness, but exclude it from visual surface selection because it contributes no reusable layout or content pattern. ### page.sitemap-xml - entry_id: page.sitemap-xml - identifier: sitemap.xml - primitive_class: Page - file_ref: apps/website/src/pages/sitemap.xml.ts - functional_role: Exposes a machine-readable sitemap for search crawlers. - default_semantics: API-style XML endpoint rather than a human-facing content route. - default_visual_character: utility-dense - tenantatlas_relevance: none - suitability_class: D - markers: [] - notes: Keep visible in the inventory for route governance, but it is not a rebuild candidate for visual or narrative surfaces.