feat(docs): enhance comparison documents with Fern components

- Add CardGroup with icons for top 10 enterprise gaps in summary
- Convert detailed feature sections to Accordions in full document
- Add Info, Success, Warning, and Launch callouts throughout
- Enhance key links section with Cards for better organization
- Improve visual hierarchy and readability with collapsible sections
- Make documents more digestible and scannable for sales engineering use

Co-Authored-By: Chris McDonnell <[email protected]>

Author: devin-ai-integration[bot]

fern/products/docs/pages/resources/stainless-comparison-full.mdx

@@ -5,11 +5,13 @@ description: Comprehensive enterprise feature comparison between Stainless Docs
 
 # Stainless Docs vs Fern Docs: Enterprise Feature Comparison
 
-## Executive Summary
+## Executive summary
 
+<Info title="Overview">
 Fern Docs is a production-ready, enterprise-grade documentation platform with comprehensive features for large-scale API documentation, while Stainless Docs Platform remains in early access with significant feature gaps for enterprise deployments.
+</Info>
 
-**Key Enterprise Advantages of Fern:**
+**Key enterprise advantages of Fern:**
 
 1. **Production Maturity**: Fern is production-ready and battle-tested, while Stainless explicitly warns of "breaking changes before 1.0" in their early access phase.
 
@@ -33,9 +35,10 @@ Fern Docs is a production-ready, enterprise-grade documentation platform with co
 
 ---
 
-## Detailed Feature Comparison
+## Detailed feature comparison
 
-### 1. Platform Maturity and Stability
+<AccordionGroup>
+<Accordion title="1. Platform maturity and stability" defaultOpen={true}>
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -50,9 +53,9 @@ Fern Docs is a production-ready, enterprise-grade documentation platform with co
 
 **Gap Analysis:** Stainless is not ready for enterprise production deployments where API stability and backward compatibility are critical. Fern's production-ready status makes it suitable for mission-critical documentation.
 
----
+</Accordion>
 
-### 2. Content Authoring and Governance
+<Accordion title="2. Content authoring and governance">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -70,9 +73,9 @@ Fern Docs is a production-ready, enterprise-grade documentation platform with co
 
 **Gap Analysis:** Stainless requires all authors to use Git workflows and code editors, limiting collaboration to technical team members. Fern's visual editor democratizes documentation authoring, enabling technical writers, product managers, and support teams to contribute without Git expertise.
 
----
+</Accordion>
 
-### 3. API Reference and Interactive Testing
+<Accordion title="3. API reference and interactive testing">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -91,9 +94,9 @@ Fern Docs is a production-ready, enterprise-grade documentation platform with co
 
 **Gap Analysis:** Stainless lacks an interactive API testing environment, forcing developers to use external tools like Postman or curl. Fern's integrated API Explorer reduces friction and enables developers to test endpoints without leaving the documentation, with automatic credential injection for authenticated users.
 
----
+</Accordion>
 
-### 4. RBAC, Versioning, and Multi-Product Support
+<Accordion title="4. RBAC, versioning, and multi-product support">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -117,9 +120,9 @@ Fern Docs is a production-ready, enterprise-grade documentation platform with co
 
 Fern's RBAC and versioning capabilities are essential for enterprises with complex API portfolios and diverse user bases.
 
----
+</Accordion>
 
-### 5. AI-Powered Search and Assistance
+<Accordion title="5. AI-powered search and assistance">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -147,9 +150,9 @@ Fern's RBAC and versioning capabilities are essential for enterprises with compl
 
 Stainless offers basic RAG search without the operational controls needed for enterprise deployments where answer accuracy and compliance are critical.
 
----
+</Accordion>
 
-### 6. Authentication and Security
+<Accordion title="6. Authentication and security">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -169,9 +172,9 @@ Stainless offers basic RAG search without the operational controls needed for en
 - Compliance with security policies requiring authenticated documentation access
 - Integration with existing identity providers (Okta, Azure AD, etc.)
 
----
+</Accordion>
 
-### 7. Hosting and Deployment
+<Accordion title="7. Hosting and deployment">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -197,9 +200,9 @@ Stainless offers basic RAG search without the operational controls needed for en
 
 Fern's self-hosted Docker container includes all necessary services (PostgreSQL, MinIO, MeiliSearch, FDR, Next.js UI), making it suitable for regulated industries (healthcare, finance, government) that require on-premises deployment with full data sovereignty.
 
----
+</Accordion>
 
