feat: lay groundwork for "peach" help center theme

peach/README.md

@@ -0,0 +1,36 @@
+# Peach Theme (Help Center)
+
+Example Help Center site using the Peach theme.
+
+## Structure
+
+```
+├── index.mdx                     # Homepage (hero + search + group tiles)
+├── getting-started/
+│   ├── index.mdx                 # Directory page (frontmatter-only)
+│   ├── quick-setup.mdx           # Article
+│   ├── first-project.mdx         # Article
+│   └── invite-team.mdx           # Article
+├── billing/
+│   ├── index.mdx                 # Directory page
+│   ├── change-plan.mdx           # Article
+│   ├── invoices.mdx              # Article
+│   └── payment/
+│       ├── index.mdx             # Sub-category directory page
+│       ├── add-card.mdx          # Article
+│       └── bank-transfer.mdx     # Article
+├── integrations/
+│   ├── index.mdx                 # Directory page
+│   ├── slack.mdx                 # Article
+│   └── github.mdx                # Article
+└── docs.json
+```
+
+## Key differences from docs themes
+
+- `root` is **required** on every group (every category is visitable)
+- Directory pages (group root pages with empty body) auto-render a `<PageList />` of children
+- If a root page has content, the directory listing is shown alongside it (like API playground pages)
+- `description` and `image` for categories come from the root page's **frontmatter**, not `docs.json`
+- Breadcrumbs default to on (`styling.eyebrows: "breadcrumbs"`)
+- Navigation is tile/list-based instead of sidebar

peach/account-security/audit-logs.mdx

@@ -0,0 +1,23 @@
+---
+title: "Audit logs"
+description: "Track who changed settings, published updates, or modified access-sensitive parts of the workspace."
+author:
+  name: "Jordan Lee"
+createdDate: "2026-03-10"
+icon: "history"
+---
+
+Audit logs help security, support, and content owners answer an important question quickly: **what changed, and who changed it?**
+
+## Common events to review
+
+- user invitations and removals
+- permission changes
+- authentication setting changes
+- production publishes
+- integration updates
+
+<Info>
+  Audit logs are especially useful during incident review. When a site changes unexpectedly, start
+  by confirming whether the cause was a content publish, a settings change, or an access update.
+</Info>

peach/account-security/data-privacy.mdx

@@ -0,0 +1,31 @@
+---
+title: "Data privacy"
+description: "Understand how to handle customer-facing content, user access, and vendor review processes responsibly."
+author:
+  name: "Maya Patel"
+createdDate: "2026-03-10"
+icon: "shield-check"
+---
+
+Privacy questions usually come up during procurement, security review, or when teams start embedding product-specific information into their docs workflows.
+
+<AccordionGroup>
+  <Accordion title="What kind of content should we avoid storing in docs?">
+    Do not place secrets, raw credentials, or customer-specific private information in published
+    docs content. Treat the docs repository like a product surface that needs the same security
+    discipline as application code.
+  </Accordion>
+  <Accordion title="Who should be allowed to access internal documentation?">
+    Restrict internal content using your authentication model, group membership, or separate sites if
+    the audience differs significantly.
+  </Accordion>
+  <Accordion title="How should we respond to vendor review questions?">
+    Keep a short, stable internal checklist for privacy, data handling, subprocessors, and retention
+    so support and security teams can answer consistently.
+  </Accordion>
+</AccordionGroup>
+
+<Warning>
+  A help center should be easy to browse, but that does not mean every page should be public. Keep
+  audience boundaries explicit.
+</Warning>

peach/account-security/index.mdx

@@ -0,0 +1,12 @@
+---
+title: "Account & Security"
+description: "Control who can access the workspace, what they can do, and how activity is audited."
+icon: "shield"
+---
+
+Security settings should support collaboration without making the content workflow brittle.
+
+<Tip>
+  Start with sign-in and permissions. Audit logs and privacy workflows become much easier to reason
+  about once access boundaries are already clear.
+</Tip>

peach/account-security/login-and-sso.mdx

@@ -0,0 +1,35 @@
+---
+title: "Login & SSO"
+description: "Set up sign-in rules that are easy for employees to use and straightforward for admins to enforce."
+author:
+  name: "Jordan Lee"
+createdDate: "2026-03-10"
+icon: "lock-keyhole"
+---
+
+<Badge color="purple" size="sm">Enterprise</Badge>
+
+Single sign-on helps teams centralize access, enforce offboarding, and reduce ad hoc password management.
+
+<Steps>
+  <Step title="Choose the identity provider">
+    Confirm which identity provider will own the user lifecycle and what attributes must be passed
+    during sign-in.
+  </Step>
+  <Step title="Configure the SSO connection">
+    Add the provider details in your security settings and verify the callback values before you
+    save the configuration.
+  </Step>
+  <Step title="Test with a small admin group">
+    Validate sign-in with a limited set of internal users before you enforce SSO for everyone.
+  </Step>
+  <Step title="Roll out gradually">
+    Communicate the change to teammates, document the new login flow, and keep a fallback admin path
+    available until the rollout is stable.
+  </Step>
+</Steps>
+
+<Note>
+  If your team uses SCIM or automated user provisioning, make sure the expected roles and group
+  mappings are agreed on before you enable sign-in enforcement.
+</Note>

