topic Re: Order of modules in editor of custom blog template in CMS Development

Order of modules in editor of custom blog template

LvanAggelen — Wed, 11 Jun 2025 12:50:09 GMT

I have created a custom blog module for our client, which has a mixture of standard tags, static modules, 'hidden' standard tags, and the post_body all over the page.

In the editor, these modules are shown in a particular order:

First the hidden tags
Then the post_body with its modules
Then all the static tags and modules

My client remarks, which I think is fair, that this is not coherent with the order as they appear in the template, and thus confusing. Is there are way to show all these modules in the same order as they appear on the page? Or any other order?

Re: Order of modules in editor of custom blog template

Jaycee_Lewis — Thu, 12 Jun 2025 15:07:19 GMT

Hey, @LvanAggelen Thanks for your question. Do you have an example you can share? My experience in the community is that sharing links and screenshots when possible is always helpful for troubleshooting along with you. With more details, it may be possible for our community members to tell you if this is malleable or if it “working as designed” but not like you expect.

Talk soon! — Jaycee

Re: Order of modules in editor of custom blog template

LvanAggelen — Mon, 21 Jul 2025 09:48:32 GMT

Hi Jaycee,

Apologies for the late reply. Kindly take this example:

In the template I have the following items in order:

Inline widget - Image
Module - USPs
The post body (the blog content)

In the back-end the order is completely random. The 'hidden' image is on top grouped with other 'hidden' modules. Below that comes the Blog post with its content. And below that come the modules. These are in order, but it starts with one that is placed in the header, and then all the others (that are all also before th Blog post). Not really workable IMO.

This is especially confusing if you want to create dynamic templates with a checkbox. E.g. there is a hidden module (checkbox) to hide or show a section (with static modules). The checkbox would be miles away from the actual section that you are hiding/showing.

If I were to make a suggestion, I would dispay all the modules exactly in order as they appear on the page, and behind the module name, just show the type of module.

In my example template that I've sent, I would like to see:

- Banner (Hidden module)

- USPs (Static module)

- Blogcontent (dropdown with all the modules)

etc

Let me know if this is a bit clearer.

Kind regards,
Luuk van Aggelen

Re: Order of modules in editor of custom blog template

Jaycee_Lewis — Tue, 22 Jul 2025 18:31:21 GMT

Thank you @LvanAggelen 👋 Let's invite some of our community experts to the converstaion. Hey @evaldas

@Anton @MichaelMa do you have any tips or next steps for @LvanAggelen? — Jaycee

Re: Order of modules in editor of custom blog template

Anton — Wed, 23 Jul 2025 09:00:58 GMT

Hey @LvanAggelen,

thanks for the detailed information.
Quick question - are you using the same base.html for the blog as for other pages like landing pages and does this base have static modules as well?
Just asking because - if this is the case - what might be happening here is that some static modules are coming in from the base and getting mixed with the ones from the blog.

First thing I would try is, creating a seperate base.html without the modules if they're not required or move them to the blog template if they're required and put them in the right order.

As for the hidden banner module:

Why are you using a hubspot module/function for a static image? Wouldn't it be easier to simply hardcode it with an img-tag like <img src="PATH-TO-IMAGE" alt="ALT-OF-IMAGE">?

This would reduce the module list while keeping the functionality.

As for the "uitgelichte afbeelding" if-statement, unless you're using a different featured_image than the blog image, I would recommend to simply use the featured_image functionality of the blog post like

{% if content.featured_image %} <figure class=""> <img src="{{content.featured_image}}" alt="{{content.feature_image_alt_text}}" loading="lazy" class="hero-image"> </figure> {# using the require_css inside the if-statement will load the css only if the statement is true and therefore increase performance. This is just an example #} {% require_css %} <style> .hero-image{ width:1920px; height:600px; } </style> {% end_require_css %} {% endif %}

A few other thoughts:
If you're using individual booleans, choices and other HS functions inside a template, you could think about creating a "configuration module" that would contain all the different settings for each blog post, add it to the template, set the module to export_to_template_context=true and access all the settings from the module accross the template. I think this would be easier in the future.

Also, do you mind sharing the whole template code? Maybe there are a few other topics

best,

Anton

Re: Order of modules in editor of custom blog template

LvanAggelen — Wed, 23 Jul 2025 09:34:24 GMT

Hi Anton,

Thanks for the reply. The modules are indeed from the base template, but they are required. The thing is that they are indeed mixed up, because the module list in the back-end does not maintain a logical order. That's what I'm after, that the back-end can maintain the same order as the modules appear in the template; and not as they are now (grouped by type, placed wherever).

As for the template suggestions; the image is not hardcoded, the URL shown there is my 'default' but can be overwritten when editing the image module. The standard blog image is indeed used elsewhere in the template, this is a seperate image that falls 'outside' the blogcontent section.

The configurator is not a bad suggestion, thanks. That will place them with the other modules, but honestly only fixes about 25% of the confusion. Thanks nonetheless.

To be fair, I think I'm probably making more of a 'feature suggestion' than reporting a bug by now. I figured by now this is how HubSpot does things. I just hope there will be a logical ordering (or an option for alternative ordering) at some point.

Kind regards,
Luuk van Aggelen