You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing some accessibility linting tools for #396, I noticed that sitemap.xml contains lots of url pointing to the default zola html for non-rendered section/page (see here for example).
It seems this is due to how the generate_* tooling generates the content, as we end up with lots of markdown files that actually do not correspond to a section/page in content (they are used to build lists like here instead).
A possible solution that I tested would be to add render = false to the generated sections front matter, and manually exclude the generated pages from the sitemap. There is no equivalent to render = false for pages, so this need to be done with an extra attribute and a custom sitemap template, but this does not completely solves the problem as the invalid html is still built. The simplest way to fix that would probably to have the render attribute be implemented by Zola for pages, otherwise we would need to change how list pages are generated to avoid going through some intermediate markdown.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
While testing some accessibility linting tools for #396, I noticed that
sitemap.xml
contains lots of url pointing to the default zola html for non-rendered section/page (see here for example).It seems this is due to how the
generate_*
tooling generates the content, as we end up with lots of markdown files that actually do not correspond to a section/page incontent
(they are used to build lists like here instead).A possible solution that I tested would be to add
render = false
to the generated sections front matter, and manually exclude the generated pages from the sitemap. There is no equivalent torender = false
for pages, so this need to be done with an extra attribute and a custom sitemap template, but this does not completely solves the problem as the invalid html is still built. The simplest way to fix that would probably to have therender
attribute be implemented by Zola for pages, otherwise we would need to change how list pages are generated to avoid going through some intermediate markdown.The text was updated successfully, but these errors were encountered: