SoBold is pleased to announce that they have renewed their contract with Transport for London to manage and support a bespoke Cookie Consent Management Tool for use across TfL’s portfolio of websites which includes 30 domains.

SoBold recently became only the 3rd Platinum Certified Cookiebot Partner in the UK having been an authorised Reseller of Cookiebot since the new General Data Protection Regulation (GDPR) came into place on 24 May 2018.

Transport for London’s desire to extend its relationship with SoBold for a further year, highlights the importance of the work SoBold are doing to manage its bespoke Cookie Consent Management solution across its portfolio of website which have missions of visitors per month. The contract renewal cements SoBold’s position as one of the leading Cookiebot resellers. 

For more information on SoBold’s work to date with Transport for London, see their case study.

SoBold Technical Director, Sam Phillips said:

It is great to see Transport for London renew its cookie management contract with SoBold for a fifth successive year. Over the last year we have continued to evolve their bespoke solution adding in full IAB TCF support as well updating the design to reflect TFL’s updated guidelines. We’re looking forward to continuing to support TfL over the next 12 months.

Would you like these insights straight to your mailbox?

Your emailSubmit

I consent to my submitted data being processed and stored by SoBold in compliance with Privacy Policy

March 8th is still an important date to remind us of the brilliance of being a woman in our society. Even though it can be a struggle every day, we know that women are capable of anything and we are very proud to celebrate the achievements of these creative and intelligent women.

Hedy Lamarr

Who can live without Wi-Fi nowadays? In 1942, Hedy invented the technology that later helped the creation of wireless signals. 

Rear Admiral Grace Hopper

If you’re not in the programming world, you may not have heard of COBOL. This programming language created in 1952 is still used on business applications to this day. Grace was one of the first ever compilers and her work led to the creation of COBOL.

Margaret Calvert

Even in the age of Sat Nav, you’ve probably relied on a road sign at some point, right? Either driving or walking down the street, the reliable signs are a source of comfort when technology fails. Margaret was part of the team that redesigned the whole UK road sign system. It all started in the late 1950s and her work still guides us even to this day.

Carolyn Davidson

‘Just do it’ – the famous tagline from a brand you might have heard of, called Nike. The tick logo was first developed by Carolyn when she was just starting design and the idea behind it to represent speed and motion. Even though the Nike tick is now one of the top 10 most recognised logos worldwide, Carolyn has only made $35 from her design.

Susan Kare

We all know Apple. We all know that they’ve conquered the world of technology by consistently presenting unique designs with both their hardware and software. What you probably didn’t know was that Susan was the designer responsible for developing all the typefaces, icons and other elements that serve as the core for what we now know as the Apple brand.

Would you like these insights straight to your mailbox?

Your emailSubmit

I consent to my submitted data being processed and stored by SoBold in compliance with Privacy Policy

A content management system (CMS) is a type of software-based technology, used to build and manage websites and other digital products. A CMS allows you to easily create, edit, and publish digital content across a range of online channels, such as the web and mobile. This is the most common technology platform used by businesses to build assets such as websites, with almost two thirds (63%) of all sites on the Internet now delivered via a CMS. 

With that in mind, it’s clear why most businesses today are heavily reliant on this technology. Whether you’re developing something new from scratch or switching from an old platform to a new one, selecting your CMS is an extremely important decision with a lot riding on it. But with such a vast landscape of digital solutions to navigate, and so many different options available, finding the right CMS can be overwhelming. 

To help you through the process of finding the right CMS, this article compares four of the most common options for large businesses. We’ve also listed their pros and cons, and provided some additional considerations that will be useful for you to think about along the way.

First, the Criteria

A CMS can be used to build various digital products and assets, from websites and mobile apps to bespoke systems like staff portals and internal training platforms. Particularly in large businesses, it’s common to need to create some bespoke features, functionality, or digital processes as well. Whatever it is you need, you should aim to find a platform that’s capable of delivering on your specific requirements. 

Here are some points to include in your criteria when researching the options for your CMS:

• Bespoke development capabilities
• Easy integration with existing systems and legacy technology 
• Scalability and performance in peak traffic 
• Enterprise-grade security 
• Quick and easy editing capabilities 

Now we’ve covered what a CMS should be able to do when you start implementing it within your business, let’s look at the different platforms available to you.

Option 1 – Drupal 

The Pros: 

• Drupal is a highly secure platform, which is a crucial quality for a CMS to have. 
• It’s very intuitive for users who have coding experience or advanced content management skills. 
• It has a great community of users surrounding it, which contributes a lot of value and is able to provide support.
• It also has hundreds of unique thematic options to choose from when designing your site. 

The Cons: 

