Content Portal · Capabilities

What the Portal Does

Publishing workflow, version control and supersession, permission-scoped search, a reader built for long technical documents, and controls over how content leaves the platform.

Publishing workflow
Content moves through an explicit draft and publish cycle rather than appearing the moment it is uploaded. A publication can be drafted, reviewed, and released deliberately, and large ingests can be retried in place when a source file fails to process.
- Draft, review, and publish as distinct states
- Batch ingest through packages, with a parser that unpacks and registers contents
- Failed items surface with statistics and can be retried individually or in bulk
- Presigned direct-to-storage upload, so large files never route through the application server
Versions and supersession
Every publication carries its version history. A new issue supersedes the previous one rather than overwriting it: the old version remains addressable and is marked as superseded, which matters when an incident investigation needs to establish what a maintainer was actually looking at on a given date.
- Full version history per publication, with a defined current version
- Explicit supersede relationships between documents
- Version-aware search, so you can search across current content or across history
Search
Full-text search across the library, scoped to what the signed-in user is permitted to see. Results respect permissions at query time rather than filtering after the fact, so a user never sees the title of something they cannot open.
- Full-text indexing across publications and their contents
- Permission-scoped results
- Search with or without historical versions included
Reading and navigation
A reader built for long technical documents rather than for casual browsing: generated tables of contents, page-level navigation and linking, and illustration assets served alongside the page they belong to.
- Generated tables of contents for structured navigation
- Page-level addressing and deep linking
- Illustration and asset handling tied to the rendition
- Favorites, so a maintainer can pin the ten documents they use daily
Distribution controls
Controlled release, not just controlled access. Downloads can be watermarked per user, content can be shared to named recipients, and bulk export exists for the cases where a customer genuinely needs an offline set.
- Per-download watermarking
- Share a publication with a specific recipient
- Bulk export for offline or archival delivery
- Notifications when content a user depends on is revised