Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Dec 29 2020
Dec 29

As the needs of individuals and businesses keep evolving, so do Content Management Systems. A CMS facilitates the creation of a digital empire, providing all the basic infrastructure needed to create a website. A traditional or coupled CMS is where the front end and the back end are bound together. This means that the developers working in the back end and the users experiencing the front end interface are both interacting with the same system. In comparison, a headless CMS is where the front end and the back end are managed separately. 

Choosing the optimum CMS for your business

Before we go on to understand when to choose headless CMS and the right way to do it, it’s important to understand the provisions of coupled CMS, the right way to choose it and when you should stick to it for all of your web development needs. The right CMS should reflect your agendas and objectives seamlessly through your content. It acts as a bedrock on which the content of your business is built upon, hence choosing the right one is crucial.  Following are the points that should be kept in mind while you narrow down on a CMS - 

  1. Identifying the core functions that your business needs is central to the idea of selecting a CMS. A little foresight is required to avoid any glitches in the future. For instance, if your business deals with rolling out similar kinds of content at regular intervals, easy to use templates can prove to be quite beneficial in the long run, as a bulk of repetitive work is easily automated. Similarly, if you are looking to expand your website into several domains in the future, omnichannel support is what you need to look out for. 

  2. If your business requires several people to login and post content on your website or make changes to it, it is essential that you choose a CMS that is not too complicated in its functionality. It should be easy to use even for the non technical teams.

  3. With users streaming content from several devices, the website must contain the provisions for being mobile friendly at the least. According to a Socpub survey, 57% users would never recommend a business if it had an incompetent mobile website. With UX (User Experience) gaining higher priority online, a CMS must be inclusive of the demands of its users and should also hold the potential of fulfilling those.

  4. The CMS must include the analytics parameters in its interface, or include the provision to team up with Google Analytics or HubSpot for a comprehensive analysis of your business.

  5. If you see your business making use of forms etc. to fill in surveys or feedback, User Interaction is another area that you need to consider while picking up a CMS. Does it provide this service? Or if not, does it enable third party integration for chats or comments

These sum up to the fact that along with user friendliness and utility tools, scalability and flexibility to adapt to various changes in the future are also essential features for a CMS in an ever changing, ever evolving world. Lastly, and most importantly, also consider how secure a CMS is and whether you can trust the system with all the data you’re uploading on it. 

Benefits of traditional CMS

There are some key areas where a traditional, coupled CMS still works the best. You need to look out for one if -

  1. You are a small business with limited operation that doesn’t require a bunch of diverse tools. If your content is largely monogamous and unidirectional, or if you’re in the pre alpha phase of your business and the focus is mainly on experimenting with content and greater investments aren’t supposed to be made presently, a traditional CMS will work the best for you. 

  2. Your primary deliverable is content, hence your team doesn’t comprise developers and coders. One of the benefits of traditional CMS is that it is  easily the most convenient, as it comes loaded with all the basic tools that one could possibly need. The coupled architecture of the website increases responsiveness and bugs or issues are less likely to happen, giving you a seamless workspace.

  3. Presentation or graphics aren’t the centre stage occupants in your business, and are lower on the priority list. If a compromise on the visuals doesn’t affect your brand because your focus areas lie elsewhere, go for a traditional CMS. The effort that goes into making a headless CMS functional isn’t worth your time and money in this case.

  4. Lastly, budget constraints can also be a viable reason. If you resonate with point number one, ie, you’re a small business, chances are that you are bootstrapped or haven’t been funded yet. The benefits of traditional CMS include availability of the core functionalities and the subtraction of any hassles of hiring developers, and also the associated costs, hence in this scenario, it might be the one for you.

Apart from these, editing and customising page layouts with minimal technical knowledge is also a big pro in traditional Content Management Systems.

When to choose headless CMS?

However, you need to check the underlying differences in the monolithic and headless architectures. The one size fits all approach will not work for a number of businesses out there, and that will happen when a coupled CMS doesn’t turn out to be inclusive of all the needs of an enterprise. These days content has become a really diverse term, encompassing various kinds of outputs needing different delivery channels. If you’re wondering why to choose headless CMS, you can consider going for one if -

  1. You are dealing with diverse content. If your business is looking to publish to different channels, the flexibility that your website needs will articulate only when you use a headless CMS. Although a traditional CMS can also publish to multiple channels, it is embedded into the very design of a headless CMS, making the delivery much faster and the final output much more user friendly. At one click, you can publish content that is accessible in the form of non web content (like a mobile app), an e-commerce website, digital signage, IoT etc. 

  2. You prefer a central nodal location to deliver content across channels. Any inconsistencies in the published material are ruled out as the source remains unitary, which might be a potential risk while using traditional CMS. Also, owing to these functionalities of a headless CMS, you never lose track of the market velocity and your content remains in sync with the demands of your users. 

  3. Your future plans include expanding into different verticals, or are, better yet, undecided. Since the technological sphere keeps changing and upgrading at the drop of a hat, it is very natural for you to want to implement bigger changes on your website down the lane. A headless CMS gives you enough space to scale your website, hence, in a way, future proofing it. So if the game plan isn’t crystal clear, a traditional system could prove to be too restrictive and you might fare better utilising these benefits of headless CMS.

  4. You are an organisation with its core focus on User Experience. If your business wants to build a truly differentiated customer experience, you will benefit immensely from researching on how to choose headless CMS that fits your needs and making it your core software. With enough tools at your disposal to survey and analyse what your users want, you could go berserk with creativity. Such provisions aren’t present in a traditional CMS.

  5. You have, or are, a team of developers. Headless CMS is, without a doubt, a piece of heaven for developers. One of the many benefits of headless CMS is that it is frontend agnostic, translating to custom, efficient coding to tackle any issues. Moreover, the developers aren’t limited by the tools provided in a traditional CMS and are free to tailor anything that adds to their productivity.

