ReXDocumentation

About ReX ​

ReX (short for RemedyX) is an advanced content architecture that unifies your digital experiences across platforms. Developed by inherent.design, it’s built on functional composition principles, enabling rich, interactive content that flows seamlessly between Node.js servers, browsers, and service workers through a unified type system and extensible middleware ecosystem.

Documentation Structure ​

This documentation is organized into the following main sections:

Core Documentation ​

• [TODO] Essentials: Essential knowledge for getting started
• Concepts: Detailed explanation of key concepts and principles
• Guides: Step-by-step guides for common tasks
• Reference: Complete API and type reference
• Patterns: Implementation patterns and recipes

Technical Documentation ​

• Architecture: Architectural decisions and system design
• [TODO] Examples: Code examples demonstrating various use cases
• [TODO] Testing: Testing strategies and patterns
• [TODO] Troubleshooting: Common issues and solutions

Project Documentation ​

• Project Management: Planning, tasks, and reviews
• Business: Business-focused documentation
• Templates: Documentation templates

Key Features ​

• Dynamic Composition: Create sophisticated behavior through functional composition and middleware patterns
• Universal Platform Support: Consistent experience across Node.js servers, browsers, and service workers
• Content Type Flexibility: Unified interfaces for various content formats with rich metadata support
• Extensible Architecture: Enhance capabilities through pluggable middleware and adapters
• Client-Server Harmony: Seamless type sharing between frontend and backend environments

Getting Started ​

New users should start with these resources:

1. [TODO] Key Concepts: Understand the fundamental concepts
2. [TODO] Getting Started Guide: Quick introduction to basic usage
3. Architecture Overview: Understand the system architecture

Current Development ​

The project is currently focused on:

1. Improving documentation organization and consistency
2. Standardizing the type system across all components
3. Refining architectural boundaries between system layers
4. Enhancing the developer experience with better examples and guides

For the latest development tasks, see the current task list.