This repository contains the official documentation for the DeployStack ecosystem. Visit deploystack.io to learn more about our platform.
Key directories in this repository:
.
├── docs/
│ ├── assets/
│ │ └── images/
│ ├── deploystack/
│ ├── docker-to-iac/
│ └── sidebar-links.json
└── markdown-rules/
- Store all documentation files in the
./docs
directory - Place images in
./docs/assets/images
- Use absolute links for all references:
- Documentation:
/docs/docker-to-iac/index.md
- Images:
/docs/assets/images/example.png
- Documentation:
When creating new documentation:
- Add new pages to the appropriate subdirectory in
./docs
- Follow the established file naming conventions
- Ensure all links are absolute paths
- Include necessary sidebar entries in
sidebar-links.json
For diagrams and architectural images (optional):
- Use draw.io for creating diagrams
- Export as PNG with included diagram data for future editing
- Place files in the appropriate subdirectory under
./docs/assets/images
If you want to upload images, please minify them.
Our deployment process uses two main branches:
main
: Development branchprod
: Production branch
- Create feature branches from
main
- Submit pull requests to
main
- After approval and merge to
main
, changes are automatically validated - Merge to
prod
to deploy to deploystack.io/docs
The CI pipeline includes:
- Markdown linting
- Link validation
- Automatic versioning using semantic release
- Production deployment triggers
# Install dependencies
npm ci
# Run markdown linting
npm run lint:md
# Check for dead links
npm run lint:links
Releases are managed automatically through our CI/CD pipeline. When merging to the production branch:
- Changes are validated
- Documentation is built
- Content is deployed to deploystack.io/docs
- 📚 Check our Documentation
- 🎯 Report issues on GitHub
- 📧 Use Discord to chat with us at https://discord.gg/UjFWwByB