Keeping in mind the changing nature of the web world, CMS that initially started out as a traditional system have been branching out and expanding their use case by facilitating headless or decoupled versions of themselves. 

A good example of a proficient headless CMS is decoupled Drupal. In this variant of Drupal, one can work seamlessly even with relatively low Drupal specific knowledge, and make use of multiple new functionalities like nodal content delivery, enhanced performance parameters across channels, the leeway to create custom interfaces, and align their UX to the preference of their target audience. With its backend secure and its front end agnostic, Decoupled Drupal focuses on giving you the best of both worlds, backing endless possibilities of content creation and delivery. 

Graphic using green and orange texts and boxes to structurally compare traditional and headless CMS


Challenges of headless CMS

However, before finalising one, you might want to look out for the following concerns regarding a headless CMS -

  1. The simplicity of the CMS goes for a toss. With increase in tasks and technical scenarios, a headless CMS isn’t as simple to use as a coupled one, where all the tools are pre made and are at your disposal. It would not make the cut if your business requires multiple people interacting with the website on a daily basis, as it would get too complicated for most. 

  2. To work with a headless CMS you would need to be a developer, or have the financial capacity to hire one. Hence, if you are a small team and don’t have enough resources to allocate to developers, a headless CMS would be too far fetched of an investment. Since it requires building the front end presentation templates of the website, mobile apps, etc. working on making a headless CMS functional necessitates the need of technically proficient resources,

  3. The perfectionist in you wouldn’t like the fact that you can’t see a preview of what the final content will look like while working on a headless CMS. Most marketers prefer having a beforehand idea of the visuals of the published material, and a CMS with no presentation template will pose a problem in this case.

  4. Lastly, you might not need it. A flexible front end means deployment of ample time and monetary resources towards creating things that already are present in a coupled CMS. If the investment isn’t worthy enough for your business or doesn’t have sufficient ROI (Return On Investment), the challenges of headless CMS will outnumber its benefits.

Conclusion

The trajectory at which you plan your business to progress is something that should determine crucial Ifs and Buts of choosing the perfect Content Management System. Your business needs to go headless only if it fits in the path you’ve chosen, and even then, at your predetermined pace. 

Dec 17 2020
Dec 17

Open source is gradually sliding into the workspace of most developers these days, as they prefer a model that listens to their needs, and is also something that they can exercise some control over. As opposed to closed source where only the management can change, edit, and contribute, open source welcomes all opinions - from all nooks and corners of the world. 

Why open source?

In recent times, we’ve been seeing a number of big companies using open source software (OSS) in business and preferring it over the proprietary model. This shift can be attributed to multiple reasons.

Working with open source translates to minimal costs and time incurred in surveying and researching on market-needs discovery. As the software is accommodative of all the suggestions that developers make and even lists out the best contributions, open source becomes a self sustaining model with outpouring innovation. Hence, a reason why open source is good for businesses is because it consequently relies much less on its own internal resources, and is free to tap the ideas that make their way in externally. 

It generally sees a greater diversity in its contributors, ranging from academic researchers to full time developers. This leads to the inclusion of a wide variety of themes and modules, and the approach becomes quality driven. This increases the market competitiveness, thus reaping long term benefits. These are the primary grounds due to which open source adoption statistics have been soaring in its favour.

But, why contribute to open source?

Multiple reasons have been identified as to why big companies that use open source find it in their best interest to contribute to it. In the diverse community of OSS users, corporations find greater innovative capability, and the relationship turns symbiotic. There exists a give and take of ideas from which the entire pool of users, companies using open source in business included, benefit from. It also becomes a passive form of CSR (Corporate Social Responsibility), as a little shared goodwill never hurt anyone. 

Apart from that, being in close proximity to the market of end users acts as an innovation catalyst. A recent McKinsey report talks about this phenomenon called ‘Developer Velocity’, referring to the act of enabling developers to create an environment and a subsequent methodology where their talent is left free of any friction - which results in newer, fresher, unbound ideas.