-### 8. Redirects, SEO, and Large-Site Operations
+<Accordion title="8. Redirects, SEO, and large-site operations">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -224,9 +227,9 @@ Fern's self-hosted Docker container includes all necessary services (PostgreSQL,
 
 Stainless lacks documented redirect capabilities, making it unsuitable for migrations or large-scale content reorganization.
 
----
+</Accordion>
 
-### 9. Analytics and Observability
+<Accordion title="9. Analytics and observability">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -251,9 +254,9 @@ Stainless lacks documented redirect capabilities, making it unsuitable for migra
 
 This data-driven approach enables continuous documentation improvement. Stainless lacks documented analytics capabilities.
 
----
+</Accordion>
 
-### 10. Extensibility and Integrations
+<Accordion title="10. Extensibility and integrations">
 
 | Feature | Fern Docs | Stainless Docs |
 |---------|-----------|----------------|
@@ -278,9 +281,12 @@ This data-driven approach enables continuous documentation improvement. Stainles
 
 Stainless emphasizes Astro's ecosystem but lacks the enterprise integrations Fern provides.
 
+</Accordion>
+</AccordionGroup>
+
 ---
 
-## Technology Stack Comparison
+## Technology stack comparison
 
 ### Fern Docs
 - **Frontend**: Next.js (React) with SSR/SSG
@@ -312,9 +318,10 @@ Stainless emphasizes Astro's ecosystem but lacks the enterprise integrations Fer
 
 ---
 
-## Use Case Recommendations
+## Use case recommendations
 
-### Choose Fern Docs When:
+<AccordionGroup>
+<Accordion title="Choose Fern Docs when" defaultOpen={true}>
 1. **Enterprise Requirements**: You need RBAC, SSO, versioning, or multi-product documentation
 2. **Regulated Industries**: You require self-hosted deployment with full data sovereignty
 3. **Interactive Testing**: Developers need to test APIs directly in documentation
@@ -326,7 +333,9 @@ Stainless emphasizes Astro's ecosystem but lacks the enterprise integrations Fer
 9. **Production Stability**: You need a stable, battle-tested platform with backward compatibility
 10. **Comprehensive Support**: You want white-glove migration and ongoing support
 
-### Choose Stainless Docs When:
+</Accordion>
+
+<Accordion title="Choose Stainless Docs when">
 1. **Early Adopter**: You're comfortable with early access software and breaking changes
 2. **Simple Documentation**: You have straightforward documentation needs without versioning or RBAC
 3. **Astro Expertise**: Your team prefers Astro and wants deep customization control
@@ -338,9 +347,12 @@ Stainless emphasizes Astro's ecosystem but lacks the enterprise integrations Fer
 9. **Cloudflare Preference**: You're committed to Cloudflare's ecosystem
 10. **Patience for Maturity**: You can wait for the platform to reach 1.0 stability
 
+</Accordion>
+</AccordionGroup>
+
 ---
 
-## Migration Considerations
+## Migration considerations
 
 ### Migrating from Stainless to Fern
 - **Effort**: Medium - Content can be migrated from MDX/Markdoc to Fern MDX
@@ -374,11 +386,13 @@ Stainless emphasizes Astro's ecosystem but lacks the enterprise integrations Fer
 
 ## Conclusion
 
-Fern Docs is the clear choice for enterprise organizations requiring production-ready documentation with advanced features like RBAC, versioning, interactive API testing, visual editing, enterprise SSO, and full-stack self-hosting. The platform's maturity, comprehensive feature set, and robust infrastructure make it suitable for mission-critical documentation at scale.
+<Launch>
+**Fern Docs is the clear choice for enterprise organizations** requiring production-ready documentation with advanced features like RBAC, versioning, interactive API testing, visual editing, enterprise SSO, and full-stack self-hosting. The platform's maturity, comprehensive feature set, and robust infrastructure make it suitable for mission-critical documentation at scale.
 
-Stainless Docs Platform shows promise with its Astro-based architecture and SDK-native approach, but remains in early access with significant feature gaps for enterprise deployments. Organizations should wait for Stainless to reach production maturity before considering it for critical documentation needs.
+**Stainless Docs Platform shows promise** with its Astro-based architecture and SDK-native approach, but remains in early access with significant feature gaps for enterprise deployments. Organizations should wait for Stainless to reach production maturity before considering it for critical documentation needs.
 
-For enterprises evaluating documentation platforms today, Fern Docs provides the stability, features, and support required for successful API documentation programs.
+**For enterprises evaluating documentation platforms today**, Fern Docs provides the stability, features, and support required for successful API documentation programs.
+</Launch>
 
 ---