| title | Contributing Guide | ||||
|---|---|---|---|---|---|
| description | How to contribute to the SmythOS docs project. | ||||
| keywords |
|
Thank you for helping make SmythOS documentation better!
We welcome all contributsions: whether you’re fixing a typo, adding a new guide, or sharing feedback, every contribution counts.
- Fix typos, unclear language, or broken formatting
- Add new examples, visuals, or code snippets
- Create or suggest new pages and guides
- Report outdated information or bugs in the docs
- Improve structure, navigation, or accessibility
- Fork the repo on GitHub and clone it locally
gh repo clone SmythOS/smyth-docs - Install dependencies
npm install - Start the local dev server
npm run start
- Follow the Style Guide
- Use
.mdxfor all docs pages - Always include frontmatter at the top:
---
title: Page Title
description: Short summary
keywords: [keyword1, keyword2]
sidebar_position: 1
---- Break content into clear sections
- Use InfoCallout, TipCallout, or WarningCallout where helpful
- Keep code samples working, and always use
<codeblock>for code - Keep language consistent with existing docs
- Create a new branch
git checkout -b update-page-title - Make your edits
- Commit with a clear message
git commit -m "docs: improved Data Pool page structure" - Push and open a pull request to
mainon GitHub, describing what you changed
- All pull requests are reviewed by a maintainer (currently Umar)
- We check for clarity, technical accuracy, and a user-focused style
- You may get feedback or requests for changes before merging
- PRs are usually reviewed within 1–3 days
- Ask in our Discord community
-
- For bug reports or feature requests, open an issue on GitHub.
Thanks again for making SmythOS docs better!