Upgrade Your Drupal Skills

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

See Advanced Courses NAH, I know Enough
Feb 26 2021
Feb 26

This is the first of the two-part series on ‘Formulating a business case for a new CMS’. The first part debates on open source CMS and proprietary CMS. The second part will discuss various other factors that are to be considered before opting for a new CMS for your business.

A successful business is resultant of an array of decisions, whether big or small, leading to its conception, formulation and finally, execution. With digital being normalized to the extent where it is the only way we know of to access a ton of products and services, a solid online presence has come to be of utmost importance for a business. A lot of times, businesses prefer going for a CMS (Content Management System) instead of building a website from scratch, as a CMS gives you a pre-built website, good to go as it is, or easily customisable even without having a dedicated team of developers and related coding knowledge.

What are the options?

The first step towards making a business case is to weigh your available options side by side. As a business choosing a new CMS, you will be rendered the following options -

A) Proprietary Model CMS

A CMS built under the proprietary backdrop will have a unitary ownership. Every tool and feature available will be created and listed by the owner organisation, and will be served to the end user in a transactional manner, with not much deliberation involved as everything sources back to one single origin. 

B) Open Source CMS

On the contrary, in an open source CMS model, apart from a few core features, contributions are invited from everybody. The model opens up avenues for discussion and innovation for its end users thus forming the likes of a community, working together for the greater goal.

Due to the community benefits that come along with an open source CMS, recent statistics point towards an increase in inclination towards adopting an open source model for a business.

blue and pink bar chart analysing the likelihood of large companies to opt for open source cmsSource : The New Stack

The said benefits can largely be summed up in the following points.

grey chart with blue lines mapping the benefits of open source adoptionSource : SASwhite chart using blue lines to map the customer benefits of using open sourceSource : SAS

Business Case : Open Source CMS vs. Proprietary CMS 

For a better understanding of the business case for a CMS of either kind, let’s compare from various dimensions the features of Open Source and Proprietary CMS models with a business point of view -

The Costs

In a proprietary model, since it is the organisation that bears all the cost of maintenance, addition and subtraction of features, upgradation and bug fixation, it will recover these expenses in the form of subscriptions, licenses etc. You might need to pay yearly renewal fees or monthly usage charges. Along the line, be prepared for cost surprises, as they may initially be hidden, but will pop up soon enough.

If you’re wondering why to choose an open source CMS in this case, it is because it’s free to use with no charges in the form of subscriptions or premiums.

Hence, both the models do need some form of monetary support, and it is the business owners’ call what they want to invest their money on. 

Customisation

With the homogeneity that comes with proprietary CMS models, also comes rigidity in terms of customisation and personalisation, since there’s very little that is left to you for deliberation. Hence, if your business thrives on establishing unparalleled user experience by tapping on features like personalised feed and customisable layouts, go for open source. An open source model remains connected to its user base owing to continuous contributions and ongoing discussions within the community, making the field research for customisation much easier. 

On the other hand, if your requirements do not place much focus on the look and feel of the site, and rather banks on niche content for niche audiences, the associated costs and effort that comes with customisation is not that high utility for you and this is when to choose a proprietary CMS.

Complexity

Needless to say, all the additional features and tools make open source CMS unnecessarily complex. A small business with limited resources might find it too overwhelming to delve into web development especially if it is not their calling. However, the open source community, like that of Drupal, for instance, is available at your disposal any time. Just leave your questions in the dedicated forum, someone from the Drupal Community, that comprises millions of members, would surely revert. Or, if you wish to get web performance optimisation services or support and maintenance services, you can also partner with a digital agency which specialises in Drupal. In the case of proprietary CMS, with a single vendor to reach out to, things can be streamlined here as well.

Reliability

A proprietary CMS is a one-stop-shop experience, everything is handed out to you at once and you have very little to worry about if your area of expertise lies elsewhere. You can certainly rely on it in customary scenarios where you’re looking for greater stability of the product. But what must be kept in mind is that the ownership decides the lifespan of every service offered, and reliance takes a hit if the products you’ve based parts of your business on are changed opposite to your liking, or even removed. You also need to rely on the owners for bug fixes.

On the other hand, in case of an open source CMS, when our surrounding technology sphere undergoes change, open source is the first to reflect it, as it consists of users, and more importantly, contributors, from all across the globe. It gives one the freedom to work on a part of the software that is useful to them, hence creating their own safety net.

Security

Proprietary CMS models bank on security by keeping their source code under wraps, which might backfire as any bugs that creep into the source code will remain hidden from the public eye as well. Although the source code being open in open source models has drawn speculation, it is widely known for bug fixes being very prompt as multiple hands are working constantly to make it error free. Snyk found out in one of their reports that there were lower vulnerabilities reported across popular open source ecosystems, and that there was an improved security mindset within open source organisations. 

Bulkiness 

Proprietary software packages come in a bulk, installing various components that you might never end up using, as choosing exactly what to install isn’t everybody’s cup of tea. Open source softwares are based online, taking up negligible computer storage space. If bulkiness is your area of concern because you already have a lot of bulk on your plate, closed source might add to the problem.

Expertise Required

Open source is a developer’s paradise. If you have the expertise to work on an open source software or can afford people with the needed skills, nothing like it. However, if your website requires multiple people being on board to handle the content on a regular basis, it might not be the best choice for you. A closed source software doesn’t need any technical knowledge or coding skills to work seamlessly, while open source does. People with little to no technical experience can also work on proprietary software.

Innovation

The flexibility and space for innovation that comes with an open source software is unparalleled. Open source is like a self service buffet, each user is free to take what he or she wants, but it does not end there. New ideas for the betterment of the software and the community are always invited. In comparison, closed source models have a few people deciding on the features of the software, so it is impossible to cater to everybody. If your business’ future is to thrive on change and creativity, it is best to go for an open source model to avoid a fix in the future.

In open source communities, we see newer ideas and technologies on the ground not only sooner, but also on a continuous test drive with multiple technicians already working on the issues as soon as they’re detected. Open source CMS Drupal has held quite a starry record in unleashing new trends and making those functional as an open source platform. Macro trends in the industry like Continuous Delivery for superfast project deliveries, microservices infrastructure for small, autonomous services and machine learning for ‘intelligent’ web development’ have been brought to good use by Drupal. Hence, newer technologies see optimum utilisation with the backdrop of an open source community. 

Most importantly, the satisfaction of working with open source and contributing to it

Contributing to open source also has a plethora of hidden, indirect benefits. A company that is known to contribute to the common good is sure to build a positive, welcoming and compassionate brand value both within and outside the company. Developers involved in working on the open source components would be interacting with similar abundantly skilled people from all around the globe. Hence, not only is open source the right thing to do, it is equally exciting and challenging to work on. A person constantly interacting with the community is bound to gain a lot of dynamic experience, leading to a much faster growth rate as compared to a stagnant worker. And at the end of the day, one walks home satisfied and content with the feeling of having contributed to the bigger picture, to have fulfilled a bit of their own social responsibility. 

Companies as big units also find it important to provide funding to the community as a part of their CSR (Corporate Social Responsibility). Since they derive so much in terms of components and knowledge from the open source community, it only makes sense at the end of the day to give back to it. More on large companies' preference for open source here.

Drupal as an open source software has time and again seen how contributions and community engagement keep the platform afloat. Drupal acknowledges each contributor by issuing them credits for their work, and derives essential data from the trends of contributors. For example, if they see minimal engagement from a social or ethnic group, the inclusion statistics are likely to be revisited in order to analyse whether Drupal is accessible to everybody to engage and contribute in. Drupal also states in its Values and Principles that the bigger goal is to foster a learning environment leading to collaborative decision making and overall excellence. To know more, take a look at what makes open source recession proof, how it has tackled Covid-19 problems, and how Drupal stayed on top in the coronavirus pandemic.

At present, Drupal receives contributions from thousands of organisations and individuals who believe in the power of open source. Learn more about the approaches and perks of contributing to Drupal here.

Conclusion

The process of choosing a new CMS should be undergone carefully after thorough analysis of every aspect of the business cases for different softwares. The CMS is what you choose to represent and associate your brand image with, hence it should do justice to your goals, agendas and vision.

Feb 22 2021
Feb 22

Today, everything is being done online. If you are not online, you just might be considered antiquated. From social media to e-commerce, every aspect of the online world is, thus, improving by leaps and bounds. We are benefiting from these advancements, so no complaints there. 

All the advantages that we are able to reap from the online world, from the websites we so eagerly use, are dependent on a particular system. This is the system that they are built on, the more versatile it is, the better the website’s versatility is going to be. And this is exactly what we expect from our web experiences and the system provides almost every time. 

Drupal and Contentful logos can be seen together.


It is the Content Management Software, I am raving about. There are plenty available for the developers to choose from. However, we’ll be talking about two of them in particular, comparing them actually as they are strangely a bit alike and a bit different too. These are Drupal and Contentful. So, let’s begin.

Parameter

Drupal   Contentful Market Share  Founded in 2000, Drupal has a substantial market presence, with a million sites using it  Launched in 2013, Contentful’s market share is impressive too Decoupled Architecture  Drupal offers efficient decoupling with an API-first infrastructure  Decoupling features are similar to Drupal

Performance and Scalability 

If optimised properly, Drupal provides impeccable performance and limitless scalability  Contentful offers great performance too, however, it poses technical limitations Security  Quite reliable and the most secure open source CMS with a proactive community constantly working on issues  Good, however, bugs can be a common occurrence Content Workflow  The content modelling and editorial experience is wholesome for the authors, Views system being the highlight Contentful works differently, but offers an equally wholesome experience to content authors Pricing  Free to install and configure, there can be other costs depending on the scale of the project  Not free, being a proprietary software, has a standard monthly cost to be paid Third-party Integrations  Integrates seamlessly with third party tools and application  Matches Drupal in this regard Community  The Drupal community is over a million and growing  Contentful does not have such a wide community, but its Community Plan is a step towards it Migrations  Difficult in the past, but a breeze with the launch of Drupal 9 The CLI tool helps in migrations, making them automated Responsiveness  Designs, themes, images and tables, everything is mobile-friendly with Drupal  The responsiveness to mobile devices is quite impressive as well. Multilingual  Translates content, configurations and interfaces in over 90 languages Offers translation services similar to Drupal, but in 30 languages Accessibility  Drupal follows WCAG 2.0 and ATAG 2.0 guidelines for accessibility  Contentful follows WCAG 2.1 guidelines SEO  Drupal has a module for every SEO need, be it keywords or links Contentful also supplements SEO needs, but it is dependent on the creation of dedicated content types

Understanding the CMSs and their abilities 

Drupal, leading as an open source  

Drupal has been around for two decades. The 15th of January 2021, marked its 20th birthday, being around for this long, it has mastered all the nuances of content management and digital experiences. It is a digital experience management system that has the potential of driving web content onto multiple platforms to provide personalised experiences that would allow your users to connect with your organisation.

The kind of content management tools Drupal comes with are not only sophisticated, but also stimulate perpetual innovation. The great thing about Drupal isn’t its numerous modules, themes and templates, even though they are great too, but it is the fact that Drupal is open source and accessible to far more people than a proprietary software would be. 

A line graph is showing Drupal usage statistics. Source: BuiltWithA table is showing the number of sites using Drupal at different points of time.Source: Drupal.org

Contentful, not the conventional CMS

Contentful was founded in 2013 by Sascha Konietzke and Paolo Negri in Berlin. It hasn’t been around as long as Drupal, but it isn’t the new kid on the block as well. In simple terms, Contentful is a content infrastructure, a platform that would allow you to create, manage and distribute content to any platform. 

This pretty much sums up the definition of a CMS. So, why did I say Contentful was not conventional?

Other CMSs, Drupal included, come with out-of-the-box content models that you have to choose from. However, with Contentful you have the liberty to create your own content models and you get to decide which content you want to manage. The RESTful APIs provide you the ability to deliver your content across multiple platforms, including websites, mobile apps, be it iOS, Android or Windows. From Google Glass to infinity, it is your pick. You can utilise the potential of Contentful on your own or a team. The uncluttered UI makes assigning custom roles and permissions a breeze. Contentful is a modern content platform that paves the way for faster launches.

A bar graph shows the market share of Contentful in different countries since it was founded.Source: BuiltWith 

Drupal vs Contentful: Putting them under the microscope

How efficient is decoupling? 

Usually a CMS is equipped to manage content in the backend and push it to the front-end templates that essentially provide the desired user experience. This meant that a CMS served as an all-in-one system that provided for all the development needs. However, that is changing with decoupling, where-in the frontend and the backend are two different entities, independent of each other.

Drupal 

With Drupal, you can decouple the frontend from the backend where you want to, making the content become reusable chunks that are independent of the presentation layer and always prepared for delivery to as many sites and apps.

When you decouple, you get the benefit of Drupal’s presentation-neutral content. The REST API, GraphQL, JSON:API and all the different alternatives that you get in decoupled Drupal ecosystem to build a front-end as you want, with any technology you want, is amazing

These are a few of the tools and frameworks that decoupling Drupal would allow you to take up and build interactive sites and apps. You can get the complete insights on what frontend technology to use with decoupled Drupal architecture here.

You also get the opportunity to future-proof your project by refreshing designs without re-implementing the entirety of the CMS.

Contentful 

Since decoupling is dependent on one principle, that is the separation of the frontend from the backend, I wouldn’t say that Contentful is all that different from Drupal in this regard. 

  • It is an API-first content infrastructure.
  • It makes front-end layers less rigid and more versatile, with a number of tools and frameworks.
  • It acts as a content repository delivering your content.

All of this is achievable through Drupal as well. What is different are two things;

  • It has its own Contentful API, delivered through a CDN, while Drupal operates on RESTful APIs, JSON and GraphQL. 
  • Next is the fact that Contentful uses an approach known as JAMstack, JavaScript, APIs and Markup; while decoupled Drupal uses MERN, MangoDB, Express, React, NodeJS.

There are also chances of API requests turning wrong. When that happens, the Contentful server will automatically create an error, with an appropriate HTTP status code in the header along with a JSON response in the body. 

How reliable is the performance and scalability?

Drupal 

Drupal comes equipped to handle any and all performance scalability needs an organisation might have. However, it would only be able to do that if you optimise it properly, that is a contingent for scalability. 

For instance, sites operating on Drupal 8 and later versions come with tools that will allow you to scale on the frontend and the backend. 

Blazy
Content Delivery Network 
Server Scaling 
Site Monitoring tools 

All account for a better performing Drupal site that is always ready to accommodate for traffic spikes and content growth making your site always available. To know more, read these comprehensive guides to Drupal performance optimisation techniques and scalability provisions.

Contentful

Contentful was made to scale to compensate for your site’s growth much like Drupal. It has taken into consideration all of the dimensions of growth that a site or app may face and categorised them into seven categories.

It is prepared to handle 

  • heightened levels of traffic, data and usage; 
  • the addition of more projects, products and channels; 
  • an increased level of complexity and sophistication in use cases;
  • an expansion in global markets; 
  • an elevated number of internal users; 
  • an enhanced pace of development; 
  • and cater for an advanced level of security for business perpetuity.

At the end of it all, Contentful comes with certain technical limits upon the infrastructure. These are enforced to mandate a lack of interruption on the shared-service infrastructure functions, however, they are limits all the same. Reading them before using Contentful would be wise.

How sufficient is the security?

Drupal 

In terms of security, Drupal is on the higher level of sufficiency, if not the best. The kind of features it comes equipped with make it a frontrunner. A Sucuri’s report even showed that Drupal is amongst the most secure open source CMS out there.

Drupal security is very competent because of; 

  • Its expert security team, adhering to the guidelines set by Open Web Application Security Project; 
  • Its community, being proactive and analysing any security issues; 
  • Its implementation of a secure access through strong passwords that are even encrypted;
  • Its secure codebase; 
  • Its control over the most trivial user access; 
  • Its encrypted database; 
  • Its APIs, ensuring validation of data and preventing malicious entry. 

Contentful 

Contentful almost competes with Drupal in terms of security, I have used the term almost because there is a catch. 

Talking about the positives, Contentful’s security infrastructure is based on Amazon Web Services, making it quite impressive. 

  • It has ISO 27001 compliant data centres; 
  • It comes with data storage, that is encrypted at rest along with an encryption of all forms of communication in transit; 
  • It comes handy with a web application firewall, brute force prevention, data retention policy, threat detection and two-factor authentication along with security audits. 

Despite all of these measures, Contentful isn’t totally secure from hacks. There are bugs and fixes that are often highlighted, and with a large codebase like that of Contentful, it is almost understandable. Therefore, its Bug Bounty Program was launched to reward hackers for finding these issues and vulnerabilities. 

How streamlined is the content workflow?

For a content management system, the content is the most essential part, its creation and management to be streamlined for the CMS to be successful.

Drupal 

In terms of content modelling and the editorial experience, Drupal’s abilities are more than impressive. 

  • Drupal offers numerous field types like boolean, comments, date, email, links, timestamp and numbers, inclusive of decimals, integers and floats. 
  • Drupal’s Field Group module enables you to custom group fields, allowing easy customisations for your editors.
  • The Views system helps in creating an experience that has enhanced uniqueness because it gives you the power to add any field to the view, pull relationships as well as executing many operations at once.
  • Then there is the Content Moderation module along with the Workflows module that can define an innumerable count of arbitrary publishing states and workflows. You could have a largely diverse team, and still be able to map out your preferred workflow before implementing it.

Majority of these are unfound in Contentful, however, it does have its own share of tools accounting for a streamlined workflow.

Contentful 

Contentful doesn’t really fall behind Drupal in content workflow by a substantial margin. Its abilities are almost as good as that of Drupal’s. Contentful’s default editorial experience is extremely easy to understand and use. However, when you decouple it, say using React, you would have to part with the default features. 

  • Contentful offers field types as many as Drupal’s, however, it doesn’t highlight specific format types like email and links and physical addresses. But then it has a JSON object, which Drupal is missing out on. 
  • Contentful uses widgets to define each field type. 
  • Default content views make viewing and filtering content very easy. 
  • Contentful also has easy field restoration with a referencing experience for searching and creation of entities, both of which aren’t found in Drupal.

Contentful’s content modeling and editorial workflow are quite different from Drupal, but effective all the same.

How pocket friendly is the pricing?

Drupal 

Being an open source software, Drupal is free to install and configure. If you have the right human resources, it is absolutely free. However, if you don’t, then it is going to cost you. And these costs depend on the kind of site you are building.

Costs would be dependent on; 

  • The size of the site you are aiming for, the bigger the project, the higher the cost; 
  • The kind of complexity it is going to mandate in relation to workflows, integration and multilingual sites;
  • The timeline and the team you would be relying on; a bigger project would need additional team members like project managers and quality assurance personnel;
  • Then there is the question of the Drupal agency to do all of this for you, if you cannot, which is going to cost you.

Contentful 

Contentful isn’t associated with being free like Drupal. It has different pricing models for different needs of developers and organisations.

  • If you are looking to build a personal site as an individual developer, Contentful would be free for you.
  • If you are looking to power a modern stack site or two with enhanced authoring roles and technical support, you could take up a free trial and then subscribe to Contentful starting at $489 per month.
  • And if you are looking to build hundreds of digital experiences while scaling your content platform, you can get a custom plan from Contentful for your specific needs.

I wouldn’t say Contentful is too heavy on the pocket as is, but including the cost of hiring developers and staff and it would become more expensive than Drupal. 

How effective are the third party integrations?

Drupal 

Drupal is renowned for its abilities to integrate itself with third party tools and applications. Be it analytic platforms, e-commerce verticals, ERP systems or email and marketing systems, Drupal works well with all of them.

Its API-first focus, like Contentful, makes it essential for finding connections to make content reach to other sites and apps. And third-party integrations are just the way to do that.

Contentful 

Contentful comes with UI extensions that are able to integrate themselves with external APIs and third party data. From e-commerce sites to YouTube to local translators, Contentful can merge itself with a number of tools. 

There is also the fact that Contentful has successfully integrated itself with Gatsby and Metalsmith as its official projects proving its abilities further in this regard. Drupal and Contentful aren’t all that different in terms of third party integrations.

How helpful is the community?

Drupal 

Drupal is a large platform, operational all over the globe. This means that its community is also spread throughout the world. And it has, the Drupal community has over a million users in as many as 230 countries, isn’t that an achievement in itself?

People from different backgrounds, different skill sets and different perspectives come together to improve Drupal and enhance its community ties. Perks of contributing to open source are immense and this guide to Drupal contribution will shed more light on the advantages that you get.

Contentful 

Contentful does not have a community as wide as Drupal’s. However, it is making strides towards building one. It has devised and launched a Community Plan that would empower individual developers to build as they like, without incurring any costs as opposed to its 14-day free trial. 

The community also provides technical support through its slack channel, where thousands of developers are active and ready to help.

How seamless are the migrations?

Upgrades and migrations are inevitable when it comes to web development. Usually developers do not look forward to the hassle they bring along. So, do Drupal and Contentful bring on the hassle or eliminate it?

Drupal 

With Drupal 9 having launched last year and Drupal 10 on the horizon, there is a lot of anxiety amongst the Drupal 7 and 8 using folks. The primary reason for the anxiety being the looming EOL dates and the heavy-duty upgrades. 

However, the anxiety isn’t necessary at all.

Talking about the switch from Drupal 8 to 9, as per the makers, this upgrade is considered the easiest in almost a decade. By following a four-step guide, you can have your current site ready for the functionality and better security standards of Drupal 9 by using the Upgrade Status

As for the upgrade from Drupal 7 to 9, easy is not a term that would be used to describe it. The migration will overwhelm you, but all the advantages of Drupal 9 will make it seem worth it. Developers can make the upgrade themselves with the help of Upgrade Status and Drupal Module Upgrader. These help in letting you know whether your themes and modules are competent for Drupal 8/9 and converting your custom code respectively. Explore the ultimate guide to Drupal 9, all the burning questions that you may have about Drupal 9 and the must-have modules to start your Drupal 9 website to know more

Contentful 

Contentful has a tool that helps in the migration process, making it rather easy by using CLI. The Contentful migration CLI helps developers to script changes to the content model with a fine-tuning that wasn’t possible before. Using continuous integration services along with it will also help you in validating the deployment before it hits production. 

Installation and configuration of the Contentful CLI; 
Writing of your own migration script; 
And applying the migration with CLI, is all you need to do to make it happen. 

The result would be getting documented and versioned content types along with automated and predictable migrations that can be repeated in other environments.

How versatile is the responsiveness?

Drupal 

In terms of responsiveness to devices, Drupal is a pro. Providing an optimal visitor experience is one such feature of Drupal that makes it worth everyone’s while and responsiveness is its core. 

Drupal offers; 

  • Responsive designs;
  • Responsive themes; 
  • Responsive images and breakpoints; 
  • And even responsive tables; 

All of these enable Drupal sites and apps to identify the width and height of any device and adapt itself accordingly, making it mobile and user-friendly at the same time. 

Contentful 

Contentful is often referred to as a mobile content management system, meaning it was built keeping in mind the fact that developers and authors would want to publish content on the go through a smartphone or tablet and Contentful makes that work seamlessly.

It optimises mobile performance with three features; 

  • Selective sync;
  • Image auto-compression; 
  • And providing support for offline persistence.

This makes it as good as Drupal in responsiveness.

How fluent are the multilingual sites?

Drupal 

Another one of the benefits of Drupal is the fact that it caters to a multilingual audience very well. With inbuilt language handling abilities, it provides localised digital experiences that are both fast and easy to get.

  • It can translate content, configurations and interfaces. 
  • It can be run in 90+ languages.
  • It also provides an overview screen for translators, making their work easier.  

Access this guide to Drupal’s multilingual capabilities to know more.

Contentful 

Much like Drupal, translations in Contentful also take place in-house. It has a six-step process to make translations happen, which isn’t very complex or rigid. You can add and delete the locales (languages) from the settings as and when you wish, provided you have administrative access. 

The only aspect that pales Contentful in front of Drupal is the number of languages supported. Sadly, Contentful only offers translations in 30 languages. 

Contentful uses locales to define the varying languages a site might use. This allows you to define localisations of content easily enough. However, when you have to work with multiple locales, it can become confusing for your authors. That being said it is an insurmountable task, organisations have worked with as many as 30 locales at once. 

How universal is the accessibility?

Drupal 

Drupal follows the WCAG 2.0 and ATAG 2.0 guidelines to make its projects accessible to people with disabilities. 

Features for screen readers are a major part of it, with the inclusion of drag and drop functionality, colour contrast, image handling, form labeling and exclusion of null tags, to name a few. 

Drupal accessibility also transcends from the users to the developers, with themes, modules and community sites making an inclusive developer environment. 

Contentful 

Contentful also offers similar features and functionalities for accessibility like Drupal. The only major difference is that it adheres to WCAG 2.1 guidelines, which are more recent. 

Building sites that are easy to adapt, navigate, have distinguishable elements and are keyboard accessible are some of Contentful’s accessibility principles. It also implements automated accessibility testing to check whether the project is compliant with the set standards or not. 

How friendly is the SEO?

Drupal 

Drupal has powerful SEO tools that can enhance your site’s visibility by a landslide. When I say tools, I mean modules, the use of which can make you a pro at SEO. 

Mastering the keyword game through Real-time SEO for Drupal; 
Mastering the linking game through Linkit module
Mastering the duplicacy predicament through Redirect module

Drupal can and will keep you at your A-game in terms of SEO. The Ultimate Drupal SEO Guide will help you become acquainted with all the right SEO modules. 

Contentful 

When you use Contentful as is, there aren’t as many SEO privileges to enjoy. For instance, a media page would only have a title and a description. That’s not to say that Contentful doesn’t provide for SEO. 

It does, however, for that you would need to provide more information. This means you would need to create a dedicated content type for the media files you will have. 

Once that is done, you Contentful will enable you to; 

  • Take command of the SEO; 
  • Put in the right tags (which are only used for organising and searching content, sadly); 
  • And add alt text for your accessibility. 

The change in the content type helps you to create whatever suits your needs and preferences, which is a good thing. There is one thing to remember that the extended metadata for these media files would be stored in the content tab, rather than the media tab, where the actual file would be located. This can be a little confusing. 

The bottom line

In the end, I wouldn’t say one is definitely better than the other. There are aspects wherein Drupal prevails over Contentful, like security and performance; however, there were also areas, wherein Contentful gave Drupal a run for its money, like accessibility and responsiveness. I’d say that both are great at what they do and saying one is entirely better than the other wouldn’t be appropriate. So, I’ll leave it to you. 

Feb 19 2021
Feb 19

A whole lot of mental, physical and monetary investments later, your website is finally moving on the track. You have a good traction, and keep up with the trends with updated content and regular revisions. When you have eventually got the hang of managing a full fledged online presence on your website, the first thought that is likely to show up on your mind is to extend it even further. 

Blue background with light blue arrows, addition sign and light blue drop


For reaching a wider audience, optimising mobile experience, and building an alternative marketing solution, mobile app development is perhaps the best way to move forward with one’s business plans. 

What is Flutter?

blue arrows on white background with the text flutter


Flutter is a cross-platform mobile application development framework, more like a software development kit, that was created by Google in 2018. It is used to build applications for several operating systems, both mobile and desktop, and the web, from a single codebase. It is written with Dart programming language. In addition to this, Flutter is an open source platform and invites community contributions into their code repository. 

Ever since its launch and subsequent expansion into development for desktop and web, Flutter has seen widespread adoption and expansion. According to Stack Overflow Trends, Flutter has surpassed both React native and Xamarin in terms of the questions asked about their respective technologies. Google Trends display an increasing  interest of users in Flutter, with searches about the framework soaring since the past two years as well, while Google also claims that Flutter has been adapted by over 500,000 developers for app development.

white graph with blue red and yellow lines mapping the number of questions asked about flutter, xamarin and react yearlySource : Stack Overflow

Why use Flutter?

There are plenty of options available for mobile application development. Despite the presence of other similar frameworks and Flutter being relatively new in the market, in terms of popularity Flutter continues to be one of the most successful app development models among developers. This can be attributed to the following reasons  -

Widgets

Flutter makes the job of development easy with the use of widgets. Widgets are building blocks - each facilitating a part of User Interaction and Experience (UI and UX). Stateless widgets are static frameworks that don’t store any data and exist for the purpose of streamlining your inputs. For example, the Text widget lets you create stylised text and the Row and Column widgets let the user create layouts in vertical and horizontal directions. Similarly, the Container widget creates a rectangular, contained layout visual with margins and padding. Box decoration can be used to customize the rectangle. On the contrary, if the widget in question performs a function when activated, it is called a stateful widget. Examples of such widgets in Flutter are InkWell, Checkbox, etc. Thus, everything doesn’t need to be formulated from scratch, with various pre made layout builder widgets available for the developer.

Open source

What makes Flutter stand out from the rest of its competitors is that it is an open source platform. There are various ways in which an open source model builds its progress over proprietary models in software development. When the cause is community driven, there is always a certain proactiveness both from the users and the owners for driving towards betterment and growth. With no proprietary limitations, the developer community is free to indulge in knowledge sharing, code alterations, and discussing associated challenges with one another leading to better bug resolution in terms of analysis and frequency. Hence, choosing Flutter for application development means having a flexible framework that is open to customisations along with having a community to discuss and also solve your resulting issues with. To know more about the power of open source, read how open source communities work together, how much contributions are valued, why large companies believe in open source, why open source is recession-proof, and last but not least how open source has been impactful during Covid-19 pandemic.

Single codebase and Cross Platform

Although Flutter launched as a mobile application development framework for Android and iOS in 2017, it was quick to expand into the arenas of mobile, desktop and web in the following year, becoming multiple device compatible. A major pro of Flutter over other similar app development frameworks is that it has a single codebase to compile applications, ie, there isn’t a need to code separately for different operating systems and devices, enabling seamless simultaneous app creation even when you’re dealing with multiple platforms and gadgets at the same time. This makes Flutter both developer and user friendly, as the content needs to be formulated only once and is compatible with most of the devices one would want to access it from.

Dart 

Flutter uses a programming language called Dart, which is a relatively simple language with a small learning curve. Its features are a little similar to other languages, but are fitted into a unique syntax and infrastructure. Therefore, developers using Flutter don’t need to invest a lot of time and effort into the process of learning the basics and starting to build applications, which makes the framework ideal for users of almost all experience standings. Due to this, Flutter is suitable even for a small business or a startup that cannot afford experienced developers in their team due to the simplicity of the programming language. 

Integrated Tools

The codebase being integrated at a single place also accelerates the speed and convenience of coding, as the Hot Reload feature updates every change in the source code - allowing developers to see the changes made in the code real time. The work culture in such a case becomes transparent and hurdle free. Tools for developer convenience also include a package called DevTools, a compilation of performance and debugging tools meant to be used for both Flutter and Dart. DevTools is in the beta release at present and is undergoing alterations.

Drupal for Mobile App Development

White background with a blue drop

While we talk of application development, an important player in the market remains our good old CMS (Content Management System), Drupal. The range of mobile apps Drupal can deliver is impressive. The constant evolution and adaptation of Drupal is what has manifested into the huge user base of the CMS, which is currently hosting over 600,000 websites

The usage statistics for Drupal throughout the years are mapped on this graph -

white graph with red and blue lines mapping drupal's growthSource : BuiltWith

Drupal also has a domineering presence across several industry verticals.

red, blue, yellow pie chart showing the presence of drupal throughout various industriesSource : SimilarTech

Accordingly, in the arena of mobile app development, Drupal has seen significant advancements over the years.

  • As an API-first CMS, Drupal makes it easy to communicate smoothly with any application. It is these APIs that link Drupal to the mobile application.
  • Drupal provides plenty of development kits, libraries, modules and sample apps to make application development easier. This simplifies the job of a Drupal developer who might be well versed in PHP, MySQL and HTML but not so much in device-specific native mobile app programming languages like Java or Swift. Elements in Drupal like Waterwheel Swift and OneDrupal Android help manifold in bridging the gap. 
  • Application development is made even easier in Drupal by seamless compatibility with app development frameworks like Vue, React, Angular and Flutter. Drupal pairs well with all of these frameworks to create fast and responsive applications both for the web and mobile. 

The primary reason for which a business wants to build a mobile app is to reach a wider audience and expand marketing avenues. With both Drupal and Flutter occupying large parts of the commercial spectrum, let’s dig in a little deeper into how these can be used together. 

Case Study : Drupal with Flutter 

Drupal’s greatest strength is its ability to mould into any customisation, and in case a customisation does not exist, creating an API for your requirement is always an option. Drupal allows for decoupling and connecting with Flutter through its web services like REST API. Recently, Opensense Labs had the opportunity to take up a project from a leading media and publishing company in Malaysia. 

The primary agendas were - 

  • Refurbishing an already existing but poorly maintained website.

The website was previously built on WordPress, but the organisation wanted to shift to Drupal CMS for improved management of the ever renewing, large volume of content and efficient multi channel delivery. 

  • Developing a mobile app containing the same data as the website, from scratch.

To reach a wider audience and improve UX, an app was to be created to reach the readers faster. This is where Flutter came in.

Processes and solutions -

To start off with, the major work to be done was migration from Wordpress to Drupal and connecting Drupal with Flutter:

  • Since the website dealt in news and media with numerous reports published daily, the number of articles to be migrated were over 30,000. Content migration to Drupal was achieved by following processes like writing custom Drush commands among others
  • Rest API was used to connect Drupal and Flutter. While Drupal acted as the powerful backend managing content, Flutter helped in building a native mobile app.

Along the way, some major hurdles with performance and scalability were addressed:

  • Being a news website, the traffic was pretty inconsistent which led to a few malfunctioning issues. To tackle this, the entire infrastructure was built on AWS which allowed for auto scaling and scheduled scaling to be used. This made sure that the number of instances were increased and decreased as and when traffic saw a spike or a decline respectively.
  • Even though the APIs were created, there were some performance issues due to the large amount of content on the site, with numerous news articles being published daily. Right use of cache tags helped improve the performance eventually.

To make the website and the application function optimally and in sync with the company’s agendas,

  • Firebase was used for enabling Push Notifications, and manual permission was given to the admins for sending notifications leaving no room for error.
  • For ads, the DFP (DoubleClick For Publishers) module was used to serve ads from Google. Interstitial ads were placed between the length of the articles for maximum clicks. A basic level of ad optimisation was also done by the team to ensure better revenue. 
  • Upvote and downvote feature for the news articles was enabled using the Voting API module.

Conclusion

Drupal and Flutter are both significant players in the software arena. We are likely to see plenty more use cases where the efficacy of both Drupal and Flutter is utilised to formulate seamless mobile applications.

Feb 16 2021
Feb 16

Every morning we get up and something big has happened somewhere in the world. Sitting in the capital of India, we get to know how the inaugural ball went on in the capital of the United States. And how are we able to get this knowledge?

It is the media and publishing industry that constantly reports all the national and international happenings to our households. From getting to know about election results to knowing the extent of natural calamities and political unrest, we know it all. 

The role of the media is all the more important today, it has essentially become the voice of the voiceless all over the world. With such a magnitude of responsibility, the media and publishing businesses need to be at their A-game all the time. 

Today, we’ll try to understand how they can enhance their online presence for a rich user experience with the help of Drupal. Before doing that, let’s shed some light on the changes in this industry and understand the consequent change in their web needs. 

What changed over the years?

