ahmido
44e472ec18
## Summary - refresh website copy and structured content datasets - update docs content in EN and default locales - adjust website UI auth-related components and smoke tests - add Spec Kit artifacts for feature 404 public content messaging ## Validation - committed and pushed from branch `404-public-content-messaging` ## Target - base branch: `website-dev` Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #396
158 lines
6.5 KiB
Markdown
158 lines
6.5 KiB
Markdown
# Public Content Contract: Spec 404 Content Architecture & Messaging
|
|
|
|
This feature has no REST, GraphQL, Laravel, Filament, Livewire, Microsoft Graph, database, queue, job, policy, RBAC, or product runtime API contract.
|
|
|
|
The contract is the public static website content behavior that reviewers and smoke tests must verify.
|
|
|
|
## Core Public Routes
|
|
|
|
The following German default routes must render intentionally and expose Tenantial-specific content, metadata, and CTAs:
|
|
|
|
- `/`
|
|
- `/platform`
|
|
- `/pricing`
|
|
- `/contact`
|
|
- `/trust`
|
|
- `/legal`
|
|
- `/privacy`
|
|
- `/terms`
|
|
- `/imprint`
|
|
- `/welcome-to-docs/`
|
|
- `/guides/intro/`
|
|
- `/guides/getting-started/`
|
|
- `/guides/first-project-checklist/`
|
|
- `/platform/evidence-review/`
|
|
|
|
The following English route mirrors must remain consistent where they are intentionally exposed:
|
|
|
|
- `/en/`
|
|
- `/en/platform`
|
|
- `/en/pricing`
|
|
- `/en/contact`
|
|
- `/en/trust`
|
|
- `/en/legal`
|
|
- `/en/privacy`
|
|
- `/en/terms`
|
|
- `/en/imprint`
|
|
- `/en/welcome-to-docs/`
|
|
- `/en/guides/intro/`
|
|
- `/en/guides/getting-started/`
|
|
- `/en/guides/first-project-checklist/`
|
|
- `/en/platform/evidence-review/`
|
|
|
|
## Homepage Messaging Contract
|
|
|
|
The homepage must satisfy:
|
|
|
|
- hero copy identifies Tenantial as evidence-first governance for Microsoft tenant configuration
|
|
- first two homepage sections allow a reviewer to name at least three of backup, restore, drift, findings, evidence, audit trail, exceptions, and reviews
|
|
- section headings read as a coherent sequence from product category to buyer problem to operating model to capability proof to evaluation
|
|
- each major section adds distinct meaning rather than repeating the same product claim
|
|
- CTAs match the visitor's likely decision stage
|
|
- homepage copy stays suitable for later Spec 405 spacing and visual polish
|
|
|
|
## `/platform` Product-Model Contract
|
|
|
|
The public `/platform` route must satisfy:
|
|
|
|
- explains backup, restore, drift, findings, evidence, auditability, exceptions, and reviews as one operating model
|
|
- explains Tenantial as governance-of-record, not helpdesk, device-action, or blind automation
|
|
- frames product-like previews as static/demo/illustrative where needed
|
|
- does not import, inspect, or cite `apps/platform` as an implementation source
|
|
- does not imply that the public website connects to a Microsoft tenant, runs Microsoft Graph calls, or shows live tenant data
|
|
|
|
## Pricing And Evaluation Contract
|
|
|
|
Pricing and evaluation copy on `/pricing` and homepage evaluation surfaces must satisfy:
|
|
|
|
- commercial language is contact-led and framed around evaluation, rollout scope, or scoped conversation
|
|
- no checkout, instant subscription activation, self-serve billing, account creation, or fixed unsupported entitlement claims
|
|
- managed rollout language reads as a scoped commercial conversation rather than a fake fixed plan
|
|
- pricing/evaluation CTAs route to `/contact` or another intentional route/anchor
|
|
- visual language requirements are limited to content clarity; broad layout polish remains Spec 405
|
|
|
|
## Trust, FAQ, Footer, And Legal-Adjacent Contract
|
|
|
|
Trust-sensitive public copy must avoid unsupported:
|
|
|
|
- SOC 2, ISO, or other certification claims
|
|
- Microsoft endorsement or partnership claims
|
|
- compliance guarantees
|
|
- recovery guarantees
|
|
- uptime guarantees
|
|
- fake customer logos
|
|
- fake testimonials
|
|
- fake "trusted by" claims
|
|
- real customer evidence implications
|
|
- public website live-tenant-data implications
|
|
|
|
FAQ and footer copy must close the page intentionally without adding fake workflows, fake proof, or unsupported support commitments.
|
|
|
|
## CTA Contract
|
|
|
|
Every public CTA, navigation item, footer link, docs link, and visible form-like control must satisfy:
|
|
|
|
- resolves to an intentional route, anchor, static asset, mailto link, or legitimate external URL
|
|
- no public `href="#"` placeholders
|
|
- primary contact/demo paths route to `/contact` or an intentional contact section
|
|
- secondary educational paths route to product, pricing, trust, docs, or legal explanations
|
|
- localized public links remain in the current locale where a localized route exists
|
|
- labels avoid login, signup, account creation, checkout, subscription, instant provisioning, automated scheduling, or guaranteed backend submission implications unless those workflows exist
|
|
- CTA language is normalized by intent family before individual labels are rewritten
|
|
|
|
## Metadata Contract
|
|
|
|
Each rendered canonical route must provide:
|
|
|
|
- Tenantial-specific page title
|
|
- Tenantial-specific page description
|
|
- route-appropriate canonical, Open Graph, and Twitter summary values
|
|
- no ScrewFast, construction, hardware, manufacturing, template, TenantAtlas, TenantPilot, or TenantCTRL residue in public metadata
|
|
- no unsupported proof claims in title, description, Open Graph, Twitter, schema, or docs metadata
|
|
- sitemap and robots behavior preserved from Spec 403 unless a website-scope correction is documented
|
|
|
|
## Docs Exposure Contract
|
|
|
|
Exposed docs routes must:
|
|
|
|
- contain intentional Tenantial-specific content or be hidden from public navigation
|
|
- avoid placeholder theme content
|
|
- avoid unsupported product behavior claims
|
|
- avoid support, legal, integration, compliance, or recovery commitments not supplied by the product/business
|
|
- keep public docs separate from `apps/platform` implementation documentation unless a future spec explicitly changes scope
|
|
|
|
## Product Preview Contract
|
|
|
|
Static product previews must:
|
|
|
|
- be framed as illustrative, static, or demo content where needed
|
|
- avoid implying live tenant data
|
|
- avoid internal Laravel/Filament implementation details
|
|
- avoid turning visual labels into product runtime taxonomy
|
|
- communicate meaning through text or labels, not color alone
|
|
|
|
## Browser And Accessibility Contract
|
|
|
|
Validated public routes must:
|
|
|
|
- avoid body-level horizontal overflow on representative desktop and mobile viewports
|
|
- keep primary navigation, CTAs, footer links, FAQ controls, and visible controls keyboard reachable
|
|
- show visible focus states for interactive elements
|
|
- remain understandable with reduced motion
|
|
- keep primary content and links usable if JavaScript fails where reasonably possible for a static marketing site
|
|
|
|
## Scope Contract
|
|
|
|
Implementation and validation must not touch:
|
|
|
|
- `/Users/ahmeddarrazi/Documents/projects/wt-website/apps/platform`
|
|
- Laravel providers, migrations, policies, jobs, queues, database, Filament resources, Livewire components, Blade views, tenant/workspace/RBAC code, Microsoft Graph code, or AuditLog behavior
|
|
|
|
Scope proof command:
|
|
|
|
```bash
|
|
cd /Users/ahmeddarrazi/Documents/projects/wt-website && git status --short -- apps/platform
|
|
```
|
|
|
|
The command must print no output.
|