Proposal · RFP v2.1

10. Mandatory CMS and editor autonomy

Chrysal Website 2027 · Extended draft · 19 October 2026

All RFP chapters

RFP-hoofdstuk 10

Independent editing

The website proposal recommends WordPress with a managed block editor and reusable patterns within brand agreements.

Approach Deliverables Added value

Our response & approach

Building pages independently

The editorial team must be able to create and further develop pages independently. We therefore recommend the WordPress block editor with a limited, carefully designed set of components and page layouts. Editors combine text, images, evidence, quotes, downloads, related solutions and contact blocks. Fixed design settings safeguard color, spacing, typography and accessible use. WordPress supports reusable patterns; we configure the precise editorial capabilities for Chrysal. [10]

Autonomy with clear boundaries

For example, an editor can create a new campaign page by choosing an approved pattern, replacing the image, adding a knowledge block and selecting a contact block for the right market. A new arrangement of existing components does not require a developer. A genuinely new function or a new component with different behavior does require design and development. That distinction makes the autonomy realistic.

Managing media and documents

Media management includes agreements on file names, crops, alternative texts, captions, rights and language. We generate suitable image formats and sizes and provide filters by media type or market where needed. We only build an external DAM integration if the added value and available interfaces justify it. For documents, we record type, language, version, scope of application and validity.

Organising review and publication

Preview, revisions, drafts and scheduled publication support daily work. For content approval, we set up a workflow in which experts do not have to manage the CMS themselves. An expert can assess a draft through a controlled preview or an agreed review document; the editor processes it and publishes. Global and local permissions, restoring a previous version and changing linked content are tested.

Testing the CMS choice with real content

We substantiate the CMS choice with a demonstration using Chrysal content. In doing so, we compare the proposal with the current way of working and discuss relevant alternatives if a requirement makes this necessary. We do not recommend an expensive separate publishing layer if there is no clear need for it. Custom development remains limited to the content schema, components, permissions and integrations that demonstrably have value.

Documenting management and handover

We deliver a configured CMS, a component catalog, management instructions and an overview of extensions, licenses and upgrade policy. Code and configuration are placed under version control. Chrysal receives the agreed access to its own content, data and custom source code, subject to open source and vendor licenses. This supports transferability and limits dependence on a single provider.

Concrete deliverables

CMS demonstration with Chrysal content
A demonstration using representative Chrysal content to test daily editorial tasks and the proposed CMS workflow in practice.
Reusable components, patterns and media configuration
A managed set of building blocks and media fields with which pages can be assembled consistently, without requiring development for every content change.
Preview, version control, publication and permissions
A configured publishing workflow with roles, previews and recovery options. We test this with the people who will manage the website.

Added value of Afdeling Online

Non-technical editors can combine existing building blocks themselves; new functional behaviour deliberately remains development work.

We test management requirements with designers and developers together. The editorial team sees early on what it can adjust independently and where new functional behaviour requires development. This makes freedom concrete and prevents expectations that the CMS cannot fulfil.

Source: supplied draft proposal dated 19 October 2026. Amounts, team staffing and service agreements require internal confirmation before sending.

Chapter 9 Chapter 11

Save this page as PDF

The print version is formatted as a document, without buttons or navigation. Choose “Save as PDF” in the print dialog.