ahmido
0da1b38764
Some checks failed
Main Confidence / confidence (push) Failing after 43s
## Summary - implement the website-only core IA for Spec 215 with canonical Home, Product, Trust, Changelog, Contact, Privacy, and Imprint routes - reduce primary navigation to the core buyer journey, retain legal/supporting pages as secondary surfaces, and redirect `/security-trust` to `/trust` - add route metadata, sitemap/canonical handling, changelog publishing, and updated smoke coverage for the new IA contract ## Testing - `corepack pnpm build:website` - `cd apps/website && corepack pnpm exec playwright test` - integrated browser smoke validation for core routes, secondary routes, `/security-trust -> /trust`, hidden optional routes, mobile nav, and Trust/Changelog to Contact paths ## Notes - keeps all changes local to `apps/website` and the Spec 215 artifacts - preserves the website working contract with no `apps/platform` runtime coupling Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #252
91 lines
3.8 KiB
TypeScript
91 lines
3.8 KiB
TypeScript
import type {
|
|
AudienceRowContent,
|
|
FeatureItemContent,
|
|
HeroContent,
|
|
PageSeo,
|
|
} from '@/types/site';
|
|
|
|
export const solutionsSeo: PageSeo = {
|
|
title: 'TenantAtlas | Solutions',
|
|
description:
|
|
'TenantAtlas keeps MSP and enterprise outcome framing available as a supporting page without requiring it for the first public read.',
|
|
path: '/solutions',
|
|
};
|
|
|
|
export const solutionsHero: HeroContent = {
|
|
eyebrow: 'Retained supporting page',
|
|
title: 'Keep MSP and enterprise audience-fit detail published without letting it crowd the core route set.',
|
|
description:
|
|
'The product helps different organizations answer similar governance questions, but the surrounding workflow, accountability, and evidence needs are not identical. This page stays available without becoming required orientation for every first-time visitor.',
|
|
primaryCta: {
|
|
href: '/product',
|
|
label: 'See the product model',
|
|
},
|
|
secondaryCta: {
|
|
href: '/contact',
|
|
label: 'Start the working session',
|
|
variant: 'secondary',
|
|
},
|
|
highlights: [
|
|
'Separate MSP and enterprise language on purpose.',
|
|
'Keep the product story stable while the buying context changes.',
|
|
'Stay secondary to Product, Trust, Changelog, and Contact.',
|
|
],
|
|
};
|
|
|
|
export const solutionsAudiences: AudienceRowContent[] = [
|
|
{
|
|
audience: 'MSP',
|
|
title: 'MSP operating model',
|
|
description:
|
|
'Managed service providers need tenant-scoped operational truth, repeatable review workflows, and a way to explain change history to customers without drowning in manual evidence gathering.',
|
|
bullets: [
|
|
'Keep per-tenant history and restore posture reviewable during service delivery.',
|
|
'Support a higher tempo of customer change while preserving a clean audit story.',
|
|
'Give account and delivery teams a shared language for exceptions, findings, and follow-up.',
|
|
],
|
|
cta: {
|
|
href: '/contact',
|
|
label: 'Discuss MSP delivery fit',
|
|
variant: 'secondary',
|
|
},
|
|
},
|
|
{
|
|
audience: 'Enterprise IT',
|
|
title: 'Enterprise IT operating model',
|
|
description:
|
|
'Internal IT and security teams need durable version truth, change visibility, and review evidence that can stand up to operational leadership, audit, and cross-team scrutiny.',
|
|
bullets: [
|
|
'Reduce uncertainty around who changed what and when across the Microsoft tenant surface.',
|
|
'Support internal review packs, exception handling, and evidence collection without fragmented tooling.',
|
|
'Keep restore and remediation conversations grounded in the current tenant state and the relevant history.',
|
|
],
|
|
cta: {
|
|
href: '/trust',
|
|
label: 'Inspect the trust posture',
|
|
variant: 'secondary',
|
|
},
|
|
},
|
|
];
|
|
|
|
export const solutionsSignals: FeatureItemContent[] = [
|
|
{
|
|
eyebrow: 'Why buyers care',
|
|
title: 'The product is serious about both velocity and control.',
|
|
description:
|
|
'Teams can move quickly without giving up visibility, confirmation discipline, or explainability when a risky change needs review.',
|
|
},
|
|
{
|
|
eyebrow: 'Where it lands',
|
|
title: 'The product belongs in the operating layer, not just the reporting layer.',
|
|
description:
|
|
'Visitors should understand that TenantAtlas helps teams make safer decisions about configuration state rather than merely summarize activity afterward.',
|
|
},
|
|
{
|
|
eyebrow: 'How it reads',
|
|
title: 'The story changes by audience, but the product truth does not.',
|
|
description:
|
|
'MSP and enterprise readers see their own operating concerns reflected without the site inventing two different products.',
|
|
},
|
|
];
|