feat(news): newest-first ordering, 5-per-page pagination, community-discussions window (#73) - #75
Merged
Merged
Conversation
…s window Closes #73. The announcements feed rendered oldest-first (REST creation order, never sorted) — every feed now sorts descending at the fetch layer, and the announcements cap rises 10 -> 30 so the archive has room. News paginates at five per static page: /{locale}/news/ plus /news/2/… with per-page canonical + hreflang parity, prev/next arrows and numbered links; the subscribe form, Show and tell, and the new community section render on page 1 only — archive pages are pure list. The community window answers 'why isn't #472 on the site': News read only Announcements (+ Show and tell), and #472 lives in Compliance & classification. Rather than flooding the archive with support threads, a third section shows the five newest discussions from every other category — original language only (D4/D5), deep links to GitHub — so the community's voice (including #472) is visible without changing what Announcements means.
…s, delete button, composer deep link Closes #74. Replaces the #69 how-to-post wording with the maintainer's actual hand-holding reply from keel#472 — the one that converted a self-described non-technical reader into a first post: 'curious-reader, gardenshed99, anything'; 'nothing about it looks odd'; 'If you post and hate it, there's a delete button'; the four-step signup walkthrough with the compliance-classification composer deep link ('no navigating, no hunting for the right place'). Email privacy is stated as fact — GitHub never displays the address on discussions, so the copy says so without inventing a settings step. EN/AR/FR, revs bumped.
|
Contributor
Author
|
Correction for the record (independent review caught this): the PR body claims the Show and tell section renders on page 1 only — it is not gated by |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #73
Closes #74
#73 — News ordering, pagination, community window: feed sorted descending at the fetch layer (was oldest-first), announcements cap 10→30, static pagination at 5/page (/{locale}/news/, /news/2/, /news/3/…) with per-page canonical + hreflang parity, prev/next + numbered links; subscribe form, Show and tell, and the new From the community discussions section render on page 1 only. The community window shows the five newest threads from every category except announcements/show-and-tell — original language only — which is why #472 now appears without flooding the archive with support threads.
#74 — How-to copy in the voice that worked: the community page's how-to-post card now carries the maintainer's actual reply wording from keel#472 (usernames like curious-reader/gardenshed99, 'nothing about it looks odd', the delete button, the composer deep link, 'no navigating, no hunting'). EN/AR/FR.
Verified: newest-first on all locales (2026-08-21 leads), 5 items/page, pager links, per-page canonicals, #472 visible in the community section, new copy rendering in all three locales at 390px with zero overflow, astro check + build clean.