• Drupal can be hard to work with for non-technical users, as it lacks simplicity and provides limited customisation.
• It can take a long time to get up and running, which means your costs will be quite high if you work with an agency partner.
• It’s also worth noting that the version of Drupal most businesses use now (Drupal 7) will be reaching end-of-life soon.

Option 2 – Sitecore 

The Pros: 

• Sitecore is purpose-built for large businesses, guaranteeing an enterprise-grade experience. 
• Sitecore is a robust CMS with a high level of in-built security.
• It actually provides a fully-managed ‘digital experience platform’ that comes with more capabilities than the average CMS. 
• It also offers great personalisation and excellent pre-built features. 

The Cons: 

• Sitecore is an expensive option, even if you have a large budget to work with.
• It requires you to procure licenses to begin using it, and also restricts certain capabilities unless you progress to higher tiers of licenses. 
• It typically runs with hierarchical, complex workflows that might be frustrating for small or agile teams. 

Option 3 – Umbraco

The Pros: 

• Umbraco’s scalability makes it very suitable for large businesses.
• It’s free to use and open-source, with an active community of users supporting it.
• It allows you to manage a high volume of pages easily and efficiently.
• It’s another platform that comes with a high level of in-built security.

The Cons: 

• It can be difficult to work with for the average user. As with Drupal, Umbraco is mostly suitable for more technical users who have coding skills or some development experience.
• This complexity again increases the likelihood of higher costs with your agency partner (if you go that route). 
• It’s common for sites built with Umbraco to be reported as slow, for both back-end editing and the front-end user experience. 

Option 4 – WordPress 

The Pros: 

• WordPress is extremely scalable and dynamic. It can easily grow and evolve as your business grows, continuing to meet your changing needs.
• It’s renowned for its ease-of-use. Because of this, it enables you to deliver your projects quickly and efficiently.
• It’s highly customisable, making it ideal for bespoke development. With the right knowledge and skills, you can build almost anything with WordPress. 
• It also typically comes with a very low total cost of ownership (TCO). You won’t need to add on new features or capabilities, nor pay for costly extra work to handle platform upgrades or updates.

The Cons: 

• If you apply too many plug-ins, WordPress sites can slow down and experience dips in performance, but a good agency partner should encourage you to minimise the use of these.
• Some still see WordPress as an unprofessional platform used mostly for small blogs, but that old myth couldn’t be further from the truth today.
• WordPress is a secure platform, but plug-ins can create vulnerabilities if they’re not tested well or taken from untrusted sources. Again, a good agency partner should guide you with this to reduce the risk and prevent any issues.

Interested in learning more? Check out our related article here, where we explore the benefits of WordPress for large businesses in greater detail. 

A Brief Word on Agency Partners 

As touched on earlier, you’ll also need to consider whether you want to take the approach of working with an agency partner or not. For large businesses, most development projects tend to involve complex requirements that are almost impossible to manage without the support of an experienced agency. 

An agency partner can provide you with strategic guidance, platform-specific skills and tools, and expertise to help you gain as much value from the technology as possible. While it’s perfectly valid to decide to implement a new CMS without an agency working alongside you, doing so will probably make things a lot more challenging, a lot more expensive, or possibly both.

All the platforms mentioned here have their benefits. But they’ll each be significantly easier to use, and will deliver far greater return on investment (ROI), if you have an experienced partner involved. 

How to Choose the Best Option for Your Business  

Keep in mind that every business is unique and every web development project is different. These platforms are all good options in their own way, but a solution that works well for the majority of organisations might not be the right choice for you. 

Whether you’re building a bespoke website or migrating an existing site to a new platform, you have to be thorough in your assessment and make the right choice for your specific business.

To really understand the pros and cons of these options, you first have to be clear about exactly what you need and what you’re aiming to achieve. You’ll then need to determine which solution best aligns with your requirements, budget, and strategic objectives.

If you’re in the process of assessing solutions to help you deliver a bespoke development project, read our comprehensive guide to evaluating and selecting the right platform here.

Would you like these insights straight to your mailbox?

Your emailSubmit

I consent to my submitted data being processed and stored by SoBold in compliance with Privacy Policy

A fresh-faced Leo joined SoBold in August 2019, with a big booming smile and speaking in broken English. It was immediately clear how driven he was to learn and pick up new skills and it was a no-brainer to offer him a job to join our development team.

For much of his first year at SoBold, Leo was glued to Google Translate to try and properly understand the tasks he had been set, but each and every time the output of his work would be the same, outstanding.

As Leo’s English picked up, as did his confidence and skill-set and he made it clear that he wanted to focus on Back-End Development and he really wanted to take SoBold forward. Leo championed innovation in our development approach and much of the workflow we do today has been driven by Leo’s desire to set the highest of standards.

He is a key figure at SoBold and we are very fortunate to have him.