Time changes everything and everyone. People change their appearances, their style and their thought processes over time. Something that may be important for them is highly likely to become trivial in the distant future. This is what happened to people’s perspective towards the media and publishing industry and the change in point of view led to a substantial change in the running and management of this industry. 

Think of a decade ago, were we as dependent on smartphones and other mobile devices as we are now? The answer is no. However today, from teenagers to the elderly, everyone is glued to their third limb, being the smartphone or smart devices in general. Look at the usage in the graph below to get a clearer idea.  

A bar graph shows the global monthly data consumption on various smart devices .Source: Deloitte.com

Once reading a news article on a smart gadget was a novel thought. However, today it is an everyday occurrence. And that is the pivotal shift that the media and publishing has had to take. The readers are more inclined to reading news updates on their phones. And that is why, this sector has had to transcend from print and paper and provide their audience with digital platforms that are easy to access anytime, anywhere and on any gadget.

What the change comes down to is the delivery mechanism. The media and publishing outlets are performing their duties much in the same way. They are reporting much in the same way. The stories that need to be told are being told and the questions that need to be raised are being raised. However, all of this is happening on digital platforms and it happened in four phases. 

A circular diagram is showing the four waves witnessed by the media and publishing industry.The four waves of the media and publishing industry. Source: Weforum.org

I wouldn’t say that the physical medium of media has become antiquated, not by any means. I still see my dad having his morning tea with a side of the front page news of The Times. However, he also gets constant updates on his phone about the world happening without having to wait for the next day’s paper. 

And that is the change that has happened, that is how the evolution of the media and publishing industry took place, with the core values still remaining the same. 

Look at this report by Statista to understand the emergence of digital media platforms. With such a substantial amount of revenue, I’d say it has come out with a bang.

Revenue statistics for digital media and publishing industry are shown in the US.Source: Statista 

What do media and publishing houses seek today for digital presence?

Like we just discussed above, the media and publishing houses have transformed a great deal in the way they relay information to their audience. Today, there isn’t just one kind of audience and you can’t just build your entire persona around that one category. From young people perusing news on their smartphones to the minority population fluent in their own regional language, the media and publishing industry has to be able to provide for the diversity they have in their audience.

With the move towards digitalisation, we are going to take a look at the needs and requirements of this sector as they are in the present day.

Ease of publishing 

The primary purpose of a media and publishing business is to provide its audience the content that they need. This purpose mandates that the site has an enhanced ease in editing and publishing content, be it blogs, articles or press releases. These content pieces should not be limited to text, images, audios and videos are as equally important as the powerful words of a news writer, and that is the first requirement of this sector today. Faster production and publication of content across multifarious channels is key. 

Friendliness towards the search engines

Now that we have published the article with ease, the next major requirement is to ensure that it reaches the audience it was intended for. If I talk about myself, I always end up at Google whenever I want to read about a major or even minor happening in the world. This is true for most of the readers out there. That is why, Search Engine Optimisation is essential today. 

Producing SEO friendly content would help your content become all the more visible to a wider audience and garner organic traffic for your site. With over 3.5 billion searches everyday on Google, I’d say there isn’t any harm in taking advantage of SEO by adding the necessary words and phrases to your articles. Everything about SEO and its implementation can be accessed here.

Amiability to social media 

Social media is a game changer for the media and publishing industry, allowing it to take its content across the globe in mere seconds. Therefore, social media integration is key, with Facebook becoming the front runner, being that it is the largest platform. 

Having a social media handle, providing sharing options on your articles and creating custom posts of your social media handles, all three of these would lead to a streamlined integration with social media channels. With over half the world population using these platforms, it is only wise.

Responsiveness of design

Next major requirement for the media and publishing industry in going digital is the need to be responsive. Websites that can only be browsed efficiently through a desktop are essentially doomed for failure. Being responsive to all sorts of mobile devices, especially the smart phones, is integral to media outlets. Accelerated Mobile Pages are a trend that more and more websites are following. These help in delivering a smooth experience of browsing for all your users across all the touchpoints. Here is your complete guide to web design.

Warmth of personalised experiences

Coming to the final requirement, which is personalisation. Every web user today is treated differently, since they have different taste. We, as web developers, become aware of these tastes through web cookies. Therefore, as a media and publishing site, you have to become aware of your audience’s likes and dislikes and provide a personalised experience for them that they end of loving. Informational noise and never-changing ads need to be left in the previous decade. Your complete guide to web personalisation is available here.

Why is Drupal great for the media and publishing industry?

Sports, FMCG, Food, FinTech, Elearning, Government, healthcare, nonprofit, travel, or whatever website you need to build and whichever industry segment you belong to, Drupal has just the right ingredients to build your digital presence. Media and publishing industry is no different.

Drupal is an open source Content Management Software that has a worldwide presence and is renowned for its efficiency in managing content. It has clientele from multitudinous trades and businesses. And with a community of over a million, it is indeed a force. It is a force that is equipped to provide digital experiences that enable you to connect with your audience no matter where they are.

I would not get in every minute aspect of Drupal, because that’ll make this blog quite lengthy and nobody wants that. Rather I would only talk about those aspects of Drupal that make it extremely compatible with the media and publishing industry. So, here goes.

Drupal eases content management and distribution 

The thing about media sites is that they are not limited to just one, they have a huge family with many subsidiary sites. The higher number of co-dependent sites means that you would have to have a lot of content to deal with. Drupal comes quite handy here, as it acts as a single home for all the sites. 

And the amount of content that results in would not be bother as well.  Be it photos, videos, audios, podcasts or graphs and analysis. Everything would be seamless in terms of production, management and distribution with Drupal. Have a look at an example of how content authoring can be performed at ease with modern solutions like Layout Builder module in Drupal core.

Drupal eases the mobile transition 

I believe I am going to be mentioning this one for a third time now, but mobile responsiveness is pretty high on the priority list so it deserves another mention. When we talk about user engagement, a modular design is key and when that design is flexible to respond to any device the engagement soars. Drupal provides a number of modules to achieve the same.  To know more, read about mobile-first approach and Drupal’s provisions for building mobile solutions at scale.

Drupal eases multilingualism

With media sites catering to a large number of audience worldwide, language can become a problem. Drupal provides multilingual support that makes publishing the same content in different languages an ease. Drupal offers translations in as many as 94 languages. More on Drupal’s multilingual capabilities here.

Drupal eases profits and lessens costs  

Drupal is equipped to make you money as well. Advertisements, promotions, subscriptions and one-purchases, all are inclusive in Drupal modules that result in media outlets being more profitable. 

Then is the fact that Drupal is open source, which means it is free of cost. There isn’t any licensing fee required to be paid. All you need to do is install and configure it and you’ll be ready to go. Learn more about the perks of contributing to an open source CMS like Drupal and being a part of a growing open source community here.

Drupal eases the security concerns   

Drupal security is one of the best in the market. With modules for authentication, password protection and encryption, your data is always going to be safe. Open Source security isn’t anything to be taken lightly and Drupal has proven that. Here is a survey to prove that. 

There is a pie chart depicting the percentage of security issues in various CMSs, Drupal being one of least of them all.Percentage of security issues in a sample group. Source: Acunetix

With this level of ease, you can become relaxed and bask in the efficiency of Drupal and become free of the burdens of running a media site that you might have to endure otherwise. However, you would have to write stellar pieces that are able to resonate with the audience and accomplish what they were set out for. That is a burden you would have to bear, Drupal wouldn’t be able to do so.

Here is a glimpse of Drupal at work with digital media houses

Drupal has indeed proven to be one of the best CMSs for the media and publishing industry. I don’t just say it for the sake of it, I come bearing proof. OpenSense Labs has worked with many media and publishing houses to build impressive experiences for their web portals with Drupal and here are some of these sites. 

Men's Health 

Men’s Health magazine is a global brand, which publishes in close to 60 countries. It required a software that would provide an ease of management for the content authors, with an adaptable content architecture that would be responsive and browser agnostic. It also required to balance the performance and images conundrum without trading off on either of these. And Drupal was able to fulfil all of these requirements and an impressive digital experience was created. 

Read the complete case study of Men’s health to know more.

Earth Journalism 

Earth Journalism Network is a leading non-profit environmental new network that aims to improve the quality and quantity of environmental reporting. With such crucial work, it required the best. Drupal provided ease in publishing and managing varying categories of content types with a heightened flexibility. Drupal also had the right kind of core and contributed features that allowed for better design scope and ability to handle enormous amounts of content. 

Here is the detailed case study of Earth Journalism Network.

Farm Journal 

Farm Journal is a leading US publication site for agricultural news with a host of subsidiary sites serving varying sectors of this industry. With such a magnitude of services, its content needs were becoming a challenge. Drupal was able to overcome this challenge with ease. Customer sites were enhanced, upgrades were made faster and convenient, the architecture was made scalable and modular in nature and most importantly, the content journey, from the editors hitting save to the consumer clicking read, was reduced to mere seconds.

To know about everything that went on in the Farm Journal project, read this case study

AgWeb 

A part of the Farm Journal brand, AgWeb was able to improve its brand identity as well as user engagement with Drupal’s help. Being an agricultural news site, AgWeb needed to improve its web performance, at the same time the site’s SEO needed to be kept intact, while improving the site’s web SERP rankings. ReactJS was also implemented as part of progressive decoupling for a better frontend experience.

Take a look at the AgWeb case study to understand the project better.  

All of these are a blatant proof of Drupal’s efficiency in this constantly evolving domain of publishing and you would be wise to choose it.

Conclusion 

The news, newspaper and article sites are growing at an impressive pace. Therefore, having a CMS in your corner that is powerful enough to let you scale in accordance to the growth rate is ideal. Drupal is just that, it can do and achieve things for a media site that other CMSs may not be able to. And we at OpenSense Labs have actually witnessed that with all media projects. So, trust me when I say that you cannot go wrong with Drupal. For any doubts you may still please feel free to contact us.

Feb 09 2021
Feb 09

A myth is a pretty powerful thing, especially if you end up believing it. Even if you don’t, it does dampen the prospects of whatever it is associated with. It’s like if someone told you that the latest smartphone, which is exorbitantly expensive, is not worth the price. In such a scenario, even if you had the means of buying it, you would end up thinking twice. And you don’t even know whether the myth is true or not. That is how powerful a myth can be. 
 
A myth, a misconception, a false belief, whatever you call it, follows as many things as you can imagine. It follows you and me, and it also follows the inanimate objects, making their abilities seem weaker than they actually are. 
 
And it is one such thing that we are going to be discussing and try to debunk the falsified claims that have been following it for a long time. The thing I would be talking about is actually a software, a Content Management Software by the name of Drupal
 
Drupal is used to build websites, websites that are feature packed and give a powerful performance, yet there have been many claims made that try to show Drupal in a bad light.
 
Today, you and I will get into all of these and ensure that all the myths associated with the name Drupal are busted so colourfully that they can never ever be claimed by anyone. So, let’s start with the most common misconceptions about Drupal.

# Drupal tends to be difficult to use

Any software or system that you may end up using, the foremost aspect that you would look out for is its usability. It might be able to provide you with a ton of features and functionality, but if you cannot figure out how to use it, all of that would be a waste. So, on the same note, let me tell you the first Drupal myth. 

The most common myth about Drupal is the fact that it is very difficult to use by all the parties involved. Developers find it tedious to work with, marketers can’t get a hang of it and the content authors and editors, well, they feel that they are way out of their element. 
 
This myth is not true at all. Drupal is a little complex to use, at least in comparison to its competitors. However, it requires that level of complexity to be able to do its job properly. For instance, Drupal provides umpteen number of modules, all of which are able to provide you with any kind of functionality that you may be on the lookout for. Selecting from these could be a daunting task, but it is also a necessary one. 

Let us look at some of the Drupal complexities to understand why they are mis-conceptualising an easy-to-use CMS.

  • Drupal’s large codebase seems intimidating, but the system only loads what you need, so the point is basically moot here. 
  • Drupal uses more memory, so it is perceived that if there is an out-of-memory error, it would become very difficult to solve, making the experience pretty complicated. 
  • Then, there is the fact that Drupal is built on PHP. Since that is a language many developers lack experience with, the myth of difficulty in use prevails all the more.
  • The last one would be the lousy UX experience Drupal provides to the non-technical users. Being a content editor myself, I would say that this isn’t true at all. I have been able to use Drupal with ease to edit and publish my content and so far the experience hasn’t been lousy in the least. 

That is my take on Drupal ease-of-use. There is an acclimating period required, but that is true of any new technology.

# Drupal migration and upgrade tend to be an insurmountable task

Migrations and upgrades are an inevitable part of website development. There will come a point when the version you have built your site on is going to become so basic and on the verge of being obsolete that you would need to upgrade or migrate to something new and better. 
 
With Drupal, the story is the same. From the first version of Drupal that was launched almost two decades ago to Drupal 9, which is the current version, there is a stark difference that is too obvious to ignore. 
 
The myth going on is that these migrations and upgrades of Drupal are very difficult, complex and will most likely give you a headache. The truth behind it is quite the opposite. 
 
I would be wrong to say that Drupal migrations do not require any work because they do. Imagine moving from your home in India to the US, there would be work required and lots of it too. However, the work won’t be too much to make you rethink the move because the other side is too special to give up. 
 
Coming back to Drupal, the upgrades are usually seen from Drupal 7 to 8, 8 to 9 or directly from Drupal 7 to 9. All of which are possible scenarios for your site and its enhanced functionality. 
 
Drupal 7 users can first upgrade to Drupal 8 and then move on to Drupal 9. Or, they may choose the best route by going directly to Drupal 9 to ensure that the upgraded site has maximum expected life.
 
For the Drupal 8 to Drupal 9 upgrade, there are six steps involved; only 6 and not a bazillion.  

  • First, you would need to ensure that your hosting environment aligns with the platform requirements mandated by Drupal 9.
  • Then you would need to update to Drupal‘s more current versions, it could be Drupal 8.8.x or 8.9.x. 
  • Once that is done, you would need to ensure that all your contributed projects are compatible with Drupal 9 by simply updating them. 
  • When that is out of way, you would be required to build custom code that is also compatible with Drupal 9. 
  • In the penultimate step, you will be asked to update the core codebase of Drupal 9. 
  • And as the final step, all you have to do is run update.php and that is it. 

There is also a step by step guide in the upgrading section provided by Drupal to help in the transition process with all the details you may be looking for. 
 
It is true that upgrading from Drupal 7 to 8 or 9 can be pretty intricate. Drupal Community took cognisance of this matter and made sure upgrading to Drupal 9 would be the easier you can get. As a matter of fact, the upgrade to Drupal 9 has been deemed as the easiest upgrade of the decade. This in itself should have been enough to pop this myth there and then. Access this ultimate guide to Drupal 9 to know more. You can browse through our complete list Drupal 9 FAQs that answers every burning question that might have regarding Drupal 9.

# As Drupal 9 rolled out, Drupal 7 and 8 tend to be less efficient

Since we just talked about the upgrading to Drupal 9, I felt this myth that has been for a while now needed some straightening too. 

The myth is that since Drupal 9 has launched and is the most advanced and feature-packed version of Drupal, the earlier editions of Drupal, namely 7 and 8, are simply no longer viable. 

This is not by any means true. It will come true at one point of time, but that point is very distant in the future; not according to me, but the makers themselves claim so. 

  • If I talk about Drupal 8, which is reliant on Symfony 3, it would be supported by Drupal until the 2nd of November, 2021, since that is how long the life of Symfony 3 is expected to be.
  • Talking about Drupal 7, its community support was earlier marked to end by November, 2021. However, with COVID and the consequent crisis, that has been extended to by a year. So, Drupal is expected to be supported by the Drupal community until 28 November, 2022

This support is proof that Drupal 7 and 8 would still be fully functional for a couple of years, and their efficiency is not going to be marred by any way. The sites and projects reliant on them will continue to bask in all the glorified features of Drupal. Don’t believe anyone who tells you otherwise. Dries Buytaert, the founder and project lead of Drupal, takes pride in continuing to care for old software. Drupal 7 released almost a decade ago and continues to get the sort of care and attention from the Drupal Community it requires to function well. He wishes more and more software is well-maintained like Drupal is.

Another thing that I want to add is that even if the community support dies down, there is still the vendor support that lets the project be efficient. For Drupal 7 sites that support is extended to 2025. Let me also tell you that there are still many Drupal 6 sites which are performing efficiently through the vendor support. 

Yes, the end of life would come for the older versions sooner than the later versions, but that is how life in general works, don’t you agree?

# Drupal tends to be heavy on the pocket

Financial considerations are one of the major aspects to pivot someone’s intentions towards taking up a project or software. The same is true for Drupal as well, taking us to the next myth.

It is perceived that Drupal is extremely expensive, making it hard for smaller organisations to take it up as a software to build their websites.

Drupal is an open source software, which means it is free of cost, so this myth is a little funny to say the least. Yes, open source software is not entirely free or rather its implementation and maintenance is not free. It would definitely cost you to hire Drupal developers to make that happen. From maintaining Drupal modules and updating your digital properties to migrating Drupal to the most current version requires skilled developers who are not always economical. However, these costs are not exorbitant, at least not in comparison to proprietary software, with its licensing fee and other perpetual expenses. 

Then there is the support of the Drupal community, which is always there to help you in any dilemma you find yourself in. Any and all of your questions will always be answered. This also means you get to take advantage of the abundance of experience found throughout the community, you can simply build on solutions that have already been created. 

Apart from this, your non-technical staff, especially your content authors are not reliant on developers to post and edit the content. This frees up the developers, leading to savings. Finally, the migration from one Drupal version to the next is also not expensive at all. So, if you are planning to shift to Drupal 9 from 8, remember the switch from Drupal 8.0 to 8.1, the migration would be that simple. 

Now, you tell me, is this not cost effective?

# Drupal tends to lack in security

For any web application, it is extremely important to be secure. Having security issues often make you vulnerable and prone to hackers and that outcome is never going to be favourable. 

So, this Drupal myth states that the CMS is not secure at all. It is an open source software and that is reason enough to doubt all of its claimed security features. 

Let me start by telling you that Open Source security cannot be taken lightly. Also known as Software Composition Analysis, Open Source Security provides the user an opportunity to garner more visibility for his application. From examining binary fingerprints to using professional and proprietary research and corroborating it with scans is done to build elements and tools that help developers in building safer applications. 

Focusing on Drupal, it is deemed as one of the most secure CMSs in the market, not just in the Open Source market, but the proprietary as well.

A pie chart depicts of results of sample group survey for security of various CMSs.Source: Acunetix

The above image clearly shows Drupal leading the way in terms security, being the CMS with the least issues faced as per a sample group’s findings.

Let’s find out why. 

  • Drupal’s security team works with the community to tackle any security issue as soon as it arises. 
  • Drupal’s API and default configuration is equipped to handle security issues like XSS, injection and forgeries with standard solutions. 
  • Drupal provides a lot of out-of-the-box security features like secure access, granular user access control and database encryption to make it all the more secure. 
  • Then there is the fact that many prominent government agencies use Drupal to build and manage their online projects. This speaks to its security measures. 

So, no Drupal does not, by any means, lack in terms of security, rather its security is almost impeccable and really hard to breach.

# Drupal tends to be unscalable and gives a meagre performance

Despite how great your site is now, there would come a point when its present state is no longer viable with your business goals. And that is when you would need to scale your site accordingly and boost its performance. This leads us to the next myth. 

It is often presumed that Drupal is not very scalable and its lacklustre performance in terms of higher traffic load and more content growth is not appreciable by any means. 

As an answer to this preposterous myth, I just want to say that, if that were the case, why would sites like The Weather Company and NBC, which have a daily audience in hundreds of thousands use Drupal? The justification is the exact opposite of the myth. 

Drupal can handle traffic spikes, it can handle content growth and it can handle an incredibly elevated user count and it can do it all like a breeze. All you have to do is optimise Drupal to its best abilities. It provides a number of features and modules for you to work with to manage your site’s performance and scalability. Be it the Blazy module to provide integration or the Content Delivery Network to offload your site’s delivery, Drupal has you covered.

I think this misconception should be clarified now. These guides to Drupal performance optimisation techniques and scalability offerings would clear the air further.

# Drupal tends to be inaccessible

Web accessibility refers to a website or application being built in a manner that anyone can access it with ease, anyone has a special focus on people with disabilities. The World Wide Consortium has set a few guidelines that web developers have to follow to become universally accessible.
 
According to this Drupal myth, it is assumed that Drupal is not universally accessible. It is not meant to be used by people with disabilities and can cause them harm, if they were to use Drupal sites. 
 
There is absolutely no truth in this misconception. Drupal stringently follows the WCAG 2.0 guidelines and has built its features accordingly.  

  • The Olivero theme for the front end in Drupal 9 is the prime example of Drupal’s accessibility. With focus on colour, contrast and fonts in accordance to the WCAG 2.0 guidelines, it is universally accessible. 
  • The use of HTML5 and WAI-ARIA has led to better semantics of purpose and behaviour of the web pages for the screen readers. 
  • The use of alt text in images helps in making them accessible to the visually impaired. 

These are simply a few examples of Drupal’s accessibility features and values. To understand web accessibility completely, read our blog Design Considerations for Accessibility and know that Drupal follows each one of them.

# Drupal tends to be unequipped to handle large site

There are two kinds of websites, the first one is for small businesses and the second one falls under the big business umbrellas. Taking these categories into consideration, we come to the next false claim. 

Many believe that Drupal is only competent to handle smaller sites, when it comes to the larger businesses and their web needs, Drupal may fall short. 

To clarify this bizarre claim, let’s just look at some of Drupal’s clientele. Tesla, Oxford University, European Commission, NBA and the French Government are just a few names that do not need an elaboration, people already know them. With such an elite clientele, is it justified to say that Drupal cannot handle large sites? I think not. 

Drupal is well equipped to provide enterprise grade services and features that include; 

  • Impeccable user management; 
  • Impeccable content management; 
  • Impeccable admin interface; 
  • Impeccably easy coding; 
  • Impeccable technology stack; 
  • And an infrastructure that resounds all the impeccable innovations in it. 

That is a whole lot of impeccable, but that is Drupal for you.

# Drupal tends to be incompatible with mobile devices and unsuitable for mobile solutions

Today, it is the responsive sites that reign over the internet. If you have a site that is compatible with the computer and the mobile phone, you can consider yourself amongst the rulers, metaphorically speaking of course. 
 
Drupal is often understood as a CMS that is not mobile-friendly, which means the sites and applications built on Drupal are not able to support responsive designs. 
 
Again, this isn’t the case. Rather Drupal works on the ideology of building sites that are responsive and creating web applications that provide an enthralling visitor experience, regardless of the device they may be using. This means that Drupal is compatible with mobile devices as well as desktops, since it has the ability to offer a seamless content experience to every user every time. So, the myth is debunked. 

# Drupal tends to be disintegrated with third-party tools

Confining a website to just one tool and software has become a thing of the past. With more technological innovations come more third party integrations. And where does Drupal stand in all of that?
 
According to the myth, Drupal is not at the top of the integrations list. Rather it is assumed that Drupal does not work well with other tools and has an isolated digital marketing philosophy as well. 
 
And there is very little truth in this assumption. In fact, Drupal has the ability to integrate itself with a massive ecosystem of digital marketing technologies and other business applications. It allows you to have the chance of tapping into the most popular tools of the present as well as the chance to do the same in the future. 
 
Drupal also has an API-first rule, which essentially means that your content can easily be connected to other sites and applications. This means your words would resonate with a much wider audience, making them all the more powerful.

# Drupal tends to have an inflexible and uneasy content workflow

Content is basically the voice of your site, so it is wise to choose a platform that makes your voice the loudest and most clear. Does Drupal do that?
 
The myth related to content workflow doesn’t believe that. As per the misconception, it is believed that Drupal is quite inflexible in terms of content and using it for creating, editing and publishing the content is not easy at all.
 
Let me start debunking this Drupal myth with its Admin Interface. This helps you in creating the exact content architecture that you want. You get to display only the content suitable for every context. The use of Drupal efficient display mode tools and Views makes this task all more fun. You can add any media type you want, be it images, videos or pdfs. Then there is the fact that you can customise your menus to make them aligned with the user’s device. 
 
And there is more. 

  • You can create and edit in-place. You can simply browse to a page, click on the content and start editing then and there. 
  • You can edit from any mobile device, iPads, smartphones or tablets, android or iOS, your pick. 
  • You can make revisions multiple times and keep track of all of them even months after. 

Is this what you call inflexible and difficult? 
 
Modules are Layout Builder and Paragraphs are renowned for the ease they provide to editors and content authors.

# Drupal tends to be unfriendly with SEO

SEO and all that it encompasses is essential or more like life-saving for your website and its visibility on the web. Since that is what brings in the numbers, you know how important that should be. 
 
So, the myth that is doing that rounds is that Drupal is not SEO friendly. It does not have the features to heighten the visibility of your site on Google or any of the other search engines.
 
Do you think that could be true?
 
I certainly don’t and neither should you. Drupal has dedicated features and modules that help you get the best out of SEO. Take the SEO checklist module for instance. Being an SEO module, it helps you be on top of all the SEO related tasks and ensures you are reminded of them. It is always being updated with the latest SEO guidelines so that you are aware and ready to tackle all of them. 
 
From modules capitalising on your URLs to tags and onto communication and editing, Drupal will have you covered for every SEO dimension you can think of. Our blog, The ultimate Drupal SEO guide will help you get an even elaborated explanation of Drupal’s SEO capabilities, which by no means are lacking.

# Drupal tends to be incompetent as a headless CMS

Going headless or decoupling has become a trend as it allows the developers to use the different technologies available in the site building process and make it all the more impressive. 
 
With Drupal, it is often assumed that decoupling would mean more work and less benefits. You would have a lot on your plate when you decouple Drupal and the result would be a dysfunctional and mismanaged site. 
 
This is nowhere close to the truth. When you decouple, you would have a separate frontend and backend development and management; both of which will be interdependent and connected through an API. Yes, you would most definitely have to part with some of Drupal’s out-of-the-box features, but that isn’t necessarily bad. 
 
With decoupling, you would be able to build a frontend the way you want to, with whatever technology you want to. Fancy React, go for it. Have a liking for Angular, go for that. You would be using Drupal as a content repository and since Drupal knows its contextual ABCs pretty well, you will be in great hands. You can publish your content across varying channels and manage it from one place. 
When you go headless, you will get to choose from the best frontend technologies and get the best at the backend layer with Drupal. The best of both worlds for you. 
 
Now, do these features portray incompetence to you? 
 
Read about everything you would want to know about Decoupled Drupal, Decoupled Drupal Architecture, how to decouple Drupal and some of the success stories to get an understanding of how competent decoupled Drupal can be.

# Drupal tends to be efficient with multisites

Many organisations have subsidiary businesses for which they need to build multiple sites. They might want these sites to become a replica of each other, offering the same features and functionality, yet be different to each other. 
 
There is a false claim being made that Drupal cannot optimise multisites. It cannot provide the separate individual sites their own database, configuration or even the URL/ domain names .
 
Drupal offers a multisite setup that is pretty efficient and well-equipped to handle all the requirements.

  • You would be able to manage all your Drupal sites running on the same version of Drupal core, which ultimately saves you time. 
  • You would be able to update all your sites simultaneously when there is a  new release because all of them would have one codebase. 
  • You might have some drawbacks through the multisite setup, but by using Aegir hosting system, you would easily overcome them.

Inefficient isn’t a term that should go with Drupal, since it is anything but that. So, manage your sites from across the globe from your laptop while sipping coffee on your kitchen island with Drupal. I consider this pretty efficient.

# Drupal tends to be hostile to multilingual sites

Like I talked about in the previous point, sites today aren’t confined to a region, they are almost universal. An American brand is also famous in India and it gained popularity because it was able to resonate with the Indian audience at a personal level in their language and dialect. 
 
Everybody knows that Drupal can handle multilingual sites, but many believe that Drupal isn’t great at that. Translations and other multilingual features tend to be below average. And that is just a myth.
 
Translations are the most crucial for multilingual sites and Drupal offers not one nor two, but four translation modules in Drupal 8. From content to configuration and interface, everything can be translated to the local language with ease. You can install Drupal 8 in as many as 94 languages without any need for the installation of extra components. Moreover, custom translations are often packaged and deployed on several properties, so you developers have lesser language related headaches. Everything on Drupal’s multilingual capabilities can be accessed here.
 
I would not call Drupal hostile to multilingual sites, would you?

# Drupal tends to only be suitable for a few industries

A CMS builds and manages websites. Since these websites can be for any business and field, a CMS should be able to cater to their industry type. 
 
There is a Drupal myth going around that states that the CMS isn’t meant for every industry. It only caters to a few, and I am not even sure which ones account in those few. 
 
This one is probably the most ludicrous misconception of them all. I can understand that people may be skeptical about open source security, but this is just nonsensical. I mean if a CMS is able to build a site for a retail business, what is stopping it from building one for a blogger? Kind of bizarre, isn’t it?

A list of the many sectors Drupal caters to is shown.Source: Drupal.org

This is a list of industries that has Drupal imprinted on their web services. And the extensiveness of the list is clarification enough for the myth.  From publishing houses and educational institutions to government agencies and charitable organisations, Drupal serves the majority of the industries.

# Drupal tends to become a pain when it comes to support, maintenance, hiring and partnering with digital agencies

Working with Drupal on your own can become challenging. You would need support and expertise of someone who has worked with the CMS and knows its ins and outs with clarity and that is a Drupal agency. 
 
This Drupal myth states that the hiring of Drupal agencies is a blood-sucking task, which would drain you of the same. Add to this the support and maintenance of Drupal and you might just give up on site building altogether. 
 
Let me start with Drupal agencies, there are a lot of them for you to choose from. The good thing about that many agencies is that they try to outweigh each other in terms of the services they offer and you end up with everything you desire. Being a part of OpenSense Labs, I can proudly say that we rank amongst the top 5 Drupal agencies in the global Drupal marketplace.

A list of Drupal agencies is shown with their marketplace rankings. Source: Drupal.org

Talking about support and maintenance, whichever agency you may choose, you are bound to get some very convenient services in this regard. 

These are only a few of the support and maintenance features available and they won’t let you be in any kind of pain.

# Finally, Drupal tends to be incompetent with the emerging technologies

We live in a dynamic world, where everything is transitory, from human life and thoughts to the technologies we have become so dependent on. These changes are basically advancements that aim to enhance our quality of life and all of the experiences in it. So, how does Drupal come into the picture and what is the myth?
 
This Drupal myth states that the software cannot work well with all the new technologies coming on every day and its integration with them is almost impossible. 
 
Do I have to say that this is untrue? I’m sure you know that by now. Drupal and its abundant content-heavy sites mandate that it utilises the latest technologies to make the user experience even more delightful.
 
The use of artificial intelligence in the form of chatbots, cognitive search and digital voice assistants like Alexa on Drupal sites is probably the most justified clarification to the bizarrely unjustified claim. Along with these, the streamlined incorporation of Virtual Reality, with all its realness, IoT and Blockchain into Drupal sites is further proof of the myth being a colossal misconception. Our blog, From conception to reality:Drupal for futuristic websites will shed further light on this notion. 

Conclusion

Drupal is one of the very best content management systems in the market. Its features and abilities are truly astounding. Believing some false claim that says that Drupal is anything but one of the finest would be a mistake you do not want to make. Yes, there isn’t everything Drupal is great at and yes, it may even have some flaws, being perfect is almost impossible after all, but all of Drupal’s imperfections are not enough to dampen its overall appeal. 
 
So, if you have chosen Drupal to provide your site’s groundwork, rest assured that you have made the right choice. We, at OpenSense Labs, have clients from across the globe asking us to build their sites using Drupal and to this day, not a single one of them has gone disappointed. 
 
Finally, the moral of the story is that don’t believe everything you hear, at least not until you have proof of its trueness and I think I have managed to tell you all of Drupal’s truths for you to shun all of Drupal’s myths. Debunking Drupal myths was fun. 

Feb 09 2021
Feb 09

Drupal being an open source project relies significantly on its community for contributions, promotion and overall expansion. The user base adds to Drupal in terms of coding, testing, bug fixation on the software, also contributing themes, modules and distributions regularly. Acknowledging the important role that the community plays and also its requirements, Drupal comes up with Initiatives to streamline and channelize everyone’s efforts to a common high priority goal.

Drupal Initiatives are common upcoming goals in the Drupal sphere prioritised according to commercial interests and their effect on the community. Initiatives are formulated around a feature, a new module, or an alteration in any element of the software. Usually, 

  • user research, 
  • proposals by Drupal Core Maintainers,
  • advice of key community members, and
  • inputs from the board of directors

are taken into account before launching an initiative. 

How core development and strategic initiatives come about in Drupal?

To understand the functioning of initiatives better, let’s skim through the life cycle of Drupal initiatives.

Proposition 

To start with filing Drupal initiatives, the first step would be to file a proposal. Although absolutely anyone could propose an initiative in Drupal, it is recommended that certain factors be taken into consideration before the said proposal. It needs to have a proper backing of relevant data along with a farsighted vision of what the end result would look like. It is recommended that the proposed initiative should have a positive market impact on Drupal and adds sufficient value to both the software and the principles that it stands for. Discussion with the community must also take place before bringing an idea on the floor, and subsequent revisions must be done accordingly with respect to the feedback received. Lastly, an individual wanting to get a proposal approved also needs to be patient with the whole process, as in a large community like Drupal, things move forward in a pretty organic fashion.  

                                                                                                        
Prioritisation

The sites supported by Drupal are diverse and cater to a plethora of end users, therefore prioritising initiatives in such a manner that every user persona is appropriately benefitted assumes utmost importance. Hence, several Drupal initiatives might be proposed, but only a few get highlighted. This is done in accordance with Drupal.org Prioritization Criteria. Prioritising can be a tricky business as while one initiative might affect every Drupal user one-on-one, another might influence a small segment of users but at the same time be essential for Drupal’s core. Keeping all these things in mind, propositions are ‘accepted’, ‘rejected’ or ‘postponed’. The accepted proposals are then prioritized.


Roadmap

The association’s staff are tasked with weighing the impact of the Drupal initiatives against the spectrum of affected audience. Once a bunch of initiatives are finalised, they’re listed in the Current section of the roadmap. Architects are assigned to supervise the initiative, the member also acting as the lead for that particular initiative. His job is to ensure accessibility to open discussions and related information. Weekly or biweekly meetings are done between the staff liaison and the community working on the initiative all throughout its execution, and the completed draft is then submitted for review.

The time taken to get done with an initiative is highly variable. A smaller one might take a few days while a lengthier initiative can also span a few months to complete. 

For core initiatives, the process looks a little different than this. Initiatives that are identified as being of utmost importance to Drupal and the community are included in strategic initiatives by Dries Buytaert himself, who is the founder and project lead of Drupal.

For an initiative to be included in this category, it must have the following -

  • Surveys or statistics figures substantiating the validity of the initiative.
  • An underlying vision that could result in a breakthrough for Drupal.
  • Requirement of channelised resources as it is high priority.
  • Due to its larger scope and influence, need for multiple stakeholders to come together and collaborate on it.

Major Ongoing Community Initiatives

Drupal Community initiatives are projects where the user base comes together to work on several components of Drupal like contributed modules and themes or even Drupal Core. These are some major ongoing Drupal initiatives -

