クリエイティブな才能を開花させよう

NicolePereira · ‎4 2, 2025

Currently, we make a form for every language we support. For us this means we will have 7 versions of the same form just for localization. Then we need to combine reporting and duplicate workflows and manage all these forms on localized pages. We'd like to have multi-language variants of a form with the ability to assign multiple sub-languages to a form, and the right form displays automatically based on the selected language. This could be a great enhancement to localization heavy HubSpot customers.

NicolePereira · ‎4 2, 2025

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.

karstenkoehler · ‎1 24, 2023

Hello product team, For HubSpot admins, one of the biggest challenges is keeping a portal organized, cleaned up and prevent overall chaos. Especially in Enterprise portals with sometimes hundreds of users, it's almost impossible to get users to follow a naming convention for email names, landing page names, workflow names. Quickly this becomes a cat and mouse game where HubSpot have to constantly chase and remind users to name their assets correctly. Why is this currently a bad user experience for users? Naming conventions are usually documented outside of HubSpot, in a wiki, stored as a Google Doc or something similar along the same lines. Forcing them to interrupt what they're currently doing, look up a naming convention and then come back means that they're losing time. They also have to leave HubSpot momentarily. Even then, they might misunderstand the naming convention and type in an incorrect name. Why is this currently a bad user experience for admins? Incorrect naming means that list or workflow filters for Recent conversion might not work. It can also mean that reports become a mess, if these reports are pulling in asset names. If admins have to look into this on a permanent basis, in portals where there are new assets every day, this takes time away from developing the HubSpot portal and generating more value for all users. Here's what a solution could look like To solve this, it would be great if there were tools to enforce a naming convention. Ideally, admins would specify what constitutes a correctly named asset and similar to the forms editor, arrange fields to their liking. Here's a quick mockup of what this could look like when creating a new page. The user could select from dropdowns which team they belong to, the language of the assets, the asset type, include a title and date. The system would then generate a title from this that cannot be further edited. Admins should be able to specify the options for each dropdown, separators, order and field validation (e.g. max length for a title). (In case this is eventually introduced, please consider to make this a feature that is at least included in all Professional and Enterprise subscriptions.) I would love to see this for all assets in HubSpot: emails, workflows, lists, campaigns, imports, properties, files etc. Thanks in advance for reviewing!

jaymewelch · ‎7 24, 2025

The old method for adding a section to a web page had search box so users could search for the section they want to add. You removed this with the latest implementation. Please add it back in. Scrolling through and looking at small images to find a section takes 10 times longer. You also removed section template descriptions. These are used to guide users on when its best to use one section over another or what common use cases are. It would be great to add this back in as well.

FrancescoM839 · ‎4 14, 2023

The Saved Section is really helpful, but it's missing the essential editing part. On my website I have re-used a section several times and I had to edit them one by one since there is no "Global Update". That can be an easy feature to add with a huge impact

Jnix284 · ‎5 26, 2023

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).

KPruett · ‎5 22, 2025

Currently, only legacy forms are available to be used in custom modules. In order to add a form created with the new form editor to a page, the only option is to use HubSpot's default 'form' module that's provided in the drag-and-drop editor. It is fundamental that the ability to utilize new forms in a custom module is added ASAP.

CElis · ‎7 21, 2023

Hey, I would really like to have the option to update my subscribtion page by drag and drop. In fact, I dont see why all system pages, e.g. 404, are not featured in the drag and drop builder. Even when changing the page via coding a lot of problems and frustrations arise. We dont seem to have any problems with the normal landing pages and websites. Please implement this feature. Greetings.

CAnderson87 · ‎4 25, 2023

This is a two-for-one idea. First, ideally searching would open a search window that could be recalled once clicking away by using the browser's back button. Second, the search results would be a customizable table or card view. As a sales rep, I'd like my search to open in a window, so that I can return to my search results if I click on the wrong result, without re-searching. As an admin, I'd like to customize the fields shown for search results. I'd like to do this from a search layout, not a field option, so I can see exactly the way the search will appear for users and design an optimized view.

NFricano · ‎11 20, 2024

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?

クリエイティブな才能を開花させよう

Allow forms to have multi-language variants

Create multi-language subgroups on pages

Enforce naming convention for new assets

Put search back in section template list

Edit Saved Section and Global Update them

Allow FontAwesome version 6

Allow for new forms to be used in custom modules

Subscription page building by drag and drop

Customize Search Results

Case Studies Beta proposed enhancements

実装済み

ベータ