TenantAtlas/apps/website/src/content/pages/product.ts

import type {
    CalloutContent,
    FeatureItemContent,
    HeroContent,
    MetricItem,
    PageSeo,
} from '@/types/site';

export const productSeo: PageSeo = {
    title: 'TenantAtlas | Product',
    description:
        'TenantAtlas explains backup, restore, version history, drift, findings, evidence, and reviews as one operating model rather than a loose feature list.',
    path: '/product',
};

export const productHero: HeroContent = {
    eyebrow: 'Product model',
    title: 'Explain the product as one operating model before asking a buyer to trust the route map around it.',
    description:
        'TenantAtlas treats Microsoft tenant governance as one connected system: observe the current state, preserve immutable history, detect meaningful change, and support reviews or restores with the context operators actually need.',
    primaryCta: {
        href: '/trust',
        label: 'Review the trust posture',
    },
    secondaryCta: {
        href: '/contact',
        label: 'Start the working session',
        variant: 'secondary',
    },
    highlights: [
        'Backup, restore, versioning, auditability, drift, and evidence belong in one explanation layer.',
        'Trust and changelog should deepen the product read, not replace it.',
        'Audience-fit detail remains secondary until the core model is understood.',
    ],
};

export const productMetrics: MetricItem[] = [
    {
        value: '6',
        label: 'Capability areas',
        description: 'Backup, restore, versioning, audit, drift visibility, and governance workflows are made legible as one system.',
    },
    {
        value: '100%',
        label: 'Queryable versions',
        description: 'Version semantics stay tied to who changed what, when, and in which tenant context.',
    },
];

export const productModelBlocks: FeatureItemContent[] = [
    {
        eyebrow: 'Inventory and drift',
        title: 'Current-state inventory and drift visibility establish what the tenant actually looks like now.',
        description:
            'The product starts with last-observed tenant state so teams can compare real configuration truth instead of relying on partial memory or exported spreadsheets.',
    },
    {
        eyebrow: 'Backup and versioning',
        title: 'Snapshots and versions preserve immutable history without replacing present-tense truth.',
        description:
            'Backups and versions are explicit artifacts tied to tenant context, operators, and timing so the history remains reproducible and queryable.',
    },
    {
        eyebrow: 'Restore safety',
        title: 'Restore is handled as a governed operation, not as a blind push.',
        description:
            'Preview, validation, selective scope, and confirmation reduce the risk of turning a recovery step into a new incident.',
    },
    {
        eyebrow: 'Audit and review',
        title: 'Differences become reviewable signals instead of noisy raw deltas.',
        description:
            'Human-readable summaries and structured differences help operators and reviewers decide what changed, who needs to know, and what deserves follow-up.',
    },
    {
        eyebrow: 'Findings and evidence',
        title: 'Findings, exceptions, and evidence stay anchored to operational truth.',
        description:
            'Governance discussions stay attached to the real object, version, and review context instead of drifting into separate manual trackers.',
    },
    {
        eyebrow: 'Baselines and governance',
        title: 'Baselines, reviews, and operator safety belong to the same workflow.',
        description:
            'The product is built so teams can explain actions afterward, not just execute them quickly in the moment.',
    },
];

export const productNarrative: CalloutContent[] = [
    {
        eyebrow: 'What it is',
        title: 'The point is not “backup plus reporting plus restore.”',
        description:
            'The point is to reduce operator uncertainty by keeping those capabilities connected through the same source material and the same decision flow.',
        tone: 'accent',
    },
    {
        eyebrow: 'What it is for',
        title: 'A calmer path from observation to action.',
        description:
            'Teams can move from understanding the current tenant state to comparing history, planning remediation, or reviewing restore options without leaving the product model behind.',
    },
    {
        eyebrow: 'What it is not',
        title: 'No generic dashboard theater.',
        description:
            'The product story avoids pretending that another alerting page or compliance badge alone solves governance discipline.',
        tone: 'subtle',
    },
];