Skip setup questions on the template path and collect name, photo, and description without recommendations.

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.
This commit is contained in:
adilallo committed 2026-11-09 17:34:33 -07:00
1 parent 53d236d0d5
commit 6498d52541
37 files changed
+1450 -733

No files matched your search

+12 -27
View File
@@ -249,34 +249,19 @@ decision-approaches → conflict-management → confirm-stakeholders → final-r
| API detail | `app/api/templates/[slug]/route.ts` (`GET` — §9.4) |
| API catalog | `app/api/create-flow/methods/route.ts` (`GET` — §9.2); `lib/server/governanceCatalog.ts` |
**Marketing UIs** may omit `facet.*` (curated ordering only). When facets
are passed, templates are ranked and `scores` may be returned. Template **Customize**
now prefills the custom-rule flow via
[`buildTemplateCustomizePrefill`](../../lib/create/applyTemplatePrefill.ts)
(applied in `CreateFlowLayoutClient.tsx`) and routes to `core-values`
when Community already has input, else to `informational`. Template **Use
without changes** writes `template.body.sections` into `state.sections`.
Direct catalog / marketing entry routes to `community-name` and Next/Back
collect only name, description, and optional photo, then
`confirm-stakeholders`. A leftover draft title does not skip those
identity steps. In-flow (`?fromFlow=1` after the community questionnaire)
skips identity and opens `confirm-stakeholders`. The user
exits via the normal
`final-review → handleFinalize → publishRule` path and picks up the
server-enforced 401 sign-in gate for free.
When the user picks a template **before** completing the community
stage, both handlers still apply their side effects eagerly (prefill or
`sections`/`summary`) and pin a
**Marketing UIs** omit `facet.*`. Templates carry no recommendation; the
grid is curated order with no RECOMMENDED tag. Seeded facet marks remain
in the database unused. Template **Customize** opens a name / photo /
description dialog, prefills cards via
[`buildTemplateCustomizePrefill`](../../lib/create/applyTemplatePrefill.ts),
and routes to `core-values` (setup questions skipped). Template **Use
without changes** writes the template’s cards and routes to
`final-review`. Identity is collected in the dialog or on the
final-review Rule card. The pin
`pendingTemplateAction: { slug, mode: "customize" | "useWithoutChanges" }`
on `CreateFlowState`. Customize then routes to `informational`. Direct
Use without changes routes to `community-name` (identity-only skip list
while the pin is set). Once the user reaches `/create/review`, `CommunityReviewScreen`
consumes the pin and `router.replace`s past itself — to `core-values` for
`customize`, to `community-name` for `useWithoutChanges`. The
community-review screen is therefore only shown when the user came from
"Create Custom" (no template), matching the intent already expressed at the
template-review step.
stays for the rest of the wizard so decks skip the engine. See
[`docs/create-flow.md`](../create-flow.md). The user exits via
`final-review → handleFinalize → publishRule`.
---