Les grands esprits se rencontrent

We have several blogs with posts in multiple languages. We would love to import all the posts and associate them together with an ID so they can automatically be added to a multi-language group. This includes the importing of tags and authors in the correct multi-language groups. We have 5 blogs and 3500 posts between them all. Manually associating posts to a multi-language group is impossible and now we are forced to build an API-based application to create the posts.  ... Afficher plus

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! ... Afficher plus

When inserting an anchor link within the rich text field in web/landing pages, or the blog's editor, please provide some extra parameters in its Advanced dialog:   Classes - A text field that lets you type in multiple classes. E.g. Typing class1 class2 would output as: class="class1 class2" ID - A text field that lets you type a unique ID. E.g. Typing id1 would output as: id="id1" Title - A text field that lets you type in tooltip text. E.g. Typing External link would output as: title="External link"   ... Afficher plus

When we set up blogs, we often need to migrate between portals and retain archived and draft posts.   First, there is no option to import from a HubSpot export. which seems strange. We export/import between HS portals frequently during portal migrations, yet HubSpot isn't an option in the dropdown. Second, there are no mappings for Status, Archived, or Language in the blog content import. It's a terrible experience to have to import all posts as either Draft or Published and then hand-edit them. Right now, I'm battling whether to hand-alter the status/archiving of thousands of posts in a huge blog, or resort to storing everything "not currently visible" to a backup CSV, which wasn't what our client wanted. ... Afficher plus

It would be great if we could set up an automation that notifies us if any of our blog posts get over a set number of views.    Currently, we can only track views per contact instead of all views per blog post!  ... Afficher plus

As all of you might know the current blog post is just a simple rich-text which is fine for general posting. But many of our customers want a flexible solution. Like multi-column grids with different content-types like images, text, accordions/toogles ...    The only way to achive this right now is a custom module with all possible content types and pre-defined layouts and a repeater function.    It would be awesome if the blog post would get the drag&drop functionality so that every customer/user could design each blog post to his needs.  ... Afficher plus

I think AMP creates noise for non technical blog creators. They could create AMP versions of posts not knowing the technical SEO impacts. What do you think? Should I enable this? Shouldn't I enable this? What is AMP? Tons of questions for no n technical users.   ... Afficher plus

You should be able to list multiple authors on a blog! ... Afficher plus

Hi team, it would be nice if we allow the flexibility to edit blog tag meta description easily for SEO purposes. Thank you! ... Afficher plus