Pablo Iranzo Gómez

I've tried manually applyng the change on my deployment: ~~~diff diff --git a/themes/elegant/templates/article.html b/themes/elegant/templates/article.html index 7b63b8eb..146e2f84 100644 --- a/themes/elegant/templates/article.html +++ b/themes/elegant/templates/article.html @@ -95,7 +95,7 @@ {% for tag in article.tags|sort...

At least it doesn't break anything, so it might make sense to implement something like this ahead of the commits they mention on pelican

Perhaps pelican has been optimized, but still should be relevant to use the new approach even if there's some seconds in difference

> Any progress here? Not that I'm aware, if you think that this can be fixed, feel free to submit a PR so that we can get it merged ASAP...

@silverhook what do you miss in configuration to cover this?

I think that archives, categories, etc are more related to pelican itself. But yes, I recall that there was a setting related with tipue (but can't recall what was) Thanks!

I was thinking about: - custom head - custom footer - custom body With those defined in variable, and pointing to an existing file, source that file as a jinja...

Yes, for some point yes, but for a 'stats' scripts we don't support you want on headers, let's say for example adobe analytics, or if you want a custom footer...

https://github.com/Pelican-Elegant/elegant/pull/439 is related with this, but using the 'add new feature' approach

Can you point me towards the place where the '1 row' is made? I would like to have a look at it to think a bit