ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
website-dev
TenantAtlas/specs/400-tenantial-homepage-visual-rebuild/data-model.md
ahmido be314c577f Spec 400: rebuild Tenantial homepage visuals (#387) 
## Summary
- rebuild the public Tenantial homepage around an evidence-first Microsoft tenant governance narrative
- replace the old hero visual with a new static dashboard preview and add dedicated Trust Bar and Feature Pillars sections
- update the shared public shell, navigation, footer, dark design tokens, assets, and homepage content to match the new brand direction
- align website smoke coverage and Spec 400 artifacts with the rebuilt homepage

## Testing
- not run in this pass
- updated website smoke specs under apps/website/tests/smoke

## Note
- `website-dev` was pushed to `origin` so the requested PR base exists remotely
- the remote `website-dev` branch is an ancestor of `origin/dev`, so this PR may also show upstream `dev` history relative to that base

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #387
2026-05-18 14:38:11 +00:00

6.7 KiB
Raw Permalink Blame History

Data Model: Tenantial Homepage Visual Rebuild

This feature introduces no persisted database model, no runtime API schema, and no platform data contract. The models below describe static public website content that supports implementation and test planning.

Entity: Homepage Message

Purpose: Defines the first-read Tenantial brand, product category, promise, and CTA hierarchy for /.

Fields:

  • brandName: Must be Tenantial.
  • eyebrow: Must communicate "GOVERNANCE THAT EARNS TRUST" or equivalent.
  • headline: Must be "Evidence-first governance for Microsoft tenants."
  • supportingCopy: Must mention backup, restore, drift detection, snapshot-backed audit context, evidence, and structured reviews.
  • primaryCta: CTA with label Book a demo and an intentional destination.
  • secondaryCta: CTA with label Explore the platform and an intentional destination.
  • trustBullets: Up to three short trust cues.

Relationships:

  • Owns one primary CTA and one secondary CTA.
  • Appears before Dashboard Preview and supporting homepage sections.

Validation Rules:

  • Exactly one primary page heading must be present.
  • Public visible copy must not include old/template brand names.
  • CTA hierarchy must remain primary Book a demo, secondary Explore the platform.

State Transitions: None.

Entity: Header Navigation Item

Purpose: Defines one visible public header label and its behavior.

Fields:

  • label: One of Platform, Solutions, Resources, Pricing, Company, Sign in, Book a demo.
  • destination: Existing route, known external URL, or no-link/de-emphasized text for unavailable sign-in.
  • priority: Primary CTA, secondary utility, or navigation.
  • behavior: Link, CTA, or inert/de-emphasized label.

Relationships:

  • Header owns multiple navigation items.
  • CTA items point visitors toward Contact or Product routes.

Validation Rules:

  • Must not point to dead template routes.
  • Book a demo must remain the primary visible action.
  • Sign in must not imply implemented auth unless a real sign-in destination exists.

State Transitions: None.

Entity: Static Dashboard Preview

Purpose: Communicates product-near governance posture using static demo values.

Fields:

  • overallPosture: Static demo value 92%.
  • findings: Static demo value 14.
  • driftDetected: Static demo value 7.
  • evidenceItems: Static demo value 1,248.
  • backupStatus: Static demo value 98%.
  • panels: Recent findings, drift timeline, backups and restores, reviews, evidence spotlight.
  • statusLabels: Text labels that explain status meaning without relying on color only.

Relationships:

  • Contains Dashboard Metrics and Dashboard Panels.
  • Appears with or immediately after the Hero.

Validation Rules:

  • Must not depend on backend/API/auth/tenant/platform data.
  • Must not claim to be live or realtime.
  • Must remain readable on desktop and usable on mobile without body-level horizontal overflow.
  • Status meaning must be available through text, not only color.

State Transitions: None.

Entity: Dashboard Metric

Purpose: A single static value in the Dashboard Preview.

Fields:

  • label: Human-readable metric name.
  • value: Static demo value.
  • tone: Healthy, warning, critical, evidence, or neutral.
  • description: Short text explaining the metric.

Relationships:

  • Belongs to Static Dashboard Preview.

Validation Rules:

  • Tone must not be the only status signal.
  • Value must be static and clearly demo-like.

State Transitions: None.

Entity: Trust Statement

Purpose: Provides credibility without fake proof.

Fields:

  • title: Short credibility statement.
  • description: One-sentence explanation.
  • claimType: Product focus, workflow discipline, audit review workflow design, or operator governance.

Relationships:

  • Appears inside Trust Bar.

Validation Rules:

  • Must not use real customer logos unless verified.
  • Must not claim SOC 2, ISO, 99.9% uptime, or named customer trust unless verified.
  • Must not overstate security/compliance posture.

State Transitions: None.

Entity: Feature Pillar

Purpose: Describes one required Tenantial homepage capability.

Fields:

  • title: Backup, Restore, Drift Detection, Evidence, Audit Trail, or Governance Reviews.
  • description: Concise capability explanation.
  • iconLabel: Meaningful accessible label or decorative status.
  • proofBoundary: Copy note ensuring unsupported claims are avoided.

Relationships:

  • Feature Pillars section contains exactly the required six capability pillars unless implementation explicitly keeps four to six cards while preserving all required capabilities.

Validation Rules:

  • Required capability titles must be visible.
  • Copy must be short and product-specific.
  • Unsupported security/compliance promises are forbidden.

State Transitions: None.

Entity: CTA Section

Purpose: Repeats the homepage's primary next step near the bottom of the page.

Fields:

  • headline: "Build tenant governance on evidence, not assumptions." or equivalent.
  • primaryCta: Book a demo.
  • secondaryCta: Explore the platform.

Relationships:

  • Mirrors Homepage Message CTA hierarchy.

Validation Rules:

  • CTA labels and destinations must match actual behavior.
  • CTA text must not clip on mobile.

State Transitions: None.

Entity: Footer Link Group

Purpose: Provides public footer navigation without template residue.

Fields:

  • groupTitle: Platform, Solutions, Resources, Pricing, Company, Contact, Legal, Privacy, or Security.
  • items: Intentional links or route aliases to existing public pages.
  • brandName: Tenantial.

Relationships:

  • Footer owns multiple Footer Link Groups.

Validation Rules:

  • Footer must not contain AstroDeck/template content or old public brand names.
  • Legal/privacy/security links must point to existing routes where available.
  • No fake social proof.

State Transitions: None.

Entity: SEO Metadata

Purpose: Defines public search/social metadata for the homepage.

Fields:

  • title: Tenantial - Evidence-first governance for Microsoft tenants.
  • description: Tenantial-specific summary of backup, restore, drift detection, audit trails, evidence, and structured reviews.
  • ogTitle: Evidence-first governance for Microsoft tenants.
  • ogDescription: Evidence-oriented governance positioning without unsupported certification, uptime, customer, or security guarantees.
  • canonicalPath: /.

Relationships:

  • Applies to Homepage Message and public route /.

Validation Rules:

  • Must not include AstroDeck/template titles.
  • Must not include old public brand names.
  • Must not include unverified customer, certification, or uptime claims.

State Transitions: None.