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

We do a lot of site migrations from WordPress and other CMS' to HubSpot, and as we know WordPress always has the trailing slash and other CMS's have it, and in order to not hurt any SEO we need the ability to keep this. When it comes to HubDB Dynamic Pages, there is no way to add the trailing slash in the path column. It would be great if there was just a global control to have this turn on if we need.   ...その他を表示

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. ...その他を表示

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. ...その他を表示

Current Behavior: The {{ brand_settings }} HubL context variable provides access to branding assets (such as logos, color schemes, and domains) but is currently scoped exclusively to the portal’s primary (top-level) Brand Kit.   Use Case: Portals configured with multiple Business Units each maintain distinct Brand Kits. However, there is no programmatic way via HubL, CMS modules, or HubSpot APIs—to access the Brand Kits of these secondary Business Units.   Request: Extend the {{ brand_settings }} variable to allow developers to programmatically retrieve branding assets for any Business Unit Brand Kit within the same portal.   This would enable dynamic theming and asset management in multi-brand environments without requiring manual workarounds.   Benefits: Simplifies development for portals using HubSpot Business Units by exposing brand assets for all units natively in HubL templates and modules. Enables more flexible, scalable multi-brand CMS and email template designs. Eliminates reliance on external asset management or custom property workarounds. ...その他を表示

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, ...その他を表示

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). ...その他を表示

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.      ...その他を表示

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?   ...その他を表示

Features like serverless functions to consume APIs and quering HubDB in Hubl makes hubspot a CMS to build more interactive applications quickly than just marketing websites. But we see one limitation in our use case where we are storing certain information in HubDB and need that information for marketing automation but its not accessible in workflows or in custom reports. Do you all think it would be nicer to have HubDB data made available in workflows and custom reports to create more customized experience for users? ...その他を表示