Source homepage Project descriptions from each repository's canonical copy #130

New issue

Open

opened 2026-08-27 03:25:09 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-27 03:25:09 +00:00

Collaborator

Outcome

Every description beneath a homepage Project card comes from the project's own canonical repository copy, rather than an agent-written paraphrase.

Why

The existing card descriptions match the intended editorial style, but they were free-handed. That loses Kai's voice and can make a card subtly inaccurate even when it reads well. The website should surface the project's own words.

Source rule

For each project card, take the description from the first available source in this order:

The repository README's opening description or About section.
The repository description.
A project-owned overview document explicitly designated as canonical.

Keep the selected copy verbatim apart from purely mechanical presentation changes such as whitespace. Do not combine sentences from several sources or invent connective copy. If no suitable canonical text exists, leave the card without a description and record the missing source as follow-up work.

Store the selected source location alongside the website data so a later edit can be traced and refreshed without rediscovering the decision.

Acceptance

Every homepage Project card's beneath-banner description points to a specific canonical source in that project's repository.
No card description is agent-authored marketing or a stitched paraphrase.
The visible copy remains concise and follows the existing card layout.
A change to a source repository can be audited against the website's recorded source location.

## Outcome Every description beneath a homepage Project card comes from the project's own canonical repository copy, rather than an agent-written paraphrase. ## Why The existing card descriptions match the intended editorial style, but they were free-handed. That loses Kai's voice and can make a card subtly inaccurate even when it reads well. The website should surface the project's own words. ## Source rule For each project card, take the description from the first available source in this order: 1. The repository README's opening description or About section. 2. The repository description. 3. A project-owned overview document explicitly designated as canonical. Keep the selected copy verbatim apart from purely mechanical presentation changes such as whitespace. Do not combine sentences from several sources or invent connective copy. If no suitable canonical text exists, leave the card without a description and record the missing source as follow-up work. Store the selected source location alongside the website data so a later edit can be traced and refreshed without rediscovering the decision. ## Acceptance - Every homepage Project card's beneath-banner description points to a specific canonical source in that project's repository. - No card description is agent-authored marketing or a stitched paraphrase. - The visible copy remains concise and follows the existing card layout. - A change to a source repository can be audited against the website's recorded source location.

No milestone

No project

No assignees

1 participant

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

coilysiren/website#130

No description provided.

Rows
Columns