Text & structure
Paragraphs, headings, quotes, lists, dividers — the editorial backbone.
The platform
One book graph. Three focused rooms.
Most programs scatter a course across a doc editor, a quiz tool, a file share, and a spreadsheet. Panjera holds all of it in one structured graph — every book, page, component, question, translation, and reading signal connected — and gives each role its own focused room over that one structure.
The content model
Pages are structures, not walls of text.
Every page is built from typed components with their own editing, rendering, translation, and progress behavior. Because the pieces are structured, the platform can translate them field by field, track interaction on each block, and keep every revision coherent.
Structured, component-based content
Callouts & disclosure
Key ideas, notes, warnings, accordions, and step-by-step reveals.
Media
Figures, galleries, audio, video, and files with captions and credits.
Questions & activities
A dozen question types today, question sets, and activity launchers — graded in place.
Formatted notation
Mathematical and scientific notation rendered properly in every theme.
Layout & showcase
Columns, framing, and presentation blocks for pages that need staging.
These categories are the shape of the catalog, not its limits — the full set ships with the platform, keeps growing, and can be extended for your program. Every component renders identically in Builder preview and the reader.
Builder — the authoring room
Authoring that keeps the book intact.
For authors, editors, reviewers, translators, and instructional designers. Builder treats a book as a graph of chapters, pages, and components — every decision stays attached to the content it describes.
Structured editing
Reorder chapters, split pages, and compose from the component catalog without the book falling apart.
Comments where the work is
Review threads anchor to the exact page and block they discuss — feedback never drifts away from the content.
Live reader preview
Open the real reader — typography, themes, direction — on the draft before anything is published.
Publishing discipline
Publishing freezes a revision readers can rely on while the draft keeps moving. Nothing disappears between versions.
A media library that tracks use
Figures, audio, and files are reusable assets that know where they're used across the workspace.
Workflow tasks on the book
Plan reviews, translations, and fixes as Pending → Working → Done — owners, assignees, and due dates stay attached to the book they belong to.
Try it here — the book's task board
Pending
2Resolve review comments on Chapter 2
Approve the Farsi draft of “The journey downhill”
Working
1Replace the river-profile figure
Done
1Tighten the checkpoint question bank
Owners, assignees, due dates, filters, CSV export, and a drag-and-drop kanban — tracked per book, right where the work happens.
A live sample of Builder's workflow tasks. The full Workflow Center adds owners, filters, due-date views, CSV export, and drag-and-drop — per book, where the work happens.
Reader — the learning room
A reading room that keeps attention on the page.
Learners pick up exactly where they stopped, in the theme and language they prefer, with their own annotations along for the whole journey.
Continue reading
The book remembers the chapter, page, and position — across sessions and devices.
Highlights, notes, bookmarks
Select to highlight, write private notes, drop bookmarks — annotations stay with the reader through new revisions.
Questions in the flow
Interactive questions grade in place with explanations, and progress reflects real interaction.
Progress and checkpoints
Authors can set checkpoints that structure a learner's path; the platform enforces them server-side, not just visually.
Four themes, every direction
Light, Paper, Dark, and Night — with right-to-left reading and localized numerals as first-class citizens.
Try it here — three of the reader's tools
0 highlights
The journey downhill
Leaving its source, a young river cuts a steep and narrow valley. Tributaries join it, and at every confluence the river grows stronger. Where the land flattens, the river slows, meanders, and sets down its sediment.
Live samples on a fixture page. The product goes further: generated narration with word-level sync, a dozen sticky-note papers, five bookmark styles, annotation search, and more.
Admin — the operations room
A control room, not another editor.
For the people who run the workspace: accounts, access, book states, and reading progress — legible at a glance, without becoming an author.
Admin-provisioned accounts
No open sign-up. Administrators create accounts, send set-password invitations, and disable access when needed.
Books at a glance
Draft, review, and published states across the workspace, with a direct path into Builder when a book needs work.
Reader access & progress
See who can read what, approve access, and follow reading progress across books and cohorts.
Media oversight
The workspace media library shows what exists, where it's used, and what's grown stale.
Progress & insight
One interaction, heard everywhere.
Finish a page and the platform hears it. Read-to-advance marks real progress, checkpoints gate what must be mastered first, xAPI-compatible learning events stream into your instance — and the instructor's view updates as it happens.
Progress and learning signal
In the reading room
One basin, one system
Checkpoint — pass to continue
A watershed can contain many smaller watersheds.
Finish the page above to unlock.Divides and boundariesLocked by checkpoint
Learning events
- experiencedPage · One basin, one systemearlier
- progressedChapter 2 · 38%earlier
xAPI-compatible statements, captured per component and batched to your instance.
The instructor's view
43%this reader
- Pages read
- 3 / 7
- Checkpoints passed
- 1 / 3
- Awaiting grading
- 2 open responses
Progress, access, and a grading inbox — per book, per cohort, per reader.
Sample data, live in this page. In the product: a dozen question types, activity shapes from quiz to capstone, open responses landing in a grading inbox, and checkpoints enforced server-side — not just visually.
Languages & direction
Multilingual is the model, not a plugin.
A book carries language variants at the structural level — each language has its own pages built from the same graph, so translations stay aligned with the source as both evolve.
Multilingual, right-to-left content
Translation with review discipline
Field-level translation workflows detect structural drift between source and target, and route changes through review — not silent overwrites.
Right-to-left, properly
Farsi, Pashto, Arabic and other RTL languages get true right-to-left reading — layout, controls, and flow, not mirrored text in an LTR frame.
Localized numerals
Eastern Arabic numerals render throughout the reading experience where the language calls for them.
Title
The journey downhill
Approved
سفر به پاییندست
Paragraph
Tributaries join the young river, and at every confluence it grows stronger.
Approved
جویبارها به رود جوان میپیوندند و در هر پیوندگاه، رود نیرومندتر میشود.
Figure caption
Figure · The river's profile from source to sea.
Approved
شکل · نیمرخ رود از سرچشمه تا دریا.
Source and translation are linked field by field — watch what a source edit sets off.
The same discipline at any scale: field-level links, drift detection instead of silent overwrites, and review states on every block. Machine-drafted translation runs are optional and land in this same review flow.
Connected services
More capability, when you connect it.
The core platform is self-contained. Organizations that want generated narration, translation runs, or the grounded tutor connect a workflow engine and their own model-provider credentials — capabilities activate per deployment, under your keys.
Narration and connected services
Optional — requires connected services
Grounded reader tutor
Learners ask questions scoped to the page they're reading; answers cite the book itself so they can follow the reference back.
Narration
Generate section narration with cost caps per workspace; readers listen inline with a synchronized transcript.
Translation runs
Machine-assisted translation drafts flow into the same review workflow your translators already use.
Drafting workflows
Turn source documents into structured book skeletons that authors then shape — drafting help, not autopilot.
Watch a run
Triggerblock publishedqueued
Fetch block text¶2 · Where rivers beginqueued
Synthesize speechworkspace voicequeued
Attach audiowith synced transcriptqueued
Ready
- Run log — press “Run this workflow”.
Three of the platform's system workflows, replayed with fixture data. Connected deployments watch real runs live — queued, running, completed — with logs, artifacts, and per-workspace cost caps.
These run on your own provider credentials, activate per deployment, and can be left off entirely.
Deployment & architecture
Built to be an organization's own system.
Panjera deploys per organization from one codebase and a reviewed configuration — not a fork, not a shared multi-tenant pool.
Your own instance
Each deployment serves one origin — your portal domain — with content, accounts, and sessions scoped to it.
Your cloud project, when required
Deployments can live inside your organization's own cloud account, keeping data under boundaries you control.
Server-owned sessions
Sign-in uses secure, HTTP-only server sessions — no tokens floating in browser storage or URLs.
No tracking by default
The public site and portal ship without third-party trackers. What your learners read is your organization's business.
See it with your content
The best demo is your own book.
Bring a course book, a syllabus, or a rough manuscript. We'll show you what it looks like as a structured, multilingual Panjera book — and talk plainly about fit.