Knowledge Base
Support customers and employees with a definite source of knowledge and documentation. Build custom content types, fetch content via a powerful API, and distribute to any necessary channel—like a dedicated website, content in apps, or snippets on third-party sites. As for the editors, our Content Studio provides an intuitive and user-friendly UI for efficient content management.
Customers running knowledge bases
Flexible content types
Custom content types is created through Enonic's schema system, where you can combine multiple input types and sets. Schemas can even be reused across content types, and our powerful APIs enables content reuse across different channels.
Tree structure
The tree structure offers a neat overview, and can reflect your website or a logical structure for managing your content. Create, publish, sort, duplicate, and archive content items with custom access rights.
Workflow and roles
Collaboration and approval processes are essential in an editorial environment. Enonic therefore features a content status workflow, issues system, and granular permissions and roles management.
Read our knowledge base case studies! 💡
What they need, when they need it, where they are
Required to comply with both regulation and user expectations, the Norwegian Directorate of Health aimed to deliver complex information from several sources through multiple channels to different users—in one solution.
Untangling complexity with a powerful enterprise search
Faced with many complex sources, the Norwegian Electronic Health Library turned to Enonic for efficiently curating, cleansing, and distributing search data to healthcare professionals.
Knowledge is power ✏️
What is structured content?
Why you should focus on creating structured content and not building web pages in the age of headless and omnichannel.
Why editors should use structured content
Stop building pages, start building reusable, consistent, and flexible content instead!
How to model healthcare content structure in Enonic
Use Content Studio to establish content types, taxonomy, and create templates and components as preparatory means for building a truly robust healthcare content model.
