export const NAV_ITEMS = [
    { label: 'Standard.site', href: '#' },
    { label: 'Introduction', href: '#introduction' },
    { label: 'Definitions', href: '#definitions' },
    { label: 'Verification', href: '#verification' },
    { label: 'Questions', href: '#questions' },
]

export const SECONDARY_NAV_ITEMS = [
    { label: 'Documentation', href: '/docs/introduction' },
]

export const EXTERNAL_LINKS = [
    { label: 'bsky.app', href: 'https://bsky.app/profile/standard.site' },
    { label: 'tangled.org', href: 'https://tangled.org/standard.site' },
    { label: 'pdsls.dev', href: 'https://pdsls.dev/at://did:plc:re3ebnp5v7ffagz6rb6xfei4/com.atproto.lexicon.schema' },
]

export const PRINCIPLES = [
    {
        title: 'Unified discovery',
        description: 'One schema for indexers and tooling. No more supporting multiple lexicons.',
    },
    {
        title: 'Content portability',
        description: 'Users move between hosts without losing their content, audience, or metadata.',
    },
    {
        title: 'Community ownership',
        description: 'Maintained by the developers building on it. No single platform controls the standard.',
    },
    {
        title: 'Minimal governance',
        description: 'Coordination through adoption, not committee. The schema evolves as the ecosystem does.',
    },
]

export const FAQ_ITEMS = [
    {
        question: 'How do I implement this?',
        answer:
            'Publish records using the site.standard.publication and site.standard.document lexicons. Reference the schema definitions for required and optional fields. If you have questions, reach out via Bluesky.',
    },
    {
        question: 'Can I extend the lexicons?',
        answer:
            'Yes. Additional properties pass through validation. Platform-specific features can live alongside the standard fields. The schema defines a shared baseline, not a constraint.',
    },
    {
        question: 'Why is content format not specified?',
        answer:
            'Different platforms structure content differently. Forcing one format would limit adoption. Standard.site focuses on metadata for discovery and portability. Content remains an open union that each platform defines.',
    },
    {
        question: 'Why not just use lexicon.community?',
        answer:
            'Lexicon.community is a broader effort with more formal governance. Standard.site was created to move quickly on a specific problem that a few teams had already solved independently. If it makes sense to merge efforts later, that remains an option.',
    },
    {
        question: 'Who maintains Standard.site?',
        answer:
            'A small group of developers building long-form platforms on AT Protocol. Founding members are developers from Offprint, Leaflet, and pckt.blog. Governance is informal. Changes are discussed openly and adoption determines what stays.',
    },
    {
        question: 'Who owns the domain?',
        answer:
            'The domain is registered by an individual contributor, but credentials are shared among founding members. Ownership is a practical detail, not a claim of control.',
    },
    {
        question: 'How can I get involved?',
        answer:
            'Start by implementing the lexicons. If you find gaps or have suggestions, open an issue or join the discussion. The standard improves through use.',
    },
]

export const LEXICON_TABS = [
    'site.standard.publication',
    'site.standard.document',
    'site.standard.graph.subscription',
    'site.standard.graph.recommend',
]