TenantAtlas/specs/404-public-content-messaging/quickstart.md
ahmido c261b1c632 feat(website): tighten homepage messaging and trust flow (#398)
## Summary
- tighten homepage messaging, hero support copy, trust teaser flow, and CTA routing for the website public-content rollout
- align shared website copy, smoke expectations, and spec 404 artifacts with the latest messaging pass
- replace the previously closed PR for `404-public-content-messaging`

## Commits
- `44d27395` feat(website): tighten homepage messaging and trust flow
- `1ddbd28b` feat(website): refine public content messaging rollout

## Validation
- `git diff --check`

## Notes
- local Playwright MCP output remains untracked and was not included

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #398
2026-05-25 20:35:33 +00:00

6.5 KiB

Quickstart: Spec 404 Public Website Positioning & Content Architecture

Scope

Work only in:

/Users/ahmeddarrazi/Documents/projects/wt-website/apps/website
/Users/ahmeddarrazi/Documents/projects/wt-website/specs/404-public-content-messaging

Do not touch:

/Users/ahmeddarrazi/Documents/projects/wt-website/apps/platform

Verify Current Repo Truth First

Run the required repo checks before editing:

cd /Users/ahmeddarrazi/Documents/projects/wt-website && pwd
cd /Users/ahmeddarrazi/Documents/projects/wt-website && git status --short --branch
cd /Users/ahmeddarrazi/Documents/projects/wt-website && find apps/website -maxdepth 3 -type f | sort | sed -n '1,160p'
cd /Users/ahmeddarrazi/Documents/projects/wt-website && cat package.json
cd /Users/ahmeddarrazi/Documents/projects/wt-website && cat pnpm-workspace.yaml
cd /Users/ahmeddarrazi/Documents/projects/wt-website && cat apps/website/package.json

Install Dependencies If Needed

cd /Users/ahmeddarrazi/Documents/projects/wt-website && corepack pnpm install

Run The Website Locally

cd /Users/ahmeddarrazi/Documents/projects/wt-website && WEBSITE_PORT=4321 corepack pnpm dev:website

Open:

http://127.0.0.1:4321

Read-Only Content Audit

Review public content sources before editing:

cd /Users/ahmeddarrazi/Documents/projects/wt-website && rg -n "Policy Governance|Microsoft 365|provider-extensible|Intune|Google|AWS|DSGVO|GDPR|AVV|TOM|ISO|BSI|automatic restore|autonomous remediation|href=\"#\"|lorem ipsum|ScrewFast|TenantAtlas|TenantPilot|TenantCTRL" apps/website/src apps/website/public

Audit these content surfaces first:

  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/data_files/site-copy.ts
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/data_files/constants.ts
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/pages/HomePage.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/pages/PlatformPage.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/pages/PricingPage.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/pages/TrustPage.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/pages/ContactPage.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/sections/navbar&footer/Navbar.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/sections/navbar&footer/FooterSection.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/components/Meta.astro
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/src/content/docs
  • /Users/ahmeddarrazi/Documents/projects/wt-website/apps/website/tests/smoke

Content Review Checklist

For the homepage:

  • hero identifies Tenantial as policy governance and Microsoft 365 first
  • provider-extensible language stays future-safe and does not claim live non-Microsoft support
  • operating-model section covers observe, evidence, detect, review, decide, and audit
  • capability framing emphasizes policy evidence, drift/change detection, governance reviews, controlled recovery, provider readiness, and decision traceability
  • audience and boundary sections add meaning instead of repeating the hero
  • CTAs match real buyer-stage destinations

For /platform:

  • explains the governance model more deeply than the homepage
  • keeps Microsoft 365 first focus without collapsing back to Intune-only framing
  • frames previews as static/demo/illustrative where needed
  • does not cite or depend on apps/platform
  • does not imply live provider connection, Graph execution, or live tenant/customer data

For pricing/evaluation:

  • remains contact-led and scoped
  • avoids checkout, subscription activation, self-serve billing, account creation, or unsupported entitlement claims
  • CTAs resolve to /contact or another intentional target

For trust/FAQ/footer/legal-adjacent content:

  • no unsupported German hosting, DSGVO/GDPR, AVV/TOM, ISO/BSI/NIS2, endorsement, or customer-proof claims
  • no fake logos, testimonials, or compliance badges
  • no autonomous remediation or automatic restore claims
  • no public website live-data implication

Build Validation

cd /Users/ahmeddarrazi/Documents/projects/wt-website && corepack pnpm build:website

Smoke Validation

cd /Users/ahmeddarrazi/Documents/projects/wt-website && WEBSITE_PORT=4321 corepack pnpm --filter @tenantatlas/website test:smoke

Static Claim And Scope Validation

cd /Users/ahmeddarrazi/Documents/projects/wt-website && grep -RIn -e 'href="#"' -e 'Intune Management Tool' -e 'Intune backup tool' -e 'DSGVO compliant' -e 'GDPR compliant' -e 'ISO certified' -e 'Google supported' -e 'AWS supported' -e 'automatic restore' -e 'autonomous remediation' -e 'neutral SaaS visual' -e 'lorem ipsum' apps/website/src apps/website/public 2>/dev/null || true
cd /Users/ahmeddarrazi/Documents/projects/wt-website && git diff --check
cd /Users/ahmeddarrazi/Documents/projects/wt-website && git status --short -- apps/platform

The apps/platform command must print no output.

Manual Browser Review

Review these routes in desktop and mobile widths:

  • /
  • /platform
  • /pricing
  • /contact
  • /trust
  • /legal
  • /privacy
  • /terms
  • /imprint
  • /welcome-to-docs/
  • /guides/intro/
  • /guides/getting-started/
  • /guides/first-project-checklist/
  • /platform/evidence-review/

Check:

  • the homepage hero no longer frames the product as Intune-only
  • the public category is policy governance and Microsoft 365 first
  • provider-extensible wording does not imply live Google/AWS support
  • the operating model is visible and coherent
  • Intune appears only as one domain when named
  • trust copy does not overclaim compliance, hosting, certification, or automation
  • CTAs are concrete and intentional
  • no href="#" placeholders are visible or emitted
  • no forbidden residue terms appear in visible copy or metadata
  • keyboard users can reach navigation, CTAs, footer links, FAQ controls, and visible controls
  • visible focus states are present
  • no body-level horizontal overflow occurs

Handoff

Implementation summary must document:

  • changed public routes and shared copy surfaces
  • provider-posture and claim-safety decisions
  • CTA and navigation changes
  • metadata changes
  • validation commands and outcomes
  • deferred follow-up work for later public website specs
  • apps/platform untouched confirmation