Product design

The memory of the product — every design doc, CEO plan, decision record, and presentation deck behind what Raklet ships, in one place. When you need to know why a feature looks the way it does, what was deliberately cut, or who decided it, start here.

What belongs here

Anything design-flavored: /office-hours design docs, CEO plans, decision records, dashboard designs, feature specs, and the polished presentation decks we share with stakeholders. Operational runbooks and pure test plans live under their feature areas (Testing, Payments, etc.) and are cross-linked below where they pair with a design.

Releases changelog

• Product releases — what shipped to production, grouped by customer impact, newest period on top. This is the source for our monthly product-update emails; it embeds screenshots from each PR's evidence.

Presentation decks

The stakeholder-facing decks — self-contained HTML, committed here so they outlive any PR-evidence storage.

• Polls v1 — engineering handoff for the smallest shippable structured-input feature: a poll post type on the social wall, anonymous by default, single/multi-choice, server-enforced close. Scope deliberately cut to a v1; election-grade features deferred behind a customer-validation gate.
• Member-created events — letting members submit their own events to an organisation (submit/edit flow, ticket types, online/location toggle, image upload, currency).
• Portal modernization — the member-portal reskin report: Bootstrap 4.3.1 baseline, CSS-only .SettingsModern scoped-override pattern, phased Settings → Profile rollout.
• Digital cards — field configuration — Help Center draft for ENG-15: five configurable field slots, barcode defaults, Apple Wallet front/back layout, and automatic plan benefits on wallet passes. Screenshots on rakletlocalfiles blob storage.

---

By module

Events

• Member-created events — design — the /office-hours design doc (problem, wedge, scope).
• Member-created events — CEO plan — active execution plan and scope commitments.
• Member-created events — test plan.
• Admin KPI dashboard — design — the events analytics dashboard for organisers.
• Admin KPI dashboard — eng-review test plan.
• Admin events list — test plan.
• Event email reminders — plan — automated reminders, per-org default template, backfill, visibility.
• Event email reminders — handoff · CEO review · PR writeup.

Pages

• AI Page Builder — design — APPROVED. Skip the drag-and-drop arms race; generate a complete, data-aware member portal from minimal input (URL/PDF/description). Hybrid: AI portal wizard at onboarding + AI single-page chat in-product, behind a validation gate.
• AI Page Builder — eng review — /plan-eng-review follow-up locking LLM choice, token-rendering architecture, and validation-gate instrumentation.

Membership

• Digital cards — field configuration (Help Center draft) — ENG-15 configurable card fields, barcode behavior, and wallet layout.
• Multiple currency in membership plans — design for per-plan currency. (test plan · unit tests)
• Membership plan — create defaults — decisions on default values at plan creation.
• Application form settings.
• Application approval — payment controls.
• Contact subscription membership fees.
• Subscription data import.
• Group membership data import.
• Public address lookup.

Fundraising

• Donation / fundraising detail page — redesign — ENG-87. Three directions (Momentum / Editorial / Focused Card) for the member-facing donation detail page; problem analysis, recommendation, and screenshots. Gathering team feedback.

Coupons

• Membership coupon process · surface flows · task list.
• Ongoing membership coupons.

Payments

• MRR dashboard — subscription cache decision — the decision doc that supersedes the prior MRR draft.
• CRM live MRR + Stripe Connect dashboard — the early DRAFT, superseded by the decision doc above (kept for lineage).
• MRR dashboard — incremental per-customer refresh · Redis prewarm.
• Recurring membership billing flow.
• Scheduled payment subscription eligibility.
• Stripe — existing account OAuth · PaymentIntent card saving.

Jobs

• Admin dashboard — design — the Jobs module dashboard.
• CustomMembership status one-time task.

Portal

• Member portal modernization — design — APPROVED. The design doc behind the Portal modernization deck: reskin the dated member portal that's cost named deals.
• Locked content redirect behavior.

Settings

• Roles limit flow.
• Cookie consent (GDPR) — design — ENG-276. Own-build consent banner (default-deny), per-org vs shared cookie scope, persistent withdrawal + Privacy settings card; the GDPR response to the Zachęta security review. (implementation reference)

---

Process & strategy

How we decide and ship — design-flavored process docs, not feature designs.

• Engineering workflow — the AI-implementer / human-gatekeeper model: 9 phases, 2 hard gates (Plan, QA).
• Server-side test-coverage plan — the 1.5% → 80% line-coverage initiative.

---

Adding a design doc

Drop the markdown under its feature folder (e.g. docs/events/) and add a line here under the right module, plus its own feature-area nav: entry in mkdocs.yml. For a stakeholder deck, commit the self-contained .html into docs/product/ and link it under Presentation decks above — don't rely on PR-evidence blob URLs, which aren't a permanent home.