Composer Support in Core Initiative

Composer dependency manager for PHP does not have an official dedicated Support, although there do exist several documented ways to use it wherever necessary. Owing to the manager’s widespread adoption by a number of contributed modules, an initiative has been set up to create a Composer Support in Drupal Core. 

Bug Smash Initiative

As the name suggests, the bug smash initiative is meant to contribute towards bug resolution. It is a core issue focusing on bugs in the newer versions of Drupal that have been recently launched. Issues resolved under this initiative are tagged accordingly under the same name.

Documentation and Help Initiatives

The goal here is to improve, with the help of extensive documentation, the user experience of a Drupal evaluator, developer or site builder. The initiative also focuses on achieving a better in-house Help system by adding high utility features like a topic based help provision.

Workflow in Core Initiative

This initiative is working towards bringing upgrades in Drupal’s content workflow, preview and staging features with the aim to provide content authors and editors sufficient tools to review and deliberate upon the content before it is rolled out.

Drupal Open Curriculum

The open curriculum initiative is self explanatory - the aim here being the provision of a systematic and structured training to new recruits in Drupal. Features like in-class sessions, self learning along with training exercises are to be included, culminating with on the job learning. It is targeted towards developer entrepreneurs owning Drupal agencies with new hires learning Drupal or individuals curious about the software.

Accessibility contribution

Another really important initiative is to ensure compliance to web accessibility norms set by various governments and organisations. Greater awareness regarding accessibility by individuals suffering from certain ailments has led to widespread adoption by the players, and the Drupal community aims on pitching in every idea and suggestion to improve accessibility for its users.

Major Ongoing Strategic Drupal Initiatives

Some major ongoing strategic Drupal initiatives are as follows -

Automatic Updates

This initiative aims to solve the inconvenience that comes with having to manually update a Drupal site after updates have been incorporated in the software, as one running behind the deadline might compromise on the standard and security of a website. Hence, the community is working on automated updates to provide a safe and secure environment for pre programmed updation, and also to cut down maintenance costs of a Drupal website.

Decoupled Menus

An initiative for decoupled menus is also ongoing, aiming for better synchronisation with front end JavaScript

Orange background with black flag and text talking about decoupled menus, one of the ongoing Drupal initiativesSource : Drupal.org

Drupal 10 Readiness

The Drupal 10 readiness initiative provides a timeline for things that need to be wrapped by 2022 to facilitate the release of Drupal 10 in June, or latest by December that year (which is 2 years after the release of Drupal 9). Milestones that need to be aced are updating dependencies before Drupal 10’s release, removing deprecated APIs, helping module contributors maintain the modules’ updation, and consecutively speeding up the launch of Drupal 10. The primary components of this initiative are -

pink background with a horizontal arrow, surrounding text talking about Drupal upgradesSource : Drupal.org

Easy out of the box

Ease of use has become a matter of prominence in recent years, which is why Drupal 9 was largely focused on making the update easier and convenient to use and incorporate by the users. Another area under maintenance now is the enabling of the new Media Library, Layout Builder and Administration Theme by default in Drupal for added user satisfaction.

New Olivero Front-End Theme

Olivero is set to become the new default frontend theme by replacing Claro. As design is what truly manifests changing technologies and advancements for the end user, upgrades  in terms of modernity and functionality are essential for proper representation. The new theme is also meant to include support for Drupal’s second level navigation and the embedded media. Staying laser focused on accessibility, the theme is also supposed to be fully WCAG (Web Content Accessibility Guidelines) AA (mid range) compliant.

Conclusion

Drupal Initiatives are a good way to both bring the community together and stay afloat on the productivity factor. Some major changes in the past have been triggered by initiative action, for example, several design changes, changing Drupal’s default markup to one that conforms to HTML5 standards, making Drupal mobile first, etc Hence, initiatives have brought together people of diverse backgrounds and experiences to create something global together, affecting both the individuals personally but also the community at large. 
 

Jan 22 2021
Jan 22

The way websites are perceived has changed a lot recently. The audience has started demanding more and more from the web and web developers have to provide for all the demands. What this has resulted in is the transformation of websites for the better. 

The features that today’s sites are packed with were hardly even imaginable a decade ago. A website, a web application or a mobile application, all can do wonders for the users, satiating them with their experiences. 

So, when building a website, you have to be extremely considerate of the software you use and the technologies that accompany it as it is these that will make an astounding difference in your site’s overall appeal. 

On the same note, I will try to enlighten you about one such software and technology pair that has made websites as appealing as both their developers and users want them to be, and that is Drupal and Angular. So, let’s get right on it.

Drupal’s Essence 

The Drupal logo is seen.

In essence, Drupal is a provider of innovative digital experiences that set your websites apart from the ordinary. 

Being a content management software, Drupal can make websites that actually set standards for others to follow. Convenient content authoring, impeccable performance and outstanding security are some of Drupal’s most renowned features. Whether you want flexibility and modularity or integrated digital frameworks, Drupal can ease your needs. 

With multiple add-ons;
With numerous modules; 
With several themes; 
With various distributions; 
And with multitudinal mix and match options, Drupal’s core abilities are magnified by a landslide. 

Now, the Drupal 9 has paved the way for an even more delightful web building experience. Known to be the easiest upgrade in over a decade, it is going to take Drupal 8’s innovative streak even further. Here’s everything you will want to know about Drupal 9.

NBC, MTV UK, Amnesty International and University of Oxford are some of the elite clientele of Drupal and their websites are a true epitome of Drupal’s abilities. 

“Make something amazing, for anyone”  - a motto of a kind should have been pretty self explanatory of Drupal’s essence, but it has acquired bragging rights and rightfully so. Hence, a little more elaborated boasting was mandatory.  

Taking the Headless Route 

Drupal’s abilities, features and all that it encompasses has made it one of a kind. At the top of the list of its unique abilities is its ‘headlessness’. I know this is going to sound strange, but it is a fact and a very beneficial one at that. 

Like I mentioned above, Drupal has all the features to make a web experience up and running and quite smoothly too. Having so many modules, themes and distributions, web builders would not find any need to look for additional features in their site. The entire web project would be placed inside Drupal and it would be entirely responsible for all of the project's needs. 

However, sometimes developers want to try more and Drupal lets them. It essentially removes its head, that is the presentation layer, to make room for a different one, that is other frontend technologies, and lets the developers only utilise it for its body, that would be its backend capabilities. So, in a truly Headless Drupal architecture, you would only use Drupal as a content repository and nothing else. This is also known as Decoupled Drupal, since you are going to be separating the couple, the frontend from the backend. 

When you go headless, you will be parting with Drupal’s frontend capabilities, but the separation does not have to be final. Decoupled Drupal comes with two options for you to choose from; 

  • One is the fully decoupled Drupal or the Headless Drupal. This completely segregates the two ends of a web project. Drupal takes command of the backend, while other frontend technologies, like JavaScript take hold of the frontend; both being connected by an API for the transmission of the information. 
  • Then there is the less final, progressively decoupled Drupal. In this architecture, you are still left with some of Drupal’s frontend capabilities. This means you can combine other frontend technologies to work with Drupal and get the most for your website, without losing Drupal out-of-the-box capabilities.  

Do you benefit from the going Headless?

Drupal has numerous benefits when you use it as a whole for building projects from the ground up; however, the decoupled Drupal comes with a tad more advantages. That is why it is becoming a vogue today, with several traditional Drupal sites converting themselves into the decoupled ones. 

So, yes, you will indeed benefit from taking the headless route. 

Aids in publishing on multiple platforms 

Going Headless makes it very easy to publish content on multiple platforms, be it your primary website, social media handles, intra sites or even print and media. The write once, publish everywhere features lets you capitalise all the IOT devices and publish on them.

Aids in maximising user experience 

The growth of your online business is directly proportional to the user experience you provide. The better the UX, the higher the conversions. UX is further dependent on your site’s performance. Having two separate ends enhances it, the request time is reduced with a client-side server and your site would be nothing but speedy.

Aids in making your team independent 

When you have a separated front and backend, that means you have the power to work faster. The frontend developers will only be focused on the user interface and the backend developers will only need to worry about those needs. Your teams can even make changes on their respective layers without having to worry about impeding the work of the other. All of this results in faster work speed and increased efficiency.  

Aids in enhancing creativity 

Drupal is a robust software, yet it can be stuff sometimes. You have to follow its guidelines and set standards or the work won’t get done. This hampers the development team’s creative flair. However, by adopting other, more flexible, frontend technologies through decoupling, you can let your creativity run free. 

Aids in faster upgrades 

Headless Drupal separation of concerns makes it simple to upgrade without impeding on your site’s current workings. It also gives you the opportunity to test on a dummy web service, which acts as a mockup, aiding you further in making revisions to your site.

Aids in taking advantage of JavaScript 

The final and probably the most compelling advantage of decoupled Drupal is the use of JavaScript. JS has the ability to make websites extremely interactive, with features like destructed assignment and arrow functions in the latest version. Since site interactivity with the user has taken precedence over anything else, decoupling has become more of a need. React, Angular and Vue are some of the most eminent JS frameworks that are used when going Headless. 

To know everything about headless Drupal and its suitability, read our blog, “When to move from monolithic to decoupled Drupal architecture.”

In Comes AngularJS

Now that we have discussed one part of the title, let’s move on to the second, which is AngularJS. You may know that a major reason behind going headless is the fact that it allows the user to incorporate other frontend technologies into Drupal and get the desired web building experience and the product as well. AngularJS is one such technology. Let’s get into its details.

The logo of Angular is shown.

What is AngularJS?

We ended the headless Drupal discussion at JavaScript, so it is only wise to begin the new one with JavaScript as well. AngularJS operates on JavaScript, being an open-source front-end web framework. It helps you create dynamic web pages through its structured framework. 

HTML’s template language is integral when building web projects. However, there is one problem with its use. HTML has proven its potential for static documents, however, when dynamic views come to play, it becomes lacklustre and chaotic. Now, in such a scenario, AngularJS comes in to save you. It allows you to extend the HTML vocabulary for your project, paving way for your developers to work in an environment that is expressive, readable and fast to develop. 

There aren’t many frameworks that have the ability to solve the HTML conundrum, what they do instead is abstract away HTML, CSS and JS or they might manipulate the DOM. covering up the problem is not really a solution and AngularJS provides an extension of HTML, making it worthy for dynamic views. 

The crowning jewel of AngularJS is its ability to adapt. It can easily be modified or replaced to make it suitable for any of your development needs. Whatever your workflow and feature require, AngularJS has the ability to provide. The fact that it is completely extensive and compatible with other libraries. 

Talking about the technologies Angular belongs to, it is part of the so-called MEAN stack. The MEAN refers to MangoDB, Express, Angular and Node.js. The combination of these four accounts for a firm ecosystem that is also backed by full-stack developers.

Let's look at AngularJS’ market share to understand its prominence even more. 

A list of the top industries using AngularJS is shown.(a)A list of the top websites built on AngularJs is shown.(b)A list of the countries is shown that use AngularJS with the number of websites using it.(c) | Source: SimilarTech

All of these numbers are pretty self-explanatory of AngularJS’ popularity in the market. 

What are the benefits?

Built in 2010 by Google, which is to this date responsible for its maintenance along with an entire community of developers and companies, AngularJS is quite a technology to utilise for your project’s development. It’s numerous benefits will make you believe me even more. 

Angular is flexible 

Angular by nature, or maybe its build, is extremely lightweight and concise. What this translates into is a working environment that is so extensible that you would be able to create things you never deemed possible. 

Angular uses directives 

Like we discussed above, Angular is unique because it is able to extend HTML. And this is possible because of Directives. Through these, special behaviours are assigned to the Document Object Model, which in turn enables your developers and engineers to use HTML and create dynamic and rich content. 

Angular binds your data two ways 

It is a known fact that Angular gives your developers the power of developing at a much faster rate. Multiple views, asynchronous technique, SEO friendly development are amongst a few of the immensely impressive features of Angular. And all these are possible because it works on the MVC architecture.  Because the Model-View-Controller framework synchronises the Model and the View, so when one changes, the other changes automatically. And work gets done faster. 

Angular injects dependencies 

When developers code, all the different pieces of that code have to interact with each other. This interaction also means that they are going to be affected by each other;s changes. This scenario is defined as dependencies. 

AngularJS solves this issue of dependencies in code simply by decoupling them using injectors. A dependency injector has the ability of making individual components easy to manage, test and reuse; maybe even more than before. 

Angular aids testing 

Lastly, AngularJS also makes unit testing pretty convenient for you. It has a built-in setup that makes testing the code much simpler and faster for your developers. 

The things you can do using AngularJS are much more advanced than Drupal’s frontend capabilities. So, combining the two is going to be a partnership that will make work wonders for your web project. 

The best of both worlds

The Drupal and Angular logos can be seen together.

Up until now we have been talking Decoupled Drupal and Angular individually and they have certainly been impressive enough. Both Drupal and Angular are equipped to build projects that will cater to any and all of your needs.

When paired together, they seem to be packing a punch. Your web projects will be able to accomplish so much more. Let’s have a look at some of the most intriguing features.  

Performance that will leave you spellbound 

A site’s performance is what sets it apart from others, it is what will keep your visitors scrolling through your pages and finally clicking on that coveted Buy Now tab. So, how do Drupal and Angular together help in improving your site’s performance?

If I talk about Drupal, it provides functionality in tons. Just working with drupal can make your site perform impeccably. Now, if you combine the Angular technology with it, you will end up with a performance that would be even better. That is because you will be able to offload business logic to AngularJS as it is client-side, you would not be able to do it completely, but even some part of the offload can be extremely effective. 

Furthermore, when you go Headless and take up Angular, you would use the latter for theming and presentation, while Drupal would only be responsible for the backend data source. This would enable you to move the display logic to the client-side, helping you in streamlining the backend. The resultant site is going to end up as fast as The Flash himself, for lack of a better metaphor.

Coding that will free up your developers 

When you use Drupal to build a regular, basic website, you would not need to write a lot of code and the development work would also be quite minimal. Yes, a basic Drupal site would not be feature packed and that is where AngularJS would enter. 

AngularJS will take an ordinary Drupal site and make it extraordinary, so to speak. Angular can make sites more interactive, more dynamic and richer in experience, and complex coding would not be a prominent part of this picture. 

By using directives, HTML, plain objects and other features, the JS framework requires very little effort from your developers in terms of coding. Despite the minimal efforts, you will still end up with the interactive pages that were only possible to get with a complete JS coding. 

Logic that will clean up your code structure 

You remember we talked about the MVC architecture in the previous section? I would have to be redundant and mention it again since it serves a lot of benefits when going headless. 

The Model-View-Controller architecture works on a principle that essentially segregates itself into three parts; 

Business logic;
Controller logic; 
And model logic. 

This results in a separation of your application logic from the user interface. And why is that essential? Because it aids in making the code structure cleaner, without much redundancy and more clarity. 

Imagine if one of your developers has to leave in the middle of your project. This could become devastating for your project, but an isolated code would make it extremely convenient for any other developer to pick up the left pieces and continue with the same effectiveness as before. 

AngularJS and Drupal also work well together because the MVC framework helps in eliminating a lot of backend logic from Drupal. Consequently, your site will turn out to be both extremely lightweight and efficient.

Security that will keep you shielded

Both Drupal and Angular are backed by a massive community. This means that there all the security features are always under scrutiny and the chance of things going sideways is slim to none. 

Add to this the fact the Drupal’s security protocol, if followed to the T will provide you an assurance of safety that not many CMSs can. Further adding to this, the combination of Headless Drupal and AngularJS will enable an extra layer of security to your site because there won't be any direct server-side interaction, the browser will only communicate with AngularJS.

The result of all of this would be that your site will become immune to malicious code that the notorious hackers are known to inject in your databases. And all would be well in the web world.

Everything about leveraging decoupled Drupal and different frontend technologies can be accessed here

Summing Up 

When decoupling is considered, tapping into the available frontend technologies is the paramount concern. JavaScript is most definitely at the forefront of the developers’ mind for the presentation layers. 

Angular is one of the flag bearers of JavaScript, and Drupal is a prominent name in the CMS world. Be it dynamic sites or interactive interfaces, the possibilities of with the combination of these two powerhouses. So, when are you taking them up?

Jan 20 2021
Jan 20

People today do not like to be confined, if I talk about development teams, they would hold up flags stating the same. Since development and innovation go hand in hand and constraint is the biggest enemy of innovation, you can’t tell me they are wrong to have that notion. 

Talking specifically about web developments, there are a lot of areas to explore and a lot of technologies to help you do that. So, why limit yourself, when you don't have to? Drupal has brought such an impressive trend forward that has simply satiated the developer’s desire for innovation and that is the headless approach

Unlike before, when your entire project had to be nestled inside one CMS, Drupal now gives you the opportunity to explore new technologies to your heart’s desire. This is possible because the presentation layer and the backend content become two separate entities. Drupal acts as the content repository and a frontend technology of your liking takes care of, of course, the frontend part of website architecture.

To provide a connection between the separated development aspects of the project, enters the API. An API layer is a necessity when going headless, because it transmits all the information from the front to the backend and vice-versa. 

And the three available APIs in Drupal, REST, JSON and GraphQL, are the reason behind me writing this blog. Although the purpose of all three is the same, they are quite different from one another. Today, we would be highlighting their meanings, their pros and cons and all the visible distinctions they have. So, let’s begin. 

Decoding the APIs 

The logos of GraphQL, JSON and REST are displayed horizontally.


REST, JSON and GraphQL bring in a similar outcome when they are used for decoupling Drupal. Yes, they are different too. And we would get into the difference between REST, JSON and GraphQL soon. Before that it is essential to understand their history, origin and what they were intended for because the differences actually start from there. 

REST 

REST was developed by Roy Fielding in the year 2000, the purpose behind its development was to provide a software architectural design for APIs. In simple terms, it provided an easy path for one computer to interact with another by utilising an HTTP protocol. The communication between the two computers is not stored on the server, meaning it is stateless; rather the client sessions are stored on a client-side server. 

There are six constraints necessary to implement REST in the complete sense. 

  • It needs a separated client and server; 
  • It needs to be able to make independent calls;
  • It needs to able to store cacheable data;
  • It needs to have a uniform interface;
  • It is a layered system; 
  • Finally, it needs a code-on-demand. 

REST offers a great deal of functionality without a lot of effort. For instance, if you are working on someone else’s RESTful API, you would not need a special library or special initialisation. Yes, your developers need to design their own data model using REST, but the HTTP conventions at play make programming a breeze. 

To know how REST plays a key role in decoupling Drupal, read our blog REST APIs in Drupal.

JSON: API  

JSON stands for JavaScript Object Notation. Built in May of 2013, it was designed as an encoding scheme, eliminating the need for ad-hoc code for every application to communicate with servers, which use a defined way for the same. JSON: API, like the name says, is a specification for building APIs using JSON. 

With JSON: API, communication between the server and the client becomes extremely convenient. It not only formats the way a request should be written, but the responses also come in a formatted manner. The primary aim of JSON: API is to lessen the number of requests and shrink the size of the package, all using HTTP protocol. 

Broadly stated; 

  • JSON reduces the number of requests and amount of data being transmitted; 
  • It requires zero configuration; 
  • It uses the same JSON access scheme for every piece of data, making caching very effective;
  • It offers quite a few features and gives you, as the client, the opportunity to turn them on or off. 

To know how JSON:API plays a key role in decoupling Drupal, read our blog, JSON API in Drupal.

GraphQL 

While JSON can work alongside REST, GraphQL was designed as an alternate to it and some of its inconveniences. Built in 2012 by Facebook, it acts as a cross-platform data query and manipulation language. Its servers are available in numerous popular languages, being Java, JavaScript, Ruby, Python, C#, amongst others. 

The features of GraphQL are that; 

  • It allows users to request data from multiple resources in a single request.
  • It can be used to make ad-hoc queries to one endpoint and access all the needed data.
  • It gives the client the opportunity to specify the exact type of data needed from the server. 
  • All of these add to its predictable data structure, making it readable as well as efficient. 

It was in 2015, after GraphQL was open-sourced that it became truly popular. Now its development is governed by The GraphQL Foundation, which is hosted by the Linux Foundation. 

To know how GraphQL plays a key role in decoupling Drupal, read our blog, GraphQL in Drupal.

Now that we know the basics of all the three APIs, let us have a look at their popularity status, before beginning the comparison. 

A bar graph shows the standing of different web services against each other.A glimpse at the popularity of the three APIs. Source: State of API Report 2020

REST vs JSON vs GraphQL 

Now let’s get down to the details and understand why choosing one over the other two could be in your best interest. Let’s start with the differences between REST, JSON:API and GraphQL.

How efficient is the data retrieval?

A distinction is shown between the three APIs, REST, JSON and GraphQL, in three circles with regards to data retrieval..


One of the most important aspects for an API is the way its fetches data. It could require one or more requests. Therefore, this aspect is also referred to as its request efficiency. Getting multiple data responses in a single request has to be an ideal, so let’s see how REST, JSON: API and GraphQL here. 

REST 

The REST API is innately built to capitalise one resource per request. This works perfectly as long as you only need to retrieve a single piece of data like an article. However, if you need more than that, the number of requests you would have to type in separately would be equivalent to the amount of data you need. 

One article = one request 
Two articles = two requests
Two articles and the author information stored in a different field = Two requests for the articles + a long wait for the completion of those requests + two additional requests for the author information. 

This sums up REST’s request efficiency to the T. You require to be equipped to handle a number of requests, which can ultimately stall your user experience, making it seem to go at a snail’s pace. No sugar-coating here, there are going to be a lot of round trips. 

And the problem with a lot of round trips is a lot of extra information you do not even need. This is because there is a possibility that a REST API endpoint might not have the required data for an application. As a result, the said application will not get everything it needs in a single trip, making multiple trips the only option. It's safe to say that REST over-fetches and the verbose responses can be a problem.

JSON: API 

JSON: API does not suffer from the multiple request conundrum. One single request can give you everything you want, be it one article, two or ten along with the author’s information, I kid you not. 

This is possible because JSON: API implements a concept called ‘sparse fields.’ What this does is list the desired resource fields together for easy fetching. You can have as many fields as possible. If you feel the fields are too long and would not be cacheable, you can simply omit a few sparse fieldsets to cache the request. 

Another thing to remember is that the servers can choose sensible defaults, so your developers would need to be a little diligent to avoid over-fetching. 

GraphQL 

Coming to GraphQL, it was also designed in a similar fashion to JSON: API and is competent enough to eliminate the problem of over-fetching and avoid sending multiple requests. 

GraphQL has its own queries, schema and resolvers that aid the developers in creating API calls with particular data requirements in mind. Moreover, by mandating clear-cut additions to every resource field in every query and ensuring the developers cannot skip any of it,  it is able to avoid multiple round trips. Thereby, making over-fetching information a thing of the past. 

The only problem here can be that the queries may become too large, and consequently, cannot be cached. 

How is the code executed?

The distinction between REST and GraphQL is shown with regards to code execution.


Using an API for calls involves the execution of a code on the server. This code helps in computing, calling another API or loading data from a database. All three of the APIs use a code, however, the code is implemented varies a little.

REST 

Route handlers are utilised for execution upon a REST call. These are basically functions for specific URLs. 

  • First the server receives the call and retrieves the URL path and GET; 
  • Then the functions are noted and the servers begins finding the same by matching GET and the path; 
  • After that the result is generated, since the server would have executed the function; 
  • In the final step, once the result is serialised by the API library, it is ready for the client to see. 

GraphQL

GraphQL operates in a relatively similar manner. The only difference is that it uses functions for a field within a type, like a Query type, instead of using functions for specific URLs.  

Route handlers are replaced by resolvers in GraphQL, they are still functions though.

  • After the call is made and the server has received a request, the GraphQL query is retrieved. 
  • The query is then examined and the resolver is called upon for every field. 
  • Finally, the result is added to the response by the GraphQL library and it is ready for the client to see. 

It should be noted that GraphQL offers much more flexibility as multiple fields can be requested in one request, and the same field can be called multiple times in one query.  The fact they let you know where you performance needs fine-tuning makes resolvers excellent trackers as well. 

This is simply not possible in REST and JSON. Do you see the difference in implementation? 

How do the API endpoints play a role?

Many a time, it is seen that once the API is designed and the endpoints are sealed, the applications require frontend iterations that cannot be avoided. You must know that the endpoints aid an application to receive the required data just by accessing it quickly in the view, so you could call them essential even. 

However, the endpoints can pose a bit of a problem for the iterations, especially when they need to be quick. Since, in such an instance, changes in the API endpoints have to be made for every change in the frontend, the backend gets tedious for no reason at all. The data required for the same can be on the heavier side or the lighter side, which ultimately hampers the productivity. 

So, which API offers the solution?

It is neither REST, nor JSON. GraphQL’s flexibility makes it easy for the developers to write queries mentioning the specific data needs along with iterations for the development of the frontend, without the backend having to bear the brunt.

Moreover, GraphQL’s queries help developers on retrieving specific data elements and provide insights to the user as to which elements are popular and which aren’t amongst the clients.  

Why doesn’t REST? 

The answer is simple, REST has the entire data in a single API endpoint. Being a user, you won’t be able to gain insights on the use of specific data as the whole of it always returned. 

How good is the API exploration?

A distinction is shown between the three APIs, REST, JSON and GraphQL, in three circles with regards to API exploration.


Understanding your API and knowing about all of its resources and that too quickly and with ease is always going to benefit your developers. In this aspect, all three perform pretty contrastingly. 

REST 

REST gives a lacklustre performance in API exploration to be honest. The interactivity is pretty substandard as the navigation links are seldom available. 

In terms of the schema, it would only be programmable and validatable, if you are going to be using the OpenAPI standard. The auto-generation of the documentation also depends on the same. 

JSON: API 

JSON performs better than REST. The observation of the available field and links in JSON: API’s responses helps in its exploration and makes its interactivity quite good. You can explore it using a web browser, cURL or Postman

Browsing from one resource to the next, debugging or even trying to develop on top of an HTTP-based API, like REST, can be done through a web browser alongside JSON. 

GraphQL 

GraphQL is indeed the front-runner here. It has an impressive feature, known as the GraphiQL, due to which its API exploration is unparalleled. It is an in-browser IDE, which allows the developers to create queries repeatedly. 

What is even more impressive is the fact the queries get auto-completed based on the suggestions it provides and you get real-time results. 

Let’s focus on schema now 

A distinction is shown between the three APIs in terms of schema using three circles.


Schemas are important for the development team, the frontend and the backend equally. It is because once a schema has been defined, your team would know the data structure and can work in parallel. Creating dummy test data as well as testing the application would be easy for the frontend developers. All in all, the productivity and efficiency levels elevate. 

REST

REST does have an associated expected resource schema since it is a set of standard verbiage. Despite this, there is nothing that is specifically stated in them. 

JSON: API 

In terms of schema validation and programming, it does define a generic one, however, a reliable field-level schema is yet to be seen. Simply put, JSON is basic with regards to schema. 

GraphQL

The fact that GraphQL functions completely on schemas makes it a pro in this regard. The schema used here is Schema Definition Language or SDL. What this means is that GraphQL uses a type system that sets out the types in an API because all the types are included in SDL. Thus, defining the way a client should access data on the server becomes easy. 

To conclude this point, I would want to say that when there is immense complexity in the schema and resource relationships, it can pose a disadvantage for the API.  

How simple is to operate it? 

The operational distinction is shown between the three APIs in three circles.


Operating an API essentially involves everything, from installing and configuring it to scaling and making it secure. REST, JSON: API and GraphQL, all perform well enough to make themselves easy to operate. Let’s see how. 

REST 

REST is quite simple to use, a walk in the park for a pro developer. It is because REST is dependent on the conventional HTTP verbiage and techniques. You would not need to transform the underlying resources by much, since it can be supported by almost anything. It also has a lot of tools available for the developers, however, these are dependent on their customisation before they can be implemented. 

In terms of scaling, REST is extremely scalable, handling high traffic websites is no problem at all. To take advantage of the same, you can make use of a reverse proxy like Varnish or CDN. Another plus point of REST is that it has limited points of failure, being the server and the client. 

JSON: API 

JSON: API is more or less the same as REST in terms of its operational simplicity, so much so that you can move from REST to JSON: API without any extensive costs. 

  • It also relies on HTTP; 
  • It is also extremely scalable; 
  • It also has numerous developer tools, but unlike REST, JSON: API does not need customised implementations; 
  • Lastly, JSON also has fewer failure points. 

GraphQL 

GraphQL is the odd one out here. It isn’t as simple to use as the other two. It necessitates specific relational structure and specific mechanisms for interlocking. You would be thinkin that how is this complex? Let me ask you to focus on word specific, what this means is that you might need to restructure your entire API with regards to resource logic. And you must know that such restructuring would cost you time, money and a boatload of efforts. 

Even in terms of scalability, GraphQL does not fare very well. The most basic requests also tend to use GET requests. For you to truly capitalise GraphQL, your servers would need their own tooling. If I talk about the points of failure here, even those are many, including client, server, client-side caching and client and build tooling. 

What about being secure?

The security distinction is shown between the three APIs in three circles.


The kind of security an API offers is also an important consideration in choosing it. A drastic difference is noted in REST and GraphQL. Let’s see what that is. 

REST 

REST is the most secure amongst the three. The intrinsic security features in REST are the reason for the achievement. 

  • There are different APU authentication methods, inclusive of HTTP authentication;
  • There are the JSON Web Tokens for sensitive data in HTTP headers;
  • There are also the standard OAuth 2.0 mechanisms for sensitive data in JSON structure. 

JSON:API

JSON:API is on a similar footing to REST in terms of security. The reason being the fact that like REST it exposes little resources.  

GraphQL 

It is not like GraphQL is not secure, it is; however, the security has to be manually attained. It is not secure by default and it is not as mature as REST in this regard. 

When the user has to apply authentication and authorisation measures on top of data validation, the chances of unpredictable authorisation checks rise. Now, do I have to tell you that such an event is bound to jeopardise your security? 

How is the API design pinpointed?

The distinction for API design is shown between the three APIs in three circles.


If an API has to perform well for every use case, you have to make it do so. By creating such design choices that are a result of your understanding of the users’ needs. You cannot just go with the flow, evaluating how your users are going to be interacting with your API and getting an understanding of the same is key for your API’s design. 

REST

For REST, this exercise of deciphering the user requirements must happen before the API can be implemented. 

GraphQL 

As for GraphQL, this apprehension can be delayed a little. By profiling the queries, you would be able to tell their complexity level and pinpoint the sluggish queries to get to an understanding of user’s consumption of the API. 

What about their use in Drupal?  

The distinction for Drupal installation and configuration is shown between the three APIs in three circles.


Drupal is an important player when it comes to building websites and managing their content. With decoupling Drupal becoming more and more popular, it has become crucial to understand how the APIs perform alongside Drupal. 

REST 

Talking about the installation and configuration of REST, it can be complicated at best. The fact that the REST module has to be accompanied by the REST UI module does not ease the complexity. 

With REST, the clients that cannot create queries with the needed filters on their own, since the REST module does not support client-generated collection queries. This is often referred to as decoupled filtering.  

JSON:API 

JSON:API module landed in Drupal core in Drupal 8.7. JSON:API’s configuration is as easy as ABC, there is simply nothing to configure. JSON is a clear winner in this aspect. 

Moving to client-generated queries, JSON does offer its clients this luxury. They can generate their own content queries and they won't need a server-side configuration for the same. JSON’s ability to manage access control mechanisms offered by Drupal make changing an incoming query easy. This is a default feature in JSON:API.

GraphQL 

The installation of GraphQL is also not as complicated as REST, but it isn’t as easy as JSON as well. This is because it does mandate some level of configuration from you. 

Similar to JSON, GraphQL also offers decoupled filtering with client generated queries. A less common trend amongst GraphQL projects is seeking permissions for persisted queries over client-generated queries; entailing a return to the conventional Views-like pattern.

In addition to these three major Drupal web services, explore other alternatives in the decoupled Drupal ecosystem worthy of a trial. Read everything about decoupled Drupal, the architecture-level differences between headless and traditional setups, different ways to decouple Drupal, and the skills required to build a Decoupled Drupal web application to know more.

Concluding with the basics 

To sum up, let us look at the fundamental nature of the three APIs, which entails two aspects; simplicity and functionality. 

In terms of simplicity, REST is a winner. A second would be rewarded to JSON, while GraphQL would not and could not be described as simple, complex and that too immensely with major implementations coming your way would be a more accurate description. In terms of functionality, GraphQL does offer the most. If you choose JSON over GraphQL, you would end up parting with some of its features unfound in JSON. 

All three are powerful and efficient in what they can do for your application. The question is how much complexity are you willing to take up with that power?

Jan 18 2021
Jan 18

Websites have entered a new playing field now, at least compared to what they used to be a few decades ago. They are not one-dimensional anymore. They represent a multitude of different business agendas that are essential for growth and visibility.

Websites are not just limited to words, their world has widened progressively. From animations to social media integration, websites today can do it all. A major reason for these advancements in websites and their build is the software they are built on. And that is going to be the highlight of this blog.  

We will talk about the Content Management Systems and the Static Site Generators and shed light on their uses, their suitability and whether they can work in sync or not? So let’s begin. 

Understanding a CMS 

There is a time line showing the emergence of various open source CMSs.Source: Opensource.com

Commencing with the veterans, CMS or a Content Management System have been around for almost two decades (Drupal, one of the world leaders in web content management, was initially released on 15th January 2001). Despite being that old, the conventions they are built on and the features they have been added with over the years have resulted in CMSs being as modern as modern as can be. 

From easing the workload off of the bloggers’ shoulders to making newspaper editors happy; from catering for corporations and their digital marketing team to aiding numerous government departments online and transparent, a CMS has a wide audience. 

If I had to define a CMS, I would simply call it the one-stop destination for all your website’s content needs. It manages, organises and publishes web content. What is more impressive is that content authors can create, edit, contribute and publish on their own, they do not need to be dependent on developers for that. A CMS offers a collaborative environment to build and present websites, allowing multiple users to work with it at once. Terms like Web Content Management and Digital Experience Platform are being thrown around today and they are nothing, but a modern variant of a CMS. 

Getting into the meaning of CMS a little further, you would hear two versions of it and they are essentially its break down. 

  • First would be the Content Management Application. This makes marketers, merchandisers and content creators self-reliant. They can do the contextual heavy-lifting on their own with a CMA without the requirement of a code, so, none of the guys or girls from IT would be needed. 
  • Next is the Content Delivery Application. This is basically the foundation for your content; the back-end aspect that placed your content into templates to be further presented as one website. So, what your audiences see is provided by the CDA. 

Both of these together make a CMS whole for your use. 

Moving further, after the meaning, it is time to get a brief understanding of the various categories of a CMS. Based upon different categorisations, there are seven in all.

Based on the CMS’ role 

Traditional 

Most often, a traditional CMS is used on really simple marketing sites. I have used the term simple to describe it because it is just that, be it the layout or general functionality. You can create and edit your content using a WYSIWYG or HTML editor and it would display the content as per the CSS you have used.

With a traditional CMS, your entire site is encompassed by one software. The frontend and the backend are closely connected through it, hence, it is also referred to as a Coupled CMS. 

Decoupled 

