jfraeys/coaching-site
Watch
1
0
Fork
You've already forked coaching-site
 0
Code Issues 10 Pull requests 3 Projects Releases Packages Wiki Activity Actions

Define consultation/feature-fit intake process (no design editor) #3

New issue
Open
opened 2026-10-15 23:52:13 -04:00 by jfraeys · 0 comments
jfraeys commented 2026-10-15 23:52:13 -04:00
Owner
Copy link

Define a consultation/intake process to understand a client's needs and add/remove features to fit, without offering a design editor (explicitly out of scope).

The underlying mechanism to turn features on/off per deployment already exists:

  • data/features.yaml — per-deployment feature flags (booking/newsletter/blog, default on).
  • client/ overlay mounts — per-client design via tokens.client.css, plus layout/data overrides.

What's missing is the process side, not the code side:

  • What to ask a prospective client during consultation to determine which features/flags they need.
  • How those answers map to a concrete checklist of flags to flip and overlays to create for a new site.
  • Whether any gaps exist in today's flag set (features a client might reasonably ask to drop/add that features.yaml doesn't yet cover).

Deliverable is likely a short internal doc/checklist plus any small gaps found in the flag set, not a new subsystem.

Define a consultation/intake process to understand a client's needs and add/remove features to fit, without offering a design editor (explicitly out of scope). The underlying mechanism to turn features on/off per deployment already exists: - `data/features.yaml` — per-deployment feature flags (booking/newsletter/blog, default on). - `client/` overlay mounts — per-client design via `tokens.client.css`, plus layout/data overrides. What's missing is the *process* side, not the code side: - What to ask a prospective client during consultation to determine which features/flags they need. - How those answers map to a concrete checklist of flags to flip and overlays to create for a new site. - Whether any gaps exist in today's flag set (features a client might reasonably ask to drop/add that `features.yaml` doesn't yet cover). Deliverable is likely a short internal doc/checklist plus any small gaps found in the flag set, not a new subsystem.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
design/inner-page-headers
jfraeys/fix/staging-check-report
docs/cover-floor-wording
site-separation
v0.2.20
v0.2.19
v0.2.18
v0.2.17
v0.2.16
v0.2.15
v0.2.14
v0.2.13
v0.2.12
v0.2.11
v0.2.10
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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
jfraeys/coaching-site#3
No description provided.