Marketers love HubSpot CMS more than developers because it is designed to be user-friendly for non-developers. The platform has paid that price by not giving developers a free hand.
I asked the question from my teammates and searched HubSpot communities to find out why developers dislike HubSpot CMS.
Here are the top reasons why Developer Dislike HubSpot CMS
Extensive Use of HubL
HubL is a templating language inspired by Jinja. HubSpot developers use it to build templates and modules on HubSpot CMS. Unlike other open-source platforms or frameworks, HubSpot has constrained its proprietary environment, unlike WordPress or React.
HubSpot CMS needs more flexibility and customization options than its counterparts have. That’s why, despite having dynamic content and integration options, developers still have to work around to get the desired functionalities, which is time-consuming.
Interpretation Limitations
The proprietary environment also limits the correct interpretation of the programming language HubL on other platforms, such as WordPress, which commonly uses PHP, JavaScript, and CSS.
The Starter Plan
The limitations in the Starter plan also frustrate a few developers since it allows for just 30 website pages, including HubSpot branding. Some users can still manage within those 30 pages, but you can only publish 100 blog posts on the website, which blocks your marketing efforts.
There is no SEO analytics in the starter plan, only one user is available, and no HubDB tables are available. So, you get a basic website with everything limited. Developers on the community forums stated that it is hard to scale up the website from the starter pack because it needs more basic marketing support.
There is no benefit to rising talent
Clients or individual web developers who want to start with HubSpot don’t benefit much from it since they struggle with creating a poorly performing website that is hard to maintain and takes much longer to develop.
Love for Marketers over Developers
HubSpot was initially the marketing platform, but it is still better than other options. Designing a workflow and automating the tasks is easy for non-developers. We would have heard different stories if HubSpot had given more flexibility to developers and expanded its reach over keeping the proprietary environment.