peach/account-security/roles-and-permissions.mdx

@@ -0,0 +1,30 @@
+---
+title: "Roles and permissions"
+description: "Give each teammate the level of access they need without expanding the blast radius of mistakes."
+author:
+  name: "Jordan Lee"
+createdDate: "2026-03-10"
+icon: "users"
+---
+
+Use permissions to separate ownership, publishing authority, and review access.
+
+<AccordionGroup>
+  <Accordion title="Admins">
+    Admins can manage workspace settings, integrations, authentication, billing, and content.
+    Reserve Admin for a small set of owners.
+  </Accordion>
+  <Accordion title="Editors">
+    Editors are the primary content operators. They can write, review, and publish without needing
+    access to billing or sensitive security settings.
+  </Accordion>
+  <Accordion title="Viewers">
+    Viewers can inspect content and collaborate in lightweight ways without making production
+    changes.
+  </Accordion>
+</AccordionGroup>
+
+<Tip>
+  Least-privilege access works best when roles are boring and predictable. Avoid one-off exceptions
+  whenever you can.
+</Tip>

peach/billing/change-plan.mdx

@@ -0,0 +1,42 @@
+---
+title: "Change Your Plan"
+description: "Upgrade, downgrade, or switch plans with a clear understanding of billing timing and access changes."
+author:
+  name: "Sofia Kim"
+createdDate: "2026-03-10"
+icon: "refresh-cw"
+---
+
+<Badge color="blue" size="sm">Billing</Badge>
+
+Use plan changes when you need more seats, advanced collaboration, deeper security controls, or a different support model.
+
+<Steps>
+  <Step title="Review your current usage">
+    Check seats, traffic, integrations, and any advanced features your team is already using before
+    you switch plans.
+  </Step>
+  <Step title="Compare the target plan">
+    Open **Settings > Billing** and confirm the plan includes the limits and features you need.
+  </Step>
+  <Step title="Confirm billing timing">
+    Upgrades usually take effect immediately, while downgrades may wait until the next billing
+    cycle. Review the confirmation screen before you submit the change.
+  </Step>
+  <Step title="Notify internal stakeholders">
+    If the change affects approvals, invoicing, or security features, tell your finance and IT
+    teams before the new plan goes live.
+  </Step>
+</Steps>
+
+## What changes after you switch
+
+- Billing totals may be prorated depending on your current cycle
+- Seat allowances and advanced features update to match the new plan
+- Existing content and URLs remain in place
+- Invoice format and payment collection timing may change for Enterprise contracts
+
+<Warning>
+  Downgrading can affect seat limits or advanced features such as SSO. Audit your current setup
+  before you confirm the change.
+</Warning>

peach/billing/index.mdx

@@ -0,0 +1,12 @@
+---
+title: "Billing & Plans"
+description: "Manage subscriptions, payment methods, invoices, and the billing contacts tied to your workspace."
+icon: "credit-card"
+---
+
+Use this section for everything related to renewals, payment collection, invoices, taxes, and plan changes.
+
+<Tip>
+  If you need invoice-based billing or bank transfer support, check the **Payment Methods** section
+  first. It covers the Enterprise-only workflow and what information support needs from you.
+</Tip>

peach/billing/invoices.mdx

@@ -0,0 +1,40 @@
+---
+title: "Invoices"
+description: "Download invoices, confirm tax details, and understand what to do when a payment fails."
+author:
+  name: "Sofia Kim"
+createdDate: "2026-03-10"
+icon: "receipt"
+---
+
+Invoices are available from your billing settings and provide the source of truth for charges, taxes, credits, and payment status.
+
+## Download invoice history
+
+Go to **Settings > Billing > Invoices** to view the full billing history for your workspace. Each
+invoice can be opened and downloaded as a PDF for internal record keeping.
+
+## Check tax and billing details
+
+Before forwarding an invoice to finance, confirm:
+
+- the billing entity name is correct
+- the tax ID or VAT information is current
+- the invoice address matches your finance system
+- the payment method listed is still active
+
+## If an invoice shows as unpaid
+
+<AccordionGroup>
+  <Accordion title="A card payment failed">
+    Update the card on file and retry collection from the billing page if that option is available.
+  </Accordion>
+  <Accordion title="An invoice payment is still pending">
+    Bank transfers and invoice-based payments can take longer to reconcile. Wait until the payment
+    clears before assuming the invoice is overdue.
+  </Accordion>
+  <Accordion title="The invoice details are wrong">
+    Contact support with the invoice number and describe exactly what needs to change before your
+    finance team processes payment.
+  </Accordion>
+</AccordionGroup>

