Great minds think alike

It looks like the HubL documentation is being updated quite a bit lately, is it possible to be provided update and change alerts? Does this already exist? Emails would be great but even if there were a page to go to to see what has been changed, added, expanded in the docs would be great.  The HubL docs is like the bible to a lot of us Hubspot developers and I find it very cool and helpful when the stuff I do to "hack" the templates I build turn into supported features with attribute libraries and/or use cases.  ...read more

There are a lot of suggestions for conditional fields in custom modules, as well as field groups and other variations. I think we need to go significantly further than this. Hubspot and HUBL seem to have different criteria and limitations, depending on where they are used. One significant step forward for use of Hubspot as a CMS could come through adding more capabilities to custom modules:   Conditional fields More field types in custom modules (grouped check boxes, for one?!) More liberal use of HUBL in custom modules  Perhaps this last item would be the easiest to accomplish, as it would put the onus on the developer to use HUBL to accomplish the project's goals, vs requiring Hubspot to augment the Custom Module builder UI. If we as developers were able to use all HUBL module types, or perhaps even just an expanded set -- color picker, CTA, flexible column!!, form, image src, etc..., we could build significantly more complex interfaces on our own within the system. We could also use HUBL code to make fields conditional ourselves -- as long as the Hubspot dev team reflected those conditionals in the page editor.   (FWIW, it is possible to drop hubl modules into a custom module now, but the fields in the page editor are not grouped with the other custom module fields.)   ...read more

To keep the files of a theme organized you have to split them into many files and include them via {% include %} and {% import %} into the main file. /* style.css */ {% import "Custom/page/css/settings.css" as settings %} {% import "Custom/page/css/macros.css" as macros %} {% include "Custom/page/css/custom.css" %}   /* main.js */ {% include "Custom/page/js/custom.js" %}   Everytime you make a change on an imported or included file you have to execute the following manual steps: Save the File Publish the File Save the Main File Publish the Main File (https://btyrd.de/2wpgNAI) Refresh the browser or browsers During development you have to repeat these steps many thousand times. That is not only tedious but a huge waste of time.   With liverreload you just have to save the file (http://livereload.com/)!   In modern html stacks it is a standard to provide a file watcher and live reload function. ...read more

I recently built a search for a blog using Hubl and a few lines of javascript. basically if the url contained a query then my code would search through all of the content componants (title, body, topics, etc) for each article and return any articles containing the query.    The key variable was the {{ contents }} variable that contains all of the articles information for the specific blog.    Considering that google site search premium is shutting down (and was never really brand friendly to begin with) I have seen a lot of need for an alternative. The fact is that a native site search in Hubspot is 100% possible except for one problem, there needs to be a variable like {{ contents }} that contains all live pages and blogs on the site. something like {{ site_contents }}.    I understand that, while articles have the post body field for the content, site pages are made up of all sorts of rich text modules and etc., but if you could combine all of these, per page, into some kind of sudo post body, and give us this variable you would remove the need for third party search programs.  ...read more

I am installing some bootstrap 4 templates that I created into Hubspot and I needed to add "nav-bar nav" as classes. I usually use no_wrapper=True on my modules and I just realized that the "extra_classes" classes are applied to the outer most wrapper which is removed with no_wrapper=True.   I need these classes to be on the ul anyways so an update to this would not solve my issue but it did get me thinking about advanced menus and how you can't really do much with them. With most modules you can use export_to_template_context=True and then loop through the contents, structuring the output as desired.    In a situation like this, where I am using a framework not supported by Hubspot, I have to get hacky to apply the propper classes to the ul.   I image you couldn't change extra_classes to apply to the internal html of a module instead of the wrapper because it would break the css of any site in the last 8 or 9 years that has used the extra_classes parameter. But it would be great if there was a new parameter like "internal_classes" that would apply to the most functional inner wrapper (ul in the case of the menu).   That would be the second best case scenerio, the best being us having the ability to create our own menu using export.  ...read more

It would be very beneficial to have an edit footer option in the design manager templates. Right now when you add JS to the bottom of the template (either in a custom HTML or HubL Module) it adds the content above the both the following JS lines. <script type="text/javascript" src="https://static.hsstatic.net/content_shared_assets/static-1.4040/js/public_common.js"></script> <script src="//static.hsstatic.net/slick/static-1.30/bundles/project.js"></script> This makes it hard for us to customize things like the Gallery slider. In order to add customizations (from Slick Slider) we have to do it from the "Edit footer" area in the page settings (as this code get placed below the JS files above).  ...read more

One of the biggest oversights in the COS is that it's very difficult to create looped content. As far as I'm aware, the only thing that lets you do a loop is a slider (if you use export_to_template_context), which has a limited number of fields per iteration. Consider this simple case: I want to create a custom widget where the user can create an arbitrary number of buttons. Each button has a link, text, and a few style options. Currently , they way I would have to do that is to decide what the most buttons I would ever need is, then add that number of each field (for example, five links, five button texts, five style drop-downs, and then distinct markup for all five). Obviously, a very tedious process. And if I want six for some reason, I have to go back and edit the module. So, here's how I envision this working. First, add a new option to the custom widget editor to create "field groups". Field groups could contain any number of other fields (perhaps even their own child field groups, because why not?), and would have their own labels, names, and description fields. Then, the person using the page editor would be presented with those fields grouped together visually, with add and remove buttons. Clicking add would create a fresh copy of all the fields in the group, clicking remove would remove that item in the group. Then, in the template, you would have the ability to iterate through items in the group with a for loop. Something like this: {% for button in widget.field_group_name %} <a href="{{ button.link }}" class="{{ button.style }}">{{ button.text }}</a> {% endfor %} The user can have as many buttons as they please, the page editor doesn't get clogged with useless fields, and the code remains simple and easy to maintain. This would give developers a lot of control over presentation without sacrificing ease of use for the page editor. I really can't emphasize enough how much this would simplify certain aspects of template building. ...read more

When creating templates in design manager, particularly CSS templates, it would be useful to be able to generate a dynamic URL for this, similar to the way URLs are used in File Manager.   If you are integrating a third-party plugin, such as an iframe on your Hubspot hosted page, and you need to reference a stylesheet in the source code of that iFrame via the third party website, you could just grab the URL of your hubspot css template and link it in the source.   So for example, you are placing an iframe for a job hosting board on your site, and you want to be able to style that iframe using your "main-theme.css" template as the linked stylesheet. The job hosting service could place in their source code the URL to your design manager template "main-theme.css".   This way, you could edit the css file in template builder, then refresh your page, and see the changes immediately, without having to re-upload a css file to file manager. ...read more

It would be very helpful for companies with difficult names to have a feature that shows the pronunciation of the Companies name in text form and audio form for the website.  ...read more