What it is

QOR is a set of libraries written in Go that abstracts the common features needed for business applications, content management systems, and e-commerce systems. It lives in the Go ecosystem and is published under the MIT license. The project is a complete rewrite in Go of the original QOR, which was a proprietary framework written in Ruby on Rails and used internally at The Plant, and version 1.0 is the first release to be open sourced.

The concrete problem it solves is the repeated plumbing work that appears in nearly every commerce or CMS build: an administrative interface for managing data, a review stage before content goes live, order and payment states, asset storage, scheduled batch jobs, import and export of business data, translations, per-locale models, and access control. Rather than leaving each team to write those pieces again, QOR collects them as separate modules that a developer wires into a Go application. The README is explicit that QOR is not a boxed turnkey solution, so proper coding skills are required to use it.

Key capabilities

• Admin generates an admin interface and a RESTful API for managing application data, and forms the core of the system.
• Publish provides a staging environment where content changes are reviewed before being pushed to the live system.
• Transition is a configurable state machine for defining states, events such as paying an order, and validation constraints on state transitions.
• Media Library handles asset management with support for several cloud storage backends and publishing through a CDN.
• Worker provides batch processing in the form of a process scheduler.
• Exchange moves data to and from other business applications using CSV or Excel files.
• Internationalization and Localization cover translation management with inline editing, plus DB-backed models handled per locale with locale-based querying, while Roles supplies access control.

Who uses it and how

• Teams building custom e-commerce or CMS backends in Go, where the admin module supplies the management interface and RESTful API over their own models.
• Editorial workflows that use Publish so that all content changes are staged and reviewed before reaching the live site.
• Order and payment flows modeled with

npm install && npm install -g gulp