Unlike its traditional counterpart, the decoupled CMS separated the frontend from the backend. This means they work independent of each other and a change in the presentation layer does not necessarily affect the backend repository. Through decoupling, you get the features of more than one software to base your site’s architecture on. 

Headless 

A headless CMS is more or less similar to a decoupled one. When you take up a headless CMS, your content would always remain the same, however, each of your clients, be it an app, a device, or a browser, would be obligated for the presentation of the content. 

The code in this instance is not in the CMS, rather it is an API that is used for communication and data sharing amongst the two software. This way developers can consume content through an API and content authors can start adding content at the same time. If you are looking for the ‘one size fits all’ approach, this is where you will find your answer. 

Based on cost and ownership 

Open source 

Open source CMSs are the ones that are free of cost, at least initially. You do not need to pay for any license fee for its installation; however, there can be costs that you may incur for add-on templates and more such features. 

Open Source CMSs are pretty popular today, the reason being their thriving community of developers. This results in the veterans redistributing and modifying the code, which not only leads to perpetual software improvements, but also helps the newbies in making progress. 

Proprietary 

A proprietary CMS is the exact opposite of an open source CMS, meaning it is commercial and mandates a licensing fee along with annual or monthly payments. In return for the payments, you would get an out-of-the-box system to meet all your companies requirements, continuous support and built-in functionality.

Based on the location 

On premises 

As the name suggests, this is a CMS that has a physical presence within the company’s premises. The high degree of control it offers to its users is the reason for its popularity. However, the humongous investment and the chances of human error dampen its potential. 

Cloud-based 

The name gives it away. Such a CMS is hosted on the cloud and delivered through the web. It is essentially the combination of web hosting, web software components and technical support. It provides fast implementation and deployment along with accessibility from across the globe on any device.

Why choose a CMS? 

Moving further, let’s now delve into the multitudinal features that are packed inside a CMS making it a suitable choice for you and your organisation’s virtual needs.

If I had to broadly categorise all the features of a CMS, I would end up with three major categories, which will sum up the true potential of this software. 

Content and its production needs

Producing content is the primary reason anyone takes on a CMS. It is true if you are a blogger and it is also true if you work for an educational institution and its online persona. It is the content that speaks for itself, when it comes to your site and it needs to be pristine, for lack of a better word. And CMSs help you achieve a level of control over your content production that you desire.

  • Starting with the edits, the WYSIWYG editor could be deemed as the heart and soul of a CMS. It provides you formatted text in paragraphs with quotes, superscripts, underlines as well as images and videos. Your authors would not have to work around codes for sure. 
  • Focusing on the media, images are an important part of it. Every CMS has room for them, they can be uploaded directly from your computer or archives, either within the content or you can add them in the page itself. The same is true for pdfs, animations and videos. Videos also have the option of being embedded through Youtube. 
  • Furthermore, CMSs also support multilingual and multi-channel sites. This eases the pressure off of the content authors and makes localised projects easy to run. 

Content and its presentation needs

Presentation is all about design, how it is done and how it would be showcased to the end user. There are a lot of design considerations that a CMS can help you with. 

  • A CMS would have you sorted with the right font and its size and the right colours and contrast. 
  • A CMS would have your sorted with the right responsiveness for your site. 
  • A CMS would have you sorted with the right URLs and URL logic. 
  • A CMS would have you sorted with the right templating tools to change your layout. 
  • A CMS would have you sorted with the right hierarchy for your site as well as provide the right prominence to the aspects that need it. 
  • Finally, a CMS would have your site sorted for all the right accessibility protocols to make it universally accessible. 

Content and its distribution needs

Once the content is produced, its distribution comes into play. This has a direct impact on your site's visibility. And CMSs ensure that you get the most out of it. 

  • The foremost part of distribution needs is metadata. This helps in tagging, categorising and describing your content. It includes everything from keyword insertion to identifying the distribution channels and placing access restrictions on the content. 
  • Secondly, CMSs also come equipped with automated marketing tools like analytics and A/B testing that help you understand user behaviour and help you capitalise it. You would just have to define the parameters and the automation would do the rest, be it publishing on your site or email marketing. 

Content and its management needs

Then comes the management of your content, it is a perpetual process that helps in providing an ease to the editors and developers that streamlines the builds and updates of a website. 

  • For one, a CMS helps you plan and execute the publishing of your content. You can actually schedule when and what to post and where to post it. You can also decide when something would be available for the audience to see and when it won’t be like an events’ post. Once the event has happened, it won't need to be on your site anymore and a CMS helps with that. 
  • CMSs also help you to figure out user roles and implement them. This helps in ensuring that sensitive information is only accessible to the users who have the clearance. A manager and a director are going to have different roles, so does a premium member and a regular member of your site. 
  • Finally CMS helps you in avoiding instances where you delete something important and its recovery becomes impossible. Version control and revisions are a feature that has to be in your CMS, if you want the powers to bring back the lost content. 

Apart from these main categories, CMSs are also renowned for their security, their scalability and user friendliness. There is one more thing to add and that is the fact that a CMS can go above and beyond it capabilities by integrating itself to third-parties and combining their features with its own, a headless CMS is an example of the same. Drupal is one of the most popular CMSs, when it comes to going headless. Read our blog, Decoupled Drupal Architecture to know more about it.

Understanding a new vogue: Static Site Generators 

Before understanding a static site generator, let’s shed some light on static sites, since these are what it builds. A static site is the one that is designed in a way that it remains static, fixed and constant, during its design, its storage on a server and even upon its delivery to the user’s web browser. This is the attribute that differs it from a dynamic, it never changes, from the developers desktop to the end user’s, it remains as-is.

Coming to Static Site Generators or SSG, in the most basic of terms they apply data and content to templates and create a view of a webpage. This view is then shown to end users of a site. 

Now let’s get a little technical, you know that an SSG will only create static sites, it does so by creating a series of HTML pages that get deployed to an HTTP server. There would only be files and folders, which points to no database and no server-side rendering.

Developers using an SSG, create a static site and deploy it to the server, so when a user requests a page, all the server has to do is find the matching file and route it towards the user. 

If I talk about the difference between an SSG and a conventional web application stack or a CMS, I would say that it is in the view of webpages. While an SSG keeps all the views possibly needed for a site at hand well in advance, a traditional stack waits until a page has been requested and then generates the view.

Why did SSG come along?

Static Site Generators act differently than a CMS, they are more aligned with the needs of static sites. However, their emergence has a bigger story to tell. 

Yes, CMSs are quite popular today, yet there is a drawback to that. With the rising acclaim of CMSs, some of them have become more prone to cyberattacks. The lead in security hacks goes to WordPress, with almost 90% of all hacks being experienced by it as reported by ITPRO reports of 2020. But, Drupal is considered the most secure CMS as can be seen in Sucuri’s 2019 Website Threat Research Report.

Then there is the issue of performance. CMS sites operate mainly upon their servers, meaning they do the heavy-lifting. If a request is sent, it would mean the server taking the charge of the page assembly from templates and content every time. This also means that for every user visiting your site, the PHP code would have to be run to start up, communicate with the database, create an HTTP response based on the recovered data, send it to the server and then finally, an HTML file is returned to the user’s browser to display the content after interpretation. All of this may impede the performance of the site built on CMS when compared to the one powered by a static site generator. But, it’s not like CMSes give you low-performance websites. They do have provisions for delivering high performance websites. It depends upon which CMS you go with. If web performance is your concern, Drupal can be your go-to option.

An SSG is a solution to these two conundrums, hence, it emerged with a bang. 

What can a Static Site Generator do for you?

there is clock in the middle with the benefits of a CMS written around it.

Static Site Generators solve a lot of the issues that a CMS cannot, consequently they can provide you a lot for your site’s well-being. 

SSG means better security 

In an SSG, the need for a server is non-existent and this is the reason it provides more security. As we have already established that an SSG is rendered well in advance and its ready-to-serve infrastructure helps remove any malicious intent upon your site. This infrastructure essentially eliminates the need for servers, they do not need to perform any logic or work. 

Apart from this, with SSG, you would not need to access databases, execute logical operations or alter resources for each independent view. As a result, there is an easy hosting infrastructure as well as an enhanced security because of the lack of physical servers required for fulfilling requests. 

SSG means elevated performance 

A website’s performance is concerned with its speed and request time, and SSG provides in this area as well. Whenever a page is requested, it involves a whole bunch of mechanism to get it displayed for the visitors. There is the distance it has to cover, the systems it has to interact with along with the work that those systems do. All of these take up time, shadowing your performance. 

Since an SSG site does not mandate such a lengthy iteration per visitor request, it reduces the travel time. This is done through delivering the work directly from a CDN, a distributed network of caches, which aids in avoiding system interaction. Resultantly, your performance soars 

SSG means higher scalability 

When an SSG builds a site, it is often considered pre-built. I mean that is what building all the views in advance of an actual request could be defined as, right? So, with a pre-built site, you have less work on your hands. For instance, a spike in traffic would not mandate you to add in more computing power to handle each additional request, since you have already done all the work beforehand. You would also be able to cache everything in the CDN and serve it directly to the user. As a result, SSG sites offer scalability by default. 

When should you choose a Static site generator?

Now that you know how an SSG can benefit you, it is time to understand the scenarios that would mandate taking up a static site generator and all its advantages. 

When building complex site is the goal 

If you want your website to deliver more complexity, in terms of the kind of features it provides, SSG becomes a good choice. There are many that come equipped to provide you client-side features that are ready to go. 

When creating and displaying content is the only goal

Here SSG is a suitable choice because it would generate pages and URLs for you. And these pages would give you a 100% control over what is being displayed, meaning the output would always be in your hands; content pages need that. 

When generating numerous pages is the goal 

A static site generator can create pages at a great speed. It might not be seconds, but it is quite fast. So, when creating websites that would need a lot of pages to be created, SSG’s speed comes in quite handy. 

When templating needs are complex as well 

An SSG is a powerful software, it has the ability to assess your site’s visual style and content along with its behaviour and functionality. This feature becomes fruitful, when building a website with diverse templating needs. Vue and React based SSGs would definitely help you get the versatility you need on your website, along with the standard use of concept of code reuse on your site. 

I would like to add just one more thing, and that is the fact that your team must be familiar with the static site generator that you are going to end up using. There are a lot in the market. If your team is familiar with .net, use and SSG powered with it. On the other hand if it finds JavaScript more familiar territory, go with an SSG based on that. Let your development team be a part of the discussion, when the suitability of a static site generator is being decided. 

Are Static Site Generators always the right option? 

Coming from the suitability, you would think that an SSG is a great choice. Don’t get me wrong, it is. However, it isn’t a universal software. There are instances when it may not be the right choice. So, let’s delve into these scenarios.

Not when you do not have development experience 

Static Site Generators become a tad bit difficult for amateur developers. Your developers ought to have experience to reap all its benefits. The building process is considered to be more difficult than that of a CMS, something that finding plugins for pre-built pages acn become a chore. Furthermore, there isn’t a huge community out there to help you in the development part, if you are a beginner. 

Not when you need a site built urgently 

You have to understand the urgency and SSGs are not the best of friends. From learning the build process to developing the template code, everything needs time. 

There are development scripts to be me made;
There is the complication of customised them;
There is the additional process of creating and setting Markdown files;

All of these account to more time requirements for the development process. Think of it like this, you are going to be doing all the grunt work beforehand, and that would necessitate more time. 

Not when you need server-side functionality 

When partnering with an SSG, you would be parting with some, if not many, interactive functions on your site. For instance, user logins would be difficult to create, so would web forms and discussion forums. However, there are certain options like lunr.js search and Disqus commenting to help you with your sites interactivity. I would say that these options are pretty limited.

Not when your site has to have hundreds of pages

You might think that I am contradicting myself, however, I am not. Static site generators can create a website with a thousand pages, yet the process can become tedious and awkward. For a thousand or so pages, the content editing and publishing would be cumbersome. Along with this real-time updates could get delayed and like I mentioned before build times rise consequently.

Not when website consistency is a priority 

Lastly, SSG sites offer a lot of flexibility. That should be a good thing, however, it does have a side effect and that is on your site’s consistency. This is because anything that is found in the Markdown files can be rendered as page content. Consequently, users get the chance to include scripts, widgets and other undesired items. 

Can a CMS and an SSG work together? 

Yes, a CMS and an SSG can work together and pretty efficiently at that. However, that partnership is only possible in a headless CMS. This is because a headless CMS gives room for other frontend technology to come and play and in this case that technology is found in static site generators. 

A headless CMS is pretty versatile, choosing a static site to go as its head could help you get most of the benefits that both, the static site and headless CMS, come along with. This partnership indeed has a lot to offer. Let’s find out what that is. 

Two hands shaking can be seen on the left, with the benefits of a CMS and static site generators' partnership.

Proffers easy deployment via APIs

SSGs are quite straightforward to use, especially with an API, which is the connecting force between the SSG and the CMS. Pulling data from an API for generating and deploying a static PWA to any web host or Content Delivery Network is a breeze. 

Proffers ease to the marketing team 

When you work only with an SSG, you would face difficulties as it puts a lot of boundations on the marketing team. This isn’t a problem when you partner with a CMS. 

Proffers easy editing and workflow 

Conventionally, SSGs do not have a WYSIWYG editor or workflow capabilities for the tracking and collaboration of content. You might think that it is only needed for dynamic sites, but that isn’t the case. Static sites also need that. Since CMSs have that capability, they become ideal for content before actually running the SSG; the perfect contextual partnership. 

Proffers easy updates to sites 

With a CMS, you can easily change and update the content. With an SSG, the same changes can be pulled up through the APIs and a new static site can be generated every time they are incurred. All the developers have to do is set a tool up for content pulling and generation. As a result, your site would always be up-to-date and the users would not need to be processed whenever they visit your site. 

To check out some examples of how CMS and SSG can come together, read how Drupal and Gatsby can be leveraged for developing blazing fast websites. You can also go through the benefits of going ultra-minimalistic with the combination of Metalsmith and Drupal.

Conclusion 

In the end, all I want to say is that both a CMS and an SSG have their own set of features and capabilities that make them excellent at what they do, making their users more than happy. However, when it comes to getting the best out of both of them, there is only one kind of CMS that can help you reap the benefits of this dynamic. It is up to you to decide whether you want to use them together or individually.  
 

Jan 15 2021
Jan 15

First of all, happy twentieth birthday to Drupal. Yes, you heard that right. It is Drupal’s 20th birthday! Two decades ago, an idea was conceptualised to improve the cost efficiency of an internet connection by sharing it among a group of friends. That idea has now turned out to be one of the biggest open source projects in the entire world!

People holding up placards reading 'Happy 20th Birthday' and Drupal's logo


On the occasion of Drupal’s 20th birthday, let’s look back at how Drupal has evolved organically in the past two decades to become a sustainable community over the years, one that holds immense capacity to keep thriving despite all odds.

Drupal’s growth over the years

Drupal 1.0 was launched as an open source project, drop.org, in 2001. Dries based it off Slash, a modular CMS, the first version having 18 modules one could work with. Notably, there was no bar on who could contribute to the software. 

This is what it looked like -

Black and white screen of Drupal 1 website


Isn’t it substantial, how far we’ve come?

When Drupal was upgraded, Drupal 2.0 promised a feature where one could translate or overwrite their site in a different language. This laid a major mark in expanding but also bringing together the Drupal community. Other updates included user ratings, user permission system and sections for stories and user groups.

In the third major version, nodes were made the main unit of content in Drupal - in comparison to web pages, nodes provided the much needed flexibility in the Content Management System. Every category of content - whether an article, a news report or a forum - was created as a node and subsequently managed by a node module. Thus, Drupal became more convenient to use for everybody.

Drupal 4.0 was significant for the fact that it saw expansion like never before - armed with an e-commerce module in Drupal 4.4 and an WYSIWYG (What You See Is What You Get) editor, the fourth version of Drupal lay all its doors open. Web writers without a coding background could now use Drupal too, explaining the following surge in its usage after the release of the complete fourth version. 

Following its popularity, the first ever Drupal Conference was held in Belgium in 2005. Here’s Dries Buytaert’s ID from the event:

White ID card with Dries written on itSource : Dries Buytaert's blog

This is how Drupal started transitioning into a global community in the truest sense, with people from all walks of life, across the globe using and contributing to it.

By the time Drupal 5.0 was released on Drupal’s sixth birthday, the number of contributed modules had gone up to 2500 and that of contributors was 492! Version 5.0 simplified web development by incorporating jQuery, a javascript library that made HTML way easier. Also included was a provision of pre-created but customisable Drupal packages and improved CSS (Cascading Style Sheets) management for greater speed on the sites. 

The sixth version of Drupal saw a sitewide growth and expansion - 7000 contributed modules were already in place in addition to 34 core modules and 600 custom themes. Drupal 6.0 added a rewritten menu structure, a ton of drag-and-drop features, even better security etc

With Drupal 7 and 8, customisation and personalisation had come into play in the digital sphere, and Drupal adapted accordingly. Drupal 7 provided URL handling, integration with e-commerce, and custom fields that could be brought to use across content types and users. Using installation profiles, companies could now systematically distribute their website. 

This is a snapshot of Drupal 7. Drupal had now started to look like its modern day successor, hadn’t it?

Blue and white screen showing Drupal 7's websiteSource : Drupal.org

Drupal 8 rode the personalisation tide and responded aptly to the emerging needs of its user base, adding 200 essential features, one of those being adaptability of a website to the several devices it was accessed from. Personalised feeds and suggestions also came into play as businesses started to increasingly focus on User Experience. 

Called the ‘easiest upgrade in a decade’ by Drupal, Drupal 9 hit the market in the midst of a pandemic (which started making waves soon after Drupal’s nineteenth birthday), to cater to the needs of the worldwide user base stricken by it. Drupal 9 removed deprecated code and updated third party dependencies to curate digital solutions compatible with most businesses and individuals. Well, all your burning questions about Drupal 9 answered here.

Dupal 10 is slated to release in 2022 with a bunch of new features and upgrades!

OpenSense Labs and Team love Drupal! 

We at OpenSense Labs have been working with and loving Drupal for years now. Minimal learning curve, the support of a widespread community, and customisable components are some facets of Drupal that our developers are especially fond of. As Drupal turns 20, here’s what our in house Drupalists have to say about Drupal -

Pictures of 6 developers with text above reading what they say about Drupal


Once again, a very happy 20th Birthday, Drupal! Here’s to many more years of growth and innovation!

Jan 15 2021
Jan 15

It’s true that execution translates visions of the organisations into reality. Larry Bossidy and Ram Charan’s ‘Execution: The discipline of getting things done’ corroborates the same. In the software industry, it often translates to efficacious project management. Usually, a framework and specific methodologies are followed for the successful execution of a project. While the framework and methodologies are pivotal for project management, the human aspect of it can’t be sidelined.

A vector image with a human face and brain to represent human psychology in project management


Think of a Drupal project that is being undertaken by a project manager. He or she has a mix of experienced members and newbies in the team who would help in the speedy completion and timely launch of the Drupal website. Amongst everything else, the human factor here is very important to be considered. The psychological aspects of the individuals, both the project manager and the team members, can well be the decisive factor for a project to be a success or a failure. Their perceptions, emotions, problem-solving skills, decision-making processes among others can have an astronomical impact on the way project is being handled and executed.

Key competencies in project management

A heptagon formed by circles and text inside it to represent human factor in project managementSource: Project Times

Project management methodologies constitute technical and procedural factors like scoping, scheduling, budgeting, quality assurance, risk, communications and procurement. And, they all very well established frameworks. But, it’s the people who act as the core of project management. In a study titled ‘Human factor skills of project managers derived from the analysis of the project management processes’, emphasises that people, not objectives and processes, make the project successful.

bar graph showing statistics on human psychology in project managementImportance of project manager skills | Source: ResearchGate

Creating and managing the psychological contract between leadership and team is also a must. Project managers need a set of skills to perform at his or her best. These set of skills can be put together in the ‘Eye of Competence’ model, states the research paper titled ‘The psychological contract and project management as a core competence of the organisation’. They are:

  • Technical competencies
  • Behavioural competencies
  • Contextual competencies
pie chart in green showing textual information on human psychology in project managementSource: ScienceDirect

All the skills needed by the project manager related to project life cycle (initiate, plan, execute control, close) comes under technical competencies. The personal competence elements of project managers like attitude, abilities and behaviour come under behavioural competencies that help in dealing with different team-related challenges during the project lifecycle. Aligning project management with the organisational aspects of the company falls into contextual competencies.

The psychology of project leadership

Animated picture of a man and a woman talking to each otherHelping shoppers actually helps in developing great facilitation skills | Source: UXmatters

Brett Harned, Author of ‘Project management for humans’, in one of the chapters, recalls his own experience of working in retail. As the salesman, he was incented to make sales for a commission. He recounts a particular incident when a couple came into the store and were looking for buying a gift for a family member. They started off with five pairs of sunglasses and zeroed in on two of them.  Because Brett wanted to make the sale but didn’t know the person who was to receive the gift, he shared everything he knew about the sunglasses ranging from facts about the glasses to a lot of ridiculous questions.

Eventually, they decided to buy the one they both agreed upon and were satisfied with it. They thanked him for helping them with the decision-making. This incident helped Brett understand what actually helped customers to make a purchasing decision. More importantly, experiences like this helped him understand the importance of ‘human factor’ behind the success of organisations. In organisations, it’s the people who can make projects difficult and it’s the people themselves who can make projects easier. More often than not, a project manager’s role becomes that of a facilitator because part of keeping a project on track is keeping the people on track.

flowchart with boxes connected by arrows showing human psychology in project managementMental decision process | Source: ResearchGate

The proper analysis of the human factor in project management can be done if we know how the decision-making process is actually taking place.

To start off with the psychology of project leadership, look for the objective measurement of skills and knowledge, abilities, attitudes, personality traits and educational achievements using psychometric analysis. To do this, Myers Briggs or an assessment tool from McQuaig Institute can be helpful.

Emotional intelligence (EI) is also an important element to be considered for project managers. It is basically the ability to recognise one’s own and other people’s emotions. HBR defines it as:

“From a scientific (rather than a popular) standpoint, emotional intelligence is the ability to accurately perceive your own and others’ emotions; to understand the signals that emotions send about relationships; and to manage your own and others’ emotions. It doesn’t necessarily include the qualities (like optimism, initiative, and self-confidence) that some popular definitions ascribe to it.”

A table with different coloured columns showing human psychology in project managementSource: Harvard Business Review

Daniel Goleman, Author and Psychologist, states that there are five important components of EI:

  • Self-awareness
  • Self-regulation
  • Motivation
  • Empathy for others
  • Social skills

In the conference paper, Complex project management: towards a theory of cognition for ill-structured tasks, Michael Kilpatrick says that the hurdles encountered by project managers tend to be ill-defined and open to several interpretations. The project managers have to understand the internal dynamics of the team and stakeholders.

Moreover, we need to understand that project management is both cognitive conscious (planned forms of activity) and cognitive unconscious (critical thinking skills). So, project managers need analytical, organisational, interpersonal and intrapersonal skills.

a rectangle with two diagonal lines inside it explaining human psychology in project managementSource: ResearchGate

The human side of team members and project managers

Consider the following pointers to get the highest level of productivity out of your team members in addition to making sure of their mental and physical well-being:

As a project manager, eliminate the usage of the term ‘resources’

Calling team members as ‘resources’ is the worst you can do as project managers. Because it’s not about using people to just get things done. It’s more about asking them to solve problems that are presented in your projects.

While talking to Project Managers and Scrum Masters at OpenSense Labs about this subject, I understood why the term ‘resource’ occurs in the first place. They observed that with mutiple projects, both small-scale and large-scale, being undertaken by the organisation, they, as project managers, have to be on their toes to ensure proper team effort and timely deliveries. Juggling between a multitude of projects and focussing an awful lot on deadlines, they have shown proclivity to see their team members as so-called resources. With so much going on, they agree that it does get tough sometimes to see the emotional side of a team member, but they know it themselves when things get too hectic and it’s time to put a personal touch so that everyone is at ease and takes it upon himself/herself to finish the tasks.

As a team member, choose product thinking over project thinking

One of the toughest challenges that project managers (or organisations for that matter) face is to try and elevate thinking and culture from a project level to a product level. The focus of project thinking is delivery. This could be specific features of a web application or revamp of an entire website. In contrast, product thinking enables you to focus on outcome rather than on output.

Instead of focusing on timelines and dates, there is an emphasis on the goal you want to achieve or the job to be done. So, it becomes much more difficult to put time constraints around the delivery, at least up front. Regardless of how we try and get there, we ensure that we get to the outcome more efficiently.

The project managers at OpenSense Labs encourage their team members to leverage product mindset instead of project mindset. They have observed it’s practically not possible to do micro-management of team members when involved in multiple projects. So, they expect them to show maturity and act on the tasks at hand with the product thinking approach. Because if they just focus on deliverables and finish off the tasks assigned to them, it becomes tougher and tougher for the project managers too to ensure the best result. They would rather want their team members to proactively work on tasks and come up with their own unique solution too. And, when the project managers look stressed when the deadline approaches, just hearing ‘We will take care of it, mate’ from at least one of their team members puts their mind at ease knowing that there’s a collective effort going on and it’s not just the project manager who is dedicated and concerned.

Make sure that the team is not overbooked and prevent developer burnout

Keeping your team members busy and working on tasks is a tricky thing. You need to create a balance in the amount of work that is being undertaken by your team members. This will enable you to confidently commit to deadlines on projects knowing that your team is actually available to do the related work.

Communicate about staffing as much as you can. In an organisation that is continuously handling change, you will know that it’s a tough target to hit. Nevertheless, make sure to stay ahead of the resource crunch. Your team will be appreciative of your efforts in protecting their work-life balance and work-life harmony.

Well, our project managers have always seen that the mental well-being of team members plays a crucial role for long-term planning. Constant communication and transparency in discussions with each and every member about how he or she is feeling mentally helps them understand whether or not a person is feeling overworked or overbooked. They have encouraged them to take a half day leave or even a full day leave when they are feeling low on spirits for whatever reason it can be. They have also focussed on assigning less critical tasks to less experienced members before moving on to give them the more important and complex tasks. This has helped in making a team member progress through the ranks, learn at his or her own pace and finally working on business-critical tasks when they themselves feel confident about it.

Connect with your team

Matching skills to your projects is a whole new task in itself. Connecting with your team and understanding what motivates them is crucial. Find out what your team members’ interests are. Get to know each and every team member’s work. With changing project schedules, plan how you will fill someone’s time with other work. Asking people to plan holidays and vacations in advance would help you plan ahead. Humans are hale and hearty one day and bedridden the next. So, you have got to be ready with a back-up plan.

Covid-19 pandemic affected OpenSense Labs in different ways and we found ways to cope with it. We made sure open-ended leaves are given to ones who contracted coronavirus for them to recover and be back at work when they feel completely okay. A lot of elders especially were more vulnerable during these times. And, one of our team members looked very worried about his father’s deteriorating health, so we made sure he is given some time to be with his father and the financial benefits are provided without any deductions in monthly income for his long absence from work. We have also seen that reallocating tasks to certain individuals have helped them in their learning process. For instance, we have assigned more HTML and CSS related tasks to the guys who wanted to learn frontend development. We have also ensured that we do not shout at anyone or humiliate anyone in a group call for lack of productivity. One-on-one conversations have helped us to communicate things in a proper way, understand someone’s personal setback or realise how someone’s not happy about his or her marriage-related discussions happening within the family. And, sometimes project managers, involved in several projects simultaneously, have to deal with upset clients for different reasons and our team members understand that. When the PM isn't able to join a meeting with a client, one of the team members gives assurance for filling in for him or her.

Here's how OpenSense Labs shifted to remote working environments during Covid-19 pandemic.

Consider the stakeholders as decision-makers

It’s of utmost importance to understand that no one gets trained formally or is taught at some place to be a good client, stakeholder or project sponsor. But it’s not like they don’t know how to. They do know the fact that they have to be polite and nice to a project manager. It doesn’t have to be drilled into their heads by some means. What matters the most is that they are also, at the end of the day, humans and show their emotions while working on several projects with several people at one time. Life as a client can be difficult. As a project manager, you have to help them plan their time appropriately and communicate properly.

A lot of the times our project managers would have to deal with frustrated clients. Not because of any kind of problems with our work. But because of the fact that the client's boss would be putting some pressure on him or her and asking for an update on some of the crucial tasks. Our PMs have to understand their emotions and communicate things in a way that there is a mutual understanding of each other’s emotional well-being. We have also put a particular emphasis on finishing off different tasks much earlier than deadlines for the client’s satisfaction even if it was not that urgent. And, there was an instance where one of our new guys couldn’t deliver any task for over a month. But our project manager communicated with the clients accordingly as he saw that the guy showed intent and gave enough time and space to prove that he can start delivering. His daily tasks were internally supervised and managed and it worked eventually. Sometimes, we have to deal with a situation where a guy, who has worked late hours and has given his everything to the project’s success, has to suddenly attend to his family crisis when the project is nearing deadline. We have always strived to show sympathy in such situations and provide any help to our guys we can. Our project managers have amicably discussed such situations with clients to figure out pushing the deadline to a different date or trying out another guy in place of him.

Once you have understood the importance of human factor in project management, it's time to start your next Drupal development project the right way, learn how to handle complex Drupal projects and understand why to choose Drupal for a smooth web development experience.

Conclusion

Technology will always keep evolving and change the methods by which projects are completed. Projects themselves will keep changing in nature and scope. What doesn’t change? Human factor. Ethical behaviour, consideration of others, principles of communication and a quest for knowledge and excellence are some of the examples of those invariable elements. It’s important to learn and practice ways of optimising human interaction, to build trust and confidence and to efficaciously interact with team members, internal and external stakeholders, individual in positions of authority. All these considerations will ultimately pave the way for efficient project management.

Jan 15 2021
Jan 15

If we travel back to the time, we can assuredly see Drupal as a common factor in every other website. That is to say, websites that were built in the past used Drupal as an end solution to create, store, and display content in a seamless manner for end-user consumption. However, things are not the same as they used to be a few years back. 

Now, coming back to the present, the world we live in is encountering a significant growth in APIs and interfaces demand. As a result, agile organizations are constantly striving for a fantastically positioned CMS that can manage structured content across different presentation layers, that too in a consistent manner. 

Did we just hear a fantastically positioned CMS? Well, the only answer that we could think of is decoupled Drupal and we believe most of you would agree with that. 

Decoupled Drupal holds an innovative ability to deliver an outstanding digital experience to Drupal users worldwide. Furthermore, there is no doubt that Drupal has emerged as a true winner in this deep, enduring, and dynamic digital world. However, the ruling question here is - which is the right front-end technology that you may need in order to support the next phase of web development and further dominate the modern digital landscape. This particular question is worth noting as choosing the best front-end technology will help your organization to be the dominant force powering the development of all kinds of web applications.  

Continuing with that, if you want to catch up on some really important front-end technologies that can offer top-notch results, then this blog is a treat for you. This blog will introduce you to some best front-end technologies that you may need to look out for to rule the digital market space. 

If you are looking for the right front-end technologies, we assume that you have a decent understanding of what they are. Still, we are here to give you a bit of context as it won’t harm you. 

Front-end technologies

“Just like shop fronts, front-end technologies draw your attention and compel you to engage with the site.’’ 

Starting off with the statement while walking around cityscapes, the first thing that you probably see is the shop front that is shiny enough to captivate you and draw you inside. The front-end does the same job as shop fronts. That is to say while surfing the web you get to see plenty of sites but there is one site that attracts you the most and you end up opening that site. This is nothing but simply the magic that the front-end does to the website to allure the audience. 

In the software development world, whatsoever is built falls under two categories: everything that is seen by the user and the processes that are happening in the background. In this blog, we will dive deep into the front-end part only.

Front-end technologies are everything that users see on the site and they interact with. You may have the most structured back-end programming to strengthen your application, but the front-end is what users see and mostly care about. In other words, the front-end plays a pivotal role when it comes to engaging users and encouraging them to take action. It is none other than front-end technology that works in a seamless manner to help you retain customers. Therefore, businesses that value their customers cannot afford to ignore the importance of front-end technologies.

Furthermore, speaking of the thousands of front-end technologies available in the market, the choice to choose a perfect one becomes tougher. To help you out, we have created a consolidated list of front-end technologies that can surely turn the tables in your favor. 

Ready to unveil the front-end technologies list? Yes? Let’s get started! 

Javascript

Be it a small scale enterprise or a large scale enterprise, Javascript is present everywhere and is well suited for everything. As a matter of fact, Javascripts frameworks are an important part of modern front-end development that has been widely used to build a dynamic modern application, real-time chat, eCommerce, inventory, processing, and much more. Javascript frameworks have been gaining a massive legion of followers for almost 2 decades. Consequently, there are many modern companies out there that make optimal use of these frameworks.  

Since every JS framework comes with its unique forte and shortcomings, choosing the best for your requirement is by no means an easy task. Therefore, we have listed down the top 3 JavaScript Frameworks that currently dominate the market in terms of popularity and are highly used to build web applications.

React

Reactjs is an open-source JavaScript library that is widely known and accepted for creating dynamic and highly responsive UI. Due to its component-based architecture, React is considered an efficient solution for developing fast & scalable front-end for the web as well as mobile applications. The primary focus of Reactjs is to build natural, interactive, and appealing applications with minimal coding. In addition to this, this front-end tool uses Virtual DOM in order to deliver blazing-fast rendering.

Features

Apparently, ReactJS is gaining quick popularity as the best JavaScript framework in the front-end ecosystem. The important features of ReactJS include the following-

  • Unlike other large monolithic frameworks, React js is different and has a modular structure which makes its code flexible and easy to maintain. 
  • Since React follows a unidirectional data flow, it becomes easier for developers to debug errors and know where a problem occurs in an application.
  • React js is well known for creating interactive and dynamic user interfaces for websites as well as mobile applications.

Usage Statistics

React has seemed to position itself as one of the leading content management frameworks in terms of usage as shown in the graph below. 

Graphical representation with multicoloured lines to show usage statistics of React jsSource: BuiltWith

When it comes to high traffic sites, React has seemed to perform better than other content management frameworks as represented in the graph below-

Graphical representation with dots representing market share of javascript frontend frameworksSource: W3Techs

Why pair with Drupal?

It is often believed that Drupal for the backend and React for the front-end can help you get the best of both worlds to build and maintain your websites. Well, this could happen for a number of reasons. Some of the common reasons include-

Websites with plenty of dynamic page elements and a huge amount of constantly-changing data cannot be more advantageous from this combination. 

Using React to deal with the UX complexities while relying on Drupal for handling the content can be used to offer a best in class UI experience.

Integrating Drupal with a modern library like React provides all the necessary modern mechanisms that can help you build seamless and a rich user experience. 

Angular

Next on the list is Angular. Originally designed by Google, Angular JS is a powerful and efficient open-source typescript based framework which is highly used to build client-side single-page web applications. Angular Js took inspiration from React, undergone drastic changes, and has come to the force as one of the most secure front-end JS frameworks for building enterprise-scale applications out of the box. In today’s contemporary era, more than a million websites are using Angular, including some global media giants like Google, Forbes, IBM, Microsoft, etc.

Features

Being an important part of the JavaScript frameworks, Angular is one of the most popular and powerful front-end development tools. Let’s discuss some features of this widely accepted front end framework-

  • Angular intuitive API allows you to create high-performance, complex choreographies, and animation timelines with very little code.
  • It has a client-side nature which certainly helps your website to keep cyberattacks at bay. 
  • Using the Angular methods, it becomes easy to build desktop-installed applications across Mac, Windows, and Linux.

