Add documentation/FAQ on startup program

[SahanaVP]

We offer a startup program which many folks don't know about as we get a few support tickets regarding the same: https://www.coderabbit.ai/startup-program
Ref: https://coderabbitai.slack.com/archives/C07PMSSDY2H/p1749765162099739

[linear]

ENG-1660 Add documentation/FAQ on startup program

[traycerai]

Plan

Observations

The repository has no existing Startup Program content and navigation is driven by sidebars.ts. Lint/format rules (markdownlint + Prettier) and CI will fail on broken links, so internal anchors and file names must be exact. All documentation lives under docs/, assets under static/. FAQ is centralised in docs/faq.md and is structured with heading anchors.

Approach

Add a dedicated guide docs/startup-program.md with front-matter, full content (overview → eligibility → benefits → application → FAQ → support). Link to it from both the sidebar (Get started section) and the main FAQ. Re-run lint/build locally to catch bad links, then open a PR referencing ticket #401. No runtime code is touched, only Markdown and config.

Reasoning

I explored docs/, sidebars.ts, lint configs and CI workflows, verified that no Startup Program docs exist, and collected program facts from the public landing page plus support threads.

Proposed File Changes

📄 docs/startup-program.md ^(NEW) 🔗

References

• 📄 docs/getting-started/quickstart.md
• 📄 docs/getting-started/subscription-management.md
• 📄 docs/faq.md ^(MODIFY)

Create the new Markdown file with: 1) YAML front-matter defining title, sidebar_label, description, and an appropriate sidebar_position. 2) Sections: Program Overview, Eligibility, Features & Benefits, Application Process, Post-approval Onboarding (link to docs/getting-started/quickstart.md), FAQ (with internal anchors), Support & Next Steps. 3) Internal links should use relative paths (startup-program#eligibility, getting-started/subscription-management). 4) Ensure spacing, headings, and list syntax conform to markdownlint rules; indent code blocks with tabs where needed.

📄 sidebars.ts ^(MODIFY) 🔗

References

• 📄 docs/startup-program.md ^(NEW)

Within the "Get started with CodeRabbit" category, insert a new doc item referencing the new file: { type: 'doc', id: 'startup-program', }. Position it logically after the quick-start entry so users see the offer early. No other structural changes are required.

📄 docs/faq.md ^(MODIFY) 🔗

References

• 📄 docs/startup-program.md ^(NEW)

Add a new subsection near the existing plan-related Q&A: heading ## Plans & Special Programs if not present, then a question ### Does CodeRabbit have a Startup Program? {#startup-program-faq} with a concise answer, eligibility bullet list, and a markdown link [Learn more →](startup-program). Add a follow-up question about what happens after the discount period with a link to getting-started/subscription-management.md. Maintain heading hierarchy and spacing to satisfy markdownlint.

Diagram

sequenceDiagram
  participant User
  participant Docs
  User->>Docs: Opens sidebar
  Docs-->>User: Shows "Startup Program" link
  User->>Docs: Clicks link
  Docs-->>User: Renders startup-program.md content
  User->>Docs: Follows FAQ link
  Docs-->>User: Scrolls to #startup-program-faq answer

Loading

Import In IDE

Developer Humor

A startup loves a good discount deal,
So CodeRabbit rolls out its startup appeal.
Docs appear with a cheer 🐰📄,
Support tickets disappear!
CI smiles, lint is clean—now ship that docs reveal! 🚀

---

Execution Information

Branch: main
Commit: 8d5d1ca

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.