Great minds think alike

It would be useful to be able to set a module's meta.json css_render_options and js_render_options parameters from within the Design Manager. It would help with optimising modules for page speed. ...read more

As many of you know themes can come with a lot of modules which may not be used by the marketers. If they don't use it parts of it shouldn't be rendered to achieve smaller CSS/JS.   It would be great if the developers could access the "is_availible_for_new_content" from the modules meta.json via the themes fields.json file.    possible usecase: An accordion module with multiple settings in the theme fields.json (background color, padding...)   The CSS part looks currently something like this      .accordion{ background: {{theme.modules.accordion.background.color}}; padding: {{theme.modules.accordion.vert_padding + 'rem'}} {{theme.modules.accordion.vert_padding + 'rem'}} ... }       A developer can disable/enable the whole part with a boolean and an if-statement. But this doesn't have an impact on the module usability - therefore it's not really needed.   Would be great if the devs could change the module meta.json like this   "is_available_for_new_content" : {{theme.modules.accordion.toggle_visibility}}         ...read more

Hi,   on a HubSpot Website there seems to be a lot of JS files /scripts included and loaded upon page load. For a lot of those it is unclear for me what they are even doing and somtimes not possible to determine if i even need them on my website.   It would be great in the interest of performance to be able to choose which scripts are being included and which are not ( maybe like the way we can include/exclude the loading of JQuery?). Possible Solution (based on Subscription): When a customer has purchased a certain Hub, their website could load the scripts associated with the services of this Hub.   However, if you have not subscribed to this hub, the scripts of this hub should not be included, since its services cannot be used anyway. The scripts would be loaded unnecessarily. ...read more

It would be great and a huge time saver for when you changed the 'Default File Manager Hosting Domain', it would apply this retroactively as well to files already added to pages or posts. ...read more

There should be a way for me to limit access to a website domain we are developing. I have a website that is for a company in a regulated industry and we cannot have dev pages publically exposed.  A couple of ideas:   Password protect the entire domain - currently, you can do this at the page-level - we need to to this for an entire domain while we are developing and prior to final approval to go live. Control access via a list - again this is possible for a page but not an entire domain. Same reasons as above. Permission role - somehow control access to domains via a permission role? Having the ability to control this would be extremely helpful as the staging capability does not allow us to fully test links and functionality.   Thanks,   Andrew   ...read more

Hey there! I'm the creator of the CLEAN Pro theme and one of the questions I get asked almost weekly is if there is an easy way to covert a "local" custom module into a GLOBAL custom module.   I understand that this is possible using the CLI but very impractical for your average marketer who isn't a developer.  Even so, having to go through the CLI in order to do so isn't super convenient.    I would love an option right in the Design Tools section where one could simply click a button that would create a new GLOBAL (or local) version of the custom module within a given child theme.   What do you think?  Please upvote if you agree.   Thanks! Kevin ...read more

I'd like to have a dropdown item that allows me to navigate straight from a module in the Page Editor to it's relevant file in the Design Manager.   ...read more

You can see 'file usage' when you click open each file and it will show you which website page or email it is currently being used. It would be great to be able to show that in a column.    This makes it easier to shortlist currently active used files and sort/archive unused files.      ...read more

Adding simple workflows under forms is a great addition. However, removing the ability to select a specific follow-up email inside the form module on a landing page is a huge miss. Because of this, it is not possible to use the same form on multiple landing pages that each has a different follow-up email containing a different content offer.   This means that, from now on, you have to create a separate form and a separate workflow for each content offer. This creates an enormous amount of workflows and forms within the account, which results in making the workflows cluttered. In addition, it makes changing a form very time-consuming. After all, if you want to send out a new question you have to adjust tens or maybe even hundreds of forms.   It would awesome if we could keep the follow-up email functionality after the automation beta goes live. This would help a lot. ...read more