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

export const integrationsSeo: PageSeo = {
    title: 'TenantAtlas | Integrations',
    description:
        'TenantAtlas keeps ecosystem-fit detail available as a supporting page without pretending integrations belong in the primary navigation.',
    path: '/integrations',
};

export const integrationsHero: HeroContent = {
    eyebrow: 'Retained supporting page',
    title: 'Keep ecosystem fit detail visible without pretending it is the first thing every buyer needs.',
    description:
        'This page shows the real systems TenantAtlas is built around, the workflows it expects to support, and the deliberate boundaries where speculative integration language would create more noise than trust.',
    primaryCta: {
        href: '/contact',
        label: 'Plan the working session',
    },
    secondaryCta: {
        href: '/product',
        label: 'See the product model',
        variant: 'secondary',
    },
    highlights: [
        'Microsoft-first and governance-led.',
        'Real direction only, no catalog-padding.',
        'Explains fit without implying runtime coupling to the public site.',
    ],
};

export const integrationEntries: IntegrationEntry[] = [
    {
        category: 'Microsoft core',
        name: 'Microsoft Graph',
        summary:
            'Graph remains the primary contract path for inventory, history, and restore-oriented product behavior in the platform.',
        note: 'Core product contract',
    },
    {
        category: 'Identity',
        name: 'Entra ID',
        summary:
            'Identity context matters where tenant change, privileged access, or governance reviews intersect with Microsoft tenant administration.',
        note: 'Operational context',
    },
    {
        category: 'Endpoint',
        name: 'Intune',
        summary:
            'Intune configuration state is central to the current product story, especially for version history, backup, restore, and drift visibility.',
        note: 'Current release truth',
    },
    {
        category: 'Evidence',
        name: 'Review & evidence workflows',
        summary:
            'Exports, review packs, and evidence-linked conversations should remain grounded in the actual tenant object and its change history.',
        note: 'Governance workflow fit',
    },
];

export const integrationRules: FeatureItemContent[] = [
    {
        eyebrow: 'Direction',
        title: 'Integrations should reinforce the governance model.',
        description:
            'The page is not a marketplace list. It should show which systems matter because they change the product workflow, evidence story, or operator context.',
    },
    {
        eyebrow: 'Boundaries',
        title: 'Do not imply shared public-site runtime dependencies.',
        description:
            'The website stays static and independent even while the product story references Graph, Intune, and Microsoft tenant governance flows.',
    },
    {
        eyebrow: 'Credibility',
        title: 'Speculative wishlist entries reduce trust instead of creating momentum.',
        description:
            'The public integrations page should stay shorter and sharper than a catalog full of future ideas that are not relevant to launch truth.',
    },
];