Usage Statistics

The graph below shows the market report of Angular in terms of its usage, which very evidently has seemed to receive a positive response from its users.

Graphical representation with multicoloured lines to show usage statistics of Angular jsSource: BuiltWith

Angular has been powering some high traffic websites with its prowess as shown in the graph below-

Graphical representation with dots representing market share of frontend javascript frameworksSource: W3Techs

Why pair with Drupal?

Combining Drupal and Angular together can be efficacious. It can serve as a general picture of what awesome websites/applications may look like. Let’s take a look at the numerous possibilities this combination can lead to-

  • Two is always better than one. That is to say, putting together two open-source frameworks like Drupal and Angular, we can only think of the extensibility and customizability these two can provide.  
  • Security concerns have always been the top-most priority of any website. The powerful combination of Drupal and Angular does nothing but adds an additional layer of security which makes it difficult for hackers to inject malicious code into databases.
  • Connecting AngularJS with Drupal allows you to move display logic to the client-side and streamline your backend, thereby boosting the performance of your Drupal website.  

Vue

Inspired by Angular, Vue is an open-source lightweight front-end Js framework that helps you build creative user interfaces and high-performance single page web applications. It is important to note here that Vue.js has adopted most of its features from famous front-end technologies like React and Angular with the view to deliver a better, easy to use, and secure framework. This aforesaid approach adopted by Vue can be understood by the fact that Vue provides a 2-way data binding as seen in Angular and ‘Virtual DOM’ as seen in React. Not to mention, the principal key advantage that Vue holds over other technologies is its simpler, uncomplicated, unrestrictive, and progressive nature. 

Features

Vue has encountered a massive explosion in popularity over the last 2 decades, owing to some of the most important features. Let’s take a glimpse of these features-

  • Vue is flexible in nature which allows users to write the template in HTML file, JavaScript file, and pure JavaScript file using virtual nodes. 
  • It offers different methods to apply a transition to HTML elements when added, updated, or removed from the DOM. 
  • Vue.js avoids complexity and therefore allows simpler API and design which is highly demanded by web developers who wish to build simple applications.

Usage Statistics

The usage statistics of Vue have shown a historical trend and received a tremendous rise since 2014.

Graphical representation with multicoloured lines to show usage statistics of Vue jsSource: BuiltWith

Vue has seemed to top the chart when it comes to high traffic websites, thereby gaining a competitive advantage over other frameworks as shown in the graph below-

Graphical representation with dots representing market share of frontend javascript frameworksSource: W3Techs

Why pair with Drupal?

The idea to take advantage of the best end-user experience calls out for the integration of Vue js with Drupal. Having said so, let’s take a closer look at the impact of this combination in the digital world-

  • Using Drupal and Vue as a combination can help developers to enrich Drupal interfaces with reactive features with no jQuery, use ready Vue components, or build single-page applications that consume Drupal 8 data.
  • The combination of Vue with Drupal makes Drupal competent to exhibit its magic at the back-end while the compelling features of the Vue handle the client-side.
  • When combined together, developers can request and store Drupal content as data objects by simply using the official Vue-Resource plugin.

Static Site Generators

To begin with, static sites aren’t something new. They have always been here and the roots of the web are embedded in static sites only. What’s new are static site generators that are an alternative to database-driven CMS that focuses on one main task i.e., generate a complete static HTML-based site that does not depend on databases or external data sources, thereby avoiding server-side processing when accessing your website.

Improved performance and security are just a few reasons that static site generators have exploded in popularity in recent years. Choosing the best options from a wide range of considerations can be difficult. Therefore, we have rounded up the top 3 static site generators that you can use to build your website. Let’s give them a detailed look.

Gatsby

Based on React and GraphQL, Gatsby is the most talked-about static generator that leverages the power of GraphQL in order to utilize data from different sources in your project. Gatsby is a solid choice for sites that specializes in taking advantage of pre-fetched resources for other pages and only loading the parts of a website that are needed at any given moment. Gatsby is well-known for its speed, thus by using Gatsby, you can build fast loading and fully interactive Jamstack sites. 

Features

Gatsby provides some really powerful features that can improve developer experience, site performance, and overall shipping velocity. Let’s have a look at some of those powerful features-

  • Gatsby is built with performance in mind. In other words, you can build sites with Gatsby that are 2-3 times faster and gives you fantastic performance out-of-the-box than similar types of sites. 
  • One of the greatest strengths of Gatsby lies in its open-source community. That is to say, a solid collection of API hooks allows developers to customize Gatsby at every step of the build process.
  • Built on some pretty popular technologies, Gatsby exempts you from the grueling learning process which means you don’t have to start everything from starch.

Usage Statistics

The usage of Gatsby has shown a tremendous rise over the period of time as represented in the graph below:

Graphical representation with multicoloured lines to show usage statistics of Gatsby jsSource: BuiltWith

Gatsby shows a high market position when it comes to high traffic websites. Gatsby has clearly dominated the entire market in terms of popularity and traffic compared to other popular CMS as represented in the graph below-

Graphical representation with dots representing market share of javascript frameworksSource: W3Techs

Why pair with Drupal?

Combing powers of Gatsby and Drupal are well capable of creating something truly amazing for the organizations. Sounds interesting? Let’s take a look at why pair Gatsby with Drupal.

  • Using Drupal with Gatsby is a great approach for organizations who wish to build an enterprise-quality CMS for free, paired with a great modern development experience.  
  • Pairing Drupal with Gatsby help you reap all the benefits of the JAMstack, which includes performance, scalability, and security.
  • Static site generators like Gatsby are used in combination with Drupal to build a simple website solution that offers minimal server setup and a low maintenance cost. 

Metalsmith

Simply put, Metalsmith is extremely simple which is a collection of user-defined plugins. It is worth noting that in Metalsmith, all of the logic is handled by plugins and you simply chain them together. Because of all this, Metalsmith can build anything, from blogs to documentation to web apps and just about anything that falls in between. If you are looking for a tool that can be infinitely flexible, then Metalsmith is all you need to assist you. Metalsmith collects all the information from the source files from a source directory and further writes the manipulated information to files in the destination directory. Not to mention, all manipulations are left exclusively to plugins.

Features

The developer community loves Metalsmith for its robust features. Some of the Reactjs features that distinguish it from the rest are:

  • Metalsmith owns a simple and quick configuration which means it includes plugins to generate the output as per the requirement of the source files. It generally exposes two ways to write generator configuration, including JavaScript and JSON.
  • Metalsmith API is quite small in size including only 11 methods, wherein all transformations are done with plugins. 
  • Unlike other CSS or JavaScript frameworks providing their own set of rules, Metalsmith gives you the entire freedom to decide where to store files, what we can implement, and how to implement.

Why pair with Drupal?

Combing Metalsmith with Drupal looks like an ideal choice to JS developers. There is surely more that you can obtain from this combination. Some of the notable improvements you may encounter are-

  • A combination of Metalsmith’s exceptional capabilities as a static site generator along with Drupal’s spectacular backend can be used to serve data to all kinds of clients.
  • Server data can be easily leveraged for building pages dynamically at build time using Metalsmith as a static site generator and the Nunjucks template engine.

Tome

Built-in Drupal 8, Tome is a static site generator and a static storage system for content. When Tome is enabled in Drupal, any changes to config, content, or files are automatically synced to your local filesystem. These exports can be used to fully rebuild- the site from scratch, which removes the need for a persistent SQL database or filesystem. Later on, when you feel you are all set to push to production, you can use Tome to generate a static HTML version of your site.

To simply put, everything is embedded in one repository and Drupal only runs on your local machine.

Features

If you are a fan of Drupal or are interested in working with structured content, then you must have a look at the following features offered by Tome.

  • The tome is well-capable of generating a static site only using Drupal (no JavaScript required).
  • Content is stored in Git and only uses Drupal when you need it.
  • Static build sites are always partial and cached by default.
  • Both views pagers and Media OEmbeds function out of the box

Conclusion

To sum it up, it feels great to see Drupal uniting with other front-end technologies in order to render excellent digital opportunities which is surely a pressing priority in today’s era. Moreover, we would also like to lay special emphasis on the fact that decoupled Drupal is the new innovation that companies across the world are going over. 

It is important to note here that moving from Drupal to headless/decoupled Drupal requires coordination as well as a balance between two main components i.e, front-end and back-end in order to build outstanding software and web application. Choosing the right front-end technology is quite challenging as there are chances that you get easily overwhelmed by the sheer number of technologies available. So, make sure you take out time to research and go with the one that suits you best.

Jan 13 2021
Jan 13

User Experience has gained significant prominence in recent years, and so, rightfully, have civic values. Organisations and individuals have left no stone unturned to make the globe an increasingly inclusive space for everybody. With the internet connecting the world throughout thick and thin, the right to access it must also be well distributed. Web accessibility as a phenomenon talks about how easy to navigate a particular web page is for a physically challenged or developmentally disabled person. Multiple ways in which organizations ensure web accessibility for disabled users is by adding alternative text for images, auditory or textual substitutes for video snippets, enabling screen magnification, etc. 

With the right to internet sliding into the fundamental rights of most modern day constitutions, web accessibility guidelines for businesses have become more elaborate and enforceable by each passing year. Hence, even in the commercial scenario, businesses can be highly impacted both positively or negatively owing to their policy on web accessibility standards

According to a commissioned study conducted by Forrester Consulting on behalf of Microsoft, these are the primary areas companies are looking to grow in - 

Light and dark green bar chart talking about the top business priorities of some organisationsSource : Forrester

And this is how web accessibility for disabled users helps an organization achieve these targets -

Drive Innovation

When a certain user community is diverse and each member entitled to sufficient resources, the interaction and consequent innovation, following as byproducts, become drivers of growth for the company. Making a website accessible not only broadens the application, usage and user experience but also reinstates the muted human touch that connects us as a civilization. Flexibility is another added element that comes complementary with accessibility - as when you add multiple multimedia and interface compatibility to your website, it becomes fluid; fitting seamlessly as nicely into a tab as to a mobile screen. Hence, an increase in accessibility increases and solidifies your user base ticking off a domino effect in terms of innovation and upgradation. Microsoft saw this happen in real time when the company’s management included making their online presence accessible to everyone a part of their responsibility and also their marketing strategy, driving growth substantially in turn.

Enhance your brand

To establish a proper brand identity and value, all bits signifying various important arenas should hold merit in the core ideology of a business. To propel your brand to the highest order, all these  boxes - inclusivity, accessibility, community - must be ticked. Corporations can’t move forward by denying a significant percentage of the world a solution to the problems they face on their digital platforms. Hence, web accessibility also overlaps with Corporate Social Responsibility and constitutes a part of the brand’s identity and public image. Negative public relations can lead to a downward spiral in the expansion of your business, and inaccessibility can be a major enabling factor for such a situation. Big corporations like Apple, Microsoft and Google have been applauded time and again for going the additional mile to be inclusive in their web approach. Hence, even the big players in the market realise that for enhancing one’s brand image, web accessibility has to be seamless and clog free.

“Accessibility is a core value at Apple and something we view as a basic human right.”
– Sarah Herrlinger, Director of Global Accessibility Policy and Initiatives, Apple

Increase Market reach

Expanding your user base can only lead to positive consequences, as every business wants to grow and expand. One might think that disabled population is a minority, but according to the World Bank’s Disability Inclusion Overview, 15% of the world is living with some form of disability. If you for one are unaware about the significance of web accessibility and do not have it incorporated in your online presence, a major chunk of your audience hasn’t been able to optimally access and consume all the content you’re putting out. Consequently, you are probably missing out on word of mouth marketing, which till date remains a significant growth driver. 

SEO is also a huge driver of traffic for one’s website especially if it is content based, and it is substantially enhanced by adding features like alternative text for increased accessibility. Hence, a prerequisite for a loyal customer base is a soothing user experience with no bottlenecks with respect to accessibility, and corporate benefits follow shortly. 

Minimise legal risk

Web accessibility is not only a social compulsion but also legally enforceable in numerous nations of the world, specially in democracies, where web accessibility litigation has been gaining greater ground due to focus on inclusion. Hence, accessibility norms have found their rightful place as a part of these litigations.

The Americans with Disabilities Act (ADA) has further solidified that being non compliant to web accessibility guidelines for businesses could invite a legal notice. It is a civil rights law under which numerous companies have paid monetary penalties for being inaccessible. The much famed case of a visually challenged man filing a lawsuit against Domino’s after being unable to order pizza from their inaccessible website resulted in a lot of negative publicity for the brand. Amazon suffered a similar lawsuit by a blind man who stated that even using a screen reader hasn’t been of much help as Amazon’s website and fellow acquisitions weren’t compliant with accessibility norms.

Improve the experience for everyone

It adds immense value to the ethics of a brand when they decide to roll out services that everybody has equally convenient access to, propelling the idea that their offerings aren’t meant only for a few abled, physically privileged people. Improving the experience of browsing through a website for everybody has a symbiotic effect, the company gaining from a positive public image and inclusive brand identity as well. When brands adhere to web accessibility guidelines they also promote non discrimination as an idea, thereby improving the online experience of every user in the community. On the other hand, when they don’t, brands lose out on potential customers because while most consumers may not go to the length of filing a lawsuit, they sure will make a conscious choice of not supporting or engaging with your business.

Read this complete checklist for design considerations for ensuring web accessibility standards.

Access and grow revenues

When Target got sued for an inaccessible website in 2008, cost efficiency went for a toss as they had to rebuild their entire website in addition to paying $ 6 Million penalty, which consumed much more money than if they had done it in the first place. Thus, keeping web accessibility in mind during the initial phases of creating a website can save crucial costs in the long run.

Recently, Kofax, a corporate giant, bagged a five year blanket purchase agreement with Social Security Administration, USA worth $20.9 Million by beating its competitors primarily in the arena of web accessibility. Thus, a significant business value of web accessibility is that you might reap benefits in more ways than one.

Prototype and evaluate accessible technologies

Survey consisting of questions related to web accessibility, using light and dark green bars for yes and noSource : Forrester

There has been greater effort on the part of corporations to bring accessibility to the table. Microsoft has come up with an accessible Office 365 and a new, modulated version of the Xbox to expand its user base. Google integrated morse code into its keyboard application, Gboard, to make it accessible to visually challenged people. Toyota has ventured out with a vehicle called Concept-i-RIDE - a car that replaces steering wheels and engine controls to make extra space for wheelchair bound people. By equipping a few products with accessibility features and rolling those out to serve as a prototype, brands enable crucial inputs from the consumer base and subsequent evaluation. As an added beneficial business impact of web accessibility, a sense of personalisation is also associated with accessible designs and websites. 

Build inclusive workspaces

Grey and white table containing three columns talking about the benefits of compliance to web accessibility and explanation on how these benefits were measuredSource : Forrester

Needless to say, the business value of web accessibility includes making the entire workplace more inclusive. Offices have been going the extra mile to ensure accessible workspaces in real time, using technical assistance like voice commands. The said ‘smart workplaces’ work on the principle of inclusion and equity, customising the physical environment of the workplace to suit the needs of all employees and users alike. 

For a comprehensive guide to planning web accessibility for your business, read here.

Conclusion

Web accessibility is a change that everyone has been hoping to see in the new, digitised, scientifically tempered world. With provisions in place, we finally seem to be walking towards a new reality where age old rigidities bend to accommodate everyone.

Jan 09 2021
Jan 09
“A thorough website audit can clue you into the necessary changes and will help you drive significant results.”

Websites are complex beasts and the issues that arise are of inevitable nature. Being oblivious to these issues is quite common when you don’t conduct the site audit properly and regularly. What happens next is quite obvious - you fail to identify a wide range of website issues which interrupts the potential users to access your website, thereby acting as a major barrier to the growth of your business website. 

So, the question that arises here is - what is the best possible way to optimize your website in order to hit the predetermined goals?

Unless you have been living under a rock, you already know that website audit is the resonating answer for the same. Don’t you? 

Well, a website audit is the most common yet the most efficient approach that every organization undergoes who wish to achieve goals associated with the traffic and performance boost. As a matter of fact, a good website audit takes into account all the factors including performance issues, security vulnerabilities, general site maintenance, and site changes and upgrades that can undoubtedly influence your website’s success. 

Have you ever audited your website? No? Then, now is the right time!

A comprehensive Drupal website audit is a necessity today and is highly recommended to make sure that your website is up to date and performing well. Whether you are a small business trying to optimize your site for organic search, or an agency doing the same for a client, it can be a bit difficult to know where to begin from and how in-depth your analysis should go. No need to worry, we have got you covered.

In this blog we have put together several parameters that are of great importance when it comes to carrying out an in-depth analysis of your website. Subsequently, we will be providing you the tools that will help you glean the most useful information throughout the audit process. 

Illustration explaining Drupal website audit checklists with 'Drupal website audit' written at top and several boxes containing textual information below it


Before we run into the on-page audit components, let's start with few basic but important domain level checks that every organization, irrespective of their size and nature should be updated with.

Site Map

A site map is basically a blueprint of your website that helps search engines (Google, Yahoo, and Bing) to find, crawl and index all of your website’s content. Site maps can be good for SEO as they allow search engines to quickly find pages and files that are important to your site. 

SSL Certificate

SSL certificate is the backbone of the website that enables encrypted communication between a web browser and a web server. Websites need to have a validated SSL certificate in order to keep user data secure, verify ownership of the website, prevent attackers from creating a fake version of the site, and gain user trust. 

WWW resolution

WWW resolution assesses whether your website redirects to the same page with or without WWW (World Wide Web). It is better and more convenient for users when it does. 

Robots.txt 

Robots.txt is a file that lives at the root of your website to instruct your crawling preferences to various search engines. Not to mention, a Robots.txt file allows you to lock away areas of your website that you may not want crawlers to find.

On-page Site Audit Components

Apart from the aforementioned basic domain checks, there are several other components that are capable enough to influence the outcome of the website audit. Further, these influences can either have a positive effect on the quality of the website or can provide great repercussions on the reputation of the website on the face of the direct clients as well as end-users.

1. Drupal’s Best Practices

Creating and maintaining a Content Management System (CMS) like Drupal takes both time and effort. Further, you are required to follow some basic web development practices that can help you protect that investment and simultaneously provide a great user-experience. 

With that being said, the following pointers outline some best practices that are required to program with Drupal.

Drupal Architecture

  • The content structure must include all the fields and content types. 
  • Choose limited content types and files in your development plan to avoid confusion among content creators.
  • Use new entity type and single entity type for different and similar data types respectively.

Check the code

  • Use an indent comprising 2 spaces, with no tabs and the lines.
  • All binary operators should have space before and after the operator to serve the readability purpose.
  • To distinguish control statements from function cells, they should have one space between the control keyword and opening parenthesis
  • All lines of code should comprise a minimum of 80 characters.
  • Use short array syntax to format the arrays with a space separating each element (after the comma). 
  • Use require_once() and include_once() respectively when unconditionally and conditionally including a class file. 

Infrastructure

  • Stack size should be not too large, nor too small. 
  • Dive into logs to detect errors and prepare for growth and spikes. 
  • For security issues, it’s crucial to configure to protect from internal attacks as well as external attacks.

Optimise the front-end

  • Define component elements using their own classes. 
  • Exercise and test your site rigorously to resolve PHP errors, if any. 
  • Use a stable administrative theme during development. 
  • Use DRY CSS and group reusable CSS properties together and name these groups logically. 
  • Name components using design semantics. 
  • In order to keep your designs more organized, use SASS.

Test, error, repeat

  • Get your site reviewed by peers to get an additional idea on what to do next. 
  • Set up a testing environment to get your website tested easily and quickly. 

SEO Practices

  • Use Robots.txt, so the right pages and information is indexed. 
  • Bring navigational drop-down menus into action that silently contributes to search engine optimization.
  • Enable the URL aliasing with Pathauto to ensure the search engine understands what the webpage implies. 

Security Practices

  • Always keep your core updated. 
  • Arm yourself with some additional security modules.   
  • Make sure you only use modules approved by the security team. 
  • Don’t forget to keep your backup ready to face any uncertain events.

Maintenance Practices 

  • Keep your code under version control.
  • Maintain and update separate environments for the different stages of the site.
  • Limit access to the production site for all but the most trusted users.
  • Access all logs ever and again, including Apache, Drupal, and MySQL.
  • Review and assess your architecture frequently and make plans for the future.

To go through a detailed explanation of Drupal's best practices, read here.

2. Mobile Usability

Mobile usability testing helps you identify the potential issues/problems that are hindering a mobile friendly user-experience on your website. The need to conduct a mobile usability audit is extremely important because with the advancement in smartphone browsers, more people are visiting sites using their mobile phones. 

Below are some common yet important elements that can help you to produce great mobile-friendly sites. 

Responsive Design

It allows page elements to reshuffle as the viewport grows or shrinks. Responsive design plays a pivotal role as it allows you to create dynamic changes to the appearance of your website when there is a change in screen size and orientation of the device it is being viewed on. 

AMP URL

Originally developed by Google, Accelerated Mobile Pages (AMP) is an initiative to speed up the loading time of web pages on mobile devices. The biggest advantage that AMP URL offers is faster and simpler web pages that can be displayed equally well on all device types, including mobile and desktop.

Mobile Pages Audit Tools

There are a number of tools that can help you perfectly optimize your site for mobile. Here are a few tools that that you should have in your bookmarks-

  • Screenfly
  • Google Resizer
  • Browserstack
  • Ghostlab
  • Crossbrowser Testing

Check out this guide on mobile-first design approach to know more.

3. Speed

Performing a website speed audit is important as it helps you evaluate the speed and responsiveness of the website and further identify the areas that need quick improvement. 

Page load speed

It refers to the time taken by the website to fully display the content on a specific page which directly impacts user engagement and a business’s bottom line. Page load speed is important to users for the obvious reason - faster pages result in more efficient and better on-page user experience. An ideal page load speed should vary between 2-5 seconds. 

Page Speed Audit Tools:

Market is flooded with a variety of tools that can be used to test page load and improve the website speed. Following is a handpicked list of some common tools- 

  • Pingdom
  • Google pagespeed insights
  • Google analytics site speed
  • GTmetrix
  • Dareboost
  • YSlow

4. Performance

Website Performance Testing refers to a software testing process used to determine how a particular website behaves and responds during various situations. Conducting a website performance audit is incredibly important for websites because it helps you to identify and eliminate the performance bottlenecks in the software application.

Take a look at the following list of performance elements that contribute to the response time of the website and overall end-user experience.   

HTML/CSS/JS 

  • JS and CSS count: Delivering a massive amount of CSS and JS to the browser can result in more work for the browser when parsing the CSS/JS against the HTML and that makes the rendering slower. Try to send only the CSS/JS that is used on that page and remove CSS rules when they aren't used anymore.
  • CSS Size: Delivering a massive amount of CSS to the browser can result in more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page and remove CSS rules when they aren't used anymore.
  • Image Size: Avoid having too many large images on the page. The images will not affect the first paint of the page, but it will eat bandwidth for the user.
  • Page Size: Avoid having pages that have a transfer size over the wire of more than 2 MB on desktop and 1 MB on mobile.
  • Image scaling: Scaling images in the browser take extra CPU time and will hurt performance on mobile. So, make sure you create multiple versions of the same image server-side and serve the appropriate one.
  • Documents Redirects: You should never ever redirect the main document because it will make the page load slower for the user. Instead, redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. 
  • Charset Declaration: The Unicode Standard (UTF-8) covers (almost) all the characters, punctuations, and symbols in the world. It is highly recommended to use that.

Header performance

  • Cached Header: Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! 
  • Cached Header Length: Setting a long cache header (at least 30 days) is better as it promises to stay long in the browser cache. 

Servers

  • Fast render speed: Avoid loading JavaScript synchronously inside of the head, request files from the same domain as the main document (to avoid DNS lookups) and inline CSS or use server push for really fast rendering and a short rendering path.
  • CPU rendering time: You need to be able to render the page fast which is highly reliable on which computer/device you run on. It is important to note that the limit here is high i.e., spending more time than 500 ms will alert this advice.
  • No. of requests per domain: Avoid having too many requests per domain. The reason being, browsers have a limit on how many concurrent requests they can do per domain when using HTTP/1. 
  • CPU scripting time: Do not run too much JavaScript as it will slow down the page for your user. Again, this metric depends on which computer/device you run on but the limit here is high i.e., spending more time than 1000 ms will alert this advice.

Performance Audit Tools

Here are some common tools that you can use to run website performance tests in order to achieve optimal performance. 

  • GT Metrix
  • Webpage Test

Read this comprehensive guide on Drupal performance optimisation techniques to know more.

5. Accessibility 

An accessibility audit is a comprehensive evaluation of how well your digital properties meet the needs of people with any limited ability. It is important to conduct the accessibility audit as it provides a detailed look at how and where you can enhance your digital products/services to improve digital accessibility.

Here are some of the first steps you can take to check the type of experience your website delivers for people with digital access needs:

Check your page title

  • Make sure that every page has an input title. 
  • This is usually done through the 'view source' option available in most modern browsers.

Turn images on and off

  • This can be done using an advanced option. For say, google chrome provides access to turn images on and off, which makes it easy to look for ‘disappearing’ text. 
  • Subsequently, check your image alt text for issues such as the missing or incorrect description of the image contents.

Turn sound on and off

Using the computer's sound options, turn off sound to make sure that your website is conveying the same meaningful information, with or without sound.

Manage plug-ins

  • Using special plugins, you can easily apply different views on the top of the page. 
  • For example- you can test grayscale to ensure that people who are color blind have access to each and every information available on a particular page.

Keyboard accessibility 

  • Try to operate and navigate your website without a mouse or trackpad. 
  • Check if all the functions are operable using keyboard navigation alone. 

Check Zoom in 

  • People with visual impairments often enlarge the elements to see what is present on the screen. 
  • Therefore, zoom to 200 or even 300% to check if anything pixelates or not. 

Check-up page structure and hierarchy

  • Your heading text should be H1, followed by various subheadings i.e., H2, H3, and so on. 
  • For example - follow the order 1-3, so H2 cannot come before H1 and H3 cannot come before H2.

Check multimedia elements

As per the information issued by web content accessibility guidelines (WCAG), websites must specify important information contained within multimedia elements (video/audio/photo) in a text-based alternative.

Accessibility Auditing Tools

There are some free online tools that you can use to uncover the accessibilities issues that are present in your site. 

  • Wave Evolution tool
  • Google Lighthouse
  • Sortsite
  • Pay11y
  • Stark contrast checker  

Take a look at this web accessibility planning guide and how Drupal is ensuring web accessibility standards to know more.

6. Security 

Conducting security audits are befitting to examine and identify the existing/potential threats that can jeopardize the website. Further it also involves improving the security of the website to make online business safer.

Following is a quick and easy list of elements you can evaluate to detect the security risks lurking in your website.

Ascertain the assets to focus on 

  • List out the high priority assets required to monitor and scan, including sensitive customer and company data, internal documentation and IT infrastructure.
  • Do not forget to set out a security perimeter 

Checklist your potential threats

  • Name your threats to ensure what to look for and how to adapt your future security measures. 
  • Some common security threats you might put on your list include weak passwords comprising sensitive company data, use of malware, phishing threats, unwillingness to accept service attacks and maleficent insiders.

Determine the current security performance

Evaluate the current security performance of the website to keep hackers at bay, trying to invade the company’s systems. 

Establish configuration scans

  • Setting up a higher-end scanner will help you detect security vulnerabilities.
  • Run some configuration scans to detect configuration mistakes made.

Look out for reports

Do not forget to give a detailed look at the reports generated by your auditing tools.

Monitor DNS for unforeseen events

Always keep track of the credentials used for your domain. 

Scrutinize your website

This a must task when you wish to spot some hard-to-access files and directories on your website.

Carry out internal vulnerability scan

  • Install an agent on each computer in your organization to monitor the vulnerability level.
  • Performing an internal vulnerability scan in a month or 3 months would be a great option.

Perform phishing tests

  • Perform cybersecurity training by sending out fake phishing emails to team members.
  • Running such tests would give a close-to-real-life experience of what a phishing attack is. 

Security Auditing Tools

Now that you have a plan, you might need some tools to put your plan into action. For your convenience, we have listed down a few tools that you can use-

  • OWASP Testing Guide
  • Burp suite
  • Nessus
  • Qualys web apps scan
  • Rapid7 

Get a thorough understanding of Drupal security by going through why Drupal is the most secure CMS, its provision for open source security, importance of security modules for Drupal website and Drupal website's data security strategies.

7. Search Engine Optimization (SEO) 

An SEO audit is an important facet of the website which identifies and analyzes the foundational issues affecting the organic search performance of the website. Conducting an SEO audit is extremely essential for any website as it allows you to analyze  the current SEO efforts (irrespective of fact how prolific or sparse they are) and further take immediate action on those insights.

Below are some of the most important areas that an SEO audit covers to maximize optimization-

Find and fix indexation issues

  • Make sure your site is well-indexed in Google.
  • Look for the number of pages that Google has indexed for your domain.

Conduct on-page SEO check

  • Keywords: While auditing your on-page SEO, start with the keywords. Make sure both long & short-tail keywords are incorporated seamlessly throughout the content. Moreover, adding LSI keywords help improve organic visibility eventually.
  • Optimization of headers: Use keywords in the headers. It is to be remembered that search engines including Google use H1 tags to understand the primary topic of a page.  
  • Call to actions: Curate content with the right CTAs for the maximum conversions. Good CTAs make a site look more structured and professional, attracting visitors’ attention. 
  • Optimized URL: It’s also crucial to have keyword-rich URLs for the website to improve the organic click-through-rate (CTR). The shorter the URL, the better is the ranking.
  • Meta description: Meta description plays an imperative role in SERP as Google uses description tags to generate a search results snippet. Hence, every page on your site needs to have a 160 characters meta description with a primary keyword. 
  • Internal links: Using internal links to publish new content is a must. Internal links are instrumental in establishing site architecture and spreading link equity (ranking power) at large. It is recommended to use descriptive keywords in anchor texts to give readers a sense of the topics. 
  • Schema markup: Furthermore, use Schema markup, an advanced level on-page SEO technique to help the search engine bots crawl relevant information for users. The Schema markup uses a unique semantic vocabulary (code) in microdata.
  • Image optimization: Lastly, the optimization of images with keywords in the image alt text also carries weight. This practice increases the potential to rank in image search apart from boosting the SEO efforts of webpages. 

Detect and delete broken links 

  • Check for the broken links list and find which link has the most inbound links.
  • Work through this list and either delete or replace the errors found. 

Duplicate and thin content pages

  • Check for duplicate pages as they have an adverse affect on SEO. 
  • The pages should have a decent word count else it would be considered thin content poage and might not attain a better ranking over SERP or even not get indexed.

SEO Auditing Tools

Following are the tools that you can use to track and detect errors that are hindering your site from achieving the top spot on Google. 

  • Google Analytics
  • Google Search Console
  • SEMrush
  • WooRank
  • Moz
  • Ahrefs
  • SpyFu

Access this ultimate guide to Drupal SEO to know more.

8. Consent Management

Consent management is a process that allows websites to meet legal regulations such as GDPR and CCPA by obtaining user consent for collecting their data or information. With a good consent management platform (CMP) in place, websites are able to create better customer experience and further deepen relationships with their consumers.

9. Hosting Infrastructure 

Having a quality web hosting infrastructure is essential for any website as it helps you determine the loading speed, downtime, bandwidth, and SEO factors of the website.

If you use a free or cheap web host, it will create a lot of hosting problems like frequent downtime issues for you in the future. 

Here is a list of some important things that you should consider before you choose a web hosting plan.

Fast servers 

  • Profits are directly proportional to the speed that webpages load, therefore make sure your web host offers at least a T3 internet connection.
  • Internet users lack patience and need quick results. Make sure your web host does not exceed the 30 seconds time frame. 

Unrestricted CGI Access 

CGI programs are put-to-use by many professional sites at some point or the other, therefore look for a web host that can provide you with CGI-bin access.

SSH and FTP Access

  • You can easily encrypt the data moving between your computer and your website server with the help of SSH. Doing so helps you reduce the burden on your programming development time.
  • A good web host must qualify the need to utilize an FTP with an intent to transfer files back and forth from your local computers and your web server.

Access to Raw Server Logs

This feature allows you to gain access data relating to your website’s traffic, including traffic you get per week, time period of visitors on your site, etc. 

Server Backups

  • Server backups ensure that you don’t lose out on anything at the time of uninvited events. 
  • Not all web hosting services provide automatic database or server backups, in such situations you are required to pay an additional amount to create full backups for your whole sites.

Services, Scripts, and Software

  • A good web host should offer a vast library of scripts wherein you can add forms, statistics, and other extras to your website.
  • Besides this, the scripts should also provide some e-commerce features including shopping cart software, real-time processing availability and much more. 

Tech Support

A web host of good quality should provide technical support to the website. 

Conclusion

To conclude, conducting website audits may seem like a strenuous task, but it is an important responsibility that helps you identify issues that can hinder the growth process of your website. Not to mention, the entire process may sound a bit nerve-wracking however the end results derived are worth the hard work. If you want to maximize the business benefits of your website, then a website audit is all you need to put-into effect. 
 
Furthermore, a website audit is not a one-off process that you conduct once in a blue moon. In other words, conducting a website audit is a mindset that helps you gain deeper insights into your website which further helps you stay on top of your website maintenance before it gets too late. Being successful in the digital market space requires some degree of agility and adaptability, and guess what this goes for websites too. 

Would like to put yourself way ahead of your less-informed competitors? Feel free to contact us at [email protected] and our industry experts will help you conduct a comprehensive site audit the right way.

Jan 04 2021
Jan 04

2020 has ended. (Finally!) So, is it time to rejoice? Is it time to be cheerful and optimistic?  Or, do we have to be realistic and concerned about the coming months?  We have this proclivity to celebrate and be mirthful when the New Year begins. But the fact is that Covid-19 hasn’t left yet and has actually left an indelible mark. We keep hearing about the occurrence of new Covid strains and how it is becoming more fatal than ever as days go by. Anyway, the good news is, the coronavirus vaccine is already here and multiple countries are fast-tracking the approval processes.

Beach in background and ' Drupal 2020 Year in review' written at the centre


With our strong resolve to tackle it, we have found ways to fight the gloom. 2021 has only just begun and will bring with it new challenges like every year does. No matter how difficult it gets, we will dodge everything that comes our way this year too and come out on top together. The Drupal fraternity, too, has risen to the top by uniting and becoming a force to reckon with. The Covid-19 pandemic has only made the Drupal Community to come even closer and work together. The power of the open source community was discernible as the Drupal project, which did get affected by the pandemic, witnessed an awful lot of growth in 2020. As the year has gone by, it’s time to look back, analyse, see what worked and what not and look forward to 2021 with hope.

19 years old: Almost two decades and still counting!

Drupal celebrated nineteen years of existence since it was first released on 15th January 2001. Well, it all began in 2000 when Dries Buytaert decided to put an internal site, used by a small group of people for socialising, online.

Snapshot of a tweet with a person's image on top left, textual content below it about Drupal's nineteenth (19th) birthday and an image with blue background and number 19 below it


