Theme: Fix doubled "Neuigkeiten" on start page, differentiate events from articles more #159

Merged
jtbx merged 3 commits from feat/home-double-news-heading into main 2026-06-13 21:26:39 +02:00
Owner

The start page was displaying two "Neuigkeiten" headings when both an event and an article should have been displayed on the start page at the same time. This looks broken.

With this PR the heading is only displayed once. To be able to distinguish a bit more easily between events and articles, the latter got a "newspaper" icon and have no time in the date any more.
I also increased the time an article is displayed at the front page from roughly 1 day to 5 days (and 6 hours).

The start page was displaying two "Neuigkeiten" headings when both an event and an article should have been displayed on the start page at the same time. This looks broken. With this PR the heading is only displayed once. To be able to distinguish a bit more easily between events and articles, the latter got a "newspaper" icon and have no time in the date any more. I also increased the time an article is displayed at the front page from roughly 1 day to 5 days (and 6 hours).

You can view your changes at https://staging.hamburg.ccc.de/pr159/

You can view your changes at https://staging.hamburg.ccc.de/pr159/
Owner

Looks to me like the two lists are now almost identical with differences only in the $list that goes into the range, and different behaviour in the blog-headers partial, which is already shared.

I think combining $upcoming and $articleNew would not only combine both types into one list, fix the core issue of duplication, but also it would sort events and articles by the same key, currently they are just plainly appended, internally sorted.

Looks to me like the two lists are now almost identical with differences only in the $list that goes into the range, and different behaviour in the blog-headers partial, which is already shared. I think combining $upcoming and $articleNew would not only combine both types into one list, fix the core issue of duplication, but also it would sort events and articles by the same key, currently they are just plainly appended, internally sorted.
Owner

Proposed solution for above comment at feat/home-double-news-heading-2. @jtbx

Proposed solution for above comment at [feat/home-double-news-heading-2](https://git.hamburg.ccc.de/CCCHH/ccchh-website/src/branch/feat/home-double-news-heading-2/themes/ccchh/layouts/index.html). @jtbx
Author
Owner

Schaue ich mir morgen oder spätestens am Wochenende an. Bin gerade gedanklich in meinem anderen Projekt.

Schaue ich mir morgen oder spätestens am Wochenende an. Bin gerade gedanklich in meinem anderen Projekt.
Author
Owner

I think combining $upcoming and $articleNew would not only combine both types into one list, fix the core issue of duplication, but also it would sort events and articles by the same key, currently they are just plainly appended, internally sorted.

You're not 100% correct here: As currently proposed there will be a list of upcoming events sorted by date first and then some articles (also sorted by date). And I kinda like that events are shown before articles since they are more important in my opinion.
When both lists are combined an "old" article may be above the event tomorrow however for example.

I would even reverse the article order so that the newest will be first (since they are all in the past compared to events which are in the future). EDIT: See latest commit (validated it locally and works as intended)

> I think combining $upcoming and $articleNew would not only combine both types into one list, fix the core issue of duplication, but also it would sort events and articles by the same key, currently they are just plainly appended, internally sorted. You're not 100% correct here: As currently proposed there will be a list of upcoming events sorted by date first and then some articles (also sorted by date). And I kinda like that events are shown before articles since they are more important in my opinion. When both lists are combined an "old" article may be above the event tomorrow however for example. I would even reverse the article order so that the newest will be first (since they are all in the past compared to events which are in the future). EDIT: See latest commit (validated it locally and works as intended)
Theme: Reverse article order on start page
All checks were successful
/ build (pull_request) Successful in 42s
d125380563
articles are in the past, so sorting them in descending order will result in the most recent being the first item.
Owner

Does it make sense to remove the date on articles on the home page/the blog index page? That would differentiate them more from event announcements. Also a different background color might be nice. They still look very similar I think.

Does it make sense to remove the date on articles on the home page/the blog index page? That would differentiate them more from event announcements. Also a different background color might be nice. They still look very similar I think.
Merge branch 'main' into feat/home-double-news-heading
All checks were successful
/ build (pull_request) Successful in 42s
56c5e4130a
Author
Owner

Does it make sense to remove the date on articles on the home page/the blog index page

On the home page: Maybe.
On the blog (https://staging.hamburg.ccc.de/pr159/blog/ and https://staging.hamburg.ccc.de/pr159/categories/article/): I thought about it and it looked really weird. And I would definitely like to know the publishing date when going through the pages.

> Does it make sense to remove the date on articles on the home page/the blog index page On the home page: Maybe. On the blog (https://staging.hamburg.ccc.de/pr159/blog/ and https://staging.hamburg.ccc.de/pr159/categories/article/): I thought about it and it looked really weird. And I would definitely like to know the publishing date when going through the pages.
jtbx force-pushed feat/home-double-news-heading from 56c5e4130a
All checks were successful
/ build (pull_request) Successful in 42s
to 3b5e0bec9a
All checks were successful
/ build (pull_request) Successful in 41s
2026-06-13 13:12:00 +02:00
Compare
Owner

I think the date is not really that relevant, as long as we keep posting articles, and I would see it as part of the article page.

I think the date is not really that relevant, as long as we keep posting articles, and I would see it as part of the article page.
jtbx force-pushed feat/home-double-news-heading from 3b5e0bec9a
All checks were successful
/ build (pull_request) Successful in 41s
to 2c642a0a30
All checks were successful
/ build (pull_request) Successful in 41s
2026-06-13 20:01:53 +02:00
Compare
jtbx force-pushed feat/home-double-news-heading from 2c642a0a30
All checks were successful
/ build (pull_request) Successful in 41s
to cf04a87072
All checks were successful
/ build (pull_request) Successful in 41s
2026-06-13 20:23:12 +02:00
Compare
jtbx force-pushed feat/home-double-news-heading from cf04a87072
All checks were successful
/ build (pull_request) Successful in 41s
to 3df895f734
Some checks failed
/ build (pull_request) Successful in 41s
/ cleanup-staging (pull_request) Failing after 2m17s
/ build (push) Failing after 2m29s
2026-06-13 20:47:29 +02:00
Compare
stb approved these changes 2026-06-13 21:18:48 +02:00
stb left a comment

lgtm

lgtm
jtbx merged commit 3df895f734 into main 2026-06-13 21:26:39 +02:00
jtbx deleted branch feat/home-double-news-heading 2026-06-13 21:26:39 +02:00
Sign in to join this conversation.
No reviewers
stb
No milestone
No project
No assignees
4 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
CCCHH/ccchh-website!159
No description provided.