Contributing to the Wiki
How to add and update content in the Veritect AI wiki.
Quick Start - For Everyone
Method 1: Edit on GitHub (Easiest)
- Navigate to any page on the wiki
- Click "Edit this page" at the bottom
- You'll be taken to GitHub
- Click the pencil icon to edit
- Make your changes
- Click "Commit changes"
- Add a description and submit
Method 2: GitHub Web Interface
- Go to github.com/veritect-ai/wiki
- Navigate to
docs/folder - Find your file or create new one
- Click pencil icon or "Create new file"
- Write in Markdown
- Preview your changes
- Commit with description
For Developers - Local Setup
Prerequisites
- VS Code (recommended)
- Node.js 18+
- Git
Setup Steps
# Clone the repository
git clone https://github.com/veritect-ai/wiki.git
cd wiki
# Install dependencies
npm install
# Start local development server
npm start
Your wiki will be available at http://localhost:3000
VS Code Extensions
Install these for better experience:
- Markdown All in One - Shortcuts and preview
- Markdownlint - Style checking
- Prettier - Auto-formatting
Writing Guidelines
File Naming
- Use lowercase with hyphens:
user-guide.md - No spaces in filenames
- Descriptive names
Markdown Basics
# Heading 1
## Heading 2
### Heading 3
**Bold text**
*Italic text*
`inline code`
- Bullet point
- Another point
- Nested point
1. Numbered list
2. Second item
[Link text](https://example.com)

```code block
with syntax highlighting
### Frontmatter
Every doc should start with:
```yaml
---
sidebar_position: 1
title: Page Title
description: Brief description
---
Adding Images
- Save images to
/static/img/ - Reference as:
 - Use descriptive filenames
Creating New Sections
To add a new section:
- Create a folder in
docs/ - Add
_category_.json:
{
"label": "Section Name",
"position": 5,
"link": {
"type": "generated-index",
"description": "Section description"
}
}
- Add your
.mdfiles
Best Practices
Do's ✅
- Write clear, concise content
- Use headers for structure
- Include examples
- Add links to related pages
- Update regularly
Don'ts ❌
- Don't commit sensitive information
- Avoid large images (>1MB)
- No personal credentials
- Don't break existing links
Review Process
- Self Review: Check preview before committing
- Peer Review: Tag a colleague for review
- Merge: Once approved, changes go live
Getting Help
- Slack: #wiki-help
- Issues: GitHub Issues for bugs
- Training: Monthly wiki training sessions
Quick Commands
# See your changes
git status
# Stage changes
git add .
# Commit with message
git commit -m "Update user guide"
# Push to GitHub
git push
# Pull latest changes
git pull
Tips for Non-Technical Users
- Use GitHub's web editor - No setup needed
- Copy existing pages as templates
- Ask for help - We're here to support you
- Start small - Edit existing content first
- Preview often - Check how it looks
Remember: You can't break anything! Git keeps all history, so we can always revert changes if needed.