We caught up with Leo to find out more about what he get’s up to in his day-to-day life!

At what point in your life did you decide to become a developer?

During middle school, I tried to learn how to make games, which led me to development. I started exploring different languages and realized I really liked learning the syntax of as many languages as I could. Eventually, I got into web development, and since then I have tried to expand my knowledge of web development languages, trying out new frameworks, and both front and back end sides.

Describe your typical day

As of now I’m trying out double gym days, which means an early wake up (5.30am), gym at 6am, and finishing at around 8am. Then I go to work, have my day, and when I finish I go home and back to the gym. When I get back home it’s circa 8.30pm, so I have dinner, watch something on Netflix (not too much otherwise I end up snacking), then go to my room, and if there’s time and I’m not too tired I play piano, otherwise I go to bed ready to do it all again. 

What’s your favourite project to date

Favourite project to date is Rede partners

Any advice for junior developers?

Never stop learning, be curious, and be always ready to challenge yourself, and question what you do. Change your way of doing things if someone else out there is doing it better.

If you had to change careers what would you do instead?

Theoretical Physicist or Volleyball coach

What was your most recent challenge and how did you overcome It?

Hit a plateau in terms of motivation, but managed to overcome it by getting less on my plate, and focusing on meaning, eventually, it became better.

What’s your favourite thing to do outside of work?

Workout, play music (piano, guitar), play video games (fav ones are Skyrim, Horizon Forbidden West and Fallout)

How do you think the designer/developer relationship could improve?

The main thing is communication and chemistry, once those are there the relationship improves by itself.

Would you like these insights straight to your mailbox?

Your emailSubmit

I consent to my submitted data being processed and stored by SoBold in compliance with Privacy Policy

Making the best possible choice of content management system (CMS) is crucial for the success of your website. But, these days, not only do you have to navigate the many different options – from WordPress to Sitecore to Webflow – you also have the added challenge of deciding whether to go “headless” or not. 

Whether to take the less conventional headless approach with your CMS is a decision that could cause some confusion. It could even cause some challenges with your website if you end up making the wrong choice.

In this article, we’ll help you understand exactly what a headless CMS is, when you may need to take that approach, and highlight some key considerations to make before finalising your choice. 

What is a Headless CMS?

With a traditional CMS, the back-end and the front-end of the system are directly linked. This is how you use your CMS for both the content management (back-end) and to control how the content is presented to your website visitors (front-end). 

In this context, the back-end of the CMS is sometimes referred to as the “body” and the “head” is the front-end. In a headless CMS, that front-end is decoupled from the back-end of the system, hence the term headless. With this approach, you use the back-end as normal for content management and the presentation of content in the front-end is handled completely separately. 

This is valuable because it allows you to design your website front-end however you like, without any restrictions. However, it also requires more technical work from your development agency as a trade-off. 

With a headless CMS, your content is presented to your audience on your live website by using APIs that take it from the back-end of the CMS. This use of APIs also allows you to publish the same content in a variety of different formats via different channels as well, but more on that later. 

Scenarios in Which You Might Need a Headless CMS

It’s important to understand that you should only take a headless approach if it’s the most suitable way to meet a specific set of requirements or objectives.

Some scenarios in which you might need to take a closer look at adopting a headless CMS include: 

If a large volume of content is a key component of your marketing strategy. 

If you’re going to be producing and publishing a lot of content on your website, you may benefit from a headless CMS. Many people find it easier and more intuitive managing websites in the back-end of a headless CMS.

The decoupling of the front-end also means that your development agency will be the ones responsible for ensuring your audience is presented with dynamic, engaging content. 

If you expect to have high volumes of traffic and need to maintain performance. 

If the size of your website’s audience will put a heavy demand on your CMS’s performance, a headless system could be a worthwhile investment. Using APIs, and leveraging other intelligent techniques, the headless approach often delivers faster loading times, reduces the workload on your servers, and offers greater scalability.

If you have a multi-channel marketing strategy, or need to publish content across multiple digital touch-points. 

The headless approach allows you to take one piece of content, upload it into the back-end, and seamlessly publish it across several channels, including website, mobile app, social media, email, and even internet-of-things (IoT) devices.

This can help you maximise consistency, while providing your users in each channel an experience optimised for their preferred context.

If you’re prioritising personalisation. 

As personalisation is becoming much more important in modern marketing, headless CMSs are becoming more popular in enabling those tactics. 

If you need to create personalised experiences for your website visitors based on their demographic data, past behaviour, preferences, and so on, a headless CMS may be the right option. This is a useful approach for delivering tailored content to individual visitors, improving your engagement and increasing conversions.

If you have a multi-lingual or multi-regional website. 

