Oreon Community Wiki
  • JavaScript 82.7%
  • CSS 17.3%
Find a file
Brandon L 5c0f0986fe
Merge pull request #29 from oreonhq/feat/new-docs-and-fixes
add spec troubleshooting guide, update pr guide, and fix SEO/sitemap …
2026-11-17 23:35:23 -08:00
.github chore: delete workflows 2026-06-08 12:55:35 -07:00
docs Merge pull request #29 from oreonhq/feat/new-docs-and-fixes 2026-11-17 23:35:23 -08:00
src revamp homepage and move packaging docs to dedicated section 2026-11-09 15:14:13 -08:00
static Merge pull request #29 from oreonhq/feat/new-docs-and-fixes 2026-11-17 23:35:23 -08:00
.gitignore initial commit 2025-07-15 14:24:59 -07:00
docusaurus.config.js Merge pull request #29 from oreonhq/feat/new-docs-and-fixes 2026-11-17 23:35:23 -08:00
package-lock.json initial commit 2025-07-15 14:24:59 -07:00
package.json push updated docs and policies 2026-11-16 01:12:35 -08:00
README.md change some branding-related things and add spanish and hindi 2026-02-19 17:39:13 -08:00
sidebars.js initial commit 2025-07-15 14:24:59 -07:00

Oreon Wiki

This is the community-driven wiki for the Oreon HQ, built using Docusaurus.

Writing Documentation

Folder Structure

All documentation pages should be placed in the appropriate subfolder within docs/:

  • docs/Basics/ - Fundamental concepts, installation guides, and getting started information
  • docs/Guides/ - Step-by-step tutorials, how-to guides, and practical examples
  • docs/Information/ - Reference materials, API documentation, and detailed technical information

Creating New Pages

  1. Create a new .md or .mdx file in the appropriate folder
  2. Add frontmatter at the top of your file:
    ---
    sidebar_position: 1
    title: "Your Page Title"
    ---
    
  3. Write your content using standard Markdown
  4. The page will automatically appear in the sidebar

Markdown Guidelines

  • Use clear, descriptive headings with #, ##, ### etc.
  • Include code examples in proper code blocks with syntax highlighting
  • Use relative links to other wiki pages: [Link Text](../other-page)
  • Link to external resources when helpful
  • Keep content organized with proper heading hierarchy

Contributing Guidelines

  1. Fork the repository
  2. Create a new branch for your changes
  3. Add or edit documentation in the appropriate docs/ subfolder
  4. Test your changes locally (see Development section below)
  5. Submit a pull request with a clear description of your changes

Content Standards

  • Write for your audience - assume basic familiarity with development concepts
  • Provide working code examples when possible
  • Include troubleshooting sections for common issues
  • Keep content up-to-date with current Oreon versions
  • Cross-reference the official documentation when appropriate

Development

Installation

npm install

Local Development

npm start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

npm build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

Using SSH:

USE_SSH=true npm deploy

Not using SSH:

GIT_USER=<Your GitHub username> npm deploy

If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.

Project Structure

docs/
├── basics/          # Fundamental concepts and getting started
├── guides/          # Tutorials and how-to guides  
├── information/     # Reference and technical documentation
└── intro.md         # Wiki homepage

src/
├── css/            # Custom styling
└── pages/          # Custom pages (auto-redirects to docs)

static/
└── img/            # Images and assets