Stip Documentation
Official documentation for the Stip product and platform
Welcome to STIP Documentation
This documentation provides comprehensive guides, procedures, and best practices for working with the STIP platform across all stages of development, staging, and production. Whether you're a developer building new features, a tester validating changes, or an operator managing production deployments, you'll find the information you need here.
Choose Your Environment
Select the documentation for your current workflow:
๐ Development (DEV)
Active development and feature creation. Includes setup guides, architecture documentation, APIs, and coding standards.
โ Staging
Pre-production validation and testing. Contains deployment procedures, test guidelines, and validation checklists.
๐ Production (PROD)
Live environment operations. Includes release procedures, runbooks, monitoring, and incident response.
Documentation Structure
Each environment contains:
- Overview & Goals: What the stage represents and what we aim to achieve
- Repositories: Documentation for specific code repositories and services
- User Manual: Guides for end-users and clients that are splitted by Technical and Non-Technical users
Quick Tips
Navigation: Use the left sidebar or environment tabs (DEV / STAGING / PROD) to switch between stages
New to STIP? Start with the Development section to understand our platform architecture and setup your environment
Making changes? Always follow the contribution guidelines for your environment to keep documentation accurate and helpful
Documentation Guidelines
These guidelines apply across all environments and stages:
Writing Documentation
- Clear Index: Always write a clear documentation index that describes and provides an overview of the repository
- Essential Pages: Create the following standard pages:
- Quick Start: Step-by-step guide for getting started
- Changelog: Record of all significant updates and changes
- Alerts: Use alerts to highlight TODOs, limitations, and known issues
- Organization: Group documentation into meaningful sections
- Avoid Repetition: Reduce duplication by not describing the same feature in multiple pages
- MDX Format: Follow the Fumadocs Markdown Guide for all MDX files
Best Practices
- Use clear, concise language appropriate for your audience
- Include code examples where applicable
- Maintain consistent formatting and structure
- Keep documentation up-to-date with code changes
- Use diagrams and visual aids to explain complex concepts
- Link related documentation together
File Structure
Each documentation directory must contain:
- MDX Files: Content pages (markdown with JSX components)
- Directories: Subfolders for organizing related topics
- meta.json: Navigation metadata with the following structure:
{ "title": "Section Title", "pages": [ "index", "page-name", "subdirectory" ] }