Great minds think alike

I would love it if HubDB could be added to an account as an add-on. We have many clients who would benefit from just this one feature but can’t justify the price increase to have it, which, IMO, is completely understandable given the jump in pricing. Even if the add-on version were limited to X amount of tables, it would greatly boost my team’s productivity. ...read more

It is possible to add a title and alt text to images in the File tool. However, when referencing such an image via a HubDB column, there is currently no way to read these properties: https://knowledge.hubspot.com/website-pages/use-images-in-hubspot-content It would be great to be able to do something like this (currently the "title" and "altText" properties are missing): <img src="{{ dynamic_page_hubdb_row.some_image.url }}" title="{{ dynamic_page_hubdb_row.some_image.title }}" alt="{{ dynamic_page_hubdb_row.some_image.altText }}" />   ...read more

It would be great if it would be possible to optionally add a custom name to the revision and then have some way to search.     ...read more

In my use case I f.e. don't want people to set custom font-sizes when creating content inside the Richtext-Editor in a HubDB field.   It would therefore be helpful to be able to configure which features should be exposed.     ...read more

The CMS has evolved into a great tool.  However compared to our Wordpress or Shopify website builds, we cannot provide our clients with a staging version to fully test major changes.  It is easy to proof a page or a module. But if you are launching a multi-page section that should be tested in the full website environment, good luck.  Content staging is very useful, but its not a full staging environment.  You cannot test changes in global modules, navigation, ETC. The sandbox in enterprise doesn't copy everything.  So it would take a lot of time and manual work to do a clone and keep it updated for the client to test.   We definetly NEED a good test environment where we could test the whole website with those changes in an more efficient way.   I'd love confirmation that this is on the roadmap for at least Enterprise and hopefully CMS Pro as well.  ...read more

Not everyone knows how to use the CLI and having to use the CLI to upload something as simple as a single module folder is pretty time consuming (especially if you don't already have it installed). So would be great if we had the ability to upload folders or even zip files (that are unzipped when uploaded) to the design manager. ...read more

Hi Hubspot Team,   we just launched our new website in HubspotCMS and I am quite happy with the result even if I am aware that there is still a lot to fix. The page is mostly in German and now it's time to do all the translation work into English. It would be a big game changer to have a deepl implementation where you can just click into which language you want the page to be translated. Please dear Hubspot developer make this happen, soon.   Best, Dani ...read more

GraphQL is a powerful tool that can be used (and currently is being used) in ways outside the CMS's scope. It's become a popular way to run advanced searches that the normal search endpoints can't handle. So why is it still paywalled in the pro and enterprise CMS plan? Every portal should have the ability to use GraphQL, just like every portal can use the search endpoint. There are a lot of things that people can't build currently because of their lack of access to GraphQL. Would love to see that changed. ...read more

Theme Settings is limited to certain types of fields and I've found myself wishing I could allow a user to edit globaly certain elements that require a field that's not supported: Image Field - add custom list bullets - easily switch out repeated decorative backgrounds - custom icons and misc decorative elements (ex: slider arrows, dropdown arrows, search icon, close icon)   Icon Field - set a FontAwesome icon for custom bullets - switch out misc decorative items for FontAwesome icons (slider arrows, search icon, close icon)   Gradient - For easier creation of gradients instead of having to add and use two color fields   Text - Allow the user to globally change strings throughout the templates/modules to their preferred lanuage (primarily for aria content for elements such as slider arrows/pagination, icon only buttons, filter controls, etc)     ...read more