Organize into collections
Collections are hierarchical containers — folders that hold folders and items. Each carries its own attributes, labels, workflow state, language variants, and visibility flags.
Bosca CMS
Bosca CMS is a content engine, not just a CMS: a typed, hierarchical library where rich documents, media, guides, and data live together — with real-time collaboration, adaptive media, and workflow-driven publishing built in.
How it works
Collections are hierarchical containers — folders that hold folders and items. Each carries its own attributes, labels, workflow state, language variants, and visibility flags.
Documents, guides, data records, media, bibles, and supplementary files each have a metadata record describing them — name, type, language, attributes, and labels.
Every item moves through a defined workflow — draft, review, approval, processing — before it is published or advertised, with transitions you can schedule in advance.
What makes it powerful
The platform handles collaboration, media processing, workflow, and access — so your team works on the content, not the plumbing.
Documents edit live with multiple people at once — everyone's changes merge as they type, and the editor catches back up on its own after a dropped connection.
Video and audio transcode into adaptive quality tiers with automatic quality selection, generated thumbnails, and animated previews.
Beyond prose and media, data records store typed JSON — author profiles, pricing, locations — edited through generated forms and embedded into documents.
Media is auto-transcribed into plain-text and subtitle tracks, indexed for full-text search and reused for accessibility.
Access is gated by both workflow state and independent visibility flags — Public, Public Content, Public Supplementary, Searchable.
Workflow plans schedule a transition for a future time — automated go-live, embargo lift, and content rotation without anyone standing by.
A diagnostics dashboard flags failed jobs, broken relationships, unpublished references, and guides with unpublished steps — with a triage list.
Hierarchical collections, cross-cutting categories, descriptive traits, and free-form labels organize content without duplicating it.
One record, every type
Behind every document, video, guide, and data record is one description record: a name, a content type, a language tag, free-form attributes, labels, and categories.
The item's body — rich text, a video file, a JSON record — is separate from the metadata that describes it, so the same workflow, permissions, and publishing rules apply to every kind of content.
{
"name": "Getting Started",
"contentType": "bosca/v-document",
"languageTag": "en",
"labels": ["featured"],
"attributes": { "readingTime": 4 },
"workflowState": "published"
}Go deeper
Collections, metadata, and the typed items that fill your library.
Real-time collaborative documents, guides, data forms, and templates.
Adaptive streaming, quality tiers, previews, and auto-transcription.
States, scheduled publishing, visibility, health, and moderation.
The same content the CMS manages is served through one GraphQL API — to your apps, to a BML site, to feeds and search. Studio manages it; everything else renders it.