clausmullie
commented
11 months ago I've dug a bit into this, and perhaps a way to do it would be: 1) include front matter tags on all activity indices, like
---
type: activity index
title: title-of-activity
---2) Pull them up in the activities index
{% assign activity = site.activities | where:"type", "activity index" %}3) Output them as a list (note - I'm not sure this pathing works)
<ul>
{% for activity in site.activities %}
<li><a href="{{ activity.url | relative_url }}">{{ activity.title }}</a></li>
{% endfor %}
</ul>However - I am wondering whether this a useful change. There is still the risk of human error, as if someone forgets the front matter, it won't render into the list.
So it will add some complexity and make the markdown harder to read, without necessarily reducing the risk of error.
ericherman
On https://about.publiccode.net/activities/ we list all our activities. In order to not miss any, perhaps we could add something to the front matter of an activity that identifies it as such so that we could generate the list automatically when we build. That way, there is one less thing to think of when adding or removing activities.