Open source, hence, demarcates itself clearly from stagnation. Companies that use open source software don’t lose their hair worrying about going out of fashion. Every time the market undergoes a change, it is sure to be reflected in the OSS by its community. The end result is a mutually beneficial relationship, where the company stays up to date with all market fluctuations and demands, and it gets updated whenever there arises a need - becoming a repository of high utility modules. Read more about the perks of being an open source contributor here.

Impact of large companies on open source softwares

During recent times, the open source community has seen quite a bit of infiltration from big players in the market. Large companies venturing into open source is on the path to become the norm soon. These companies are some of the major vendors of open source - 

  1. IBM has turned out to be pretty resourceful with various OSS projects, contributing to a list of platforms like Hyperledger, Kubernetes, Node.js, Egeria, etc. IBM also has a training program for OSS contributors, and goes the extra mile by sponsoring various OSS projects.  
  2. Google broke the ice by creating Kubernetes in 2014, an open source container orchestration system that automates a bunch of manual work done in managing and scaling applications. Presently, under Google Summer Of Code and Google Code In, Google invites University and high school students respectively to intern with them by contributing to different OSS projects. 
  3. Facebook’s most notable open source creation would be React Native, a mobile application framework - used to develop various applications for diverse platforms. Other OSS projects by Facebook include Hermes (javascript engine created to run React Native on Android), Detectron2, Hydra etc.
  4. LinkedIn runs a large number of OSS projects under LinkedIn Engineering - some of which are Ambry, LASER, Helix and Kafka. Apart from contributing to OSS and using OSS in business, LinkedIn also maintains a dedicated blog for the articles related to it, and a separate tab enlisting all the research work on OSS that LinkedIn community has contributed to.
  5. HPE and Intel are working on Network Functions Virtualisation(NFV) for 5G installations, partnering with open source platform RedHat for the same. 
  6. Another alliance on the frontline is that of Apple, Amazon and Google - working together under the Connected Home over Internet Protocol (CHIP) project to create an all-in-one smart home device, and in the process, share and use each other’s resources. 

Talk about the open source community is incomplete without the mention of GitHub, a software development platform that boasts of being the largest in the world. Microsoft’s acquisition of GitHub goes on to show that large companies are seeking to become major vendors of open source and are ready to invest large amounts of capital in the same. 

Hence, in the open source platforms that we see now,

  • Scalability is high - owing to cyclic contributions that not only keep the resources from stagnation but also constantly add value to it.
  • Sustenance is dependent on contributions - which might be voluntary, sponsored, or both. Since its users are also its contributors, open source leads to exemplary results with minimal investment on creating and updating its own resources.
  • Bug resolution is done by the users themselves. Constantly identifying errors and shortcomings keeps the site updated. Newer versions are tested, approved, and rewarded within the community. 

Seeing through the eyes of Drupal Community

Dries Buytaert, founder and project lead of Drupal, in one of his personal blogs, identified that open source communities are seen to be working at a steady pace even when the world suffers from recession. A collective purpose and associated ethics are the main drivers of OSS, making it resilient to external factors.

According to one of Dries’ blogs, Who sponsors Drupal development? (2019-2020 edition),  contributions to Drupal keep increasing by each passing year. The Drupal project has gained from the contributions by big companies that use open source like Capgemini and EPAM systems. Dries notes that even though the contributions from tech giants lag behind considerably when compared to the traditional Drupal businesses, he hopes to see a dramatic shift in the coming future. Apprising large enterprises about the value of contributions to large open source softwares like Drupal will go a long way. Moreover, providing better incentives can also play a huge role in increasing contributions from big companies, he feels. 

Bar graph with blue, green, and black vertical bars showing statistics on contribution by large companies on open source projects and Drupal in particularSource: Dries Buytaert’s blog

Open source has been a revelation during coronavirus pandemic. The Covid-19 pandemic couldn’t put a stop on the development of the Drupal project. #DrupalCares campaign proved successful as a number of organisations and individuals helped raise $500,000 in just over 30 days. This shows that OSS is treated as a public good - something that is non-rivalrous, and can be used by and benefits everybody. Instead of racing against each other, users of open source run together, and share its responsibility.

The future of open source communities 

More than a new concept, open source fits in like an upgrade to the software world. It is the beginning of a virtual workspace that is very user friendly and has the potential to achieve maximum consumer satisfaction.

Open source communities have also responded to the COVID-19 crisis with much responsibility, participating in and contributing to the COVID-19 Global Hackathon. Giants like Facebook, AWS, Twitter etc. have gone ahead and shared resources to assist the participants. Also, a number of open source collaborative projects have shown up to tackle problems that the world is dealing with right now, creating digital solutions as an effort to minimise the effects of the coronavirus pandemic. 

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web