TenantAtlas/specs/401-tenantial-platform-page/quickstart.md

Quickstart: Tenantial Platform Page

Prerequisites

• Work from /Users/ahmeddarrazi/Documents/projects/wt-website.
• Use branch feat/401-tenantial-platform-page.
• Keep scope limited to /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website and this feature spec directory.
• Do not modify /Users/ahmeddarrazi/Documents/projects/wt-website/apps/platform for this feature.

Implementation Outline

1. Verify the current website route structure:

   find apps/website/src/pages -maxdepth 1 -type f | sort
   

2. Add the canonical Platform route:

   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/pages/platform.astro
   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/content/pages/platform.ts

3. Update website route and navigation definitions:

   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/lib/site.ts
   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/types/site.ts

4. Update homepage Platform CTA destinations:

   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/content/pages/home.ts

5. Handle /product compatibility:

   • Redirect /product to /platform.
   • Retire or stop importing stale /product page content so the route cannot render conflicting public copy.

6. Add or update smoke coverage:

   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/tests/smoke/home-product.spec.ts
   • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/tests/smoke/smoke-helpers.ts

Validation Commands

Run from /Users/ahmeddarrazi/Documents/projects/wt-website:

corepack pnpm build:website
WEBSITE_PORT=4321 corepack pnpm --filter @tenantatlas/website test:smoke
git diff --check

Also review desktop and mobile screenshots for the mockup-aligned visual structure: split hero with dashboard preview, compact Operating Model flow, connected Governance Loop diagram, asymmetric Capabilities, Truth Layers visual, warmer Operator Workflows, Boundaries band, focused CTA, and quiet footer.

Before finalizing, also run the repository-wide constitution Quality Gates without treating Laravel behavior as the feature proof:

cd /Users/ahmeddarrazi/Documents/projects/wt-website/apps/platform && ./vendor/bin/sail artisan test --compact tests/Deprecation/IsPlatformSuperadminDeprecationTest.php
cd /Users/ahmeddarrazi/Documents/projects/wt-website/apps/platform && ./vendor/bin/sail bin pint --dirty

Manual Review Checklist

• /platform renders the Tenantial Platform page.
• First viewport explains evidence-first governance for Microsoft tenants and includes a large static dashboard/product preview.
• Operating Model renders as a compact connected flow: Snapshot, Drift, Finding, Review, Evidence, Audit trail.
• Capability section uses a larger Backup & Restore block plus Drift Detection, Findings, Evidence, Audit Trail, Exceptions, and Governance Reviews.
• Governance loop renders as a connected diagram and makes operator review, evidence preservation, and auditability explicit.
• Truth Layers render as a layer-stack or equivalent visual model.
• Operator Workflow cards are compact and visually warmer than the main control-room sections.
• Platform boundaries state that Tenantial is not a helpdesk action tool, live device action tool, SIEM, or Microsoft admin center replacement.
• Final CTA and footer do not create two equally heavy closing CTA zones.
• Homepage "Explore the platform" reaches /platform.
• Header and footer Platform links reach /platform.
• /product, if retained, redirects to /platform and does not expose stale or conflicting public copy.
• Page metadata uses Tenantial branding and canonical /platform.
• No visible or metadata occurrences of AstroDeck, TemplateDeck, Open Source, MIT, TenantAtlas, TenantPilot, or TenantCTRL.
• No unsupported claims: SOC 2, ISO, HIPAA, blanket GDPR, guaranteed recovery, guaranteed compliance, zero drift, real-time everywhere, named customers, Microsoft certification, or Microsoft partnership.
• Mobile, tablet, desktop, and wide desktop review show no body-level horizontal overflow.
• Links and CTAs are keyboard-accessible and have visible focus states.

Out-of-Scope Checks

Stop and return to planning if implementation appears to require:

• Laravel, Filament, Livewire, or Blade admin changes.
• Database migrations, persisted entities, queues, workers, or schedules.
• Microsoft Graph calls or platform API calls.
• Authentication, sessions, account creation, or demo-booking backend logic.
• Third-party tracking scripts or external embeds.
• Real customer screenshots, tenant identifiers, customer logos, certifications, or partnership claims.