System Web Systems TSF Fitness Studio
Client work · Fitness studio

TSF Fitness Studio.

Team Suresh Fitness needed more than a brochure site: a public front door, a member companion, and a staff console that could keep attendance, fees, events, and consent connected. This case study covers the problem, the system I built, and where it stands now.

Problem · solution · current status — screen archive below.

Scope

Public site • Client app • Admin app

Coverage

34 screens • 03 surfaces

Status

Live • public + member + admin

01 // The problem

A studio system, not just a website.

Team Suresh Fitness in Caranzalem, Goa needed a public front door, but the day-to-day studio work lived elsewhere: member records, attendance, fee dates, notes, events, and consent. A brochure site alone could not keep those connected, private, and usable by both members and staff.

Visitors needed

  • Programs, founder story, contact and visit information
  • Payment information and a nutrition/macro calculator
  • A clear, combined privacy policy and terms page

Members needed

  • Google sign-in, onboarding, and versioned policy consent
  • Membership/program details and payment dates/status
  • Attendance marking, history, streaks, and upcoming events

Staff needed

  • Member records, notes, and fee/payment updates
  • Attendance and event management, including opt-ins
  • Admin-only access enforced by database policies, not just the UI
02 // What I built

Three surfaces, one connected system.

TSF-CLUB is a static, multi-page front end built with HTML, CSS, and vanilla JavaScript, hosted on Cloudflare. Supabase provides the hosted PostgreSQL database, Google OAuth sign-in, and Row Level Security. There is no framework build step; the member and admin apps are separate surfaces backed by the same database and policy boundary.

Public website

Studio, founder, contact, program pages, macro calculator, payment information, privacy/terms, custom 404, and SEO resources such as robots.txt, sitemap.xml, and llms.txt.

Members app

Google sign-in through Supabase Auth, consent recorded by policy version, onboarding, dashboard, daily attendance, calendar/monthly progress, streaks, events, and profile.

Admin app

Member search/view/edit, notes, attendance, fee-status updates, event editing, and event opt-ins, with permissions enforced by Supabase policies and secure routines.

Security boundary: the client UI is not authorization. RLS policies, non-recursive SECURITY DEFINER routines, and atomic RPCs enforce member/admin access. SQL migrations are version-controlled, but they must also be applied to the live Supabase project.

03 // Current status

Live, with payment still at reception.

The public site and both apps are live on their Cloudflare-hosted domains. The member profile currently tells users that online payment setup is in progress and that payment should be made at reception; online payment processing is not assumed to be active.

  • Public website Live

    tsfclub.com serves the studio pages, programs, founder, contact, payment info, calculator, and policies.

  • Members app Live

    members.tsfclub.com handles sign-in, consent, onboarding, dashboard, attendance, streaks, and events.

  • Admin app Live

    admin.tsfclub.com handles member records, notes, attendance, fee status, and event management.

  • Online payment In progress

    The app directs members to pay at reception while online payment setup is completed.

  • Database Manual apply

    Migrations are tracked in Git but executed manually in Supabase. The attendance issue was resolved by applying the attendance migration to the live project.

  • SEO Published

    Metadata, robots.txt, sitemap.xml, and llms.txt are in place; indexing and webmaster verification remain external validation steps.

See the rest of the client work

The Web Design page collects every case study — briefs, decisions, and deliverables.