So I think you've gotten this figured out since you posted? But I figure it could be useful to add a response in case other people find this thread running into the same issue. So you've got the module itself added to the blog template, which gives the blog author the ability to edit that module for each post in the blog post editor.
So all of the module data will get stored in a "dict" that can be accessed through HubL. So if you were for example looping through the posts on your listing page with a loop like: {% for content in contents %} , then each post is represented in its loop iteration by the variable "content". The dict for the module data is "widgets". So for each post, you can access its module data by doing another loop like: {% for module in content.widgets %} . Altogether:
{# loop through blog posts #}
{% for content in contents %}
{# loop through a blog post's modules #}
{% for module in content.widgets %}
{% endfor %} {# end for module in content.widgets #}
{% endfor %} {# end for content in contents #}
And then it's just a matter of identifying the module that you're looking for. In my last example I used "module_id": {% if module.module_id == "XXXX" %} . And when you find the module you're looking for, you print the value you need into the HTML.
Let me know if you have other questions here, but it looks like you've already got it figured out.
{% for content in contents %}
<div>
<div class="feature-category">
{% for module_item in content.widgets %}
{# the name of this particular module is "Category" #}
{% if module_item.body.widget_name == "Category" %}
<a href="http://blog.indiewalls.com/test-hubspotsupport/tag/{{module_item.body.category }}">{{module_item.body.category }}</a>
{% endif %}
{% endfor %}
</div>
{% endfor %}
So I think you've gotten this figured out since you posted? But I figure it could be useful to add a response in case other people find this thread running into the same issue. So you've got the module itself added to the blog template, which gives the blog author the ability to edit that module for each post in the blog post editor.
So all of the module data will get stored in a "dict" that can be accessed through HubL. So if you were for example looping through the posts on your listing page with a loop like: {% for content in contents %} , then each post is represented in its loop iteration by the variable "content". The dict for the module data is "widgets". So for each post, you can access its module data by doing another loop like: {% for module in content.widgets %} . Altogether:
{# loop through blog posts #}
{% for content in contents %}
{# loop through a blog post's modules #}
{% for module in content.widgets %}
{% endfor %} {# end for module in content.widgets #}
{% endfor %} {# end for content in contents #}
And then it's just a matter of identifying the module that you're looking for. In my last example I used "module_id": {% if module.module_id == "XXXX" %} . And when you find the module you're looking for, you print the value you need into the HTML.
Let me know if you have other questions here, but it looks like you've already got it figured out.
{% for content in contents %}
<div>
<div class="feature-category">
{% for module_item in content.widgets %}
{# the name of this particular module is "Category" #}
{% if module_item.body.widget_name == "Category" %}
<a href="http://blog.indiewalls.com/test-hubspotsupport/tag/{{module_item.body.category }}">{{module_item.body.category }}</a>
{% endif %}
{% endfor %}
</div>
{% endfor %}