Features Page
Page and Block Editor
Authors edit content in tabbed forms laid out by the developer, with fields sized and ordered for the job. Validation runs at publish time, so authors can save unfinished work freely. Presentation settings sit on their own tab, apart from the content itself.
Content Zones
Content Zones let authors build pages out of reusable blocks, arranged by drag and drop. Developers declare which block types each zone accepts. Blocks can be shared across many pages or kept local to one.
Media Library
Media is organized in folders with drag-and-drop ordering and access rights. Files are stored in Azure Blob Storage or on the local disk. Renaming a file renames the actual file, not just its label.
Rich Text Editing
The WYSIWYG editor includes Cendia's link picker, so links to internal pages keep working when those pages move. Administrators define named toolbar templates, and each field chooses the template it needs.
Field Types
Built-in field types include text, rich text, numbers, dates, dropdowns, radio lists, checklists, links, URLs, content selectors, media selectors and content zones. Each type gives authors the right control and stores a typed value for developers.
Page Tree
Pages, blocks, media and categories each have their own tree, with drag-and-drop ordering and moves. Search covers the whole site on the server. Large sites load on demand as the author scrolls and expands.
Image Editing
Authors crop, resize and rotate images directly in the CMS. Images can be dropped straight into the editor where they're needed.
Block Designer
The Designer builds new block types inside the CMS: their fields, layout, styling and behavior. An AI assistant can propose a design from a written brief and check it in a live preview. The Designer also works without AI.
Stylesheets and Scripts
CSS and JavaScript can be written in the CMS and attached to specific pages. Each asset loads once per page.
Data Connections
Named data connections link Designer blocks to external data sources. Their credentials are stored encrypted.
Forms
Authors build forms on a visual canvas, including multi-step forms. Fields cover email, phone, file uploads and more, with layout and width controls. A form is a block, so it can be placed anywhere content can.
Submissions and Notifications
Submissions are stored, viewable and exportable in the CMS. Email notifications go out when forms are submitted. Captcha protection works without extra setup, and a form can be limited to signed-in visitors.
Multiple Websites
One installation can run several websites, each with its own host names and start page. Links between sites resolve to the correct domain automatically.
Languages and Fallbacks
Every page can have a version in each language, with language-specific URLs. A backup language fills in any content that hasn't been translated yet. A replacement language can pin a page, such as a legal notice, to a single language.
Culture-Aware Routing
Language is chosen from the URL, the site's settings or the visitor's browser preferences, in that order. Each host has a default language that needs no URL prefix.
Any block in a zone, or any passage inside rich text, can target one or more audiences. Content with no audience set is shown to everyone.
Authors define audiences from more than twenty criteria. These include geographic location, referrer, search keywords, visit history, pages and categories visited, time of day, business hours, device and browser, sign-in state, user role, query string and form submissions.
Opt-in statistics count the distinct people in each audience per day. Visitor identity is used only while counting and is not stored.
Every cookie set in the CMS is documented, and visitors can opt out of tracking. Location lookups happen on the server and never go more specific than country and region.
Authors can preview drafts on the real site, including how a page looks to a particular audience — and they can publish straight from the preview.
Preview links carry signed tokens and can be shared with reviewers. This way you can share the URL directly without having to provide instructions for the user to find the page you want to work with.
A page can have several short vanity URLs, each unique across the installation. The CMS manages permanent redirects, and a report shows every address in use and which page owns it.
A Reports area covers SEO status across every page, simple addresses and form submissions. Each report shows only the rows the viewer is allowed to see.
A Release groups changes to many pages so they can be reviewed and published together, immediately or on a schedule. Authors can preview the whole site as it will look once a release goes live. This quality of this feature is unique to Cendia.
Every save produces a version, and earlier versions stay available to review. You can also create a new draft from a previous version enabling both a current draft and one or many draft (multiple drafts) which can be scheduled to go live at different times.
A field-level comparison shows exactly what changed between two versions. Nothing is overwritten silently.
A version is not a gadget. Its part of the editing process and you can always see the most recent ones or click on [Show All] to see the entire available history.
Authors assign and track editorial work tied to specific content and releases. Tasks sit docked next to Releases for quick access.
If live content changes while a release is also editing it, the CMS records the conflict and asks for it to be resolved before the release publishes.
Reconciliation works field by field, so authors keep exactly the changes they intend.
Content can be set to publish and expire at specific times. Expired content can move to an archive automatically, where it stays available for reference.
Deleted content goes to a trash from which it can be restored. Removing one language version of a page is also recoverable.
Search
The CMS has its own search index covering all content, including drafts that authors can see. Results are filtered by each user's access rights. No database add-ons or external search service is needed.
Categories
One category tree covers the whole installation. Authors tag pages, blocks and media from a picker, and categories can drive audience rules and content queries.
SEO Fields and Sitemap
Addressable pages get SEO fields for title, description and robots directives. The XML sitemap builds itself from published content. Developers can add their own URLs to it.
Cendia ships with rate limiting, a strong password policy, secure cookies, signed preview tokens and response compression turned on.
Permissions are set on pages, blocks and media, and child items inherit them. There are six rights: Read, Create, Edit, Delete, Publish and Administer. They apply everywhere content is served: the site, the API, search, the sitemap and even raw media files.
Administrators invite users, assign groups, lock accounts and manage passwords. Groups work as roles. Sites can use any identity provider for their visitors, and Cendia checks access by role.
API keys for AI providers and other services are stored securely and managed from Settings. They're never kept in plain configuration.
A mail provider can be plugged in through configuration: logging only, SMTP or Amazon SES. New installations send nothing until mail is configured.