OQO Documentation
Welcome to the OQO documentation -- the community publishing platform with AI-powered editorial review and a Shopify-style theme engine.
What is OQO?
OQO is a publishing platform built for organizations where multiple contributors create content under a shared brand -- sports clubs where members share stories and event recaps, non-profits where volunteers contribute articles, educational institutions with student and faculty authors, or media outlets with freelance contributors.
The Problem
Most platforms assume a single author or a small editorial team. When organizations need community-driven publishing, they face a difficult choice:
- Traditional CMS (WordPress, Ghost) -- designed for one author or a small team. Adding contributors means complex role plugins, no structured submission workflow, and no editorial quality control at scale.
- Community platforms (Circle, Discourse) -- built for discussions, not polished articles. Content lives in forum threads, not in a professionally designed website.
- Enterprise CMS (HubSpot, WordPress VIP) -- per-seat pricing makes scaling to dozens of contributors expensive. Workflows exist but are heavyweight and admin-centric.
- Headless CMS (Strapi, Craft) -- powerful but require a frontend team. Contributors need developer hand-holding to publish.
None of these give contributors a dedicated authoring experience while giving editors automated quality control.
How OQO Solves It
OQO separates the contributor experience from the editorial workflow:
For contributors (bloggers): A dedicated dashboard where they create content with a drag-and-drop editor, manage drafts, and submit for review. No admin access needed -- bloggers see only what they need to write and publish.
For editors (admins): An AI-powered review system that automatically evaluates submissions for quality, tone, and brand alignment. Bloggers interact directly with the AI reviewer and receive actionable feedback -- revise-and-resubmit suggestions, not just approve/reject. The AI handles routine approvals and flags edge cases for human review, so editorial oversight scales without scaling headcount.
For designers (theme developers): A full Liquid template engine inspired by Shopify's theme architecture. Themes are self-contained packages with layouts, sections, snippets, and settings. Build with any CSS framework, customize everything through a JSON schema, and preview changes live.
Core Capabilities
| Capability | Description |
|---|---|
| Blogger Dashboard | Dedicated authoring interface with drag-and-drop content blocks, draft management, and submission workflow |
| AI Editorial Review | Automated first-pass review that evaluates quality, tone, and guidelines -- approves routine submissions, escalates edge cases |
| Liquid Theme Engine | Shopify-style templates with sections, settings schemas, and CSS hot-reload in the visual editor |
| Visual Editor | Live preview with drag-and-drop section management, real-time settings changes, and instant CSS updates |
Documentation
For Site Administrators
Learn how to manage your site in the Getting Started guide.
For Bloggers
Invited to contribute? Start with the Blogger Onboarding guide.
For Theme Developers
Build custom themes with our comprehensive Theme Development documentation:
- OQO CLI -- Local development with live sync and AI section creation
- Theme Structure -- File organization and conventions
- Settings System -- Configurable theme and section options
- Sections -- The building blocks of OQO pages
- Layouts -- Page structure, zones, and layout inheritance
- Liquid Tags -- Custom Liquid tags
- Liquid Filters -- Custom Liquid filters
- Liquid Objects -- Available data objects
- CSS Architecture -- Theme styling and compilation
- Routing -- URL structure and page resolution
- Live Preview -- Real-time editing support