So, what began as a hobby project is now a global project with hundreds and thousands of users, active contributors and a strong ecosystem. 15th January 2021 will mark the completion of two decades since Drupal came into being. With Drupal Community’s continued efforts to innovate, reinvent and evolve, Drupal has thrived and will continue to do so for many years to come.

#DrupalCares: Weathered the ‘Covid-19’ headwinds

With the Drupal Community celebrating 19 years of Drupal, a new viral disease from Wuhan was rapidly becoming the international cause for concern. Therefore, it will be incomplete without the mention of the coronavirus pandemic and its impact on the Drupal world. Without a doubt, these are unprecedented times and no one saw it coming. But, Open source, with a reputation for being recession-proof, got itself back on track with the support of millions of supporters. Drupal was no different.

A drop shaped icon with hearts surrounding it and Drupal Cares written below itSource: Drupal.org

Drupal Association, which was formed as an open source non-profit to help grow and sustain the Drupal Community, was hit financially. But the massive response to #DrupalCares fundraising campaign only showed the power of the open source community and the open source model that make projects like Drupal the best possible investment in these uncertain times. Over $500,000 was raised in just about 30 days surpassing the expectations initially set. (The plan was to raise such a large amount in 60 days.) Hundreds of businesses and organisations along with thousands of individual donors and members donated to reach the goal in record time.

[embedded content]


DrupalCon: The year of virtual events

Ever since the first gathering of Drupal contributors way back in 2005, where just about 50 people made an appearance, DrupalCon has become the global event that is highly anticipated every year. While it acts as the ideal platform for the Drupalists from around the globe to meet at one place and share intuitive ideas, DrupalCon Minneapolis 2020 was very unlikely to happen with every other nation closing their borders and putting their respective countries under lockdown to try and curb the ever-multiplying infection rate.

Collage of Screenshots from Drupal 2020 international events like DrupalCon Global 2020 and DrupalCon Europe 2020 homepages with an image of earth on top and buildings at bottom


Eventually, virtual events started kicking off everywhere. For example, the likes of Cannes, Sundance, Sarajevo, Berlin, Rotterdam, Toronto, Tribeca, Locarno, Mumbai among others joined hands for the first time to screen one-of-its-kind, free, global, virtual film festival called We Are One. And, Drupal Community, too, had its share of virtual outings in its intinerary of Drupal 2020 international conferences as it had its first ever virtual DrupalCon Global 2020. Going by its success, DrupalCon Europe 2020 followed months later. Unlike 2019, where large gatherings and in-person meetings were the norms, 2020 became the year of everything virtual. Check out Drupal 2019: Year in review to know more.

Drupal 9: The most ambitious release ever!

[embedded content]


In spite of the pandemic, the roadmap of Drupal 9 release was right on the money because of the continued efforts from the Drupal Community. From the beta test process for Drupal 9 to the release of the first beta version, everything went as per plan. Eventually, the Drupal 9 was released on 3 June, 2020. It took birth with much more usability, accessibility, inclusivity, flexibility and scalability than previous versions. After all, it was in the works for almost 5 years!

And, the release of Drupal 9 was not shorn of any fanfare either. While Drupal 8’s launch saw hundreds of release parties happening across six continents, celebrations in the time of Covid-19 was a different game altogether. For Drupal 9, the community created CelebrateDrupal.org where virtual events can be posted for people to join, photos can be uploaded of Drupal 9-resembling food items, or just simply selfies and videos could be added.

Snapshot of a tweet with a collage consisting of images of people and food items to show Drupal 9 celebration


The rebranding of Drupal had to happen along with this release. So, it did. The new brand represented the fluidity and modularity of Drupal and more importantly the Drupal Community’s value of coming together to build a greater whole.

[embedded content]


Drupal 9 is a lot easier to be leveraged by marketers and offers a streamlined way to maintain and upgrade for developers. With intuitive solutions for empowering business users, state-of-the-art new features for reaching new digital channels and further enhancing content management processes, and offering easy upgrades for avoiding the need to replatform, Drupal 9 is just what web professionals need in this day and age of ever-evolving digital landscape.

While Drupal 8’s end-of-life date has been fixed for November 2021, Drupal 7’s has been moved to November 2022 in light of the impact of pandemic. It was simply because it felt like the right thing to do and it aligned with Drupal’s values and principles that calls for building software that is safe and secure for everyone to use. This goes to show the Drupal Community’s never ending commitment to continue to care for a software almost a decade after its release. Read this ultimate guide to Drupal 9, burning questions about Drupal 9 and the key modules to start Drupal 9 project to know more.

While Drupal 9.1 was released on 2 December 2020 with new experimental Olivero frontend theme and several additions to the Claro administration theme, the plan for Drupal 10 release is already under development. Drupal 10 is being targeted to be released around June 2022.

[embedded content]

DrupalCon Global 2020 had plenty of insights to share vis à vis Drupal 10 like Drupal 10 readiness initiative, enabling Media Library, Layout Builder and Claro by default, the completion of Olivero frontend theme, offering automated updates, and adding official Drupal JavaScript components to Drupal Core.

Screenshot of a video meeting with a person's image on top right explaining Drupal 9's and Drupal 10's vision in DrupalCon Global 2020 Source: Dries Buytaert’s blog

Drupal businesses continued to grow despite pandemic

Drupal Business Survey 2020 had interesting data points to showcase. Drupal agencies have considerably done a great business without getting adversely affected by the pandemic. Financially, Drupal businesses were well placed and thrived with many asserting that results exceeded the pre-covid prognosis.

a piechart with blue coloured and red coloured separations explaining the state of Drupal during Covid-19Drupal businesses during Covid-19 pandemic | Source: Drupal.org

The survey also delineated that almost half of the Drupal companies who participated are confident that their business and on-going situation will further improve in 2021 while 20% of the companies aren’t optimistic about the coming months. As far as the industry segments are concerned, Education continues to be a sector with most Drupal projects followed by Charities & Non-Profit and Government and Public Administration.

Growth in terms of Drupal project pipeline, deal size and win rate

Graphical representations with multi coloured regions to explain Drupal usage statisticsDrupal usage statistics | Source: Drupal.org

There has been a steady growth in the adoption of Drupal 9 ever since its launch. Drupal Business Survey 2020 also indicated that the Drupal project deal size grew more than the project pipeline or win rates that, in turn, shows Drupal’s growth  to the enterprise market.

Three piecharts with multi coloured regions to explain Drupal project pipeline, deal size and win ratesSource: Drupal.org

When the survey sought to look for answers as to why Drupal is chosen for web development projects, it was observed that clients, who worked with Drupal before, most often than not, decided to stick to it (this constituted 60% of the answers). This proved that they considered Drupal as a viable option for solving their business problems. Also, the recommendations from Drupal agencies, Drupal being an open source software, its amazing flexibility and the robust security that it provides made the clients want to go with Drupal.

But, the survey also revealed some of the downsides the Drupal Community would want to give a look at and take some actions to improve further. Drupal development being time consuming and thus being expensive was one of the issues it pointed out. Moreover, Drupal being intricate and potential clients not knowing much about it also came into picture.

Increase in Drupal contributions was observed

From Drupal Global Contribution Weekend (where people more or less close to Drupal and its community participate) to the Google Summer of Code (where students developers across the world get an exposure to open source software development including Drupal), contribution-focused events are given its due importance by the open source communities like that of Drupal. Because contribution is at the core of Drupal project and it thrives because of that.

Graphical representations with multi coloured regions to explain Drupal contribution creditsNumber of people contributing to Drupal has increased over the years | Source: Drupal.org

Drupal.org’s contribution data for 2019-2020 shows that there is a 20% increase in the number of contributions to Drupal project as compared to the previous period mainly due to Drupal 9 release. Although contributed modules witnessed the majority of credits, there was an increase in the contribution credits across all project types.

Bar graph with multi coloured horizontal bars to explain Drupal contributionSource: Dries Buytaert’s blog

Even though there was a decline in individual contributors, organisational contributors increased. Moreover, 20% of the contribution credits are coming from the top 30 contributors (the top 0.4%). It was noticed that two-thirds of all contributions were sponsored. But, volunteer contributions continue to remain a pillar of success to Drupal. Also, it was seen that currently Drupal’s maintenance and innovation is largely dependent on traditional Drupal businesses and larger, multi-platform agencies are barely contributing to Drupal. Read about perks of being open source contributor and different ways to contribute to Drupal to know more.

The continued support for diversity, inclusion and equity

The US was convulsed by the nationwide protests over the death of George Floyd, an African-American man, in police custody. This incident of racially-driven police brutality once again sparked violent protests and much-needed discussions.

The Drupal Association released a statement strongly “condemning racism, racist behaviour and all abuses of power.” It reiterated its support for diversity, inclusivity and equity across all facets. Drupal thrives because of contributions from diverse contributors and it’s pivotal to its health and success. Drupal’s values and principles state that treating each other with dignity and respect is of utmost importance.

While the Drupal Association values diversity, it understands there are still plenty of things to do to create meaningful change within the Drupal Community too. The Drupal.org’s contribution data for 2019-2020 showed interesting data on gender and geographical diversity. Only 10-11% of contributions were coming from people who did not identify them as men.

Bar graph with multi coloured vertical bars to explain Drupal contributionSource: Dries Buytaerts’ blog

And, while Europe and North America continued to be the biggest contributors, Asia, South America and Africa remain big opportunities for Drupal. To know more, read about the relevance of the trio of Diversity, inclusion and Drupal.

Bar graph with multi coloured vertical bars to explain Drupal contributionSource: Dries Buytaerts’ blog

Conclusion

2020 proved to be a tough yet exciting year for Drupal. It continued to grow and weathered all the storms that came its way. It made new progress and identified where it can improve in the coming years.

2021 has begun but the Covid-19 hasn’t yet gone. It’s going to be a while before we can expect absolute normalcy to return. But until then, we shall keep moving forward, continue contributing to Drupal and grow with it.

Happy New Year to all the Drupalists!

Dec 31 2020
Dec 31

Wouldn’t you say that websites are meant for everyone. If a children’s clothing site is not able to serve the needs of all the parents that fall in its target audience, what would be the point then, right?

We know every person is different, from the way they see things to the way they analyse them. Our differences do not make us less than the next person; web accessibility has ensured that, at least in the web domain. There are people who have certain physical conditions that limit some of their abilities, they are simply differently-abled from the rest of us. 

  • Colour blindness can affect the visual perception of a website.
  • Wheelchair user-concerns can affect mobility. 
  • Hearing problems can affect the auditory elements. 
  • Photosensitive epilepsy can induce seizures in a person through certain elements on the web. 
  • Dyslexia can affect the cognitive awareness of a user. 
  • Sleep deprivation, an incidental issue, can affect your accessibility as well.

All of these and more can impair the user experience for people who are suffering from them. That is where web accessibility comes into the equation. This blog will talk about the ABCs of implementing the best practices when designing for web accessibility. 

What is Web Accessibility?

Where websites are concerned accessibility becomes an important consideration that can actually become their breaking point, if not done the right. Before I start on the long tirade on how to make the web accessible, it is equally important to understand what it actually is. 

Web Accessibility can plainly be understood by its purpose, which is to make websites and their numerous tools and technologies in such a way that people with disabilities can easily use them. It is actually as simple as that; building websites that cater to the differently abled people. 

A more thorough definition would point towards making websites that; 

  • Can be perceived by people with disabilities;
  • Can be understood by them; 
  • Can be easily navigated by them; 
  • Can be interacted with; 
  • And they can also contribute to the web through them. 

This concept or more like a principle takes into account all the disabilities that have an affect on the web user experience, be it auditory, cognitive, visual, speech, neurological or physical. 

You might be thinking that that is all web accessibility is responsible for, to make the web more accessible for people with disabilities, but there is more. 

  • From different input modes to bright sunlight affecting the UX;
  • From transient disabilities like fractured hand to ageing hampering your abilities; 
  • From a slow internet connection to an expensive one; 
  • From people in rural areas to the people in developing and under-developed nations;

Web accessibility is meant for all, it takes into account every aspect that can impede on a person’s web experience, eliminate them and make the web a place that is all-inclusive to the core.

It is a concept that is meant to highlight the web accessibility, that is a given because of its name, at the same time, it is also a concept that works towards usability and inclusion. All three are pretty closely related, perhaps that is why they are considered to be the fundamentals of web accessibility. You know what that means by now, however, with usability, the purpose is to build designs that can be used by everyone, while inclusion focuses on diversity, aiming for the participation of everyone in the experiences the web can offer. 

Do you not think that web accessibility is crucial in the way we design our websites? I am certain you do.

What is the standard for Web Accessibility?

In 2008, the new web accessibility guidelines were implemented and even in 2020, they are still prevalent. These guidelines have set the standards for accessibility that all web experience provides must adhere to. These are the WCAG 2.0 guidelines and they can be summed up in four principles. 

Make websites perceivable 

It is after perception that you actually start becoming involved in something. That is why the first principle of the WCAG 2.0 guidelines is making sites perceivable. How do you perceive something? Using your senses, right? Sight, sound and touch being the players here. So, the elements on your site need to be focused on these senses to be truly accessible. To exemplify, it would help a blind person to hear the description of a video to perceive what is going on in it. 

Make websites operable 

Making a site operable means ensuring that all users can use it with ease, by all, you know I mean including people with disabilities. Operating a website has to do with its navigation and interacting with various components. As per this principle, your site should be equipped to operate well in a keyboard-only navigation without any time constraints along with helping the user out, if he were to make some errors. 

Make websites understandable 

Next is the understanding of a website, your users should not have to spend a lot of time to understand some simple instructions. Therefore, the third principle focuses on using clear terms that make even the complex of issues easy to understand. 

Make websites robust

This last principle is a bit on the technical site. Using a clean code for HTML and CSS that meets the overall standards would make it very easy for other technology, third-party included, to depend on your site. It would make your site more robust and thus, easy to process.

How to design for web accessibility?

Now comes the important part, knowing the semantics of wens accessibility won’t do you any good, if you do not know how to implement them in web designing. It is not going to be a drastic change in the design palette of your existing website, rather some minor, yet thoughtful, changes can go a long way in achieving the accessibility standards. So here they are. 

Aptness in contrast 

I’m going to start with contrast because I feel that contrast is one of the major problems seen in accessibility, despite it being a basic one. The text and the background needs to be in contrast to make the text pop. It could be in images, buttons or plain CTAs. For this reason, WCAG has set certain parameters for contrast ratios that need to be followed to achieve the basic requirements of accessibility. There are three types of text generally seen on websites, and all three need to maintain a separate ratio. 

For body text, the ratio is 4.5:1;
For large text, it needs to be 3:1;
And for black and white text, the ratio is to be set at 21:1.

You may have noticed that the larger text had a smaller contract ratio, the reason is simple, larger text is easy to recognise. A size of 24 pixels or a 19 pixel bold would really be hard to miss. 

The homepage of NBC is shown.


Aptness in colour 

Did you know that one in every twelve men is colour blind? It may seem like a lot, but that is true. The inclusion of people suffering from colour blindness, low vision or total blindness, thus becomes very important, because they account to a massive proportion of web users. 

So, just using colour to highlight a component is a colossal mistake in terms of accessibility. You have to use other ways of highlighting the same component. 

Different coloured shapes can be seen in two boxes, one has number written along them and the other doesn't.

While the first image is a perfect example of what not to do, the second one can be considered as an epitome in using colour and keeping accessibility in the picture. 

Aptness in forms 

Today, you would hardly find a website that would not accompany a form to fill, after all that is their way of connecting with the audience. So, making the forms accessible to all audiences is key. And sufficient labelling is the way to do it. 

Every field that you have in the form needs to have a corresponding label that isn’t too far away from it. Adjacent labels are much better than the ones inside it that disappear after the field has been filled with content. 

You may know that oftentimes a form is filled the wrong way, so letting the user he has made an error is also crucial. This needs to be done using colours and an instruction or some sort of a sign because someone with colour blindness might not be able to see the red that is being highlighted in an erroneous field. 

An incorrectly filled online form can be seen.


Aptness in focus elements 

There are certain elements in a web design that require more focus than others, these are essentially the interactive elements of a site, such as the BUY NOW button. You would have read these two words before even reading the sentence because they are in capitals, meaning they are focused. 

The same ideology has to be followed by you in web designing. You should have a different highlight for when a button is hovered over, when it is reached by the keyboard and when it is touch or click ready. 

A webpage can be seen with one highlighted section to showcase the importance of keyboard focus in web accessibility.


If your focus elements are not highlighted properly, by say a keyboard, can it be possible for the keyboard user to actually get the full experience of your site, I think not. 

Aptness in media

Media is another integral part of your website, some might even say it gives life to an otherwise dull webpage and they are not entirely wrong. To keep the liveliness alive, you have to make the media truly accessible. 

Starting with images, it is extremely imperative that you provide alternative text to the same. Adding a caption and description is equality pivotal for audiences using a screen reader. Almost all the CMSs have a pretty prominent alt text option while you upload an image, ensure that you use it. 

The addition of alternative text in pictures is shown during the publishing process of a blog.An example taken from one of our blogs.

What alt text is for images, transcripts are for the audio elements of a website. For the users with auditory difficulties, transcripts that are the sole medium of inclusion. With videos, it becomes necessary to include an audio version of what is happening in them. Considering explaining complicated graphs and tables is another step closer towards accessibility. 

Lastly, I want to mention autoplaying audios and videos. Nobody wants to listen or see them and they only make the user rush to find the button to stop them. So, as a general rule of them, add audios and videos in such a way that the user willingly plays them. 

Aptness in navigation

A user won’t just access a single page on your site, if he does that, then you won’t ever achieve your targets. To go through all of the pages and potential of a website, a user would need to navigate through it and you have to provide an obvious way to do that. You can do that by multiple ways with the provision of orientation cues, a site map is one of the most common ways. 

All of this depends on the layout and the structure of your website, so ensuring that it is meaningful and logical would go a long way in achieving accessibility. A well structured layout should have a couple of things in order; 

  • It should be flexible and resizable;
  • It should have a minimum of 320 pixels; 
  • And it should be able to zoom upto 400% and in close proximity. 

All three help people with disabilities navigate easily. Imagine you are using a magnifying glass to read through all the content and options on a website, would you not prefer that the things you are looking at are close to each other? You don’t have to tell me, I already know your answer. 

Then come the keyboard users, you have to be mindful of them as well. Without getting into the reason for people using a keyword instead of a mouse, I would tell you that for these people the tab key is the most crucial. You have to keep in mind when creating the order of your design, since you do not want your user to get lost while navigating. 

Aptness in content 

The content on your website is its heart and soul; it is what lets the user know of your intentions and your work. Therefore, being extra diligent with the content and its placement is prudent to avoid clutter. 

Let's start with readability, you cannot write your content like it is Da Vinci Code, yes, some people might still understand it, but that is not the aim right. Use simple language with short sentences, short paragraphs and common vocabulary because if the audience is not understanding it, well then, it’s a moot point. 

Then there is the spacing issue, you need to adequate spacing between paragraphs, lines and individual letters as well. 

It is recommended that the paragraph spacing should be twice the font size;
the line height should be 1.5 times the font size; 
And the letter and word spacing should be 0,12 and 0.16 times the font size. 

A similar content is shown writeen in two different styles to highlight how important spacing can be in web accessibility.The difference between the two is pretty stark. 

After doing so much, also try using a font that is easy to read on multiple devices, Arial and Sans Serif are a couple that are just that. 

Aptness in controls 

Then comes the bit about controls, and what are we controlling? That would be ‘the interactive elements.’ Every website has them, be they in the form of buttons or links, they are going to be there. Accessibility would be achieved when these controls are designed so that every person, despite their disability can use them. 

For instance, a person suffering from tremors might not be able to interact with a really small icon. He would find it very difficult to select or unselect a checkbox, the same is also true for the elderly, who suffer from a reduced dexterity due to age. 

Therefore, the size of a control needs to be 44 by 44 pixels, as per the recommendation of WCAG. However, even the size of 34 by 34 pixels could be deemed acceptable, anything below it would be prejudicial. 

Aptness in feedback 

As a last point, I want to mention your part in the user engagement process. When a user does something, whether it is right or wrong, your website should give him an indication of the same. 

For instance, he has filled a form, then there has to be a confirmation message or if there has been a modification in the page he was using, there has to be a notification to alert him of the same. This is called your feedback to the user and it has to be prominently displayed for the user to really get it. 

Aptness in effects 

Photosensitivity is a disorder that can cause headaches, nausea and make the sufferer dizzy. Photosensitive epilepsy is a disorder that can induce seizures in the patient from just fast flashing lights. Since many websites use effects and hyperlinks that blink rapidly, these people would suffer a great deal if they go on and use the said sites. 

 Therefore, accessibility guidelines mandate that you use animations and effects that do not make people suffering from epilepsy and photosensitivity suffer more. This could be achieved by trying to use; 

  • Animations that are small in size in comparison with the screen;
  • Animations that go in the direction of the scroll and follow its speed;
  • And animations that are not constantly moving or blinking. 

To be on the safer side, try to provide an option to pause or hide them, if the user wants to. Some sites even give the option of slowing them down, now that is a thought. 

Access this ultimate guide to plan for web accessibility. And, for a complete guide on web design, read this.

Conclusion

I want to conclude by saying that designing for web accessibility may mandate that you follow a certain set of principles, but that does not mean that it is inhibiting your innovative streak. Think of it as a chance to transcend your abilities and make your web experiences all the more valuable. 

For that to happen, you would have to constantly evaluate your site, especially in the design and development phase. An accessibility audit would help a great deal in that. It would help you in knowing the areas that need improvement and guide you through the accessibility transformation. 

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 24 2020
Dec 24

2020 came in like an uninvited guest and brought along unprecedented conditions that the whole world continues to cope with. We had to cancel our plans, sit at home and adjust to the new normal with a hope that this chaos would clear soon. As this year brought the world to a standstill, it taught us one thing - “When something doesn't go as planned, stopping is the worst thing that you can do.”

This unprecedented time had its impact on OpenSense Labs as well. With the new restrictions across personal and professional activities, we had to take some aggressive yet sustainable steps to fulfil our promises. No doubt we succeeded in doing so and turned 2020 to yet another productive and successful year for the team and the organization.

Let’s have a look at some of our proudest achievements this year, bragging about which is mandatory :D 

The successful completion of 12+ projects 

Despite what we may be facing, life would always keep moving forward. With the same notion, OSL successfully completed 12 projects and counting in the span of this year. Allianz Loyalty Program - an intrasite and StemFuse - an e-learning program, are amongst our most fulfilling projects. 

There are different logos of OSL clients in various rectangular blocks.


Digital transformation fulfilment for 15+ new businesses

Delivering success is not the only objecting we aim for. Our business growth strategies and hard gained credibilities won us 15 new projects across the digital spectrum. The new business allianze from across the globe added up to the confidence and motivation of the team. With this, OpenSense Labs continues its journey to deliver the best in class digital experiences for its clients.

OpenSense Labs' various services are written on a dark blue background.


Stepped into the space of CDP and Mobile Application Development

We initiated our strong roadmap of enterprise solutions by expanding our technology services and expertise in the field of Customer Data Platform and Mobile Application Development. With new projects in these domains, we are continuously gaining valuable experience to bring greater efficiency, ease and power to our clients. 

Community Event : Drupalcamp London 2020

The year began with the Drupalcamp in London, before the COVID-19 strike (oh! the simpler times). A successful session over Federated search solution was addressed by our CEO. Even though later on, OSL could not take part in other virtual Drupal events, we decided to support our community by investing our time and resources heavily on Drupal support forums and projects.

A picture from one of the keynotes during DrupalCamp London can be seen, with the speaker addressing an audience.


Ranked 5th as Global Drupal Service Provider

This year, with around 100 projects and an average of 150 issue credits for every 3-months we ranked 5th as Drupal global service provider. The credit undoubtedly goes to our developers for continuous contribution to Drupal’s Core modules.

The number 5 can be seen taking prominence on a dark blue background.


Our efforts remain to be an active contributor and strive to invest more to the knowledge and support toward our Drupal community.

A better version of OpenSense Labs with website redesign

Our website, which is the base ground of our capabilities, mission and values, all-in-one, went through a redesign. Our new design language personifies our vision, our goals and most importantly, our clients’ successes. We are still the same at core, yet better equipped to understand and interact with you. 

The homepage of OpenSense Labs is shown.


An adaption of work dynamics and culture that enabled productivity

With our offices closed and all the resources operating remotely, we could experience a restricted flow of knowledge, collaboration and communication. But we slowly and steadily accommodate ourselves to this new normal. With the adaptation of new technologies and modification in the process and workflow management we are continuously trying to overcome these hurdles. 

The names of applications used for work from home are mentioned.


Team OSL enjoyed its annual excursion and holi celebration in the first quarter of this year. During the pandemic, team engagement get-togethers were on standstill. However, thanks to our human resource team, we conducted virtual activities to bond and share our experiences.

Three pictures of the OSL team can be seen in the form of collage.


The result of these came in the form of motivation and step by step achievement of our milestones.

Expanding our team - 30 new enthusiasts joined the OSL family

While several companies all over the world laid off employees, OSL takes pride in expanding its team instead. We continued adding new experts to our team from the beginning of the year and throughout the pandemic. OSL even added new departments - AI and Flutter, which opened up a multitude of job and growth opportunities. We believe that we can only work to provide excellence to our clients when we have the right team to do so.

The names of different departments and the number of new employees in them are mentioned.


Aiming to achieve newer heights in 2021

With new business goals to achieve higher organizational growth, we are fully prepared to step into the new year. Here is what 2021 holds for OpenSense Labs -  

  • Launching a new face of OSL with improved design and content. 
  • Becoming a knowledge hub around Drupal and other digital experience spaces. 
  • Catering to technology services around education-tech, AI, Loyalty Platform, content distribution and SaaS. 
  • Proffering products ranging from site audits and personalisation to cloud-based decoupled Drupal. 
  • Adding new capabilities for our client with flutter mobile app development services
  • Expanding our domain in the digital experience platforms and creating an open source community for it - TheOpenDXP
  • Further expanding our team across all the project delivery prepositions

The endless journey

2020 may be ending, but our work and our journey isn’t. This year has been great for OSL, despite its tumultuous nature. But that is life, we have to continue being positive, regardless of what we are facing. Here is to hoping another great year ahead for you and us. 

Cheers to 2021!
Cheers to a better future!

Dec 22 2020
Dec 22

With over a million Drupal sites across the world, it is suffice to say that Drupal has become an eminent name in the CMS market. Not to brag, but it is jam-packed with features, features that can make your website transcend the ordinary boundaries. Due to the many features and modules, both core and contrib, Drupal is sometimes regarded as being slightly complicated and then the question comes, ‘How to start a Drupal project?’ Today, I am going to give an answer to the same question in the easiest way possible. 
 
For you to truly understand and begin a Drupal project, it is important to get the perspective of the people involved in making the project come alive. For it is these people who will be handling the project from the get go, so the tips they give are the tips that would make a difference.

Before I get into that there is one thing I want to mention. Yes, every stakeholder is responsible for his own thing, when starting a Drupal project, however, there is one aspect of the project that needs the contribution of all parties involved. And that is defining the information architecture of a site. 

The IA is basically the organising and labeling of a website. You can call it an art or a science, that is up to you. This is an aspect that does not have one person responsible. From the content authors to the designers and the business analysts, everyone has to contribute their bit to define the IA as clearly as possible. Getting to the minutest details and getting them right from the initial stage goes a long way in achieving the project deadlines and the business requirements as well. Therefore, the involvement of the entire development team and all the stakeholders is the right way to start your Drupal project. 

Now let’s get on with the tips accumulated from the pros themselves. 

There are six bulleted points for your Drupal project's entire team.

The Developer’s Tricks  

Commencing the tips with developers and all of their tricks, since they are responsible for the fundamental makeup of a Drupal project. From a development point of view, you would have to be mindful of a lot of things before starting your Drupal project. 

Developer’s environment 

If a project needs to be at its best, it needs the right environment to grow. By the right environment, I mean three of them, a remote, a live and a local environment. You cannot skip one; if you do so, you would break the workflow, which is essentially described as local leading on to dev-stage and then on to production developers. 

Developer’s consistency 

Continuing the conversation on the developer environment, it is also very crucial for your project that all your developers have a consistent local environment to work with. Let me tell you how such a development environment would benefit you. For one, it is going to help your new developers to get up-and-running in no time and it would also eliminate the need for your developers to keep dabbling in their own local environment. Consistency always pays. 

Developer’s understanding 

How much your developers understand the Drupal ecosystem is another tip to help you in escalating the growth of your project. Discussing the common terminology with the team members helps in keeping everyone on the same page. The basics have to be clear along with a commitment to follow the system. It has been seen that the continuous integration/ continuous delivery trend has picked up a lot, however, if your developers are simply going to ignore it, then what is the point? 

Developers and Git 

You are going to have more than one developer/ programmer and you would want them to coordinate with each other. You would also end up changing your source code from time to time and you would have to keep a track of the said changes. A Git Repository would do just that for you. 

Developers and Codebase 

Moving from code changes to codebase management, Drupal 8 has a Composer template to manage your project’s codebase. This acts as standard in the said management, but there is hope for significant development in the composer projects within the Drupal community. 

Developers and Configuration system 

Drupal has its own configuration system that allows you to push non-code configuration changes between environments pretty easily. This helps in creating a robust workflow amongst developers along with a stimulating environment, wherein the members continuously upgrade and test configurations in a local setting before going towards the remote route. However, all of your developers need to be using the system, or else its benefits would never be reaped. Go through Drupal 9 configuration management strategies to know more.

Developers and auto-deployment 

You should also equip your developers with auto-deployment. The reason would be to fasten the development process and ease the DevOps process. 

Apart from these tips, you have to remember that even though your project is just in its infancy,it would be on the path of growth soon. Therefore, you must keep in mind the future scope of development while designing the architecture. 

The Content Author’s Part 

Well, this one is not really limited to the content authors, but more about their participation in the development process. Hence, it came right after the developer’s involvement. In the introduction, I talked about information architecture and this tip has to do with that. 

Focusing on the content authors first, a content author needs to update the content regularly, so they have to be comfortable with the system. You need to give them the chance to add and edit their content on a prototype site. This can only be done before the site actually goes on the floor. For best content authoring experience in Drupal, check out Paragraphs and Layout Builder modules.

The Project Manager’s Duties 

Project Managers have a leadership role in your Drupal project, perhaps that is why they are called managers. They need to have great managerial skills, after all they are the voice of the project. 

There are two aspects of project management that can make your project a guaranteed success. 

Setting feasible targets 

For one, a project manager should set such targets and milestones that are realistic and fall under the abilities of the team. Yes, pushing the team to do better is always going to be the role of leadership, but pushing them beyond their abilities would just make things a mess. 

Provide clearer targets, for instance, setting a 6-month deadline on the project does not really clarify many things. Try providing specific goals every team member would have to complete by then. For this to happen, you need to listen, more than command. Listen to the needs of the team and become their guide when they need you. You should know that providing training is a crucial part of a project leaders duties. 

Defining work roles 

Using a project tracker and totally committing to it becomes essential when starting a Drupal project. This is because a project tracker helps in ensuring more focus towards the project. However, a project tracker would only work if the work roles are clearly defined for the development team and every other stakeholder, inclusive of the project managers themselves. 

Access the expert insights on project management for complex Drupal projects for a better web development planning.

The Designer’s Role 

You must want your Drupal project to have an interface that is elegant, user friendly and serves all your business principles. This would be easy to achieve, if your web designers are competent enough to fulfil their role. So, when I was trying to find out all the design duties, our in-house designer was a great help and here are the tips he had for you. 

Determining the style guide 

At present, many Drupal sites prefer to create their own custom theme and for that to happen, your designers would need to create a style guide. There is no hard and fast rule to create one, it is entirely up to you to make it simple or complicated. There still are certain things you need to be mindful of. 

  • The style guide you create needs to have a typography and a colour palette. 
  • The typography you choose must be responsive to all devices, think of the H1s, the headers and the footers. 
  • The rules need to be set to ensure how every aspect would look in different screen widths, winging it won’t be ideal here. 
  • The elements you want to be displayed throughout the website need to be defined in the style guide. 

The user does not want your site to make his experience cumbersome, a thoughtful style guide is the way to avoid that and make things comfortable through consistency. 

Determining the wire frames 

A custom theme also means that you would be designing your own signature layout for your landing pages at least. A wireframe is going to give you an idea of how your site’s pages would be arranged and how they would respond to different screen sizes. In simple terms, a wireframe is a template of your webpages. 

Coming to its specific, it is important to focus on consistency. All your pages must follow a similar layout for you to achieve consistency. This would not only help you in reducing costs by avoiding to design one-off pages, but it would also help you in building your brand’s image. The common elements, that I talked about in the previous page, help in making the theming easy for you. 

Determining through testing

You have to test everything before you go on the ground and testing is a major part of the designer’s role. 

First comes the dry testing, which means the testing of the interactive design prototypes and that too on real-time users. If the project fails in this test, a designer would be responsible for accumulating the pain or problem point, fixing them and then testing again. However, if the testing turns out to be a success, then the designers can commence with the UI design as per the design guidelines set. 

Then is the design testing and the real-time testing of the project; it is called real-time because whatever issues are detected end up getting fixed simultaneously. 

Along with these, designers must also be thoroughly involved in defining the Information Architecture and user and market research to always be one step ahead in the designing process.

Read this comprehensive guide to web design for hammering out the right plan for your business.

The QA Engineer’s Tasks 

 A Quality Assurance engineer has a lot of tasks on his/her plate and all of them help in maintaining the quality of the project to the utmost standards. To ensure that a QA engineer should have the basic knowledge of Drupal, especially about the terms and admin portal, which helps in testing. A major part of the job is to test and test each and every aspect of the project, so it becomes helpful. 

Testing for functions

Functional testing refers to testing the functionality of the project. From testing the validation of textboxes and radio buttons to internal, external and broken links and URLs; from web forms and error messages to database and cookies, a QA tests every function, so that nothing goes wrong.

This also includes ensuring that the features built in the Drupal project adhere to the set goals and no extra permissions and settings are given based on the user roles. 

Testing for performance 

Performance testing mainly refers to validating a website’s performance, load and speed. Checking the stress limit and data load of a website. Tools like GTMtrix, YSlow, Pingdom can be used for this. 

Testing for usability 

A major consideration in the usability of your Drupal project is its accessibility and QA’s test for that. Then comes the navigation of your site, which should be easy to find, read and use, for instance by clicking on a company logo, you can reach the home, easy and simple . Finally, it is content, it has to be defined with clear H1s and H2s as well the use of SEO in tags should be optimised. 

Testing for compatibility 

Before going live with your project, you should check its compatibility with different operating systems, different browsers and their versions, different devices and different  networks, environments and hardware configurations.

Testing for security 

Focusing on security can never go wrong, that is why as the last task of a QA engineer, he/she tests the security parameters of a Drupal project prior to it going live. 

These include; 

  • Checking for any URL manipulation; 
  • Checking for Cross Site Scripting; 
  • Checking for Password cracking;
  • And checking for Drupal security updates. 

Read how QA plays an important role in software development projects.

The Business Analyst’s Responsibilities 

Up until now, we have focused on the project side of things, now it is time to focus on the business side of Drupal project and that is the responsibility of a Business Analyst. This position is the bridge between you and your consumers. The fact that effective customer communication can only be achieved through a BA, is proof of that. 

