/**
 * FAQ for the MVP architecture and launch service page.
 * Single source of truth for both the page content and FAQPage JSON-LD.
 */

export interface FaqItem {
    question: string;
    answer: string;
}

export const faqItems: FaqItem[] = [
    {
        question: 'Will this slow us down?',
        answer: 'No. The goal is to make iteration cheaper. I work incrementally—fixing foundations while you keep shipping. No rewrite mandates, no velocity freeze.',
    },
    {
        question: 'Do we need a full rewrite?',
        answer: 'Usually no. Most MVPs need structural cleanup and a clear component/CSS strategy, not a from-scratch rebuild. We prioritize the highest-leverage fixes first.',
    },
    {
        question: 'What tech stacks do you work with?',
        answer: 'I work with modern web stacks—React, Vue, Svelte, and similar. The principles (separation of concerns, tokens, components, accessibility) transfer. We can discuss fit for your stack.',
    },
    {
        question: 'How do you handle accessibility?',
        answer: 'Accessibility is baked in incrementally: semantic markup, keyboard and focus behavior, and ARIA where needed. Doing it as we refactor is far cheaper than retrofitting later.',
    },
    {
        question: 'Can you work alongside our existing devs?',
        answer: 'Yes. I pair with your team, document decisions, and hand off so you’re not dependent on me. Knowledge transfer is part of the engagement.',
    },
    {
        question: 'How quickly will we see impact?',
        answer: 'Most teams feel the difference within 1–2 weeks once foundational issues are addressed: faster feature work, fewer bugs, and safer refactors.',
    },
    {
        question: 'Do you only focus on frontend?',
        answer: "I'm product-first. Frontend foundations are often the bottleneck for early MVPs, so that's where I focus—but I align with your backend boundaries and deployment so the whole system makes sense.",
    },
];