Delivering the same content to visitors in different languages, across different locations, can also be made easier by using a headless CMS. Your localisation process can be streamlined by managing the content for all users just once in the back-end, then delivering it seamlessly in its different forms based on location or other conditions. 

Key Considerations and Potential Pitfalls

While a headless CMS can be a great choice to deliver on the requirements discussed here, it’s still not a straightforward decision in these scenarios. 

Firstly, it’s important to note that a traditional CMS like WordPress can still help you achieve all the things listed above, especially with the support of an experienced, talented agency. Secondly, there are some downsides to the headless approach that need to be considered while you’re evaluating your options.

Security

Security is an issue that needs careful consideration when looking into the headless approach. The headless architecture, and use of APIs, create more security vulnerabilities than you’d have with a traditional CMS.

It’s also common for a headless CMS to require more hands-on management in key areas such as hosting and compliance, as well as more thorough and frequent testing. 

Development Complexity

When you ask your development agency to build, manage, and maintain your website using a headless CMS, you’re asking them for more complex work than they’d be facing with a traditional system. This complexity is something you need to be aware of, both in your selection of an agency capable of delivering your requirements, and in the additional workload you’re asking them to complete for you. 

Time-to-Market 

Following on from the previous point, more complex development work often results in a longer time-to-market for your website. 

Developing a website using a headless CMS may require more time and resources from your agency to deliver the work for you. If you need to get your site up and running quickly, or if you may require future development work to be delivered quickly, a regular CMS may be a safer bet. 

Technical Skills 

Publishing content with a headless CMS may be easy, but if something goes wrong, or you need something changed, you’re unlikely to be able to do it yourself. A headless CMS requires more technical skills and development experience to maintain than a traditional CMS, even for small tasks. If you don’t have these skills in your team, you’ll be more reliant on your agency partner than you would be with a normal CMS.

Total Cost of Ownership 

All the points listed here will add up to a higher total cost of ownership (TCO). When accounting for the higher volume and greater complexity of work you’ll require from your agency, you’re likely to spend a lot more of your budget on a headless CMS. 

Unless you have specific complex requirements that demand the use of a headless CMS, it’s usually the more cost-efficient option to go with the more traditional approach.

Content Strategy

With all that said, it’s also important to consider whether a headless CMS is even necessary based on your content strategy. 

Unless you have an intricate, wide-ranging content strategy that spans various channels and platforms, it might not be worth adopting a headless CMS at all. 

Most of the requirements you have can likely be delivered by working with a reliable agency partner using a sophisticated, flexible CMS like WordPress. 

It’s also important to note that WordPress can be used in a headless context as well. This offers you a balance between a familiar, easy-to-use system and a more dynamic UX for your visitors in the front-end.

The Benefits of a Headless CMS 

If you do decide to take a headless approach, your CMS can deliver a wealth of benefits and strategic advantages. These include: 

Scalability

The headless architecture will enable you to build out your digital presence rapidly, on a large scale, across multiple channels. This scalability will be crucial for your website as your business grows and your requirements evolve. 

Customisation

Both the back-end of your headless CMS and the front-end presentation of your content are entirely customisable, tailored to your specific requirements. 

Flexibility

Headless CMSs provide a great deal of flexibility in terms of your selection of technology, content creation, and implementation of a multi-channel market strategy. 

Ease-of-Use

If you work with a skilled agency partner who can set up and manage your system for you, publishing and editing content with a headless CMS becomes quick, easy, and efficient. 

User Experience 

Delivering your content seamlessly – and consistently – across a wide range of channels and digital touch-points creates a far greater UX for your target audience. 

Performance

The headless architecture removes the need to render pages on your server. This creates the faster loading times and improved performance discussed previously, which also contributes to a better experience for your visitors. 

Competitive Differentiation

As mentioned earlier, the headless approach allows you to create a truly unique UX. In an increasingly crowded, noisy online landscape, this can help you differentiate your website and stand above your competitors. 

Future-Proofing

A headless CMS allows you to easily change or upgrade the technology you use for your front-end without having any impact on your back-end. This will help you become more agile and adapt quickly as new technology trends emerge in future. 

Making the Right Decision for Your Unique Requirements 

Ultimately, you should base your decision here on the specific requirements you have for your website and the circumstances you find yourself in. 

While a headless CMS does offer a range of innovative capabilities, the additional costs and resources you’ll need to invest may not be worthwhile. For example, the traditional use of WordPress can provide you with most of the benefits discussed earlier.

Carefully consider your objectives, your strategy, and the resources you have available. Use those to weigh up all the pros and cons listed in this article in relation to your own website project.  

The key thing is to clearly understand exactly what you need from your CMS, and use that to select the option that aligns best with your requirements.

Would you like these insights straight to your mailbox?

Your emailSubmit

I consent to my submitted data being processed and stored by SoBold in compliance with Privacy Policy