AGENTS.md β Documentation (VitePress) β
Overview β
Public documentation site built with VitePress. Hosted at https://minepanel.ketbome.lat
Port: 5173 (dev)
File Structure β
doc/
βββ index.md # Homepage (hero, features)
βββ getting-started.md # Quick start guide
βββ installation.md # Detailed installation
βββ configuration.md # Environment variables
βββ server-types.md # Vanilla, Paper, Forge, etc.
βββ features.md # UI features overview
βββ administration.md # Server management
βββ mods-plugins.md # Mod/plugin installation
βββ networking.md # Ports, reverse proxy
βββ architecture.md # Technical details
βββ development.md # Contributing guide
βββ troubleshooting.md # Common issues
βββ faq.md # Frequently asked
βββ roadmap.md # Planned features
βββ public/
βββ img/ # Screenshots and diagramsWriting Style β
Tone β
- Direct and practical β No fluff, get to the point
- Second person β "You can...", "Run this command..."
- Casual but professional β Like explaining to a colleague
markdown
<!-- β
GOOD -->
Create a `docker-compose.yml` file and run:
<!-- β BAD -->
In order to proceed with the installation process, you will first need to create a Docker Compose configuration file...Structure β
- Start with what, then how
- Use code blocks for commands
- Add tips/warnings with VitePress containers:
markdown
::: tip
Quick helpful hint
:::
::: warning
Something to watch out for
:::
::: danger
This can break things
:::Code Blocks β
Always specify language:
markdown
```bash
docker compose up -d
```yaml
version: "3.8"
services:
minepanel:
image: ketbom/minepanel
---
## When to Update Documentation
### ALWAYS update docs when:
| Code Change | Update In |
|-------------|-----------|
| New feature added | `features.md` + relevant page |
| New env variable | `configuration.md` |
| New server type supported | `server-types.md` |
| API endpoint changed | `architecture.md` |
| New UI functionality | Add screenshot to `public/img/` |
| Bug fix for common issue | `troubleshooting.md` |
| Installation steps changed | `installation.md`, `getting-started.md` |
### Screenshots
- Format: PNG
- Location: `public/img/`
- Naming: `{feature}-{description}.png` (e.g., `server-creation.png`)
- Keep file size reasonable (<500KB)
---
## Commands
```bash
cd doc
npm run docs:dev # Dev server at localhost:5173
npm run docs:build # Build static site
npm run docs:preview # Preview buildAdding New Page β
- Create
{page-name}.mdindoc/ - Add frontmatter:
markdown
---
title: Page Title
description: Brief description for SEO
---
# Page Title
Content here...- Add to sidebar in
.vitepress/config.js(if exists) or it auto-generates
Sync Checklist β
When making significant code changes, check:
- [ ]
getting-started.mdβ Still accurate? - [ ]
configuration.mdβ All env vars documented? - [ ]
features.mdβ New features mentioned? - [ ]
troubleshooting.mdβ Known issues updated? - [ ]
index.mdβ "Coming soon" section current? - [ ] Screenshots β Still match current UI?
Anti-patterns β
markdown
<!-- β Outdated screenshots -->

<!-- β Vague instructions -->
Configure the settings as needed.
<!-- β Missing code language -->docker compose up
<!-- β Wall of text without structure -->
First you need to install Docker and then you can...
<!-- β
Use headings, lists, code blocks -->