Guides new users through getting started with Meldoc. Use when a user is new to Meldoc, first time using the MCP integration, learning to navigate documentation, understanding basic concepts, or setting up documentation workflows.
Your friendly guide to getting started with Meldoc and mastering documentation workflows.
When a user first interacts with Meldoc:
👋 Welcome to Meldoc!
I can help you work with your documentation. Here's what I can do:
📖 **Read & Search**
- Find specific documents
- Search across all your docs
- Navigate document structures
✍️ **Create & Edit**
- Write new documentation
- Update existing documents
- Organize content hierarchically
🔗 **Discover Connections**
- Find related documents
- See what links where
- Explore document relationships
Would you like to:
1. 📚 Take a quick tour of your documentation
2. 🔍 Search for something specific
3. ✏️ Create new documentation
4. ❓ Learn about Meldoc features
Help users get oriented:
## Getting Started Checklist
Let's make sure you're all set up:
- [x] ✅ Connected to Meldoc (you're authenticated!)
- [ ] 📁 Choose your workspace
- [ ] 📋 Explore your projects
- [ ] 📄 View some documents
- [ ] 🔍 Try a search
- [ ] ✏️ Create your first document
**Current Status:**
- Workspace: {workspace_name}
- Projects: {project_count}
- Documents: {document_count}
What would you like to explore first?
Help users understand their workspace:
// 1. Show workspace info
const workspace = await get_workspace();
const projects = await projects_list();
// 2. Present overview
## Your Workspace: {workspace.name}
You have access to **{projects.length}** projects:
{projects.map(p => `
### ${p.name}
- ${p.documentCount} documents
- Last updated: ${p.lastUpdated}
`).join('\n')}
**Where to start:**
- 🌟 Most active project: {mostActive.name}
- 📈 Recently updated: {recentlyUpdated.name}
- 📚 Largest documentation: {largest.name}
Which project would you like to explore?
Show how docs are organized:
// 1. Pick a representative project
const project = await suggestGoodStartingProject();
// 2. Get its structure
const tree = await docs_tree({ projectId: project.id });
// 3. Explain the structure
## How Your Documentation is Organized
Here's the structure of **{project.name}**:
📁 {project.name} ├─ 📄 Getting Started │ ├─ 📄 Installation │ └─ 📄 Quick Start ├─ 📄 User Guide │ ├─ 📄 Basic Features │ └─ 📄 Advanced Features └─ 📄 API Reference ├─ 📄 Authentication └─ 📄 Endpoints
**Understanding the structure:**
- 📁 **Projects** organize related documentation
- 📄 **Documents** can have parent-child relationships
- 🔗 **Links** connect related topics across documents (use `[[alias]]` format)
**Try it yourself:**
- "Show me the Getting Started guide"
- "What's in the User Guide?"
- "Find all API documentation"
Teach search capabilities:
## Let's Try Searching! 🔍
Meldoc can search through all your documentation instantly.
**What to search for:**
- Specific features: "authentication", "deployment"
- Error messages: "connection timeout", "404 error"
- Concepts: "best practices", "architecture"
- Code examples: "python example", "API call"
**Try asking:**
- "Find documentation about authentication"
- "Search for deployment guides"
- "Show me code examples"
**What would you like to search for?**
After first search:
## Great! Here's what I found:
{search_results}
**Search tips:**
✅ Use specific technical terms
✅ Include 2-3 keywords for best results
✅ Try variations if you don't find what you need
❌ Avoid very broad single words
**Next steps:**
- Click any document to read it
- Ask me to "explain {topic}" for a summary
- Search for related topics
Guide through creating a doc:
## Let's Create Your First Document! ✏️
I'll help you create a well-structured document with proper Meldoc format.
**First, let me ask a few questions:**
1. **What's the topic?**
(e.g., "API Authentication Guide", "Deployment Process")
2. **Who is it for?**
- [ ] Developers
- [ ] End users
- [ ] Administrators
- [ ] General audience
3. **What type of document?**
- [ ] Tutorial (step-by-step)
- [ ] Reference (technical details)
- [ ] Guide (conceptual explanation)
- [ ] How-to (specific task)
Based on your answers, I'll create a structured outline with proper frontmatter!
After getting answers:
## Perfect! Here's what I'll create:
**Title:** {title}
**Type:** {type}
**Audience:** {audience}
**Suggested structure:**
```markdown
---