A group that starts from a template now enters only its name, photo, and description. Size, kind, scale, maturity, and the setup questions are skipped, and this path never calls the recommendation engine.
Customize opens a dialog, then walks the template’s values and decks with those cards first. Use without changes skips the dialog and decks and lands on final review, where the Rule card collects the same identity fields. A saved template draft that reopens on a skipped community step is sent back to values (Customize) or final review (Use without changes).
Changes
Customize dialog collects community name (required), optional logo, description, and optional city or region, then prefills the template’s cards and catalog copy.
Use without changes goes straight to final review. The Rule card uses Has Name Field: dashed logo control, required Community name, optional “What does your community do?”, and Continue stays off until there is a name.
Template decks show the template’s cards first, then the rest of the deck. No Recommended tag, no “Every Rule has”, no seven-card cut, and the engine is not called. Final-review + Add still opens the matching deck or values; Confirm returns to final review.
Back from Customize final review goes to the conflict deck. Back from Use without changes final review goes to template detail.
Templates catalog and template cards no longer show a Recommended tag. Facet scoring for those grids is unused; seedTemplateFacets data is left in place.
A template-path draft that reopens on a community setup URL is redirected so it never shows those screens.
Screenshots
How to Test
docker compose up -d postgres, npx prisma migrate dev, npx prisma db seed, npm run dev.
Open /templates. Confirm the cards have no Recommended tag and stay in curated order.
Open Consensus (or any template). Confirm Customize and Use without changes in the footer.
Customize: fill a name (and optionally a description), Continue. You should land on values with the template’s values selected, then communication → membership → decisions → conflict → named final review. Confirm the template cards are first on each deck, with no Recommended tag. Back from named final review should return to conflict. + Add on a section should open that deck; Confirm should return to final review.
Use without changes: from template detail, skip the dialog and land on final review with the template’s cards, empty Community name, optional description, and Continue disabled. Enter a name and confirm Continue enables. Back should return to template detail, not the decks.
Confirm you never see size, kind, scale, maturity, or the six setup questions on either path.
Reload a Customize draft on /create/setup-questions (or another skipped step) and confirm it bounces to values; the same for Use without changes should bounce to final review.
Notes
seedTemplateFacets and GET /api/templates?facet.* ranking are still in the repo; the template grids no longer use them for a Recommended tag.
Supermajority share is already three quarters in code; this path does not add a share control on final review.
## Overview
A group that starts from a template now enters only its name, photo, and description. Size, kind, scale, maturity, and the setup questions are skipped, and this path never calls the recommendation engine.
Customize opens a dialog, then walks the template’s values and decks with those cards first. Use without changes skips the dialog and decks and lands on final review, where the Rule card collects the same identity fields. A saved template draft that reopens on a skipped community step is sent back to values (Customize) or final review (Use without changes).
## Changes
- Customize dialog collects community name (required), optional logo, description, and optional city or region, then prefills the template’s cards and catalog copy.
- Use without changes goes straight to final review. The Rule card uses Has Name Field: dashed logo control, required Community name, optional “What does your community do?”, and Continue stays off until there is a name.
- Template decks show the template’s cards first, then the rest of the deck. No Recommended tag, no “Every Rule has”, no seven-card cut, and the engine is not called. Final-review + Add still opens the matching deck or values; Confirm returns to final review.
- Back from Customize final review goes to the conflict deck. Back from Use without changes final review goes to template detail.
- Templates catalog and template cards no longer show a Recommended tag. Facet scoring for those grids is unused; `seedTemplateFacets` data is left in place.
- A template-path draft that reopens on a community setup URL is redirected so it never shows those screens.
## Screenshots

## How to Test
1. `docker compose up -d postgres`, `npx prisma migrate dev`, `npx prisma db seed`, `npm run dev`.
2. Open `/templates`. Confirm the cards have no Recommended tag and stay in curated order.
3. Open Consensus (or any template). Confirm Customize and Use without changes in the footer.
4. **Customize:** fill a name (and optionally a description), Continue. You should land on values with the template’s values selected, then communication → membership → decisions → conflict → named final review. Confirm the template cards are first on each deck, with no Recommended tag. Back from named final review should return to conflict. + Add on a section should open that deck; Confirm should return to final review.
5. **Use without changes:** from template detail, skip the dialog and land on final review with the template’s cards, empty Community name, optional description, and Continue disabled. Enter a name and confirm Continue enables. Back should return to template detail, not the decks.
6. Confirm you never see size, kind, scale, maturity, or the six setup questions on either path.
7. Reload a Customize draft on `/create/setup-questions` (or another skipped step) and confirm it bounces to values; the same for Use without changes should bounce to final review.
## Notes
- `seedTemplateFacets` and `GET /api/templates?facet.*` ranking are still in the repo; the template grids no longer use them for a Recommended tag.
- Supermajority share is already three quarters in code; this path does not add a share control on final review.
Customize opens a dialog then walks the template decks; Use without changes lands on final review with Has Name Field. Template cards stay first, the engine is not called, and the catalog no longer shows a recommended tag.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Overview
A group that starts from a template now enters only its name, photo, and description. Size, kind, scale, maturity, and the setup questions are skipped, and this path never calls the recommendation engine.
Customize opens a dialog, then walks the template’s values and decks with those cards first. Use without changes skips the dialog and decks and lands on final review, where the Rule card collects the same identity fields. A saved template draft that reopens on a skipped community step is sent back to values (Customize) or final review (Use without changes).
Changes
seedTemplateFacetsdata is left in place.Screenshots
How to Test
docker compose up -d postgres,npx prisma migrate dev,npx prisma db seed,npm run dev./templates. Confirm the cards have no Recommended tag and stay in curated order./create/setup-questions(or another skipped step) and confirm it bounces to values; the same for Use without changes should bounce to final review.Notes
seedTemplateFacetsandGET /api/templates?facet.*ranking are still in the repo; the template grids no longer use them for a Recommended tag.