There are two major responsibilities of a Business Analyst, apart from what I mentioned above. 

Understands the project 

A BA has to clearly understand the project requirements and iterate the same to the Project Managers, who would then get the project in motion. So, it is very important to ensure that the requirements are feasible and that would only happen when the Project Manager are part of the discussion. 

Interprets the requirements 

A Business Analyst is also responsible for interpreting the project requirements to the team. What this means is that he would have to convert the business needs of the project into technical specifications. Imagine talking business to a developer, he would be the least interested in it. Therefore, it is the BAs responsibility to convey the business needs to the team in the terms that they understand. 

Brings in value 

Business analysts are known to work with real-time user data and analytics programs. They do so in order to understand and recognise user trends, the functions that are a success with the user base and the kind of problems a user would face while adopting your application. This data and its recognition is crucial for business success and BAs have a great role to play in that. 

A business analyst could be involved just at the front end, while assessing user needs or he could be involved throughout the project implementation, whatever the case, he is an important player in the setup of a Drupal project. 

The Bottom Line 

At the end of the day, a Drupal project is just a medium for you to let you enter the world of business. Your Drupal site would be responsible for generating an income for you or fulfilling your social responsibilities, like the Government of Australia’s website. Therefore, for your Drupal project to be successful, you have to align it with your business needs. When all the stakeholders have a clear understanding of your business and its sole purpose, then there is no stopping you. Saying that, the aforementioned considerations are like the starter pack of a Drupal project and you would be wise to pay heed to them before commencing your Drupal Project. 

Dec 18 2020
Dec 18

The web has become a popular destination today. An average person tends to visit it plenty of times in a single day. From finding out the weather forecast to booking a cab or ordering in, you can do it all by exploring the different aspects of the web and enjoy doing so. However, have you ever wondered how our experience of the web is made enjoyable? A ten-year old and a seventy-year-old can find an equal sense of satisfaction through the umpteen websites they surf through, despite their different intellect, but how?

The answer lies in the web design. What is that? Web design is a process that continues throughout the life of a web project. It starts with planning and conceptualisation of the website, goes on to arrange its content online and continues with the production and maintenance of the sites. 

This blog will try to cover every spec of the concept of web design, from its importance to its universal application to its principles. Before we get into that, let’s delve into the two categories of web design, which are adaptive and responsive websites. 

Adaptive design 

Like the name suggests, this kind of website design adapts itself based upon the device type or browser width. It makes use of a “user agent” that informs the server about the device that is in use, it could be a desktop, mobile or tablet and consequently shrink or enhance the screen size. In a different scenario, the design will use media queries and breakpoints to let the server know the version to implement, namely,1080p, 720p or 480p, offering much more flexibility. 

Responsive design 

The other option is to use a responsive design, which works with the proportion of container space taken up by a single element and shrink accordingly. If a header is at 25% space on a desktop site, it would remain at the percentage even in a mobile device. Like adaptive design, it also uses breakpoints to establish the need for the server and keeps changing constantly. 

With that knowledge, I believe we are all set to commence into our comprehensive guide to web design. So, let’s start. 

The Importance of Web Design 

A chart is shown describing the need for web design.Source: McKinsey & Company 

The image above clearly depicts the importance of design. Web design has to be idolised for business success through leadership, inclusion, continuity and user experience. You cannot confine it, it has to have free reins for it to boom. 

Website design is indeed one of the major contributors in your online revenue. You could say that a good web design is directly proportional to a higher revenue. Now, let me let you why. Like I have said before, the web has become quite popular, people go on it regularly and check your company's online persona to see whether you are worth their time and money or not. If you are able to impress them with your design skills, you are bound to experience an impressive conversion rate. 

In simpler terms, 

  • Design is important because it acts as the first impression of your business. 
  • Design is important because it creates a consistent brand image and encourages the user to put his trust in you. 
  • Design is important because it gives you an advantage over your competitors. 
  • Design is important because it enhances your UX, making the user’s time enjoyable rather than frustrated. 
  • Design improves your performance, reduces the load time and the bounce rate, increases the conversions and amplifies consumer service and satisfaction levels. 

Let me exemplify this, today nobody would want to spend their money on a product that they haven’t researched thoroughly, be it a watch or a car. And where do people go to execute the research? Yes, to your website. So, if you answer all the questions the user might have in your product description and alleviate all the worries, the user will most likely buy from you. And all of this falls under the web design umbrella. 

So, yes web design is critical for your website’s success, for your sales and for the longevity of your business.

The Prerequisites of Web Design

Before delving into the principles of web design, it is important to know how you would prepare for it. There are certain requirements of web design that need to be fulfilled before you can get on the floor with the actual designing. 

Finding the inspiration 

Being inspired is the first step of designing, after all can you design anything without inspiration? I think not. So, explore, research, get to the very basics and see what you like and what you don’t. Go to Pinterest, if you have to, but start looking. This would set a great tone for the entire designing project because you would have some idea of what the end would look like. 

Finding the purpose 

After inspiration, comes the part where to find your purpose. You are building a website, there has to be a reason for that. Identify it and design accordingly. Majority of the time, the purpose of a site is sales, be it memberships/ subscriptions or an actual tangible product. Keep the purpose front and center and design to capitalise it. If indeed you are selling a product, design the pages in a way that each page is an encouragement for the user to click on that buy button. Take Amazon for instance, every time I go there, either I make a long and extensive wishlist for future purchases or actually buy things. That should be the target. 

Finding the needs 

There are also specific needs that a website has before its design process actually begins. 

  • The first would be to establish your space on the internet through a web hosting service. Then you would need to adopt a domain name through which the users will identify you. Along with this, you would also need your domain name and server to be in sync, so that the browsers know where to find you. 
  • Next, figure out what structure your site would have, how many pages would it have, what kind of content those pages would include and which of those are going to be your landing pages for marketing purposes. 
  • Then comes the functionality, you cannot just wing that. Remember we figured out the purpose of your site in the previous point, that purpose would help you in figuring out the kind of features your site should and should not have. For instance, the functionality of an informational site is drastically different from an e-commerce website. All of this is decided before the designers go on the floor with the process. 

Finding the tools 

You cannot work without the tools, so finding the ones most suited for your project is a key requirement of web design. 

If you wish to build a desktop app, then tools like Sketch and Photoshop are perfect for the designers as well as the developers to create the code for the designs. However, if that is not the case and you are aiming to build a site, then you can make use of Website Builders like PageCloud, Wix and Squarespace to name a few. 

Remember to do your research and maybe even get a free trial before committing to any one of them. 

Finding the personnel 

To use the tools, you also need the right team. Designing websites is not a one man job, you need the right mix of skills to get the best possible outcome. 

  • Designers to create mockups of the site;
  • User experience experts to ensure that the mockups align with the target audience’s needs
  • Developers to get the coding out of the way, the front end developers would take up the presentation layer, while the backend developers would work on the background; 
  • Content writers and SEO experts to write for the project and make it visible on the web through searches. 

Now, you are prepared to get into the nitty gritty details of web designing. 

The Principles of Web Design 

Web designing is a long and complex process, there are a lot of considerations to be kept in mind before the process can be considered even half-way through. Here is how we at OpenSense Labs divide the process into different segments of development and ace every one. 

Information Architecture (IA)

Through Information Architecture, designers are enabled to prepare an organised layout of the information that has to be relayed to the visitors; navigation and menus, being the spine of an information architecture. However, it is the user, who is the highlight, it’s his perception and expectation of the information that guides the architect to build the perfect IA. 

Now, how does a designer achieve perfection? This is done by researching the user to the T along with focusing on usability testing. User interviews, card sorting and observing the way a user interacts with your current design through usability testing are the pathways you should be seeking. For instance, when a menu has been decided, a tree test helps the designers know its suitability. And that is IA for you. 

Navigation 

Navigation is one of the most crucial aspects of your design strategy, so getting it right is the first order of business. Navigation refers to the system a visitor follows to get through the various parts of a website. Since the aim is to ensure that the user goes as many pages as possible, it has to be simple, concise and pretty blatant. If a user has to put in an effort to navigate your site, you are certainly doing something wrong. The lesser cognitive load while navigating, the better UX. The visibility of the navigation bar is paramount. 

So, how do you do that? 

By putting the user first 

First, you have to understand the needs of your users, at least a majority of them, and create a navigation bar based upon that. This would also help you get an apprehension of the user’s priorities, like how much he repeats a task. Also, the user must always know where he is, meaning the current page he is perusing through must be highlighted from the rest of the pages. Nobody likes being lost. 

By embracing the search

You must know that many of your visitors come to your site with a specific intention. So, how do they get to that? The search bar is the most obvious answer. It acts as a shortcut for the user to get to what he is looking for. Therefore, it needs to be front and centre. At the top of the page would be ideal, either left or right with a magnifying glass icon for added visibility. Can you imagine searching for a search icon? It also needs one more thing, a decent input size; you have to be able to see what you are typing into it. To get a perfect federated search solution for your website, read about Elasticsearch and Apache Solr.

By valuing the user’s time 

This is in regards to the back button. Imagine a scenario, you were reading an article, a pretty long one at that, and half way through it, you saw an intriguing link, you click on it and upon returning through the back button, you are at the very beginning of the said article. Now tell me, would you be frustrated? I certainly would be. So, ensuring that when a user clicks on that back button, he is back to where he left is quite imperative.

By separating the breadcrumbs

There are certain secondary navigation links, aka breadcrumbs, in every web design, which i sfine. However, they become a problem, when they overshadow the primary navigation bar. Separating each level by using arrowheads or slashes is a good practise. Remember that secondary navigation is only there to support the main navigation. 

By keeping the links in line 

There are going to be external and internal links on your site and you need to provide a distinction between the two for the user. Once a link has been clicked on and visited, its colour must change from the rest. Apart from this, you have to ensure that all the links work, a 404 error is a strict no no. 

The results page is shown after a Google search.The purple links signify that they have been visited. 

By optimising scrolling 

Everybody scrolls, they start doing it as soon as the page loads. So, by optimising on it, you can actually make the navigation experience better. The content and the media is an essential part of it. Write an impressive introduction or add a great visual to intrigue the user and he will start scrolling.

You also need to ensure that the top navigation bar should always be on display. If that isn’t the case, the user might feel lost, especially in pages that are pretty long and that is not an experience a user came to you for.

Page structure 

The page structure is integral in enhancing the visibility of your interface, so that every element is easily found by the user. It is truly up to you to decide the structuring of your pages, however, I would suggest that you follow a grid. Because a rid helps in segregating the different elements of a page at the same time keeping them combined, it makes it easier for the user to understand the logical progression. One of the classic examples of modern day grid-like page structure can be availed through Layout Builder module and Paragraphs module available in Drupal as can be seen below.

The layout of a grid-like structure in web design is shown in pastel colours.


You must also aim for a structure that your target audience is familiar with, assessing your competitors is the best way to do that. Familiarity helps in building the user's experience upwards. 

Visual hierarchy 

After page structure, comes the visual hierarchy of a page. When a user visits a page, there are certain aspects that the designers want them to look at the first glance. Deciding that refers to the concept of visual hierarchy. 

A webpage is shown with different elements being highlighted at different proportions.


In the above picture from OpenSense Labs, ‘Build better, build faster’ is the highlight. A user would read without much effort from his end. The company logo is another important element. Then comes the Drupal 9 bit, being their speciality, they have made it prominent as well. 

So when you design a page, keep in mind the elements that you want to be highlighted and make their size, position and colour prominent on the page. 

It would also be beneficial to capitalise on the user’s natural way of scanning. It could be the F-shaped pattern or the Z shaped pattern. The former works with written content and the latter can be used for the non-textual pages. These further help the user in scanning easily.

A webpage is shown with an F shaped out in the content.An F-shaped pattern. Source: Instapage

Your visual hierarchy process would be easy to build, if you create mockups first. This would help you in knowing where each element would lie and avoid any errors. 

Content 

The content of your pages allows the visitor to understand you and your objective better. The simpler the content would be to read, the better that understanding is going to be. For that, you simply need to implement three things.

  • One is to be a minimalist with your words. Inundating a web page with content will only confuse a visitor. Keep it simple, provide pointers for easy maneuverability.
  • Second would be to keep the language simple, you cannot use highly complex and technical writings on a web page. Yes, there is a possibility that some users would understand it, but are we aiming for some or all?
  • Third is to ensure that your sentences are short, preferably with one idea. Noisy sentences can often baffle the visitors; 20 words or less has to be the target. Also avoid caps lock for everything that is not an acronym.

Moving on from the writing style to the specific contextual elements of a web page, let us understand how you should work with them. 

Filling out web forms

Where user interaction is concerned, web forms are the most integral. The reason being they allow you to know your users’ personal details. Any confusion here, would make the purpose of the form futile. Keep things to the point, ask what is needed with a logical progression in the questions. 

A web form is shown.Source: Bajaj Finserv

Another tip to follow would be to group similar questions in one category. For example, the educational qualifications can come under one heading and the contact information could be a separate heading. 

Tapping the buttons 

Buttons are basically links that are designed as a button to tap on; like the ‘Buy Now’ button on Amazon we love so much. These are essential for a website to enhance its interaction with the visitors. So, you have to be certain that all the buttons are actually buttons with a link taking the visitors to wherever it says it would. A non-functional button is a frustration button. Then you should also remember to aim for consistency while designing these, so that users can easily identify them. 

The most important consideration for buttons is what is written on them because that is the only thing that would attract the user. Be descriptive, be clear, be concise and make it attractive. 

Numerous web buttons are shown to depict how prominent they need to be in a web design. All the buttons here are pretty clear as to what their purpose is. Source: Vecteezy

One of the most important buttons would be the CTAs, the Call-to-Action button. These encourage the user to become a customer and improve your conversion rates. Therefore, a CTA that stands out from the normal text, that is a size different from the normal text, that has negative space to make it even more prominent and that is labelled with encouragements is the CTA that will generate more conversions. 

A webpage with four CTAs is seen.


The above screenshot shows how OpenSense Labs, after having told the visitors all its benefits, lures them to click on the CTA. 

Enunciating SEO 

After doing all of this, you also have to ensure that you follow certain SEO guidelines to enhance your visibility on the web and search engines. By focusing on the title tags, URL structure, HTML and XML sitemaps and making them user friendly can totally elevate your SEO game. 

Media 

Imagine this blog, without a single media element, an image or a video, describing what is written in the text, would that be a great experience? I don’t think I need to elaborate on the answer, you know!

So, how do you work the media in your favour?

Images 

Images are a must in web pages, however, you cannot just add them for the sake of it. The pictures on your website should be related to content on it. They cannot be random images of people or objects that serve no purpose or add any value. Other than that, the pictures should also be of good quality, distorted and blurred images are a big no-no. 

A publishes bog is shown with a customised image.


This is a screenshot from one of our blogs, the image here is simple and concise. One glance at it and you would know what the succeeding information is going to talk about. That should be the target. 

Videos 

Videos have become equally important to images and the internet speed is to blame. They are an easy way to understand a concept of a product, its features or even the message of a brand. However, you need to use them wisely.

  • Do not autoplay videos, if the user wants to see it, he would see it without autoplay as well. And definitely do not have the sound on by default. 
  • Always include subtitles and transcripts for people with disabilities. 
  • Finally, if you are adding promotional videos, which is a great idea, keep them short. 

Animation

Animation is another way to add a pop of interaction on your site, it is easy and it is fun as it breaks the contextual monotony with ease. 

  • You can add animated effects to point out user mistakes like a wrong password. 
  • You can add animated effects to your brand logo. 
  • You can add animated effects to highlight the navigation transitions. 
  • You can also add animated effects to provide visual feedback to the user, like how much percentage has been downloaded. 

Responsiveness to Devices and other Media 

Responsiveness is crucial for your site’s web design, which means that your design should be flexible enough to accommodate any device that the user might be using, be it a mobile or a desktop. Statista reported that as many as 48% users surf sites on their mobile devices. This figure does make the responsive design of essence.

So, how do you achieve the level of flexibility in your design that will help it optimise a desktop and a cell phone equally?

The foremost thing to do would be to focus on your layout and make it a single-column one as it would be easy to go through on the small screen of a cell phone. Since the space on a cell phone’s screen is limited, you can only show information that is absolutely necessary. Here the Priority+ model works really well. You would show the info that is needed and the rest would come under the ‘more’ button. Then, the size of images also needs to be appropriated when designed for responsiveness. 

Apart from these pointers, it is also important to understand that the clicks on a mobile phone are different from that on a desktop or a laptop. So, you need to be very cautious in the size of the buttons and links along with making them prominent from the other text. You can achieve all of this by creating HTML templates that are mobile-friendly or simply going for a separate mobile-site altogether.

Two screenshots of the same webpage are shown, one taken from a desktop and the other from a cellphone.A desktop site vs a mobile site. 

Mobile responsiveness aside, a website also needs to be responsive to other integrations such as cross channel and social media. Linking campaigns and integrating with social media platforms like Google+, Twitter, Facebook, Instagram and LinkedIn can do a lot to bring in business and generate a higher lead count. 

Load time 

Nobody likes waiting for a site to load, however, in spite of a site possessing great speed, there are factors that make it load slower than the developers wish to. These could be a weak internet network or a heavy site. So, what do you do to ensure that your website does not appear slow to the users? 

The primary thing to do would be to check your site for all the factors that could slow it down, for instance heavy images or having too many HTTP requests, and resolve them. Secondly, you can create an illusion of a faster loading speed for the visitors. This can be done by displaying the structure of the page in question first, thus, giving yourself a few more seconds to load the content. Facebook does it and so does Instagram. 

An unloaded instagram page is shown.


It is important to always keep track of the time it takes to load your content, as that would give you insights about the performance of your site. Remember that every second you delay is a second that would cost you. Nielsen Norman Group agrees with this notion and their three response-time limit should be set as an ideal here. Access the complete web performance guide for your Drupal website here.

Accessibility 

A web design would be considered incomplete, if it is not addressing the accessibility concern. People with disabilities need to be able to access your site without any difficulty. There are certain web accessibility guidelines you can follow to avoid that. 

Contrast 

The contrast ratios should be made keeping in mind people with a weak eyesight. Reading blue  on a black background would be easy for someone with a perfect sight, but not the others. Smaller text needs a 4.5:1 as a text to background contrast ratio, while the larger text can have a smaller ratio. WCAG’s guidelines for contrast would help you in getting to the perfect ratio. 

Colour 

You might be able to tell black from red, but everybody cannot. So, just focusing on colour to point out a feature or a mistake is unethical. You have to use words as well. 

An incorrectly filled online form can be seen.


The colour red is used to highlight the error, along with it a symbol is also used. And when you go to the erroneous column, a dialogue box appears to tell you what the mistake is. This is a perfect example of accessibility. 

Keyboard-savvy 

Motor impairments inhibits people from being able to use a mouse effectively, so they opt for the keyboard instead. So, make sure that your site is keyboard-friendly at least as much as possible. You can achieve this by making sure that all the interactive elements are accessible and the keyboard focus is loud and clear. 

A posted article is shown to highlight the use of screen reader in web design.An example of a prominent keyboard focus. 

Screen-readers 

There are going to be visual elements in your design, that is a given, however, someone blind will not be able to see them. So, for every image, you need to add an alternate text that a screen reader can read, describing what is happening in the image. 

It has also become a trend on instagram as well, with many influencers using alternate texts to describe their posts. 

An instagram post can be seen along with its caption.A caption inclusive of an alternate text.

Testing 

To ensure that your design works well and is equipped to go with your site, you have to test it out and that is the final call, the final piece in the web design puzzle. 

There are two tests you can perform;

  • One is testing repeatedly throughout the designing process. Feedback is pivotal here, it’s similar to constructive criticism. You might feel shattered that your design got such bad feedback, but in the long haul, you would be thankful that it did. Because through that you were able to create something much more powerful. 
  • Second would be A/B Testing, this works best when you conflicted between two designs. So, you run with both of them with separate audiences and see the responses. The one with the better analytics would be the better choice. 

Being original 

Being original goes a long way in creating the identity of your brand and bolstering the image of your company. You have to be creative, you have to think outside the box, you have to step up from the cliches and doing so will compel the visitors to become your customers. 

However, you have to do all of this by keeping in mind that originality does not mean that your visitors have to struggle navigating your sites. The set standard for certain categories of websites, like e-commerce, have to be adhered to. And then there is the contact us page that is an essential element in the design of every website out there. Despite this, you would still find that no two sites would have an identical contact page. That is the kind of originality I am talking about, unique yet not foreign. 

Google's search page is shown. Microsoft bing's serach page can be seen.


Even though Google and Bing essentially perform the same taks, yet their UI is quite different. Same elements, yet different. That is originality for you. 

Being consistent 

Your website is basically your brand and your brand can only have one image to portray. That is why your design needs to be consistent, portraying one single voice. By creating pages with the same colours palette, same typefaces and similar backgrounds, this consistency can be achieved. 

Imagine you are on a site, the landing page is all bright colours and bold fonts. When you move on to a different page, you find that the tone has completely changed, and the colours are muted with a minimalist feel. How would you feel? A little lost? A bit confused? That would be it. 

So, aim for consistency. I am not saying that you have to follow the same layouts, that would be impossible because some pages would have a lot more content than others. Just focus on keeping the same tones throughout. 

A webpage can be seen with different blog posts.A webpage with different team members is desplayed.


Without a second thought, you will be able to tell that these pages are from the same website. Design consistency is what makes that possible. You will see that there are elements that are different, yet there are elements that are similar. That is because every page does not have to be an exact replica of the next for the sake of consistency. 

Being credible 

Lastly, your credibility is what is going to make the visitors put their faith in you. You can work on all of the above elements, but what happens if the user still doesn’t trust you? The users won’t convert.

Long-term conversions and sales are directly proportional to your honesty. When you are honest and clear about what you are selling and that too on your home page, users will start gravitating towards you. Tell them what you are selling, why you are doing and how it would benefit them in the most honest of terms and they will consider you credible and trustworthy. 

Along with this, you can also be upfront about your pricing without any disguises. If you are claiming a cost to be $10, then it should be the same at the checkout. If there are going to be additional costs, mention that along with the $10  price. Trust me, your users will appreciate it immensely. 

The Final Call 

Web design is a continuous process that only ends when a project dies, never before that. This is just the beginning of a long road ahead, adopting the aforementioned guide would certainly be a help to your design process. But the bigger task on your shoulders as a designer. 

I would like to end by adding one more thing. Whatever you are going to design, if you design it by keeping the user and his perspective of the site in your mind, you could never go wrong with it. Good luck. 

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. 

Dec 15 2020
Dec 15

Have you ever wondered how websites are built? Sure, there is an entire army, consisting of developers, designers, project managers and business analysts, involved, but is that all? Do they work independently? Do they work day-in and day-out to build the website from the ground up? Do they have some help in doing that? 

If you are a part of the website development army, you might know what I am trying to get at. It is true that websites are built from scratch, but what is also true is the fact that these websites require some help to get the scratch go on to be a fully-functional site and that help comes from a content management system, a CMS to be short. 

There are a few in the market, with Wordpress leading the way in market share numbers, however, we would be talking about the one that is leading the way in functionality and features. And that is Drupal. 

As of November 8, 2020, there are slightly more than 1 million Drupal sites all over the world. This number is a testament to Drupal’s abilities to give your site whatever it wants. 

To that accord, there has been a new vogue in Drupal and the way it is capitalised by its sites. And that is what we are going to discuss, before that let us delve briefly into Drupal’s traditional abilities.

Traditional Drupal VS Decoupled Drupal 

There are four circles showing how the different aspects of decoupled Drupal architecture are interconnected.Source: DZone

Like I said before, Drupal is a CMS, so it is equipped to build websites from scratch. And that is what the traditional/monolithic/coupled Drupal does. From the user interface to the data access code, Drupal caters for all your website needs. Being responsible for the front and backend, the traditional Drupal helps you in building versatile web experiences.

With Drupal’s themes, templates and behaviours, it is extremely easy to create a dynamic presentation layer for your website. The fact the Drupal allows you to build and customise a live site along with providing solutions for any frontend mishaps is another compelling reason to opt for the traditional Drupal. 

Yet there are many who think that Drupal’s frontend capabilities are not as impressive as that of JavaScript. Although Drupal has a JavaScript library in its corner, it does not have the JS framework to work with, so maybe they are right. So, as a solution, the advent of decoupled Drupal architecture was seen.

The Decoupled Drupal has a slightly different story to tell than its monolithic counterpart. You would still have Drupal and its abilities at your disposal, however, you would have a little more than just Drupal to work with. With decoupling, you would simply be saying goodbye to Drupal’s frontend abilities, either completely or partially, that is up to. Drupal would only be used as a content repository and your entire presentation layer will be made up of other frontend technologies; Angular, Vue and React are some of them. 

The Decoupled Drupal has two variants for you to choose from; 

  • First would be the progressively decoupled approach, in which you would be leveraging other frontend technologies and amalgamating it with Drupal’s frontend capabilities. This could be regarded as the best of both worlds. 
  • Second is the fully decoupled web app, in which your presentation layer is going to be handled by a JavaScript framework and will be completely independent of Drupal, and it would only be used for the backend architecture. Fully decoupled Drupal architecture for static sites is another option. In this approach, Drupal acts as a content source for static sites, aiding static site generators like Gatsby to create your site by taking data from Drupal. 

To know more about the working of decoupled Drupal, how it is different from the traditional architecture and what are the specifics of the technologies involved, read our blog Monolithic and Decoupled Drupal Architectures

The Move from Traditional to Decoupled Drupal 

Now that you have a fair idea as to what decoupled Drupal is, it is time to find out when the right time is to make the move from coupled to decoupled Drupal architecture. Let me ask you a question first, have you ever made a business decision without taking into consideration the pros and cons of that decision? I’m certain, you haven’t. So, for that very reason let me tell you why decoupled Drupal architecture is advantageous. 

The motto “Write once, publish everywhere” could be the tagline of decoupled Drupal. It allows you to leverage social media, emails, the intranet, apps, microsites along with your primary publishing platform, so that you can make your content as universal as you want. This is an advantage that makes decoupling the go to option for many. Then there is the fact that through decoupling you can enhance your user experience, get upgraded faster, which would make your team work at an enhanced efficiency, along with this decoupling also provides you the opportunity to become more innovative. The JavaScript framework, which would be at play in decoupling is the icing on top. 

You might think that with these many advantages, decoupling cannot ever be the wrong choice. It doesn’t have to be, if you know what the limitations are and are equipped to combat them. The most blatant drawback of decoupling is the fact that you would be losing out-of-the-box Drupal features, for some this can be a deal breaker. Obviously, since Drupal would not be at play on the frontend, you would have to part with its capabilities; you can’t bake the cake and eat it too, unless of course you choose progressively decoupled Drupal. Another problem that is often seen in decoupling is that the coding becomes a hassle and so does identifying bugs. 

After discussing the benefits of Decoupled Drupal along with its drawbacks, it is time to ask yourself some tough questions. For it is these questions that would help you in the decision to move. 

  • Is your business reliant on multiple channels and microsites to spread and accumulate content to and from? 
  • Is it your opinion that being reliant on one technology for your entire project is not a wise choice?
  • Are you unhappy with the interactivity your website provides to its users and want to capitalise on JavaScript framework to enhance it?
  • Do you have more developers who are experts in JavaScript than Drupal? Are you planning to take advantage of their expertise in JS?
  • Have you not been using all of Drupal’s frontend assets and think they only bring in more work?
  • Is building an app a future goal of yours?
  • Are your editorial needs basic?
  • Finally, do you have the budget to decouple, because Drupal may be free, other frontend technologies aren’t?

Think of your answer to all of these questions and then read our blog When to move from monolithic to decoupled Drupal architecture to understand all the nitty gritty details behind the move.

The Final Call  

In the end, all I want to say is that there are going to be benefits and limitations for your project, in both the coupled and decoupled Drupal architectures. If you want to make a decision, consider your needs over anything else. If you feel that your current architecture is not cutting it for you, the move could then be considered inevitable and prudent. If not, then maybe waiting for a time when there is an actual need would be the sounder choice to make. There is only one answer to “When to Decouple Drupal?” and that is when you have the need. 

Dec 11 2020
Dec 11

To say that a website or a web application is deemed worthy primarily because of its content would not be totally wrong. A website’s performance does play in the equation, but it is the content that seals the deal for the user. Web builders across the world are becoming aware of this fact and that is why the web content management (WCM) systems have become pivotal for websites. 

A WCM helps you in attracting and retaining your clients and ultimately give you the revenues that you had desired from the time the idea of the website came to you. Therefore, choosing the right WCM that is suitable to all your business needs is probably one of the most significant decisions you will take for your website. 

There indeed are numerous options to choose from, however, two of these have been stealing the limelight from all the others in the recent times. And these are Drupal and AEM. So, let us compare these two to make your decision a tad bit easier. 

Parameters Drupal  AEM  Performance and scalability  Ease of expansion; impeccable performance  Growth mandates performance and stress tests Content workflow Flexible  Flexible  Marketing and engineering perceptions Community driven innovations for developers and marketers Little room for leveraging marketing capabilities outside of periphery of Adobe Cost  Free Can be expensive  Security  Extremely secure Highly secure, yet there are vulnerabilities Community  Over a million and counting  Supported by community; but pales in comparison to Drupal Responsiveness Excellent responsiveness; mobile-first approach Excellent responsiveness as well Development  Works on PHP Works on JavaScript  Third-party integrations Impressive  Good, but involves issues to be troubleshooted Upgrades and migration  ‘Easiest upgrade of the decade’ Easy to perform  Multisite Excellent multisite tools  Great multisite features as well Headless approach  Gives options for decoupling  Decouples, but only in one sense  Multilingual  Terrific with multiple languages  Competes in parallel to Drupal  SEO  More SEO-friendly modules SEO is optimised, but on a scale lesser than Drupal

Getting to know the contenders

Websites are dependent on content management systems to enhance their digital experiences. The better the WCM, the better the chances of your website’s digital content. But how do we decide which is better? Let us start by knowing what they personify. 

Drupal 

The picture displays the logo of Drupal.


If you are reading this blog, there is a high, well a very high, chance that you would know what Drupal is. Still I would tell you a little about it. 

Drupal is an open source platform that helps in building web applications and making web projects come alive. It is free to use and is being used by millions of people across the globe. Organisations like Redhat, Timex, University of Colorado are some of the elite clients of Drupal. So, to say that Drupal is a small fish in the pond of WCMs would be a dramatic understatement. 

You can create and publish content without being an engineer. And the fact that your content does not have to be confined to a certain type of layout or a specific number of content fields is just a bonus. It uses the best of PHP along with that it also abides by HTML5 and YAML standards. Twig, jQuery, Symfonyand CKEditor are some of the powerful third-party dependencies Drupal implements. All of these are responsible for making Drupal a powerful web development platform, which cannot be deterred by high traffic. 

All in all, Drupal can help you create web experiences that are both wholesome and unique to lure your target audience and never let them go. 

Up until now, Drupal has had 9 versions with multiple sub-versions of each. Although Drupal 9 is the most recent version, less than half a percent of Drupal websites use it. As many as two-thirds of them are still on Drupal 7, while over a quarter of the websites are using Drupal 8, as per a survey by W3Techs

A horizontal bar graph shows the percentage of websites using the different versions of Drupal.Source: W3Techs

Adobe Experience Manager (AEM)

The picture displays the logo of AEM.


AEM could be deemed as the opposite of Drupal, provided the fact that it is a proprietary software rather than an open source. Built by a leading content management suite, it is a WCM that its proprietor refers to as a powerhouse and given its many features, it is not an inaccurate description. 

Adobe Experience Manager is an all inclusive system for content management that is equipped to build websites, forms and mobile apps. AEM effectively manages your content and your applications in an integrated manner, leading to applications being deployed as conveniently as the content. The result is a streamlined management of your online presence and that is what Adobe capitalises on.

This sounds somewhat similar to Drupal, doesn’t it? That is because at a foundational level, both of these are performing the same work. It is the way they do the work, the means and the features they are packed with that make them different, and that is what we are going to find out today.

Before we get into that, let us have a look at some statistics involving both Drupal and AEM to get a clear picture of their market share. 

There is a pie chart denoting the number of websites for Drupal and AEM.The number of websites for Drupal and AEM. Source: SimilartechThere are two horizontal bar graphs describing the market share percentage of Drupal and AEM. The market share of AEM and Drupal. Source: WappalyzerA graph shows the standing of Drupal and AEM with regards to other WCMs.Comparison of Drupal and AEM with respect to other WCMs. Source: W3Tech

What is the degree of performance and scalability offered?

The performance of a website is probably what makes the user stay on it for a longer period of time. If it is taking more than 2 seconds for a page to load, the user may become inclined to hot hit the escape button and move onto a different site. You know you have competitors and they gain from your loss.

So, the first feature to discuss has to be performance and scalability of Drupal and AEM sites. Let us get on with it. 

Drupal 

You must have heard that on occasion many sites tend to crash, especially when there is bulk traffic on them. With Drupal, you do not need to worry about that. The busiest of sites all across the world are using Drupal to handle their traffic spikes and keep them away from the embarrassment of slow performance.

And it is not just traffic that would be managed by Drupal, it also gives you the room to expand your content as much as you want, with multiple content contributors, without having an effect on the performance.

Therefore, managing site performance and scalability is quite easy and efficient in Drupal. The only thing to remember is to optimise your site well, if you don’t do that, there won’t be any guarantees. 

Drupal provides many tools and features to make that happen. 

Read about Drupal’s performance optimization techniques and scalability provisions to know more.

AEM 

With regards to small and medium based applications, AEM’s default configuration settings do their work without much effort on your part, leading to a streamlined performance for publishing and authoring at the same time. However, the growth of your sites would require a performance and stress test, depending upon the result of these tests, you will be able to comprehend the way to optimise the system. 

The advantage of Adobe Experience Manager is that after the installation and configuration is done, the degree of complexity of your project along with your development team will be the deciding factor for the performance optimisation. Even if your system load and performance profiles change over time, AEM’s performance tune-ups will keep your system optimised. Measurements, analysis, optimisation and validation become a constant part of these tune-ups.

Also, AEM uses files from content, JavaScript and CSS to establish performance standards. It also takes necessary performance action by using caching, load balancing and CDN; almost similar to Drupal.

All in all, Experience Manager can easily scale so that your performance needs are satisfied on the basis of the demand for your digital assets.

To sum up, Drupal offers you room to expand as much as you want without hampering your site’s performance, AEM also does something similar. However, the latter comes with a stipulation of tests to ensure that. 

How smooth is the content workflow?

If performance is the spine of a website, then its content would be the blood in its veins; metaphorically speaking of course. So, it was only wise to talk about the content workflow after performance. 

Drupal 

Drupal is a big name in the WCM market and the way it lets its authors use and manipulate the content across multiple pages is the reason for it. Drupal provides an ease in content authoring that is unparalleled by other systems. It is equipped to provide all the necessary tools required by the authors to create and publish content that is customisable. The WYSIWYG editor personifies Drupal’s flexibility. The workflow and content is easily managed through authentications and permissions. 

