Skip to content

Commit 8ef7b9f

Browse files
authored
Merge pull request #264 from deploystackio/feat/mintlify
Feat/mintlify
2 parents 519cad9 + 3b478ba commit 8ef7b9f

File tree

144 files changed

+5620
-15778
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

144 files changed

+5620
-15778
lines changed

β€Ž.github/workflows/_deploy_prod.yml_β€Ž

Lines changed: 0 additions & 27 deletions
This file was deleted.

β€Ž.github/workflows/ci.ymlβ€Ž

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -34,10 +34,7 @@ jobs:
3434
run: npm run lint:md
3535

3636
- name: Run Lint Links
37-
run: npm run lint:links
38-
39-
- name: Run Lint Links
40-
run: npm run build
37+
run: npm run lint:links
4138

4239
release:
4340
name: Run Release

β€ŽREADME.mdβ€Ž

Lines changed: 218 additions & 82 deletions
Original file line numberDiff line numberDiff line change
@@ -1,128 +1,264 @@
11
# DeployStack Documentation
22

3-
This repository contains the official documentation site for [DeployStack](https://deploystack.io/docs/), The Complete MCP Management Platform, built with [fumadocs](https://fumadocs.vercel.app/). Visit [deploystack.io](https://deploystack.io) to learn more about our platform.
3+
This repository contains the official documentation for [DeployStack](https://docs.deploystack.io/) - The First MCP-as-a-Service Platform. Built with [Mintlify](https://mintlify.com), our documentation provides a modern, searchable experience for developers building with DeployStack's satellite infrastructure.
4+
5+
Visit [docs.deploystack.io](https://docs.deploystack.io) to explore the live documentation.
46

57
## Technology Stack
68

7-
- **Framework**: Next.js 15 with App Router
8-
- **Documentation**: Fumadocs for modern docs experience
9+
- **Documentation Platform**: Mintlify
910
- **Content**: MDX (Markdown + React components)
10-
- **Styling**: Tailwind CSS
11-
- **Language**: TypeScript
11+
- **Deployment**: Automatic deployment via Mintlify platform
1212

1313
## Project Structure
1414

1515
```text
1616
.
17-
β”œβ”€β”€ docs/ # Documentation content (MDX files)
18-
β”‚ β”œβ”€β”€ development/ # Development documentation
19-
β”‚ β”‚ β”œβ”€β”€ backend/ # Backend development guides
20-
β”‚ β”‚ β”œβ”€β”€ frontend/ # Frontend development guides
21-
β”‚ β”‚ └── gateway/ # Gateway architecture & implementation
22-
β”‚ β”œβ”€β”€ self-hosted/ # Self-hosting guides
23-
β”‚ β”œβ”€β”€ deploystack/ # Core DeployStack documentation
24-
β”‚ β”œβ”€β”€ assets/ # Images and static assets
25-
β”‚ └── ... # MCP guides and configuration docs
26-
β”œβ”€β”€ app/ # Next.js app directory (fumadocs framework)
27-
β”œβ”€β”€ lib/ # Documentation utilities & components
28-
└── source.config.ts # Fumadocs configuration
17+
β”œβ”€β”€ general/ # Getting started and core concepts
18+
β”‚ β”œβ”€β”€ architecture.mdx # System architecture overview
19+
β”‚ β”œβ”€β”€ teams.mdx # Team management
20+
β”‚ β”œβ”€β”€ roles.mdx # Role-based access control
21+
β”‚ └── mcp-*.mdx # MCP server guides
22+
β”œβ”€β”€ self-hosted/ # Self-hosting guides
23+
β”‚ β”œβ”€β”€ quick-start.mdx # Quick start guide
24+
β”‚ β”œβ”€β”€ setup.mdx # Installation instructions
25+
β”‚ └── docker-compose.mdx # Docker deployment
26+
β”œβ”€β”€ development/ # Development documentation
27+
β”‚ β”œβ”€β”€ frontend/ # Frontend development guides
28+
β”‚ β”‚ β”œβ”€β”€ index.mdx # Frontend overview
29+
β”‚ β”‚ β”œβ”€β”€ ui/ # UI system documentation
30+
β”‚ β”‚ └── ...
31+
β”‚ β”œβ”€β”€ backend/ # Backend development guides
32+
β”‚ β”‚ β”œβ”€β”€ index.mdx # Backend overview
33+
β”‚ β”‚ β”œβ”€β”€ api/ # API documentation
34+
β”‚ β”‚ β”œβ”€β”€ database/ # Database guides
35+
β”‚ β”‚ └── ...
36+
β”‚ └── satellite/ # Satellite development guides
37+
β”‚ β”œβ”€β”€ index.mdx # Satellite overview
38+
β”‚ β”œβ”€β”€ architecture.mdx
39+
β”‚ └── ...
40+
β”œβ”€β”€ assets/ # Images and static assets
41+
β”‚ └── images/
42+
β”‚ β”œβ”€β”€ logo/ # Logo files
43+
β”‚ └── ...
44+
β”œβ”€β”€ docs.json # Mintlify configuration
45+
β”œβ”€β”€ index.mdx # Documentation home page
46+
└── README.md # This file
2947
```
3048

31-
**Note**: The `app/` directory contains the fumadocs framework setup and should not be modified for content changes. All documentation content goes in the `docs/` directory.
49+
## Local Development
3250

33-
## Development Setup
51+
Mintlify provides a local development CLI for previewing documentation changes:
3452

3553
```bash
36-
# Install dependencies
37-
npm ci
54+
# Install Mintlify CLI globally (one-time setup)
55+
npm install -g mintlify
56+
57+
# Start local development server
58+
mintlify dev
59+
60+
# The documentation will be available at http://localhost:3000
61+
```
62+
63+
The local server provides:
64+
- Hot reloading for instant content updates
65+
- Navigation preview
66+
- Component rendering
67+
- Dark/light mode testing
68+
69+
## Writing Documentation
70+
71+
### Content Format
72+
73+
All documentation is written in **MDX** (Markdown with JSX components):
3874

39-
# Start documentation development server (http://localhost:3000)
40-
npm run dev
75+
```mdx
76+
---
77+
title: Your Page Title
78+
description: A brief description of the page content
79+
---
4180

42-
# Build documentation site for production
43-
npm run build
81+
# Your Page Title
4482

45-
# Start production server
46-
npm run start
83+
Write your content here using standard Markdown syntax.
4784

48-
# Validate documentation quality
49-
npm run lint:md # Markdown linting
50-
npm run lint:links # Link validation
85+
<Info>
86+
Use Mintlify components for callouts and special content blocks.
87+
</Info>
88+
89+
## Section Header
90+
91+
More content here...
5192
```
5293

53-
## Contributing Guidelines
94+
### Mintlify Components
5495

55-
### Writing Documentation
96+
Mintlify provides built-in components for enhanced documentation:
5697

57-
1. **Content Format**: Write all documentation in MDX format (`.mdx` files)
58-
2. **Location**: Store all content in the `docs/` directory
59-
3. **Navigation**: Use `meta.json` files in each directory to control navigation structure
60-
4. **Assets**: Place images in `docs/assets/images/` with appropriate subdirectories
61-
5. **Links**: Use absolute paths for all references:
62-
- Documentation: `/docs/development/gateway/`
63-
- Images: `/docs/assets/images/example.png`
64-
6. **Brand Colors**: Use the primary color (`text-primary`, `bg-primary`) for consistency - avoid introducing other accent colors
98+
**Callouts:**
99+
```mdx
100+
<Note>General information</Note>
101+
<Info>Important information</Info>
102+
<Tip>Helpful tips</Tip>
103+
<Warning>Important warnings</Warning>
104+
<Check>Success status</Check>
105+
<Danger>Critical warnings</Danger>
106+
```
65107

66-
### Navigation Structure
108+
**Code Groups:**
109+
```mdx
110+
<CodeGroup>
111+
```bash macOS/Linux
112+
npm install
113+
```
67114

68-
Fumadocs automatically generates navigation from your file structure and `meta.json` files:
115+
```powershell Windows
116+
npm install
117+
```
118+
</CodeGroup>
119+
```
69120

70-
- Each directory can have a `meta.json` file to configure its appearance in navigation
71-
- File-based routing: `docs/deploystack/index.mdx` becomes `/docs/deploystack`
72-
- Nested directories create hierarchical navigation
121+
**Cards:**
122+
```mdx
123+
<CardGroup cols={2}>
124+
<Card title="Getting Started" icon="rocket" href="/general/quick-start">
125+
Begin your DeployStack journey
126+
</Card>
127+
<Card title="API Reference" icon="code" href="/development/backend/api">
128+
Explore the API documentation
129+
</Card>
130+
</CardGroup>
131+
```
73132

74-
### Adding New Content
133+
**Steps:**
134+
```mdx
135+
<Steps>
136+
<Step title="Install Dependencies">
137+
Run `npm install` to install required packages
138+
</Step>
139+
<Step title="Configure Environment">
140+
Set up your environment variables
141+
</Step>
142+
<Step title="Start Development">
143+
Run `npm run dev` to start the development server
144+
</Step>
145+
</Steps>
146+
```
75147

76-
1. Create new `.mdx` files in the appropriate `docs/` subdirectory
77-
2. Add or update `meta.json` files to control navigation
78-
3. Follow established naming conventions
79-
4. Ensure all links use absolute paths
80-
5. Test locally with `npm run dev`
148+
### Navigation Configuration
81149

82-
### Asset Management
150+
Navigation is controlled via `docs.json`:
83151

84-
For diagrams and images:
152+
- **Tabs**: Top-level navigation sections (General, Self Hosted, Frontend Development, etc.)
153+
- **Groups**: Subsections within each tab
154+
- **Pages**: Individual documentation pages
85155

86-
1. Use [drow.io](https://app.diagrams.net/) for creating diagrams
87-
2. Export as PNG or WebP format
88-
3. Optimize images for web (compress file sizes)
89-
4. Place files in appropriate subdirectories under `docs/assets/images/`
156+
To add a new page:
157+
1. Create the `.mdx` file in the appropriate directory
158+
2. Add the page path to `docs.json` under the relevant group
159+
3. Test locally with `mintlify dev`
90160

91-
## Deployment Process
161+
### Content Guidelines
92162

93-
Our deployment uses a two-branch workflow:
163+
**File Naming:**
164+
- Use kebab-case: `my-new-page.mdx`
165+
- Index files represent the directory: `index.mdx`
94166

95-
- **`main`**: Development branch for content updates and testing
96-
- **`prod`**: Production branch that deploys to [deploystack.io/docs](https://deploystack.io/docs)
167+
**Links:**
168+
- Use absolute paths from documentation root: `/development/backend/api/index`
169+
- Mintlify automatically handles `.mdx` extensions
170+
171+
**Images:**
172+
- Store in `assets/images/` with logical subdirectories
173+
- Reference with absolute paths: `/assets/images/logo/dark.webp`
174+
- Optimize images before committing (compress file sizes)
175+
176+
**Frontmatter:**
177+
```yaml
178+
---
179+
title: Page Title (required)
180+
description: Page description for SEO (required)
181+
---
182+
```
183+
184+
## Asset Management
185+
186+
### Images and Diagrams
187+
188+
1. **Diagrams**: Create with [draw.io](https://app.diagrams.net/)
189+
2. **Export Format**: PNG or WebP
190+
3. **Optimization**: Compress images before committing
191+
4. **Location**: Store in `assets/images/` with appropriate subdirectories
192+
193+
## Contributing Guidelines
97194

98195
### Workflow
99196

100-
1. Create feature branches from `main`
101-
2. Submit pull requests to `main`
102-
3. After approval and merge to `main`, changes are automatically validated
103-
4. Merge to `prod` to deploy to production
197+
1. **Fork or Branch**: Create a feature branch from `main`
198+
2. **Write Content**: Add or update documentation in MDX format
199+
3. **Test Locally**: Run `mintlify dev` to preview changes
200+
4. **Submit PR**: Create a pull request to `main` branch
201+
5. **Review**: Wait for review and address feedback
202+
6. **Merge**: Changes are automatically deployed after merge
104203

105-
### Continuous Integration
204+
### Pull Request Guidelines
106205

107-
The CI pipeline includes:
206+
- Write clear commit messages
207+
- Test all links and navigation
208+
- Verify code examples are correct
209+
- Check for spelling and grammar
210+
- Ensure images load correctly
211+
- Preview on mobile and desktop layouts
108212

109-
- Markdown linting and validation
110-
- Link checking to prevent broken links
111-
- Automatic fumadocs build verification
112-
- Production deployment triggers
213+
### Documentation Standards
113214

114-
## Local Development
215+
**Writing Style:**
216+
- Write in clear, concise language
217+
- Use active voice
218+
- Address the reader directly ("you")
219+
- Avoid jargon without explanation
220+
- Include code examples where helpful
221+
222+
**Code Examples:**
223+
- Include complete, working examples
224+
- Add comments for clarity
225+
- Show expected output when relevant
226+
- Test all code before committing
227+
228+
**Structure:**
229+
- Start with overview/introduction
230+
- Progress from basic to advanced
231+
- Use descriptive section headers
232+
- Include related documentation links at the end
233+
234+
## Deployment
235+
236+
### Automatic Deployment
237+
238+
Mintlify automatically deploys documentation when changes are merged to `main`:
239+
240+
- **Trigger**: Push or merge to `main` branch
241+
- **Build**: Mintlify builds the documentation
242+
- **Deploy**: Changes go live at docs.deploystack.io
243+
- **CDN**: Content served via Mintlify's global CDN
244+
245+
### Branch Strategy
246+
247+
- **`main`**: Production branch that deploys to docs.deploystack.io
248+
- **Feature Branches**: Create from `main` for new content or updates
249+
- **Pull Requests**: All changes must go through PR review
115250

116-
When running `npm run dev`, the documentation site will be available at `http://localhost:3000`. The fumadocs framework provides:
251+
## Need Help?
117252

118-
- Hot reloading for content changes
119-
- Automatic navigation generation
120-
- Built-in search functionality
121-
- Responsive design
122-
- Dark/light mode support
253+
- πŸ“š **Documentation**: [docs.deploystack.io](https://docs.deploystack.io)
254+
- πŸ’¬ **Discord**: [Join our community](https://discord.gg/42Ce3S7b3b)
255+
- πŸ› **Issues**: [GitHub Issues](https://github.com/deploystackio/documentation/issues)
256+
- 🌐 **Website**: [deploystack.io](https://deploystack.io)
257+
- πŸš€ **Dashboard**: [cloud.deploystack.io](https://cloud.deploystack.io)
123258

124-
## πŸ’¬ Need Help?
259+
## Links
125260

126-
- πŸ“š Check our [Documentation](https://deploystack.io/docs)
127-
- 🎯 Report issues on [GitHub](https://github.com/deploystackio/documentation/issues)
128-
- πŸ“§ Join our Discord at [https://discord.gg/UjFWwByB](https://discord.gg/UjFWwByB)
261+
- [Mintlify Documentation](https://mintlify.com/docs)
262+
- [MDX Documentation](https://mdxjs.com/)
263+
- [DeployStack Main Repository](https://github.com/deploystackio/deploystack)
264+
- [DeployStack Changelog](https://deploystack.io/changelog)

0 commit comments

Comments
Β (0)