Product / Scholar Core
The headless CMS for scholarly publishing.
A single source of truth that can be validated: production quality control and publishing, from structured ingest and accessibility auditing through to a corrected, versioned, publicly readable record.
Recorddoi:10.1234/jotp.2026.014
| Version | Step | Status |
|---|---|---|
| v1.0 | JATS INGESTED | complete |
| VALIDATED | JATS4R | |
| A11Y AUDITED | PDF/UA-1 · EPUB | |
| RENDERED | HTML | |
| v1.0 | PUBLISHED | 2026-03-02 |
| v1.1 | CORRECTION | SUPERSEDES v1.0 |
Lifecycle
Ingest to record, one pipeline.
Everything after acceptance: from structured ingest to the versioned public record.
01Ingest
Structured content in (such as JATS XML), assets stored content-addressed.
02Validate
Structure checked before anything ships.
03Audit
Checked against JATS4R, PDF/UA-1, and EPUB Accessibility 1.1.
04Publish
Rendered to HTML, live on your front end.
05Supersede
Corrections and retractions update the record without losing its history.
Capabilities
Production to publication.
Structured ingest
JATS as a first-class content type: validated on the way in, with supporting assets organized and stored by content hash.
Accessibility auditing
Automated audits against JATS4R (NISO RP-47-2024), PDF/UA-1, and EPUB Accessibility 1.1, targeting WCAG 2.2 AA, across PDF, EPUB, and supporting assets.
Rendering
Content transformation including JATS→HTML rendering, with a ready-made WordPress plugin for reader-facing sites.
Versioned lifecycle
Publish, correct, and retract as first-class operations; publication stages tracked with semantic versioning.
Search
Chunk-level search across the corpus, ready for downstream AI access.
Reporting
Usage reporting that shows how published content is read and retrieved.
The record
Corrections supersede in place.
When a correction publishes, semantic versioning lets the new version supersede the old, and the history stays legible. Readers, and the AI tools reading alongside them, see the current version with its status on the record.
v1.0 → v1.1 [CORRECTION] → v2.0 [VERSION OF RECORD]
Questions
Asked early, answered plainly.
Are you claiming WCAG compliance for us?
No. Scholar Core audits your content against JATS4R, PDF/UA-1, and EPUB Accessibility 1.1 and reports findings. The compliance decision, and the evidence for it, stays yours.
Do we need Razeta to use Scholar Core?
No. Scholar Core is a standalone CMS. Razeta is a separate product for AI access, and neither requires the other.
What formats does it ingest?
JATS and other structured formats, validated on the way in. If your archive is in something else entirely, bring a sample to the demo and we will tell you plainly what works today.
Bring a sample issue.
Thirty minutes, your own material, no slide deck.
Different problem? Explore Razeta