Club operations · Strava integration
KC Prishtina 038
One place to run the club. A connected view of the ride.
KC Prishtina 038 combines a public club presence with the tools needed to manage its daily operations. Administrators, staff, coaches and members have different responsibilities, so the application brings them into role-aware workspaces. Membership, events, content, financial records and training activity are handled within a connected product rather than treated as unrelated website features.
- Next.js
- React
- TypeScript
- Supabase
- Strava
Build beyond the public website.
The administration interface includes membership applications, member records, club sections, membership plans, event registration and result publication. News, documents, media and sponsor content sit alongside those operating tools. A member portal provides a separate view of profile, membership and training information, with access shaped by the person’s role.
Financial workflows cover membership invoicing and payment status, advance payments, club income, expenses, receipts and reimbursements. Bringing these records into the same product gives club operations a shared working context. The case describes these implemented capabilities without exposing member information or internal financial records.
The club application and its responsibilities
Role-aware interfaces connect to club operations through server-side access checks. This is a capability view of the application.
People & access
- MembersProfiles, membership and trainingNext → Next.js + React
- Coaches & administratorsRole-specific working viewsNext → Next.js + React
Application
- Next.js + ReactPublic, member and administration viewsNext → Server-side access checks
- Server-side access checksApply role and access boundariesNext → Membership & eventsNext → Financial recordsNext → Content & training
Club operations
- Membership & eventsApplications, registrations and results
- Financial recordsInvoices, payments and expenses
- Content & trainingClub publishing and activity records
Turn activity imports into useful club records.
Members can connect their Strava accounts, and imported cycling activity is processed into training workflows. Activity matching helps organize sessions, while suggestions support session titles and focus. Coaches can review and edit training information, and refresh behavior is designed to preserve values they have already supplied.
The integration also supports training views, participation records and comparison features. Connection lifecycle is part of the implementation: disconnection, revoked access and deleted activities have cleanup handling. This makes the work broader than displaying an external feed; it connects activity data to the club’s own product behavior and user responsibilities.
From Strava activity to an editable club record
Matching and suggestions use rules-based automation. Imported sessions can be created before coach review; refreshes preserve coach-supplied values.
External activity
- Member connects StravaAuthorize the activity connectionNext → Activity import
- Activity importBring cycling activity into the workflowNext → Match & suggestRevoked / deleted → Connection cleanup
Training workflow
- Match & suggestOrganize activity and suggest session detailsNext → Club training record
- Club training recordSessions and participation informationReview / edit → Coach review & edits
Coach & lifecycle
- Coach review & editsRefine the imported training record
- Connection cleanupHandle revocation and deleted activities
Use the right mechanism for each workflow.
Development material records AI-assisted design and implementation work. The application itself uses rules-based automation for the examined activity-matching and suggestion workflows. Keeping that distinction clear matters: AI can help engineers build a product without every automated feature needing a language model at runtime.
The implemented product includes automated session suggestions and race-related content suggestions that administrators can review. Imported training sessions remain editable by coaches. These workflows keep routine data organization connected to the people responsible for the club’s records, without presenting deterministic suggestions as model-generated intelligence.
A full application around real operating responsibilities.
The current implementation uses Next.js, React, TypeScript and Supabase. Role-aware interfaces and server-side access checks support the separation between administration, coaching and membership. Focused test sources cover activity matching and related training calculations, with additional access-control test material in the project.
The result is a substantial application scope: a public presence, administrative workflows, a member experience, financial operations and an external activity integration. It demonstrates the custom software work involved in connecting people, permissions and data across an organization’s daily activities.
Connect your operations and integrations.
Build the admin tools, member or customer portal, and external-system workflows your organization needs.
Discuss your project