Great minds think alike

Currently, staging does not allow us to make multi-language variants causing us to move to production first then make all our variants on a default system domain, and then switch it to the live domain. If we could just get our full language page groups ready in staging we could publish to live and improve the development workflow. ...read more

We have a website where we group 22 language variants under the en-US primary page. But there are technically multiple primary languages. So having the ability to make subgroups of languages would help tap into the fallback language options. The primary language for a group becomes the fallback for all languages. If you land on a page missing that language then it will go to the primary. But we may have several languages that are associated and we'd like to select a primary for that group. For example: fr-FR (primary for this set of language regions) fr-BE fr-CH So if fr-CH is missing, Id like it to fallback to fr-FR but still have it in the larger associated group of language page variants. ...read more

There's an emerging standard called LLMs.txt which is basically like a sitemap but explicitly for LLMs. It would be great to have support for this in HubSpot CMS. While I could do it one time and upload the file to my site, really, it's best if it were being updated dynamically as my site changes over time. Today, I believe this HubSpot CMS feature lives under Content Hub. ...read more

Ideally when creating a CTA I would love to have the option to add dropshadows from the dropdown menus. ...read more

Hi HubSpot Community,   I'm writing to share some thoughts and suggestions regarding the new Case Study Beta feature. While it's a fantastic step forward, there are a few areas where I believe it could be further improved to provide users with even more flexibility and customization options.   Current Limitations:   Limited Listing Page Customization: The current listing page customization options, particularly around tag filtering, feel somewhat restrictive. Being able to create more granular filters and sorting options would significantly enhance the user experience and meet more business needs.   Lack of Child Theme: The inability to create a child theme specifically for case studies limits our ability to fully align the design with the rest of our website.    No Multilingual Variations: As with HubSpot's blog feature, the ability to create multilingual variations of case studies would be invaluable for global businesses.   Header and Footer Customization: While there are some options for customizing the header and footer, they are quite limited. This often leads to design inconsistencies across the website, as the header and footer don't match the overall site design.  Proposed Enhancements: Expand Listing Page Customization: Allow for more granular tag filtering and sorting options. (e.g., filter by solution and case study type; sort by date, popularity or custom field) Provide additional layout options for the listing page. (e.g., grid view or card view) Introduce a Child Theme Option: Enable users to create custom child themes for case studies, allowing for greater design flexibility and alignment with the overall website. (e.g. customize sections, fonts, and add new modules) Support for Multilingual Variations: Implement a similar system to the blog feature, allowing users to create different language versions of their case studies. (e.g. create a Italian version of a case study targeting the Italian market) Enhance Header and Footer Customization: Provide more flexibility in customizing the header and footer, including the ability to use custom CSS. (e.g. have more styling options for the menu items) I believe that by addressing these limitations, HubSpot can create a truly powerful and customizable case study tool.    What are your thoughts on these suggestions? Are there any other features you'd like to see added to the Case Study Beta?   ...read more

HubSpot uses parent and child themes, when a theme is downloaded from the marketplace is creates a parent theme which cannot be customised in any way.  In order to do this a user must create a child theme, if a child theme is created all assets still refer to the parent theme's assets so these can be updated and work as a part of the parent theme.    The option exists to clone any of the assets from the parent theme to the child theme if customisation is required, this then stops these assets being updated when the marketplace parent theme assets are updated.    It's very easy for a user not used to this process to think they need to clone all assets to their child theme in order to use them, or to do it "just in case" then may possibly need to edit later. It's not clear in any way that this completely severs the asset from the parent theme and thus the updates. Leaving people in a place where their theme's assets may always need to be manually updated without them knowing about this until it's too late.    It would be hugely beneficial, and a quick win to have at least a warning showing users that this will stop automatic updates happening to these assets to help them only clone what's needed ...read more

Developers are limited to using version 5.14.0 and can't update themes to version 6.   Who: developers creating themes and marketers using themes What/goal: ability to use the latest icon sets Value: adds backwards compatibility   If the theme was created with 5.0.10 it is not possible to update to 5.14.0 because 5.14.0 is not downward compatible with 5.0.10. Updating the icon_set would break the icons on existing website pages where 5.0.10 was used.   Fontawesome introduced downward compatibility with version 6, but since HubSpot doesn't allow version 6, it's not possible to update existing themes.   Editing to include that without this update, users can't select TikTok or the new Twitter X icons.   Editing to include the icon field now supports v6.4.2 which works for all new themes or custom themes (doesn't resolve backwards compatibility issue). ...read more

Currently, you can only sync from the production to the sandbox. If could also sync in the other direction that would be awesome and will allow development teams to mimic their actual deployment flow. In development, it is uncommon to create something in production before creating it in a test/dev environment. Cheers, ...read more

I would like to be able to create my own personalized drag and drop email templates in the design manager. So instead of starting to create new drag and drop templates from scratch each time and adjusting them to the CI guidelines OR cloning templates which I have created according to CI, I want to build the basic templates by using the design manager. This way, users can select from my company-specific templates when creating emails (rather than choosing the five templates provided by HubSpot) and they are still able to be creative and do their dragging and dropping, but with certain design limitations.    This functionality is essential for large companies in order to ensure that CI guidelines are being adhered to. If not implemented, the drag and drop is basically useless. Also, simple cloining of drag and drop emails won't do the trick: Just think about the end of the year when the copyright date needs to be changed. This needs to be coordinated by using a global module (just like in the old Design Manager). That's just one of many exmaples where the new drag and drop reveals its weaknesses.      ...read more