www/www-from-model
10
0
Fork 0
Code Issues 6 Pull requests Activity Actions

remove boilerplate 'recent' overview #19

Merged
jsheunis merged 2 commits from config-recent into main 2026-04-22 12:24:03 +00:00
Conversation 4 Commits 2 Files changed 3 +9 -3
adina commented 2026-04-20 08:21:56 +00:00
Member
Copy link

The 'Recent' section would show the content/samples files,
pointing to documentation and other boilerplate content.
I've replaced this config according to
https://jpanther.github.io/congo/docs/homepage-layout/#recent-articles.

I've also adjusted the description to something non-hugo related (the
first sentence of the current website) as an interim improved
description

The 'Recent' section would show the content/samples files, pointing to documentation and other boilerplate content. I've replaced this config according to https://jpanther.github.io/congo/docs/homepage-layout/#recent-articles. I've also adjusted the description to something non-hugo related (the first sentence of the current website) as an interim improved description
The 'Recent' section would show the content/samples files,
pointing to documentation and other boilerplate content.
I've replaced this config according to
https://jpanther.github.io/congo/docs/homepage-layout/#recent-articles.

I've also adjusted the description to something non-hugo related (the
first sentence of the current website) as an interim improved
description
msz requested changes 2026-04-20 16:53:36 +00:00
msz left a comment
Member
Copy link

As far as removing boilerplate goes, it's a definite yes.

But, given that we want the index page to be a project page, I would personally go as far as removing the "recent" overview altogether (homepage.showRecent = false in params.toml). It's my opinion though.

If we want to keep the "recent" feature the way you suggest, then we would need one more change in our current setup. Congo theme uses the mainSections config value in its recent-articles.html partial, where it loops over this: (where .Site.RegularPages "Type" "in" .Site.Params.mainSections). However, because of our taxonomy (ab)use, our projects are not regular pages, they are term pages. So we would need to override (copy) that partial to use something else (.Pages, possibly excluding something). Or rethink using taxonomies, but again, that's probably just me.