peach/billing/payment/add-card.mdx

@@ -0,0 +1,37 @@
+---
+title: "Add a Card"
+description: "Add or replace the credit card used for automatic billing on your workspace."
+author:
+  name: "Sofia Kim"
+createdDate: "2026-03-10"
+icon: "credit-card"
+---
+
+<Frame
+  hint="A saved card is the fastest way to keep renewals and seat changes uninterrupted."
+  caption="Example billing settings screen with payment methods, renewal date, and billing contacts."
+>
+  <img src="/images/billing-settings.svg" alt="Illustration of a billing settings screen with payment method and billing contact sections." />
+</Frame>
+
+<Steps>
+  <Step title="Open billing settings">
+    Go to **Settings > Billing > Payment Methods**.
+  </Step>
+  <Step title="Choose Add card">
+    Select **Add card** or **Replace card** depending on whether you already have a payment method
+    on file.
+  </Step>
+  <Step title="Enter card details">
+    Add the card number, expiration date, CVC, and the billing address associated with the card.
+  </Step>
+  <Step title="Save and confirm">
+    Save the payment method and verify it appears as the default card for future invoices and seat
+    changes.
+  </Step>
+</Steps>
+
+<Info>
+  If your finance team requires invoice-based billing instead of a card on file, use
+  [Bank transfer](/billing/payment/bank-transfer) instead.
+</Info>

peach/billing/payment/bank-transfer.mdx

@@ -0,0 +1,45 @@
+---
+title: "Bank Transfer"
+description: "Set up ACH or wire transfers for invoice-based billing on eligible plans."
+author:
+  name: "Sofia Kim"
+createdDate: "2026-03-10"
+icon: "landmark"
+---
+
+<Badge color="purple" size="sm">Enterprise</Badge>
+
+Bank transfer billing is a good fit when your finance team needs purchase-order workflows, invoice approvals, or payment collection outside of a card network.
+
+## How to get started
+
+<Steps>
+  <Step title="Confirm your billing model">
+    Make sure your contract supports invoice-based billing and bank transfer payments.
+  </Step>
+  <Step title="Send your finance details">
+    Contact [support@mintlify.com](mailto:support@mintlify.com) with your billing entity, billing
+    address, and any tax information your invoices require.
+  </Step>
+  <Step title="Wait for remittance instructions">
+    Mintlify will provide the invoice workflow and remittance instructions tied to your contract.
+  </Step>
+  <Step title="Pay against each invoice">
+    Use the invoice number in your remittance reference so the payment can be reconciled quickly.
+  </Step>
+</Steps>
+
+<AccordionGroup>
+  <Accordion title="Do we need a purchase order?">
+    If your company requires a PO, send it before your first invoice is issued so it can be added
+    to the billing workflow.
+  </Accordion>
+  <Accordion title="Can we keep a backup card on file?">
+    Yes. Some teams keep a backup card for smaller overages while using bank transfer for primary
+    subscription invoices.
+  </Accordion>
+  <Accordion title="What if our payment is delayed?">
+    If your finance team expects a delay, notify support and include the invoice number so the
+    workspace can be reviewed before renewal or suspension logic runs.
+  </Accordion>
+</AccordionGroup>

peach/billing/payment/billing-email.mdx

@@ -0,0 +1,22 @@
+---
+title: "Billing contact email"
+description: "Update the email address that receives invoices, renewal notices, and payment follow-up."
+author:
+  name: "Sofia Kim"
+createdDate: "2026-03-10"
+icon: "mail"
+---
+
+Keep your billing contact current so invoice reminders and renewal notices reach the right team.
+
+<Steps>
+  <Step title="Open billing settings">
+    Go to **Settings > Billing**.
+  </Step>
+  <Step title="Update the billing contact">
+    Replace the old finance or operations email with the address your team actually monitors.
+  </Step>
+  <Step title="Confirm future notices">
+    Make sure the new contact receives invoice copies, failed-payment notices, and renewal alerts.
+  </Step>
+</Steps>

peach/billing/payment/index.mdx

@@ -0,0 +1,12 @@
+---
+title: "Payment Methods"
+description: "Add a card, switch to invoice-based billing, or update the contact details used for billing communications."
+icon: "wallet"
+---
+
+Choose the payment setup that matches your team. Most workspaces use a card on file, while larger teams may move to invoice-based billing and bank transfer.
+
+<Tip>
+  Keep your billing contact current even if you pay by card. That is where failed-payment and
+  renewal notifications are sent.
+</Tip>