With regards to the content architecture, Drupal excels here as well. You can create just the right architecture based on your needs with the help of an Admin Interface or programmatically, the choice is yours. With display mode tools and Views, you can display only the content you want to be displayed based on the context, be it images, videos or even pdfs. Modules, like Paragraphs and Layout Builder, help you get the best out of your content by letting you micromanage the minutest of details. Moreover, Drupal workflows support annotations, it can reuse images in various components and it can easily support several individual fields in a single field with multi-fields. All of these provide a great user experience and the fact that it is equally good on multiple devices is another forte of Drupal. 

Apart from the creation of the content, the way it is stored and accessed is also imperative, after all we are talking about a content management system. In Drupal, the content is stored in a database, in a hierarchy, if you want, wrapped in Symfony. The interaction to the data by Drupal is usually done through MySQL, although there are other databases available as well. 

AEM 

The user experience to content authors provided by AEM is tough to compete with as well, although Drupal does manage that feat. Adobe Experience Manager not only integrates the content with other adobe technologies, but it also provides a high degree of flexibility and drag and drop user interface for almost all tasks, thereby making content authoring a breeze. 

Content in Adobe is not one single body, it is divided into multiple smaller components that in turn provide an immense degree of control to the content author because he can manage the smallest of parts of the content body. The feature of content fragments helps in editing the content to the most granular level with each component, be it text, images or videos given a separate fragment. The pre-existing templates in AEM work in a similar fashion to Drupal’s modules, allowing all the more ease in content creation. However, the fact that these individual components can be reused across multiple articles, makes AEM different from Drupal. 

Coming to content storage and access, AEM stores content as files instead of a database, which are wrapped up in Adobe CRX. And these files are accessed through Apache Sling. This web application framework provides an interface that can be accessed programmatically by developers to retrieve content. 

Drupal and AEM are more or less the same in terms of content, flexibility being the forte of both and the drag and drop feature being the focal similarity. The only difference that is blatant to me in terms of content is the way it is stored and retrieved. Although both use frameworks, the way these frameworks work is quite contrasting. 

How do Drupal and AEM align with your Marketing and Engineering goals?

There are two sets of people who are considered to be the building blocks of a website and it is their input that takes a web project to the next level. These are the engineers and the marketers. So let us understand their take on Drupal and AEM to highlight their difference further. 

Drupal 

Drupal, being an open source platform, comes with a great deal of benefits. The number of open source components found can be overwhelming for your engineers for all the right reasons. The primary one being the fact that Drupal is the synonymous of a developer-centric ecosystem. What this means is that you would be benefiting from the knowledge and expertise of other developers. This encourages learning like nothing else.

As for the marketers, Drupal again provides. For one, Drupal equips the marketers to edit or update page layouts without the presence of a developer. Earlier this feature was only found in AEM, but now Drupal is also packed. Then, there is the fact that Drupal allows the marketers to choose the tools they want to outside the jurisdiction of Drupal. Any leading marketing automation tool you might get compelled by would be perfectly used with Drupal for your gains. 

AEM 

Like I have already mentioned, AEM is a proprietary software, meaning that it does not have any of the benefits of an open source. In terms of an engineer, this can be a major drawback. You must be wondering why? The answer is simple, there wouldn’t be a developer pool, whose knowledge could be tapped into. So, the technical costs become high and you might find yourself solving an issue that has been resolved by numerous developers, but you can’t know that since AEM is not an open source and the locked code prohibits you from knowing. 

Adobe has many fancy, for a lack of better word, marketing tools that can effectively urge any marketer to take it up. The integration with these Adobe tools helps in providing a page building experience that is simply impressive. However, there are two things that make it lag behind Drupal; 

  • For one, only Adobe tools can be used, you cannot access other marketing tools available in the market;
  • And secondly, although agile marketing is provided, the fact that other developers in the community cannot contribute to it can be slightly disheartening. 

This is not to say that Abode is inferior or Drupal is superior, they are just different in the eyes of the marketers and engineers. 

It is pretty clear who is the winner here, a developer would always prefer a pool to stimulate innovation. Drupal's vast community provides that and AEM’s doesn’t.

What are the cost implications?

Whether something fits your budget or not is an important consideration when you are  considering to adopt a practise or in this case a WCM. How do Drupal and AEM fare in this regard, let’s see. 

Drupal 

In terms of costs, Drupal is going to be a clear winner and I think you knew that even before reading this blog. Drupal is an open source software, that means it has zero licensing fee. However, this does not mean that it is free, there would still be money required to build it. This is primarily because Drupal sites are built from scratch. You have to hire experts to take that seed Drupal provides and water it to become a full-fledged tree, you get the metaphor, right? 

When your site is built to be fully functional, then the costs for maintenance would start following, which is understandable. Drupal provides you the advantage of scaling the maintenance and support costs to align with your budget, and that is all we can ask for. I wouldn’t call Drupal to be free, but it is pretty economical. 

AEM

Compared to Drupal costs, AEM travels in uncharted territory. The costs start to pile on from the get-go. Since it is a proprietary software, you have to pay a licensing fee. Add to this the cost of building, including the hiring of developers, and the costs would be substantial. And then there is the cost of maintenance, although for support, AEM does provide a dedicated team, thank goodness for that. The average cost of AEM license and implementation can be around $100,000 to $200,000.

In the times of the pandemic, AEM can be way out-of-the-league for many organisations looking for a WCM.

Drupal is free of cost and this is one fact that would always make it outshine AEM, which, on the other hand, cannot be free, being a proprietary software. 

How good are the security measures?

Everybody has vulnerabilities, humans and websites alike. Our vulnerabilities might take us longer to overcome, however, websites are not that tricky. Security measures that are both sound and effective can help even the most faulty of codes become hack-proof. In this regard, let us try and figure out the standing of Drupal and AEM.

Drupal 

Many think that open source software is more prone to security breaches simply because they are open. However, that isn’t the case. Open source security, aka, Software Composition Analysis helps in giving the users the chance to attain a higher visibility level for their open source applications. For this, a lot of elements come into play. The binary fingerprints are examined, research both professional and proprietary is utilised, corroborating the research with scans and providing all of this to developers in the form of tools. So, no open source by no means can be regarded as unsafe and insecure.

The security elements of Drupal are top-notch and help you overcome the most severe security problems. The proof lies in the fact that numerous government agencies have trusted Drupal to build their sites and Drupal has passed all their stringent standards. Drupal’s Security Team is equipped to address all the security issues that are reported, be it in core or contrib modules. The members of the team are experts in security measures from across the globe, validating the reliability of Drupal in terms of security. 

  • The password policies of Drupal are the first sign of it being safe with minimum length, complexity and expiration. 
  • The limitation of login attempts from one IP address can detect brute force entry. Certain IP addresses can also be banned. 
  • The user roles in Drupal help you control what can be seen and modified by uses on any given page. 
  • The database encryption Drupal provides can be configured to become extremely strong for applications that warrant high security, be it to the whole website or certain parts of it. 
  • The Form API oversees the validation of all data entries into the database by scrubbing them so that XSS, CSRF and other malicious data entries are stopped in their tracks. 

All of these account for a safe and secure system for all your website building needs. 

A pie chart depicts the percentage of vulnerabilities in Drupal and two other CMSs.Percentage of security issues in a sample group. Source: AcunetixA bar graph us showing the comparison between different WCMs' security.Source: Sucuri Blog


AEM

Unlike open source, proprietary software is considered to be intrinsically safe and less prone to vulnerabilities. Again, that is not the case. There are instances when AEM sites have suffered major breaches. Something as simple as forgetting to use “nosamplecontent” during publishing can give just the opportunity a hacker was waiting for. This is because sample content is often under production and many know the user passwords. Saying this does not negate the brilliant security measures AEM does provide, my point was simply to enunciate that proprietary software is not immune to vulnerabilities. 

To say that AEM’s security features are similar to that of Drupal would not be entirely wrong. This is because Drupal has covered all the possible vulnerabilities that need to be prevented and worked the security measures around them. Since AEM wanted to do the same, like it should, the similarities come as no surprise. 

  • The security console to manage user access;
  • The theme language of AEM, HTL, has an intrinsic design to prevent XSS hacks; 
  • The AEM checklist helps in ensuring that all the security precautions are done as needed.

However, take a note of the security vulnerabilities of AEM that were reported in the recent past:

There is table showing the security vulnerabilities of AEM. Source: CVE Details

Do AEM’s security features sound similar to Drupal? I am certain they do. AEM is quite secure in itself, however, it has been reported for authentication bypass vulnerability and cross-site scripting vulnerability which should be taken into consideration.

How well are they tied to the community?

The developer community is vast and extremely supportive of each other, so as the next point of difference, let us look at how community plays a role in Drupal and AEM. 

Drupal 

There are plenty of advantages in contributing to open source. It pays dividends to both the contributors and the open source software itself. The support of the community is probably the best feature of being an open source. And Drupal has a pretty large one, with over one million members. This means the intellect of the million developer minds will be found in the core and contrib parts of Drupal, driving innovation further. Developers from across the globe could provide you a peer review for all your projects. 

Another advantage of an open source community is that it helps you thrive even in the most difficult of times. Therefore, the chances of Drupal going out of business are slim to none. The long term success of Drupal is almost a guarantee with its million volunteers. Learn more on how open source has remained recession-proof and how it has stayed relevant in the times like Covid-19 pandemic.

AEM 

With AEM, the story is different. A proprietary software does not have a community as impressive as an open source’s. There are still many AEM  user forums, but it does not match Drupal. 

The lack of community support somehow inhibits the force of innovation and makes AEM seem a little pale against its counterpart, Drupal. 

How responsive is their web design?

The user is the focal point of any web application, it is he who is at the heart of every decision made for the website. Therefore, a responsive web design that would take into account the user’s needs and his environment is of the essence. On this note, let’s compare the two. 

Drupal 

When responsive web design comes into the picture, the first thing to cross your mind is that it has to be mobile friendly and Drupal sites are just apt with that. Drupal is known for its responsive designs that provide the best experiences despite the device. 

It is Drupal’s aim to support a seamless content experience throughout the lifetime of its websites with its mobile-first approach. The out-of-the-box responsive elements have made it the premium choice of developers and content authors alike.

  • The ability to add and edit on the go is a must have and Drupal provides. 
  • The built-in themes with responsiveness embedded in them allows your webpages to fit all screen types. 
  • The ability to change the width and height of images depending on the device is also provided by Drupal through breakpoints. 
  • Even the tables in Drupal 8 are responsive with high, medium and low priorities available to assign to them.

AEM 

AEM is also up there in the responsiveness game, with many features making it a friend of all the mobile devices.

  • Using single or multi-columns for layout;
  • Manipulating the text size based on the screen size;
  • Displaying only priority content on smaller screens;
  • Providing device-specific tools for access;
  • Taking into account the window dimensions to assess the size of images to be displayed.

When web responsiveness is prioritised, you would not have any qualms about the future of your site because it would be secure leading to boundless capabilities. In this aspect, both Drupal and AEM pass, that too with flying colours.

Are there any development constraints?

Next comes the part where development is concerned, do Drupal and AEM have development issues? Do they limit the developers in their building? Or do they give them proverbial wings to fly on? Let us find out.

Drupal 

Drupal is renowned for building digital platforms that are transcending the boundaries of digital media in the present day. Its LAMP technology stack is the reason for it. Linux, Apache, MySQL and PHP, all four provide you agility, pace and flexibility to meet your enterprise’s development needs. 

One drawback of Drupal that is often cited by its counterpart is that it's not highly available. The reason being the fact that it does not provide multiple database instances, meaning one change to one database automatically changes all of them. Even though it is true, does it really account as a development constraint? 

Focusing on PHP, it is often considered to be a less advanced version of Java simply because it does not include state memory constructs. Therefore, tracking data separately becomes exhausting.  

AEM 

AEM developers need to be fluent in HTML, CSS, HTL, JavaScript and Java to develop on top of AEM, no PHP required like Drupal. The best feature of AEM development is the fact that it uses HTL instead of JSP for front-end development. This removes the chances of human error leading to XSS and secures your site a little more.

The drawback I talked about in Drupal is not really an issue in AEM, but does that really make it better? AEM is expensive as we have already established, its exorbitant costs are justified by providing an extravagance that may not really be needed. I mean what would globally distributed data centres do for a local website? They do sound appealing though.

AEM has Java instead of PHP and yes, it can do a lot more per process, but this would increase the complexity levels and make the overhead go on the higher side along with the chances for faults.

I would say that figuring out which is better between PHP and Java is a moot point, both have their own abilities. The fact that many leading organisations use them on their websites speaks quite loudly for their capabilities. Don’t you think so? 

How well do they support third party integrations?

Being able to integrate itself with other applications is often regarded as a great feature of a WCM. Both Drupal and AEM are able to do it, however, one of them stands out as the better option. 

Drupal 

Third party integrations have become a rudimentary need for open source platforms. Since Drupal is an open source, it comes with an intrinsic ability to integrate well with other platforms. Drupal was architecturally designed to be both scalable and modular, this makes it competent to allow third party integrations with ease. With the Services Layer and Library API being equipped to handle all the integration needs, the process goes by smoothly. 

Drupal can integrate with numerous analytics platforms such as Google Analytics, Salesforce and HubSpot.  It can make the ecommerce businesses feel connected with all the varying aspects they mandate. For example, Drupal Commerce can integrate with Magento. There are plenty of options for media integration too such as Colorbox and Slick Carousel. If you need an enterprise search solution for your web application, Drupal has got you covered and gives you Search API Solr.

AEM 

AEM is known to have a vast number of tools in its collection, however, it is also able to integrate itself with other applications.

  • Integrating with Amazon web services is easy with Amazon SNS connection;
  • Email marketing becomes convenient with ExactTarget;
  • Capitalising on social networking is also done through integrating Facebook Connect and Twitter;
  • Sales and CRM software are integrated through Salesforce.

There are other integration tools available as well for your convenience.

Despite all of these, AEM has certain issues with integrations which require troubleshooting. AEM does talk about these and mentions ways to overcome the problems as well.

For instance, some integration issues are known in AEM such as the Report Importer causing high CPU/Memory usage or the non-visibility of targeted content in preview mode when using custom page components. 

Even taking troubleshooting integration issues into account, AEM is still quite good with integrations, especially given the fact that it is a proprietary software.

Concluding this point, I would say that both Drupal and AEM have elaborate tools of integration for every field and need of a business. However, when troubleshooting is concerned, it does put a damper on the impressiveness of AEM. 

Are upgrades and migration easy-to-do?

Technology keeps enhancing and new updates keep on coming, so it is a matter of time before the version you are using becomes a thing of the past and something better is on the market. The question is how do Drupal and AEM fair in the upgrade and migration aspect?

Drupal 

Like I have already mentioned, Drupal 9 is the most recent version, yet not many sites have upgraded themselves to become Drupal 9 sites. However, they would have to because; 

as of November, 2021, Drupal 8 would not be supported; 
and after November, 2022, the same would be true for Drupal 7.

So, how do you update them? Let’s talk about the switch from Drupal 8 to 9, as per the makers, this upgrade is considered the easiest in almost a decade. By following a four-step guide, you can have your current site ready for the functionality and better security standards of Drupal 9 by using the Upgrade Status

As for the upgrade from Drupal 7 to 9, easy is not a term that would be used to describe it. The migration will overwhelm you, but all the advantages of Drupal 9 will make it seem worth it. Developers can make the upgrade themselves with the help of Upgrade Status and Drupal Module Upgrader. These help in letting you know whether your themes and modules are competent for Drupal 8/9 and converting your custom code respectively. Explore the ultimate guide to Drupal 9, all the burning questions that you may have about Drupal 9 and the must-have modules to start your Drupal 9 website to know more. 

AEM 

With AEM, the story revolves around a similar terrain, with more steps though. Upgrades from AEM 6.0 to 6.5 involve a lot more work than Drupal would. Separate migration tools are needed for making the entire upgrade a success. For instance, if going from a version older than AEM 6.2, you would need JMX bean to migrate your assets.

However, if we look at the upgrade from AEM 6.3 to version 6.5, the task of migration is totally eliminated. The new format for the SegmentNodeStore is the reason for it. 

The title ‘easiest upgrade of the decade’ has stolen the show, making Drupal upgrades more attractive and user friendly than AEM. 

How do they answer the multisite request?

Having multiple variants of a single website is not an uncommon trend, it is practised by Drupal sites and AEM sites equally. How do they fair then?

Drupal 

Drupal’s multisite setup helps you in gaining the many advantages of having multisite simply because it allows you to save on time and effort by running all your Drupal sites on a single codebase. 

Running easy updates for security issues, saving on hosting expenses, using Simpletest and functional PHP unit-based tests are few of the many use cases for multisite in Drupal

AEM 

For AEM, the Multi Site Management function does all the heavy lifting for you in capitalising the multisite feature. MSM allows you to monitor and control mobile and web properties into one integrated interface for all so that your global presence is defined by its consistency. Live Copy Overview and Blueprint Configuration Management are the two interfaces responsible for making the use of MSM easy for you. 

MSM is a great tool for creating user-friendly web experiences at the same time providing you localised control with regional teams having the power to edit. It also makes recycling your content a breeze. 

Drupal and AEM are not much different in terms of the multisite versatility, both equip their sites to make the most of one codebase or interface, and aim for consistency. 

How fulfilling is their headless approach?

Going headless has become immensely popular today. I mean who would want to pass on the chance of tapping into the latest technology without parting with their trusted WCM. Here is how Drupal and AEM perform. 

Drupal 

In a headless approach, the WCM is merely a content repository and nothing else and Drupal is a fine one at that. The separation of the front from the backend is pretty streamlined in Drupal with REST, JSON:API and GraphQL, being the APIs holding them together. 

Drupal is known for its flexibility and that can be seen even in its headless approach, with three alternatives to choose from. 

  • The progressively decoupled Drupal has a presentation layer that is built using Drupal and other frontend frameworks, like JavaScript.
  • The fully decoupled Drupal completely segregates the two ends of the site and Drupal is just responsible for the content while a JavaScript framework like React manages frontend
  • The fully decoupled Drupal for static sites allows a static site generator like Gatsby to build a frontend by being its source. 

AEM 

A major reason for opting for a headless approach is to publish the content on as many platforms as possible, the web, mobile apps and other channels. With AEM’s headless approach, you can do that. It allows you to “manage and re-use” page elements or the entire experience, if you want, across numerous channels. This is done through grouping content and layout. 

Like it is for decoupled Drupal, AEM also has customisable APIs as a core component of going headless. On top of this, it gives the developers the choice to choose a default or custom JSON output. The AEM HTTP API provides a smooth transition into headless inclusive of content fragments. 

The headless approach for Drupal and AEM have a set of advantages accompanying them. However, the option of choosing the way and degree of decoupling, gives you something to ponder on, doesn’t it?

How do they help sites be multilingual?

We live in a world where diversity is a constant and diversity means being multilingual. Today, more and more sites are trying to be multilingual, so how do Drupal and AEM help them? 

Drupal 

With Drupal, you can create customized sites in any language, web applications in multiple languages and displays that have multiple admin languages. You get to translate your content completely, so that your business has a wider audience. And you also get the option of choosing a language interface for the administrators, content authors and translators. 

Drupal has been designed in a way that it can promote multilingual sites. The four modules, Language, Locale, Content Translation and Configuration Translation, created to ease the language transition are proof of my earlier statement. 

AEM 

AEM has a similar story to tell. It can also support multiple languages and that too with ease. The fact that it provides both human and machine translation workflows makes it a great choice. 

You might be thinking how it supports human translation. It does so the old fashioned way by sending the content to an actual translator and once it is done, the translated copy is sent back to AEM and it works its charm on it. 

The six-step process of translating content does not leave much room for errors and you get a perfect copy of content in whichever language you may need it in. 

Both Drupal and AEM are close to perfect in their multilingual feature and it is safe to say that this one is a draw. 

Finally, can they help you capitalise on SEO?

Search Engine Optimisation helps your site become more visible and visibility brings in traffic and you must know what happens then. 

Drupal 

Drupal is best friends with SEO, that is why it has all the modules required to make the most of its friend. 

You might know that keywords are an essential part of SEO practices, and Real-time SEO for Drupal helps in ensuring that the keywords are there without seeming spammed. Links are equally important in SEO practices, so there is the Linkit module. For duplicate content, there is the Redirect module to help you. And these are just a few, for an entire checklist, read our blog, The Ultimate Drupal SEO Guide for 2020.

AEM 

AEM lets you get the best of SEO and URL management by helping you optimise them. It makes you focus on the minutest of details, so that you never make an SEO error. 

For instance, when you have translated a content, you might forget to translate the URL and AEM’s SEO guide would never let that happen. From configuring the dispatcher to creating and XML sitemap, AEM takes care of all things. 

Drupal might have a tad more SEO-friendly modules than AEM. Although AEM does cover all the essentials, factors like keywords, headers and footers do not take precedence in it like they do in Drupal.

The Bottom Line 

The purpose of this blog post was not to draw out a clear winner because frankly speaking, there simply can’t be one. I might even give you a winner, but then there is a high chance that you might disagree. Taking all the features into consideration, Drupal does tend to come out with better prospects, even if the margin is not that huge. AEM would be close second to Drupal in terms of functionality and features. 

If I had to give you my perspective, for me, the end line is the cost. Since Drupal is free and AEM is not, it would become difficult for me to adapt to AEM and its exorbitant cost implications, at least initially. So, for me the winner would be Drupal. However, for you, it could be AEM and that is fine too.

Nov 30 2020
Nov 30

Building websites that are completely mistake proof is often considered to be a massive undertaking, which many-many times is not properly executed. Since there are so many parameters to fulfil and so many corners to oversee, mistakes tend to happen. You may not even realise that you have done something wrong in the development process, it could be much much later when you actually undergo a website audit that you come across the mistake that has been made.

Drupal websites are equally prone to mistakes. Despite the CMS being one of the best, there are still occurrences when things go wrong and the impact is felt on the engagement, conversions and consequently, the sales.

To not let that happen, I have compiled a list of mistakes that you need to steer clear of when building or working on a Drupal website. These are errors and oversights that many developers and content authors have experienced first-hand and you can certainly try to learn from their mistakes.

So here are the most common mistakes witnessed on Drupal websites.

A pencil is shown after having erased an error on the extreme left and the mistakes to avoid in Drupal are written in bullets in the rest of the space on a white background.


Where can you go wrong with the content? 

A good website is often considered to be the one with outstanding content, since that is what keeps the audience engaged and leads to conversion. Therefore, content is crucial for a website, both for the front-end and the back-end, so content should be one of the priorities in the website designing process. Due to this fact, there are a number of areas where the developers can go wrong with the content. 

The first common mistake witnesses with the architecture of content is using too many content types that you actually do not use. The unused content types are just going to burden your database and I am certain, you would not want an additional table in your database for three content types that you do not even use. Having content types with no nodes will have the same effect. Performing an inventory will help you get the mistake resolved.

Moving on from the unused to the used, content structures are extremely valuable for your editors who are going to fill them up and if they end up confused, what will be the point of it all? Standardising your content types is going to help you a great deal. 

  • Strike off the content types that are similar to each other, like news and articles;
  • Do not add new fields for every content type;
  • And most importantly, plan a structure prior to it, winging it may not work with your website content.

Content types have an effect on the performance of your website as well. So, if you do not want to drain the performance of your site by adding unnecessary complexity, you would be wise to avoid these mistakes.

What about your display mismanagement?

After content comes its display and Drupal is best in that game. With many different features available for use, Drupal can make your display game strong as well, you capitalise it wisely.

Creating a view for every list is both impractical and a waste of time. Focus on reusing Views as much as possible along with parameter based rendering.

Do you use PHP code in your database? If so, avoid doing that, instead you must write all the codes in the modules or themes itself.

Planning, optimisation and segregation are essentially the building blocks of a great website display. 

  • Planning to render the content types you need;
  • Optimising the Views you already have;
  • And segregating logic from presentation.

These three would have a visible effect on the display architecture.

What aspects of functionality can make your site lag behind?

The functionality of a Drupal site depends on the number of modules used and the way they interact with each other. Your code and how much of it you use is a major contributor in that. 

The most common mistake in this sense is the ignorance of code standards. This becomes more of a problem when there are more than one developers and everyone is using a different type of code. In such a situation, not only would the standard be lost,  but it would also become difficult for a developer to understand the other’s code. Therefore, the adherence to Drupal’s Coding Standards becomes a great help to uniformalise the code and make the functionality a breeze. 

Another obstacle in functionality are unorganised patches. Code modifications and bug fixes mandates the implementation of patches, however, they become a problem whenever there is an update. You can forget all about re-apply the patch or forget to change it in accordance with the new version. This can very well affect the functionality of your website, so organising them is essential. 

Having too many modules, too many roles and too much custom code, despite there being contrib modules for the same is bound to affect the functionality as well. Evaluate and re-evaluate your site for its needs to overcome these functionality hindrances.

Is your performance and scalability not up to the bar?

User Experience is directly proportional to the performance of your website; the more streamlined the performance is, the richer would the UX be. 

Here are three scenarios that can impact your performance in all the wrong ways.

  • The foremost is improper JS/CSS aggregation settings. This is supposed to combine and compress JS and CSS files from the modules in the HTML, leading to lesser load times and higher performance. And you will be saying goodbye to that with the improper aggregation.
  • The next mistake is that of inundating your site with too many modules. Drupal may have numerous modules to offer, but you can’t be using too many of them. Doing so would only slow you down and hamper your security as well. Only keep the modules that you would be using, messing up your code, performance, overheads and security is simply not worth it.
  • A sound cache strategy also goes a long way in performance enhancement. Caching too soon, caching at lower levels and not knowing what and when to cache all contribute in a lowered performance.

Drupal websites can be scaled by millions of users within seconds and that is what makes these sites great. Drupal offers many modules to enhance the performance and scalability, Blazy, Content Delivery Network and Server Scaling, being just a few of them. Not installing these could be deemed as a mistake. Access the Drupal performance optimization and scalability provisions checklists to get more insights.

Are you facing possible security breaches?

Security has become one of the major concerns amongst website builders. Therefore, protecting your business from the menace of hackers and all the havoc they can cause is paramount. 

You must have your security measures in place, however, there still may be certain areas where you may have become complacent and that just gives the break the hackers need. 

  • Primarily, you need to keep your website updated, all the core and contrib modules, despite you using or not using them. Updating a module would mean that Drupal’s security protocols are being updated with them and you make yourself secure with that. You cannot have your projects falling behind on various levels of Drupal’s security advisories.
  • Now, you can install the “ Update Manager” module to keep yourself updated. The “Available Updates” will give you a friendly reminder of applying the available security updates.
  • Next on the list of security blunders is not giving the Input Filters in Drupal their due importance. You might have configured the full HTML Input Format to every user or you might have completely disabled the HTML filtering. Both of these instances can give malicious code to enter your website and you know what happens then.
  • Continuing on similar lines, many sites also configure their servers improperly leading to unwanted access to them. On some occasions, servers are seen displaying their version numbers, which is like giving an open invitation to hackers. Server configuration and permissions should be a priority for every site builder.
  • It is also important to ensure that all the users accessing your site by logging into it are the ones you want. By implementing a password policy, removing old users and updating staff roles, you will be taking a step towards better security.
  • User roles are quite important in running a website, however, they can become overused quite quickly too, which not only slows down your website, but if they are misconfigured, it can lead to major security breaches.

Drupal has proven to be one of the best CMSs in terms of its security measures, it has you covered from every corner, but only if you let it. From granting secure access to providing granular user access control along with database encryption and preventing malicious data entry, Drupal will keep your site protected, provided you let it.

Have you made any infrastructural oversights?

The infrastructure of your website is decided by the stacks you have, which includes the server, database and the software layers like Varnish. Going into development with a firm plan for your infrastructure is the only way to go, an oversight in this area can be quite damaging. 

The common mistakes in this area are;

  • The size of the website’s stack is extremely large or extremely small.
  • Not preparing for growth by consistently checking the logs for error and the identification of the weaklings.
  • Having an ideal sized server, but not configuring it properly, which can make the traffic forego Varnish.
  • Allowing remote connections to the server can make the website more vulnerable.

Misconfiguration can be avoided by simply using the right tools for it. MySQLTuner is one amongst many, its performance suggestions help in improving the infrastructure as well.

Are you following your maintenance goals?

Maintenance of a website starts after the development is done and continues for the entirety of the life of the website. Considering this fact, you have to be very diligent with the maintenance process as making the wrong moves can be brutal.

Here are some of these wrong moves.

  • Not following Drupal updates is a more common mistake than you would think. By doing this, you are going to be hampering security and making your site vulnerable to Drupalgeddon attacks.
  • On the contrary, there are also times when we update the modules, but we forget to remove the older versions. This too happens a lot of the time and can cause many problems.
  • It is not just the modules that need to be updated, the development environment should also be up-to-date and friendly for testing.
  • Then there is the code, which is not using the Version Control System like Git, even the deployment of files should come directly from there. Also, using it, but not leaving messages for other developers related to the changes made can lead to chaos. It is, thereby important to always keep the VCS repository clean.

The crucial aspects of maintenance is time and consistency. When you do it timely, only then would it become a worthy practice. The review and assessment of your architecture in timely intervals along with all the logs, be it Apache or Drupal is a great headstart for the maintenance process.

Are you universally accessible?

Websites today need to transcend the parameters that used to confine them and their audience in the past. The sites and applications need to be built on a foundation that would make them fit for each and every user. Drupal has worked for the same, it aims to make websites accessible to all, including people with disabilities, by making itself an all-accessible tool. 

Web accessibility has become of the essence today, and persons with disabilities are at the core of it. Websites need to be designed keeping in mind their needs, be it a broken hand or a temporary sight loss. It isn't just me who believes this, World Wide Web Consortium’s guidelines agree with me as well. W3C two sets of guidelines are ardently followed by Drupal and your website should do the same, thus, support and foster inclusion. 

Despite its importance, many developers tend to overlook the accessibility features and that is where they go so very wrong. 

  • Not focusing on balanced contrast levels that can work under sunlight;
  • Not incorporating a form validation error verbiage to aid the visually impaired; 
  • Not using buttons over CTAs.

These may seem like minor errors to you, but they can go a long way in making your Drupal site accessible to everyone. Read this comprehensive guide to plan for web accessibility to know more.

Is your site SEO friendly?

Being SEO friendly is almost as important as building a website. Search engines bring in big numbers of traffic, so optimising them is crucial; yet we tend to forget to fine-tune the SEO details and focus on all the other aspects. At the end of the day, a website is an online business and business cannot survive without its clients and being SEO friendly is the way to go. Going wrong in this area can be extremely detrimental.

Look at the following aspects of a website and see how many you are and aren’t doing. 

Are your URLs user friendly?
Are your images small in size, with filled out alt texts?
Are you making your paragraphs short to make the text easy to scan through?
Are you using robots.txt for pages that you do not want crawled?
Are you creating an XML roadmap to help Google easily understand the structure of your website?
Are you researching your keywords?
Are you adding internal links to make your less popular pages gain attention through the more popular ones?

A positive answer to all of these means that your SEO game is strong and a contrary answer would let you know your mistakes.

To avoid the contrary from happening, Drupal provides a number of modules to help you capitalise on the SEO front. The SEO checklist module is a proof of that as it helps you by ensuring that you are following through on the latest SEO practices. Then there are the modules that aid your URL precision, like Redirect, Pathauo and Easy Breadcrumbs.From easing the process tags to helping in communication with search engines to providing the essentials for editing, Drupal has all the right SEO modules in its corner and not using these would be a colossal mistake on your part. Read our blog, The Ultimate Drupal SEO Guide 2020, to know more about these. 

Can being multilingual pose a problem for you? 

Today, languages that are regionally spoken have started getting more prominence than ever before, especially in the international community. A french website would not be successful in India, if it is in French, not many people speak that language, so it would have to be in a locally accepted language. Being multilingual also opens the doors for many mistakes to occur. 

  • Using the same URL for all of your multilingual websites; 
  • Not giving the user a chance to avoid a redirect to the international website;
  • Using an automated translator, instead of actually hiring content authors fluent in the language;
  • Foregoing to translate the imbedded parts of the site like meta tags and descriptions;
  • Not focusing on the foreign market trends and the keywords appropriate to it;
  • And lastly, not writing the content in accordance with the local language and dialects. You can’t be calling ice lollies popsicles sticks in India.

You have to be totally attuned with the language of the region that you have followed for the multilingual project to work. Learn more on Drupal’s multilingual capabilities here.

Is having a multisite presence worth it?

Depending on your business and its needs, having multiple sites can be a good solution for you. However, managing then can become a bit of a hassle and often lead to big blunders. 

Some examples of such blunders are;

  • Traffic is one of the major concerns here. Running multiple sites means you have one codebase and many sites on it, so if one is inundated with traffic, all of them could slow down as a result.
  • A mistake in the syntax of one site could mean a mistake in the syntax of all.
  • Updates become a headache as well. For Drupal sites, you have to run an update.php in order to update the site and doing that on multiple sites is going to bring on the headache.
  • And finally, if you do not use Aegir, you are going to regret going multisite.

Is your Decoupled Drupal approach the right one?

Drupal offers an impressive front-end technology to make your presentation layer as good as you want, yet it does not include all the front end technologies there are on the market. Taking advantage of JavaScript and Static Site Generator would mean to decouple Drupal and separating the front-end from it. Even if you want to take on decoupling, it may not want to take on. The decoupled Drupal can bring more drawbacks then. 

  • If you wish to capitalise Drupal’s in-built features, Decoupling would be a mistake, since you would end up parting with them.
  • If your front-end requirements and Drupal’s front-end capabilities are aligned, taking on Decoupling would only be an unnecessary effort on your part.
  • If you do not have either the budget or resources to tap into the hottest technologies, then even if you want them it is not going to be fruitful.
  • If you are only publishing content at one place, you would have no need for decoupling.

For a detailed explanation, read our blog, When to Move From Monolithic to Decoupled Drupal Architecture.

Finally, what about web hosting, are you doing it the right way?

Web hosting services that provide your website its own space on the internet are pretty common. There are far too many web hosts to count, yet the decision to choose one is not easy at all, since there are too many considerations to keep in mind. 

Some of the common mistakes to avoid which signing on a web host are;

  • Testing web hosts is not uncommon, it is the right way to know whether they are valuable. However, testing on your website that is primarily bringing in the traffic could be unwise, especially if you are using a free service. Therefore, not registering with a different party can be colossal.
  • Another mistake is trusting too easily without knowing the host for too long. Therefore, not partnering with one that has a long trial could be a mistake. The longer the trial period on offer is, the more reliable the host is going to be.
  • Taking on a web host is a huge commitment, so you have to be sure that you are in the good. Not doing your due diligence before the commitment is not the right way, comparing the pricing and features along with checking if they have blacklisted IPs.
  • Not tracking your hosting uptime and speed can also be a problem. Also not checking what guarantees for uptime are provided by the hosts for the same would not be wise. If there is a lapse between the guaranteed and actual uptime, keeping a track would give you the opportunity to ask for compensation.
  • Lastly, you cannot afford to not have a backup of your site and that too regularly. You will only have the recent version of your files and assets, if you back them up.

The Bottom Line 

Every aspect of your website is important, consequently, you have to be mindful of them all. If you are not, mistakes will happen and they will cost you your site’s performance, its security and your potential customers and sales. In order to keep that from happening, you have to avoid all of the aforementioned mistakes and ensure that your website is impeccably built and maintained on all platforms. 

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