Recent changes
Wednesday November 04 2026
-
Requirements for a public-sector CMS Updated Markdown page
The index of the requirements pages - how to write verifiable requirements for a public-sector CMS and requirement wording for functions, accessibility, security, privacy, languages, hosting, integration, operations…
-
Accessibility requirements Updated Markdown page
How a public body writes accessibility requirements for a CMS tender - WCAG 2.2 AA, EN 301 549, Section 508, the public site versus the administration, authoring support and conformance evidence - and what Exponential's…
-
Exit and portability requirements Updated Markdown page
Requirement wording that keeps a public body free to leave a supplier or the product - complete exports in open formats, files, configuration, source, documentation, redirects and a tested exit - with the export tools…
-
Functional requirements for a public-sector CMS Updated Markdown page
A catalog of functional requirements a public body usually needs from a web content management system - content model, editing, approval, versions, permissions, search, forms, feeds, multisite - each phrased to be…
-
Hosting and data location requirements Updated Markdown page
Requirement wording for where and how a public CMS is hosted - on premise or by a supplier, data location, databases, operating systems, outbound connections, backups and recovery - with what Exponential's documentation…
-
How to write verifiable requirements Updated Markdown page
For procurement officers and project managers who write the requirements of a tender for a content management system - how to phrase each requirement so a bidder can answer it with evidence and an evaluator can check it.
-
Integration and API requirements Updated Markdown page
Requirement wording for how a public CMS connects to other systems - content API, authentication, directory sign-in, feeds, webhooks, mail - with Exponential's documented protocols and their status from the APIs and…
-
Language and multilingual requirements Updated Markdown page
Requirement wording for official and minority languages in a CMS tender - content translations, right-to-left scripts, administration languages, language addresses and encodings - with what Exponential documents.
-
Mapping requirements to evidence Updated Markdown page
A reference table that maps common public-sector CMS requirements to the exact Exponential pages, settings and tests that evidence them, with the documented status, for evaluators who check answers and bidders who write…
-
Open source and licensing requirements Updated Markdown page
Requirement wording for open source licensing in a CMS tender - license of the software, source availability, rights to custom work, third-party components and documentation license - with the facts of Exponential's GPL…
-
Operations and monitoring requirements Updated Markdown page
Requirement wording for running a public CMS day to day - monitoring, logs, scheduled jobs, caches, maintenance windows, upgrades and health checks - with the Exponential tools and pages that a supplier's answer should…
-
Privacy and data protection requirements Updated Markdown page
Requirement wording for the privacy part of a CMS tender - data minimization, consent records, data subject requests, retention, cookies, third parties and processing agreements - with what Exponential provides and what…
-
Records and audit requirements Updated Markdown page
Requirement wording for records management and accountability in a public CMS - version history, a tamper-evident audit trail, retention, export for archives and evidence of who published what - with what Exponential…
-
Security requirements Updated Markdown page
How to write the security requirements of a CMS tender - authentication, access control, input handling, headers and CSP, logging, updates and vulnerability handling - with verifiable wording and Exponential's…
-
Support and maintenance requirements Updated Markdown page
Requirement wording for support and maintenance of an open source CMS - who supports what, severities and response times as blanks, security updates, upgrades, the upstream project's own commitments, and how to compare…
-
What Exponential can and cannot evidence Updated Markdown page
An honest list, taken from the standards pages, of what the Exponential repository can prove to a public-sector evaluator and what it cannot - no VPAT, no ASVS assessment, no external audit, no cookie banner, no…
-
Tender templates Updated Markdown page
The index of tender and contract clause templates for buying an Exponential-based website and its services - an RFP skeleton and clauses for accessibility, security, patching, privacy, open source, custom work, hosting…
-
Tender template: acceptance testing clause Updated Markdown page
Clause text for acceptance of an Exponential site - test plan, environments, functional, accessibility, security, performance, language, backup and exit tests, defect classes and the acceptance decision - with the…
-
Tender template: accessibility clause Updated Markdown page
Clause text for the accessibility obligations of a CMS contract - WCAG 2.2 AA for the public site and the administration, EN 301 549 and Section 508 references, evaluation before acceptance, accessibility statement and…
-
Tender template: documentation clause Updated Markdown page
Clause text for the documentation a supplier delivers with an Exponential site - system description, content model, roles, configuration differences, operations runbooks, editor guides - in editable form under an open…