Inject a {taxon}_{type}_index_permalinks for every type of taxonomy index created #197
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This replaces #192. I think this is a simpler approach and results in less code needing to be written.
Usage would be either:
{% if page.tags %} <p class="tags">Tagged with {% for tag in page.tags %} <a class="tag" href="{{ site.url }}/{{ page.tag_html_index_permalinks[tag] }}">{{ tag }}</a>{% if not loop.last %}, {% endif %} {% endfor %} </p> {% endif %}... or
{% if page.tags %} <p class="tags">Tagged with {% for tag,permalink in page.tag_html_index_permalinks %} <a class="tag" href="{{ site.url }}/{{ permalink }}">{{ tag }}</a>{% if not loop.last %}, {% endif %} {% endfor %} </p> {% endif %}Either would work.
The nice things over #192 are that 1) it only creates these for taxonomies for which an index page even exists and 2) it accounts for the fact that you might have several index pages (like an Atom/RSS feed vs an HTML one). It also does not mess with anything that would require changes to the config / extension meta programming stuff and we do not have to find a way to extract the URL building stuff.
ping @WyriHaximus