How do you pick the CMS and publishing workflow for a project?

How do you pick the CMS… | Content…

We choose platform and workflow based on the client’s landscape and service goals, not by forcing a single toolset. The solution should fit the users, governance, content needs and integrations, while aligning with delivery constraints. Where it makes sense, we prototype and test pipelines and publishable processes, and we’ve documented how Azure-based pipelines can be integrated with Drupal in published work. This kind of pattern is used when it fits the problem and the client’s environment, not as a one-size-fits-all rule.

Useful next steps

Use this answer as a practical starting point. Current scope, specifications, compatibility, availability, pricing, timing and next steps should be confirmed directly with Annex where they affect a decision.

Open topic Contact Annex All Q&A

Continue The Conversation

Natural Follow-Up Questions

Previous questionWhat business problem is Content Management & Publishing intended to solve?

Annex treats Content Management & Publishing as part of a wider digital-service problem, not as an isolated output. CMS and publishing experiences that make complex content easier for teams to manage and users to access. These examples show experience with public-facing services, complex workflows, …

Before going deep into content management & publishing, the project needs a shared view of the problem, the users, the important stakeholders and the current environment. These examples show experience with public-facing services, complex workflows, accessibility, governance, content publishing, tes…

Annex's published work does not point to a single mandatory toolset for content management & publishing. The pipeline was built in Azure and integrated into Drupal. These examples show experience with public-facing services, complex workflows, accessibility, governance, content publishing, testing a…

A strong signal is when content becomes duplicated, hard to update or trapped in documents. These examples show experience with public-facing services, complex workflows, accessibility, governance, content publishing, testing and secure digital delivery. We simplify complex business problems every d…

Annex uses evidence during delivery rather than treating quality as a final inspection step. Secure and Scalable Comprehensive testing for accessibility, load, and security ensured a reliable, future-proof system. We made it easy for the AER team to add and edit the website over time, and created a …