As far as removing boilerplate goes, it's a definite yes. But, given that we want the index page to be a project page, I would personally go as far as removing the "recent" overview altogether (`homepage.showRecent = false` in `params.toml`). It's my opinion though. If we want to keep the "recent" feature the way you suggest, then we would need one more change in our current setup. Congo theme uses the `mainSections` config value in its `recent-articles.html` partial, where it loops over this: `(where .Site.RegularPages "Type" "in" .Site.Params.mainSections)`. However, because of our taxonomy (ab)use, our projects are not [regular pages](https://gohugo.io/quick-reference/glossary/#regular-page), they are term pages. So we would need to override (copy) that partial to use something else (`.Pages`, possibly excluding something). Or rethink using taxonomies, but again, that's probably just me.
config/_default/languages.en.toml Outdated
@ -11,3 +11,2 @@
mainSections = ["samples"]
description = "A powerful, lightweight theme for Hugo built with Tailwind CSS."
mainSections = [["posts", "projects"]]
msz commented 2026-04-20 16:18:09 +00:00
Member
Copy link

I think this should be an array of strings, ie. only single brackets would work: ["posts", "projects"].

I think this should be an array of strings, ie. only single brackets would work: `["posts", "projects"]`.
adina commented 2026-04-21 10:41:28 +00:00
Author
Member
Copy link

ah damn, thanks for catching that! I've force-pushed a fix for this, though I'm unsure whether that is actually needed given your explanation about the taxonomy pages

ah damn, thanks for catching that! I've force-pushed a fix for this, though I'm unsure whether that is actually needed given your explanation about the taxonomy pages
msz commented 2026-04-21 11:28:49 +00:00
Member
Copy link

Thanks - this was needed because the "recent" section would not show any pages regardless of other reasons. With the fix it still doesn't show any pages, now because of the term vs regular page, but that can be solved by copying the recent-articles partial from the theme and changing the where expression.

Thanks - this was needed because the "recent" section would not show any pages regardless of other reasons. With the fix it still doesn't show any pages, now because of the term vs regular page, but that can be solved by copying the recent-articles partial from the theme and changing the `where` expression.
👍 1
adina commented 2026-04-21 12:58:43 +00:00
Author
Member
Copy link

thanks - I've done this in 7da390d7c7. At its current state, this looks like this:

image

Visually, I don't find it as nice as the regular sites (with a summary, image, and date tag)

image

I tried a while whether I could make images and summaries appear for term pages (e.g., I listed persons under 'recent', which at least have an image), but it certainly does not work out of the box, and I failed to tweak the layout enough with my weak partial-foo to bend it into shape.

image

After this brief exploration, I would echo your earlier remark whether it is even worth keeping the recent section at all. I would now argue against it, and if you agree, I'll simply disable it.

thanks - I've done this in 7da390d7c753dfc4100a88ec836e292a426defce. At its current state, this looks like this: ![image](/attachments/287e941f-713e-47ac-b9f4-17b059673928) Visually, I don't find it as nice as the regular sites (with a summary, image, and date tag) ![image](/attachments/f2fc2e3f-4990-428d-9dd8-7417bd66f90d) I tried a while whether I could make images and summaries appear for term pages (e.g., I listed persons under 'recent', which at least have an image), but it certainly does not work out of the box, and I failed to tweak the layout enough with my weak partial-foo to bend it into shape. ![image](/attachments/332b3ba4-6494-4785-b348-fac69ee348ac) After this brief exploration, I would echo your earlier remark whether it is even worth keeping the recent section at all. I would now argue against it, and if you agree, I'll simply disable it.
image.png
84 KiB
image.png
331 KiB
image.png
12 KiB
msz commented 2026-04-21 14:49:41 +00:00
Member
Copy link

Thanks for the visual samples!

I agree that we won't get it for free out of the box - we would need to customize a cascade of partials starting with article-link (by cascade I mean that one and some of those it includes). Which we might end up doing anyway at some point, because the same partial is used in other pages to show what we might call related content.

I had a look around the theme's partials; people's portraits don't show because the theme's article-link partial looks for *thumb* in page resources while we use "portrait"; the cloud of labels are all terms shown by article-meta partial (ie. theme's default taxonomy-related behavior); dates would probably show if we had them in those pages; summary is controlled by the showSummary param which can be set site-wide (we have it at false) or set for each page (taking precedence, we're currently not setting it). I'm not sure what exactly is used for the summary, not all of our pages have a nice text content at the beginning.

This goes to say: we could, if we wanted to, customize this to look "nice", and I could even see myself working on it. I know our current approach is to show changes once done rather than discuss them upfront, but without full confidence I wanted to outline the possible approach rather than implement it.

As far as the PR goes, I'm still not sure about the recent section, but it can be refined so if you decide to keep it I won't block it.

Thanks for the visual samples! I agree that we won't get it for free out of the box - we would need to customize a cascade of partials starting with article-link (by cascade I mean that one and some of those it includes). Which we might end up doing anyway at some point, because the same partial is used in other pages to show what we might call related content. I had a look around the theme's partials; people's portraits don't show because the theme's article-link partial looks for `*thumb*` in page resources while we use "portrait"; the cloud of labels are all terms shown by article-meta partial (ie. theme's default taxonomy-related behavior); dates would probably show if we had them in those pages; summary is controlled by the `showSummary` param which can be set site-wide (we have it at false) or set for each page (taking precedence, we're currently not setting it). I'm not sure what exactly is used for the summary, not all of our pages have a nice text content at the beginning. This goes to say: we could, if we wanted to, customize this to look "nice", and I could even see myself working on it. I know our current approach is to show changes once done rather than discuss them upfront, but without full confidence I wanted to outline the possible approach rather than implement it. As far as the PR goes, I'm still not sure about the recent section, but it can be refined so if you decide to keep it I won't block it.
adina force-pushed config-recent from e0cbd1730d to d10f023138 2026-04-21 10:39:52 +00:00 Compare 
thanks to @msz for idea and execution steps.
This commit takes the existing recent-articles.html partial
from themes/congo/layout/partials and copies it to override
the theme partial. Instead of listing 'Site.RegularPages' that
match the configured content in the 'mainSections'
configuration, it takes the more general Site.Pages, which
would allow listing Term Pages (see
https://gohugo.io/quick-reference/glossary/#term-page).
msz reviewed 2026-04-21 15:36:24 +00:00
msz left a comment
Member
Copy link

As discussed in the comments, this can be merged and the presentation of "recent" improved further in the future, or the recent section can be turned off altogether. I'm commenting just to dismiss the "changes requested" status (TIL there is an option to dismiss reviews, but one has to be repo admin) - edit: which didn't work but let's leave it at verbal confirmation.

As discussed in the comments, this can be merged and the presentation of "recent" improved further in the future, or the recent section can be turned off altogether. I'm commenting just to dismiss the "changes requested" status (TIL there is an option to dismiss reviews, but one has to be repo admin) - edit: which didn't work but let's leave it at verbal confirmation.
adina requested review from msz 2026-04-21 18:09:35 +00:00
adina commented 2026-04-21 18:11:03 +00:00
Author
Member
Copy link

Ha, and I can only re-request a review. Unsure if that makes it possible. I'll leave it open until tomorrow in case someone else has an opinion on turning recent off entirely or just removing the samples.

Ha, and I can only re-request a review. Unsure if that makes it possible. I'll leave it open until tomorrow in case someone else has an opinion on turning recent off entirely or just removing the samples.
adina force-pushed config-recent from 7da390d7c7 to f3267c5a06 2026-04-22 09:29:34 +00:00 Compare
adina commented 2026-04-22 09:30:27 +00:00
Author
Member
Copy link

I've kept the commit with the layout changes for now in case it becomes useful at a later stage, but I've disabled the "Recent" display at its current stage. 👍

I've kept the commit with the layout changes for now in case it becomes useful at a later stage, but I've disabled the "Recent" display at its current stage. 👍
Sign in to join this conversation.
Reviewers
No reviewers
msz
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
www/www-from-model!19
No description provided.