a•abacadigital

ABACA DIGITAL / LONDON

CMS websites

Content management for your local business. Keep services, projects, opening hours or property details up to date.

Built for the people publishing.

For a small or medium-sized business, a content management system should fit your everyday work. We start with the pages you publish, the information you maintain and the people responsible.

Explore past client work ↗

Room to grow.

We bring CMS experience and .NET development together. The right platform depends on your content, existing technology and budget. We discuss those needs before proposing a solution.

  • Content structure and page templates
  • CMS website design and development
  • Review of publishing workflows
  • Improvements and support by agreement

COMPLEX CMS PROJECTS

Sitecore & Optimizely.

We can work on complex .NET and CMS projects using Sitecore and Optimizely (formerly Episerver), drawing on hands-on professional experience.

Tell us about your platform, existing implementation and the work you need. We can discuss how that experience fits your project.

EXPERIENCE BEHIND THE SERVICE

Professional experience. Practical capability.

This platform experience was gained through professional roles outside Abaca Digital client projects. It informs the expertise we bring to new work.

Discuss your CMS project ↗

EVERYDAY CONTENT, UNDER YOUR CONTROL

Start with what changes.

Useful editing for a busy business.

Perhaps you need to change opening hours, add a completed building project or update a service description. An estate agency may need to maintain rental property details much more frequently.

Before choosing a CMS, we identify the information that changes, how often it changes and who is responsible. That makes it easier to plan an editing experience that fits the work.

Pages or structured information?

A few editable pages can be enough for one business. Another may need repeatable records for properties, projects, products or team members, each with a consistent set of fields.

Structured content can help present information consistently in different places. It also needs more planning than a simple text editor, especially when records relate to one another.

REQUIREMENTS TO CONSIDER

The right control for your team.

Editing

Which text, images and records should staff change? Which layout elements should remain consistent?

Publishing

Does one person publish directly, or do you need drafts, previews or an approval step?

Access

Should everyone have the same permissions, or should responsibilities differ between editors and administrators?

Media

Who prepares photographs and documents, and how will the team keep them organised and suitable for the website?

These are decisions to scope together. The agreed CMS and implementation determine which features are available.

Moving content takes planning.

If you already have a website, we discuss what needs to move, what is worth rewriting and what should be retired. Pages, images, documents and structured records may need different approaches.

Content migration can involve manual work, data mapping and checking the result. Existing URLs and any redirects should be considered alongside the move, rather than left until launch.

A CMS needs care after launch.

Content editing and technical maintenance are different jobs. Your team may update the pages while platform updates, hosting, backups and application changes need a separate arrangement.

We discuss who is responsible for each part, what guidance or training your editors need, and what support is included. Licensing and hosting costs should be considered as well as the initial build.

When content needs bespoke functionality ↗

CHOOSING A CMS

Fit the system
to the business.

Does every small business need a CMS?+

No. If your information rarely changes, a straightforward website with updates handled for you may be enough. A CMS becomes more useful when your team needs regular control over content. We can discuss the maintenance and cost implications of each approach.

Can we keep our existing CMS?+

Possibly. We need to understand the platform, implementation, access available and changes required before recommending whether to retain, improve or replace it.

Can a CMS manage property listings or project records?+

Those can be suitable uses for structured content. We would define the fields, images, status changes and public presentation, along with any search or external data connections required.

What affects the cost?+

The content types, page templates, editor permissions, publishing workflows, data migration, integrations and platform choice. Training, licences, hosting and ongoing technical support should also be included in the discussion.

What should we prepare for the first conversation?+

A list of what you want to update, examples of existing content, the people who will edit it, any publishing problems and details of the current system. You do not need to select a platform first.

Have a project in mind?

Let's talk ↗