JakuninOleg

OJ CMS / CONTENT MANAGEMENT

Your website should stay easy to update

OJ CMS is my Payload-based system for teams managing a website. At KEMZ it already manages the catalog, news and documents, stores inquiries and displays Yandex Metrika analytics. I tailor sections, fields and permissions to each business.

The demo is hosted on Vercel and may require a VPN on some networks. Changes stay in your browser only; it is not connected to your website.

OJ / CONTENT SYSTEMMascot working with content in OJ CMS

01 / FOR YOUR TEAM

Update content without a developer queue

Editors need clear actions and a visible result. OJ CMS follows the work of maintaining a website:

Mascot guiding content through the OJ CMS workflow
01

Pages

Edit headings, copy, images and SEO descriptions in one place.

02

News

Prepare posts and keep new material in its own section.

03

Media

Upload images, add descriptions and find files in the library.

04

Drafts and preview

Save a change, inspect the page and publish with a separate action.

05

Settings

Update contact details, the site name and navigation without editing code.

02 / EDITORIAL FLOW

Three steps from edit to publish

These are real screens from the OJ CMS demo. Open it and try the same workflow.

01

Find the material

The dashboard shows sections and recent changes.

Sections and recent changes in the OJ CMS demo
OJ CMS / 01
02

Make an edit

Save a draft and get a warning before leaving with unsaved changes.

Page editing in the OJ CMS demo
OJ CMS / 02
03

Check the media

Images live in a library, and a file used by a page cannot be deleted accidentally.

Media library in the OJ CMS demo
OJ CMS / 03
Try the demo

03 / TECHNOLOGY

How OJ CMS and Payload fit together

Payload is an open-source CMS providing server storage, APIs and access rules. OJ CMS builds on it with my own interface, dashboard and team-specific workflows. At KEMZ this setup already handles the catalog, inquiries and Yandex Metrika. The separate browser demo shows the editing workflow without access to factory data.

Explore Payload documentation
PAYLOADAPI → WEBSITE
01

Payload foundation

Open-source collections and fields model pages, posts, products and other content.

02

OJ CMS layer

I design a focused editor on top: quick access to content, drafts, preview and safeguards against accidental changes.

03

Roles and versions

A live implementation defines staff access and publishing rules; Payload supports versions and drafts.

04

Site integration

Published content reaches the bespoke public website through an API.

OJ CMS / LIVE AT KEMZ

Catalog, inquiries and analytics in one dashboard

For the KEMZ website on Next.js and React, I integrated Payload and adapted OJ CMS to the factory’s workflows. These are actual implementation screens.

Live KEMZ OJ CMS dashboard: products, categories, news, recent changes and inquiries
Actual KEMZ interface · October 2026. Personal inquiry data is not shown.

Content and catalog

Products, categories, news and documents live in OJ CMS, built on Payload. Content has publishing states, and product edits can be saved as drafts.

Inquiries in the CMS

Website inquiries are saved before an email notification is sent. Editors can view them; processing and deletion are reserved for administrators.

Analytics alongside content

The Yandex Metrika API brings visitors, visits, page views and popular pages into the dashboard, with a selectable reporting period.

Explore the KEMZ implementation ↗

04 / CURRENT STATE

A demo to explore. A deployment to work with.

01 / DEMO

In the demo today

Edit pages and news, work with media, save drafts and open previews. Data stays in each visitor's browser. Switching roles illustrates the interface but does not replace server authentication.

02 / PRODUCTION

Already deployed at KEMZ

Catalog, categories, news and documents are stored on the Payload server. OJ CMS provides publishing states, website inquiries and Yandex Metrika API analytics. Sections and integrations are configured separately for each client.

05 / USE CASES

Where a focused editor helps

01
Mascot assembling a company website in the workshop

Company website

Update services, cases, news and contact details without a development ticket for every small change.

02
Mascot arranging a product catalog

Catalog

Products, specifications, categories and images need structure and a clear update process.

03
Mascot managing content in the editor

Content project

Several authors prepare material, review changes and publish under agreed rules.

06 / IMPLEMENTATION

Start with the team's work, then define CMS fields

  1. 01

    Map the content

    Identify which sections change, who owns them and what needs review before publishing.

  2. 02

    Design the model

    Define content types, relationships, roles and the path from draft to public site.

  3. 03

    Connect and verify

    Link the editor to the site, test publication and walk the team through everyday tasks.

NEXT STEP

Show me what your team updates

Tell me about your pages, content and editors. I will suggest a content model and explain what a production integration would take.

PROJECT ENQUIRY