Add partial decorators for better composability

[agriyakhetarpal]

This PR introduces partial decorators, a new feature in Hugo released with v0.154.0: https://github.com/gohugoio/hugo/releases/tag/v0.154.0. This will not be a user-facing change. The documentation is at https://gohugo.io/functions/templates/inner/ and is currently a bit sparse, but still understandable. From the docs: I have bumped to Hugo v0.154.5 v0.157.0 with this PR.

A partial decorator is a partial template called from any other template including shortcodes, render hooks, and other partials.

There are some more examples here: gohugoio/hugoDocs#3330.

I also tried to add something to deduplicate the grid of items and cards, but that turned out to be more complicated – the content inside needs access to outer variables such as $card and .body. I think we can go ahead with this, for now at least, since it's a net win for easy deduplication either way, and we can do this kind of work incrementally.

[netlify]

✅ Deploy Preview for scientific-python-hugo-theme ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	76a3d1c
🔍 Latest deploy log	https://app.netlify.com/projects/scientific-python-hugo-theme/deploys/69ec1d4972ad2b0008e83c45
😎 Deploy Preview	https://deploy-preview-692--scientific-python-hugo-theme.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 94 Accessibility: 97 Best Practices: 100 SEO: 91 PWA: - View the detailed breakdown and full score reports

---

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

[stefanv]

I like the direction this is taking 👍

[stefanv]

Also, it's neat that Hugo finally added that feature!

[stefanv]

5:55:50 PM: ERROR error building site: render: [en v1.0.0 guest] failed to render pages: render of "/opt/build/repo/blog/content/posts/community-stories/will_tirone/index.md" failed: "/opt/build/scientific-python-hugo-theme/layouts/posts/single.html:2:3": execute of template failed: template: posts/single.html:2:3: executing "main" at <partial "posts/post.html" .>: error calling partial: "/opt/build/scientific-python-hugo-theme/layouts/partials/posts/post.html:3:10": execute of template failed: template: _partials/posts/post.html:3:10: executing "_partials/posts/post.html" at <partial "_decorators/content-container.html" .>: error calling partial: "/opt/build/scientific-python-hugo-theme/layouts/partials/_decorators/content-container.html:7:6": execute of template failed: template: _partials/_decorators/content-container.html:7:6: executing "_partials/_decorators/content-container.html" at <inner .>: error calling inner: template: _partials/posts/post.html:6:14: executing "_partials/_internal/decorator_8e9d3f7b5767b258" at <$featuredImage>: undefined variable: $featuredImage

[agriyakhetarpal]

Restarting CI to see why Netlify is stuck

Edit: I'm just going to assume it is down, but will mark this as ready for review anyway.

[stefanv]

Needs Authors update

[agriyakhetarpal]

The atom feed template uses site.Author, which was deprecated in Hugo v0.124: gohugoio/hugo#12269, and removed in later versions. I bumped to Hugo 0.158.0 in the last few commits, so we're probably too new. I don't think we should downgrade the Hugo version, ever. I'll override this for now in our layouts, but since this has been raised: why do we need hugo-atom-feed anyway? Personally, I don't mind RSS feeds, and it looks like https://github.com/kaushalmodi/hugo-atom-feed hasn't received much activity either. So if we want to keep it, we should fork it into scientific-python and maintain it for a while (which I have no qualms doing).

[agriyakhetarpal]

We can switch to yelosan/hugo-feeds on Codeberg. It looks like it's a bit better maintained (but still not maintained well enough, though). See yelosan/hugo-feeds (GitHub mirror) too.

Another one I found is https://github.com/hugo-fixit/hugo-atom-feed, which last worked with Hugo v0.146.7.

Honestly, I'm tempted to drop it, but reading #489 and #497, I see that we did have a fork of this subtheme in the past.

[stefanv]

How about we submit a patch first and see if it gets accepted?

[stefanv]

(We can merge, using a fork of our own for now.)