✨ feat: support using info-page.html for sections

[wischi-chr]

Summary

This change makes it possible to use the info-page.html template on the root path ("/"), which in zola is always a "section" and can't be set to "page".

The related issue(s) is/are actually in zola and not really in tabi. It's a known limitation in zola that the root path has to be a section and can't be a page (see linked issues later). Because of that templates designed for pages typically can't be used for sections (and thus not as a root path "/" landing page).

Thankfully in tabi a lot of things are already pretty agnostic between sections and pages, so it only needed some minor tweaks to make the template work at the root level.

Related issues

As said before, not really a tabi issue, but here are related zola issues and discussions:

• REQUEST: Support specifying a custom landing page/homepage getzola/zola#2334
• Have root being a page and not a section getzola/zola#2553
• Can't build website when there's an index.md file in level 1 directory in content getzola/zola#2101
• Error with index.md at root of site (content/) getzola/zola#1119
• https://zola.discourse.group/t/page-content-not-available-in-content-root/534

Slightly related (but very old / fixed / obsolete)

• Need a way to treat a subdirectory as a new section, while rendering its index as a page getzola/zola#836
• Creating the root index.html as a regular page getzola/zola#99

Changes

extra-features.html

Before this change, this partial failed to render for sections, because it called the macro evaluate_setting_priority with the section as page parameter which caused the line {%- for i in range(start=1, end=components | length) -%} to fail, because start (1) was larger than the end (0) parameter.

It looked to me like the section parameter was added later to evaluate_setting_priority (because it has a default value and the parameter documentation is missing) so I made a change in extra-features.html to pass page and section separately if they are set (or "" if they are not set).

info-page.html

I updated the info-page.html to also support both pages and sections.

Screenshots

Type of change

• Bug fix (fixes an issue without altering functionality)
• New feature (adds non-breaking functionality)
• Breaking change (alters existing functionality)
  • Changes in extra-features.html should be backwards compatible, but I'm not 100% sure.
• UI/UX improvement (enhances user interface without altering functionality)
• Refactor (improves code quality without altering functionality)
• Documentation update
• Other (please describe below)

---

Checklist

• I have verified the accessibility of my changes
• I have tested all possible scenarios for this change
  • I don't think that's possible without manually checking all sites that use tabi 😄
• I have updated theme.toml with a sane default for the feature
• I have updated config.toml in tabi-start
• I have made corresponding changes to the documentation:
  • Updated config.toml comments
  • Updated theme.toml comments
  • Updated "Mastering tabi" post in English
  • (Optional) Updated "Mastering tabi" post in Spanish
  • (Optional) Updated "Mastering tabi" post in Catalan

[netlify]

✅ Deploy Preview for tabi-demo ready!

Name	Link
🔨 Latest commit	67c5d33
🔍 Latest deploy log	https://app.netlify.com/sites/tabi-demo/deploys/6776f5714c1c9800088b0511
😎 Deploy Preview	https://deploy-preview-455--tabi-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[welpo]

Thank you!

I tested using info-page.html for the main _index.md + the hierarchy with normal posts and series, and everything looks good.