feat(community): plain-language how-to-post section for readers without a GitHub account - #69
Merged
Merged
Conversation
…ut a GitHub account The community page said where the conversation happens but not how to join it. Discussion #472 showed the gap: a first-time, non-technical participant only got in because the whole process was walked through by email. Adds a 'New here? How to post' card above the category list — account required (reading open), real name not required and email never shown, it is just a web page with a comment box — plus a four-step signup walkthrough and one sentence of category guidance (compliance/classification questions belong in Compliance & classification, not Q&A; wrong picks get moved). Each open category card now also deep-links to the composer with its category preselected (discussions/new?category=<slug>); Announcements gets no composer link because that category is maintainers-only. Copy in EN, AR and FR; rev and translatedFromRev bumped to 2026-08-21.1 per convention. The site still only reads and links — this explains how to reach the place where interaction happens. Closes #48
|
3 tasks
eaitbrahim
added a commit
that referenced
this pull request
Aug 22, 2026
…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.
eaitbrahim
added a commit
that referenced
this pull request
Aug 22, 2026
…iscussions window (#73) (#75) * feat(news): newest-first, 5-per-page pagination, community-discussions 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. * feat(community): how-to copy in the voice that worked — real usernames, 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.
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.
What
Closes #48.
The community page told readers where the conversation happens, never how to join it. Discussion #472 only happened because the whole signup path was walked through over email. This adds the sentences that unblock it, directly on the page.
Changes
src/components/pages/CommunityPage.astro+ copy insrc/i18n/pages/community.ts), following the issue's sketch at its length:Start a discussion →) todiscussions/new?category=<slug>, keeping the existing browse link. Announcements gets none — that category is maintainers-only (verified via the GraphQL API: only maintainers have ever opened one), and a link ending in a permission wall would not be honest.revandtranslatedFromRevbumped to2026-08-21.1per convention — no stale banner in any locale.Scope guard
The site still only reads and links. This explains how to reach the place where interaction happens; it adds no interaction here. Changes are limited to
CommunityPage.astroandcommunity.ts(plus a small scoped style block reusing the.cardpattern).Verification
npx astro check— 0 errors (1 pre-existing hint inscripts/render-tui-shots.mjs).npm run build— 44 pages, clean.dist/{en,ar,fr}/community/index.htmleach contain: the how-to card (3 facts, 4 steps), thegithub.com/signuplink, 6 composer deep links, and nostale-banner.github.com/signupresolves;…/discussions/new?category=compliance-classificationopens the composer preselected (issue author confirmed 2026-08-21; slugs re-confirmed against the repo's categories via the GraphQL API).Closes #48