export const SECTION_ITEMS = [
  { id: 'first-checks', label: 'First checks' },
  { id: 'account-access', label: 'Account access' },
  { id: 'publishing-and-context', label: 'Publishing and context' },
  { id: 'profile-and-settings', label: 'Profile and settings' },
  { id: 'when-to-report', label: 'When to report it' },
  { id: 'faq', label: 'FAQ' },
  { id: 'related-help', label: 'Related help' },
]

export const HERO_METRICS = [
  {
    label: 'Best first move',
    value: 'Name the failure clearly',
    note: 'Broken, blocked, and unclear are not the same thing. The faster you label the problem, the faster the right fix shows up.',
  },
  {
    label: 'Most common false alarm',
    value: 'Permission or context confusion',
    note: 'A lot of apparent product failures are actually caused by the wrong active context, incomplete setup, or missing collaboration permissions.',
  },
  {
    label: 'Escalate when',
    value: 'A route is repeatably broken',
    note: 'If the same steps fail consistently and the issue is not explained by access, context, or settings, it is time to report the problem clearly.',
  },
]

export const FIRST_CHECKS = [
  'Ask whether the problem is broken, blocked, or just unclear. Those three paths have different fixes.',
  'Re-open the exact route you intended to use instead of guessing from memory or following an outdated tab.',
  'Check whether you are signed in, in the right account, and in the right personal or Group context before assuming the product failed.',
  'Reduce the problem to one sentence. If you cannot describe the failure clearly, start with the auth or account guides first.',
]

export const ACCOUNT_ACCESS_ITEMS = [
  {
    title: 'Login, reset, and verification come first',
    body: 'If access itself is failing, do not over-diagnose a Studio, profile, or publishing bug yet. Start with the auth guide and recovery paths first.',
  },
  {
    title: 'Wrong email and wrong inbox cause a lot of panic',
    body: 'Many access problems feel severe until you realize the account email, reset inbox, or verification message path was simply not the one you thought it was.',
  },
  {
    title: 'Partial access is still a useful clue',
    body: 'If some features work and others do not, the issue may be permissions, setup state, or workflow context rather than a total account failure.',
  },
]

export const PUBLISHING_CONTEXT_ITEMS = [
  {
    title: 'Personal vs Group context changes what you can do',
    body: 'Publishing problems often come from being in the wrong context or expecting personal access to behave like Group access.',
  },
  {
    title: 'Missing permission is not always a bug',
    body: 'If a Group role or shared workflow blocks an action, the fix usually lives in permissions guidance rather than product failure reporting.',
  },
  {
    title: 'Studio confusion often starts upstream',
    body: 'When Studio feels wrong, check whether the real issue is authentication, onboarding state, or the route you expected to open.',
  },
]

export const PROFILE_SETTINGS_ITEMS = [
  {
    title: 'Incomplete profile is usually a settings task',
    body: 'When the profile looks thin, inconsistent, or outdated, the answer usually lives in profile or account settings rather than troubleshooting a broken surface.',
  },
  {
    title: 'Identity confusion can feel like a feature issue',
    body: 'If the page feels wrong because personal and Group identity are blurred together, use profile and Groups help before filing a bug.',
  },
  {
    title: 'Notification or preference issues belong in settings',
    body: 'If the platform feels too noisy, too quiet, or out of sync with what you expect, the account settings guide is usually the better first stop.',
  },
]

export const REPORTING_ITEMS = [
  'Report a bug when you can reproduce the same failure on the same route with the same steps.',
  'Contact support when ownership, account identity, or a sensitive account question needs a human response instead of a pure product diagnosis.',
  'Include the route, what you expected, what actually happened, and whether the issue is personal-only or also affects Group workflows.',
  'Mention what you already checked so support does not have to restart from the most obvious first steps.',
]

export const FAQ_ITEMS = [
  {
    question: 'How do I know whether something is broken or I am just in the wrong context?',
    answer: 'Check whether the same route works after confirming login state, account identity, and personal-versus-Group context. If the failure disappears when context is corrected, it was not a product bug.',
  },
  {
    question: 'When should I use auth help instead of troubleshooting help?',
    answer: 'Use auth help when the core problem is account entry, recovery, or verification. Use troubleshooting help when the failure is broader or less clearly labeled.',
  },
  {
    question: 'When should I use account help instead of troubleshooting help?',
    answer: 'Use account help when access already works and the question is really about settings, profile maintenance, passwords, email care, or preferences.',
  },
  {
    question: 'What should I include in a bug report?',
    answer: 'Include the route, the exact steps, what you expected, what happened instead, and whether the issue repeats consistently. Clear reproduction details save the most time.',
  },
]

export const RELATED_HELP_ITEMS = [
  {
    eyebrow: 'Access',
    title: 'Signup and login help',
    body: 'Use the auth guide when the real failure starts with account entry, reset messages, or verification confusion.',
    linkKey: 'help_auth',
    tone: 'sky',
  },
  {
    eyebrow: 'Settings',
    title: 'Account settings help',
    body: 'Use the account guide when access already works and the real fix lives in profile settings, notifications, email care, or password maintenance.',
    linkKey: 'help_account',
    tone: 'amber',
  },
  {
    eyebrow: 'Publishing',
    title: 'Upload help',
    body: 'Use the upload guide when the “broken” feeling is really about drafts, metadata, publishing flow, or file-specific workflow confusion.',
    linkKey: 'upload_help',
    tone: 'white',
  },
  {
    eyebrow: 'Permissions',
    title: 'Groups FAQ',
    body: 'Use Groups guidance when the blocker is role-based access, contributor permissions, invites, or collaboration behavior.',
    linkKey: 'groups_faq',
    tone: 'white',
  },
]