Context
Associations that run conventions often keep equipment “in Excel and someone’s head”. Before an event, details disappear: what is in stock, where it sits, who took it, what is consumable, what came back. KonBase is an all-in-one platform: association inventory plus convention logistics in one web tool.
Goal
I designed and delivered an application that:
- organises association inventory (categories, locations, sets, documentation),
- streamlines convention logistics (check-out, returns, consumables, location mapping),
- provides roles, logs, and reports instead of chaotic chat-only coordination.
My role
I owned design, solution design, implementation, and up to 30 days of post-launch care.
Scope
Association module
- association registration and profile,
- inventory management (categories, locations),
- users and permission levels,
- warranties and equipment documentation,
- equipment sets,
- import/export and local backups.
Convention module
- create a convention from an association template,
- equipment issuing and return tracking,
- consumable item tracking,
- room / location mapping,
- requirements gathering and fulfilment status,
- action logging, reports, post-event archiving.
Security
- role-based access control (RBAC),
- super-admin role,
- hardened approach to log files,
- 2FA for sensitive operations,
- encryption for sensitive data.
Approach
Instead of “another CRM for everything”, I built around a real cycle: association warehouse → convention prep → on-site operations → archive. The frontend (React + TypeScript + Vite + Tailwind + shadcn/ui) is meant to stay usable under event pressure; the backend (Supabase: Postgres, auth, storage, edge, realtime) keeps infrastructure cost and ops light.
Challenges
- Two work modes — calm warehouse management vs. convention-day chaos. I split modules and flows so the UI does not mix those contexts.
- Permissions — volunteers, coordinators, admins. RBAC and action logs reduce “someone took it and nobody knows”.
- Data that must outlive the event — import/export, backups, and post-convention archiving so knowledge does not die with the event chat.
Outcome
The result is a live platform (konbase.cfd, code: GitHub) that connects inventory with convention logistics. I provided up to 30 days of post-launch care after go-live.
Stack
- Frontend: React, TypeScript, Vite, Tailwind CSS, shadcn/ui, React Router, React Hook Form, Recharts
- Backend: Supabase (PostgreSQL, Auth, Storage, Edge Functions, Realtime), TanStack Query
- Deploy: GitHub Pages + GitHub Actions (CI/CD)