Can Content Management & Publishing be improved incrementally within an existing CMS, document library or publishing workflow?

Can Content Management & Publishing be improved incrementally…

Yes, that can be possible; Annex's published work includes delivery inside existing technical and organisational environments rather than only greenfield builds. Annex worked with both ActewAGL and partners to develop an easily accessible web app to allow ActewAGL customers to administer their accounts, make payments and procure new services through the Self Service Platform. Throughout our engagement Annex worked closely with ActewAGL developers to provide the team with tools and systems to deliver new features quicker than ever before, optimising the code and ensuring the whole platform has automated tests. The sensible starting point is to identify what already works, what is constraining the service, and where integration or incremental change is safer than unnecessary replacement. The answer for an existing CMS, document library or publishing workflow would depend on its actual condition and dependencies.

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

These questions continue the same line of enquiry rather than starting a completely unrelated topic.

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, …

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…

A useful published example is **Connecting it all together — Approach and solution**. The digitisation pipeline was built in Azure and integrated into the Drupal CMS. Our solution provided a seamless experience for the document publishing team, which suits their needs now and into the future. It is …

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…