Founded
1 9 1 1

Docs

A clean public index for the README-style materials behind the platform: what exists, what is planned, what is prototype-only, and how the pieces fit together.

Presentation Use Docs should help leadership understand the build, not drown them in implementation detail.

These pages can summarize internal Markdown now and later link to fuller protected documentation when the platform matures.

docs/project-architecture.md

Platform Architecture

Tech stack, Supabase/Salesforce ownership, auth model, data contracts, route protection, and deployment structure.

  • SvelteKit + Supabase
  • Salesforce/Fonteva source of truth
  • Cloudflare Pages runtime
docs/business-logic.md

Business Logic

Membership standing, dues cycle, access control, payment rules, chapter workflows, events, store, directory, and compliance behavior.

  • IGS/NGS access rules
  • Dues and SLM logic
  • Role and badge model
docs/route-map.md

Route Map

A readable map of public pages, portal routes, admin surfaces, API endpoints, and the authentication expectations for each area.

  • Public routes
  • Portal routes
  • Admin and API routes
docs/api-reference.md

API Reference

Endpoint inventory for portal, admin, sync, payments, receipts, events, store, and operational actions.

  • Auth requirements
  • Methods and payloads
  • Operational endpoints

README Backlog

These are the next docs worth creating so the June 1 story has a crisp leave-behind.

Presentation README What is being shown, what is prototype-only, and what should be considered production-ready later.
Backend Ownership README What belongs in the shared Supabase backend versus each frontend repository.
Mobile App README Phone-first workflows, install behavior, offline candidates, and member-facing UX principles.
Deployment README Domains, environments, branch strategy, launch checklist, and rollback expectations.