Customer Success Stories

Note: This document contains placeholder success stories based on anticipated use cases. Replace with actual customer stories as they become available.

This document showcases how organizations are using the ReX content system to solve real-world challenges and achieve significant business outcomes.

TechDocs: Modernizing Technical Documentation

Company Profile

Company: TechDocs (Placeholder) Industry: Developer Tools Size: 25 employees Challenge: Fragmented documentation system with poor developer experience

Situation

TechDocs provides API services to thousands of developers. Their documentation was built on a traditional CMS that created friction in the development process:

• Engineers disliked the cumbersome process of updating documentation
• Code examples were often outdated and didn’t match the latest API
• The disconnect between code and docs led to support tickets and customer frustration
• Content team struggled with technical accuracy verification

Solution

TechDocs implemented the ReX content system with these key components:

• Integration with their CI/CD pipeline for automatic code example verification
• Custom API reference components that pull directly from their OpenAPI spec
• Collaborative editing workflow between engineers and technical writers
• Versioned documentation that matches API versions

Implementation

// Example of their API documentation component
import { APIEndpoint, CodeSamples, ResponseExample } from '@techdocs/components';

# User Authentication API

Use this endpoint to authenticate users in your application.

<APIEndpoint method="POST" path="/api/v2/auth" />

<CodeSamples
  examples={{
    curl: '...',
    javascript: '...',
    python: '...'
  }}
/>

<ResponseExample schema="auth.response" />

Results

• 62% reduction in documentation update time
• 89% decrease in documentation-related support tickets
• 40% increase in developer satisfaction scores
• 3.5x improvement in documentation accuracy
• Implementing new features with documentation now happens in the same sprint

Quote

“Before adopting ReX, our documentation was always lagging behind our API changes. Now our docs are treated as a first-class product alongside our API, with the same level of rigor and automation. The component-driven approach has transformed how our engineers think about documentation.”

— Alex Chen, Developer Experience Lead at TechDocs

FinLearn: Interactive Financial Education

Company Profile

Company: FinLearn (Placeholder) Industry: Financial Education Size: 50 employees Challenge: Creating engaging, interactive financial education content

Situation

FinLearn provides financial education to young professionals. Their previous content platform was limiting their educational effectiveness:

• Static content couldn’t demonstrate dynamic financial concepts
• Limited interactivity reduced engagement and learning outcomes
• Developers spent excessive time implementing custom solutions
• Content updates required development team involvement

Solution

FinLearn adopted ReX to create interactive financial lessons:

• Interactive calculators and visualization components
• Data-driven charts that respond to user inputs
• Step-by-step tutorials with state management
• Personalized learning paths with progress tracking

Implementation

# Understanding Compound Interest

See how your savings can grow over time with compound interest.

<CompoundInterestCalculator
  initialInvestment={1000}
  monthlyContribution={100}
  years={30}
  interestRate={7}
/>

Try adjusting the values above to see how different factors affect your long-term savings.

<ConceptCheck question="What happens to your savings if you double your monthly contribution?" />

Results

• 78% increase in lesson completion rates
• 44% improvement in concept retention scores
• 50% reduction in content development time
• 3x increase in user engagement metrics
• Content team now updates interactive examples without developer assistance

Quote

“The ability to embed interactive financial calculators and visualizations directly in our educational content has transformed how we teach complex concepts. Our users don’t just read about compound interest—they explore it hands-on. This has dramatically improved learning outcomes while reducing our development overhead.”

— Sophia Martinez, Head of Educational Content at FinLearn

DevShop: Streamlining Agency Documentation

Company Profile

Company: DevShop (Placeholder) Industry: Web Development Agency Size: 15 employees Challenge: Inefficient client project documentation and handoff

Situation

DevShop builds custom websites and applications for clients. Their documentation process was causing friction:

• Project documentation was scattered across multiple tools
• Client handoffs were cumbersome and often incomplete
• Component usage was inconsistently documented
• Maintenance teams struggled with undocumented code

Solution

DevShop implemented ReX to create a unified documentation approach:

• Centralized documentation hub for each client project
• Component-driven documentation that shows actual UI elements
• Collaborative editing between developers, designers, and project managers
• Client-facing and internal documentation from the same source

Implementation

# Client Brand Components

## Primary Button

Use the primary button for main calls-to-action.

<ComponentDemo name="PrimaryButton">
  <PrimaryButton>Click Me</PrimaryButton>
</ComponentDemo>

<CodeExample language="tsx">
  <PrimaryButton>Click Me</PrimaryButton>
</CodeExample>

<PropsTable component="PrimaryButton" />

Results

• 40% reduction in project handoff time
• 65% decrease in post-handoff support requests
• 30% improvement in developer onboarding efficiency
• 50% increase in documentation completeness
• Clients report higher satisfaction with project documentation

Quote

“Project handoffs used to be a pain point for both our team and clients. With ReX, we’ve created a documentation system that’s actually part of our development process, not an afterthought. Our components are automatically documented as we build them, and clients can see exactly how to use what we’ve built.”

— Jamie Wong, Technical Director at DevShop

EduTech: Modernizing Educational Content

Company Profile

Company: EduTech (Placeholder) Industry: Educational Technology Size: 75 employees Challenge: Scaling production of interactive learning materials

Situation

EduTech creates online learning platforms for K-12 education. They faced challenges with their content production:

• Creating interactive exercises required custom development for each lesson
• Content team couldn’t update interactive elements independently
• Difficult to maintain consistency across thousands of lessons
• Limited ability to track detailed user interactions with content

Solution

EduTech used ReX to transform their content creation process:

• Library of educational components (quizzes, exercises, simulations)
• Content team autonomy with component-driven authoring
• Consistent interaction patterns across all lessons
• Detailed analytics integration at the component level

Implementation

# Photosynthesis

Learn how plants convert sunlight into energy.

<InteractiveDiagram
  id="photosynthesis"
  initialState="sunlight"
  steps={[
    { id: 'sunlight', label: 'Sunlight' },
    { id: 'carbon-dioxide', label: 'Carbon Dioxide' },
    { id: 'water', label: 'Water' },
    { id: 'glucose', label: 'Glucose' },
    { id: 'oxygen', label: 'Oxygen' }
  ]}
/>

<MultipleChoiceQuiz
  question="What are the inputs to photosynthesis?"
  options={[
    "Oxygen and glucose",
    "Sunlight, carbon dioxide, and water",
    "Glucose and water",
    "Sunlight and oxygen"
  ]}
  correctIndex={1}
/>

Results

• 70% reduction in development time for interactive lessons
• 4x increase in content production velocity
• 45% improvement in student engagement metrics
• 60% decrease in content maintenance costs
• Content team now operates independently for 90% of updates

Quote

“The component-based approach has revolutionized how we create educational content. Our subject matter experts can now directly create interactive lessons without constantly relying on developers. This has not only accelerated our content production but also improved quality as our educators have more direct control over the learning experience.”

— Michael Johnson, Chief Product Officer at EduTech

Conclusion

These case studies demonstrate the versatility and impact of the ReX content system across different industries and use cases. The common themes across successful implementations include:

1. Bridging technical and non-technical teams
2. Accelerating content production and updates
3. Improving content quality and consistency
4. Enabling interactive, component-driven experiences
5. Reducing development overhead for content initiatives

By combining the power of React components with intuitive content authoring, organizations are overcoming traditional barriers between development and content creation, resulting in better experiences for both internal teams and end users.

Note: These placeholder case studies will be replaced with actual customer stories as they become available.