Separate public, customer, and admin tasks
Distinct user areas keep service discovery, customer booking, and business administration focused on their different responsibilities.
Index of work07 / 10
Water-service website and platform
GlassHouse Waters
GlassHouse Waters combined a public water-services website with customer and administrative workflows. I delivered the application across its Next.js frontend and FastAPI backend. The site was deployed and used previously; I no longer maintain it.
- Role
- Full-Stack Software Engineer · implementation ownership
- Engagement
- Client project
- Status
- Previously deployed · no longer maintained
(01) The problem
The business needed public service information alongside customer booking and administration workflows.
(02) What I worked on
- 01
Public service and content pages
Built pages for service information, blog content, and customer inquiries.
- 02
Customer area
Implemented account workflows for customer profiles and booking interactions.
- 03
Administration
Built administrative screens and APIs for users, services, posts, bookings, and settings.
- 04
Payment integration
Connected Paystack payment initiation and authenticated reference verification to booking flows.
(03) Engineering decisions
(04) Delivery & status
Where it stands.
The platform was deployed and previously used by the business. I no longer maintain it, so I do not link to its current domain.
- The website was deployed and previously in use, but I no longer maintain it.
- The booking flow exposes availability, but capacity locking and overbooking prevention are not claimed.
- I have not linked the current domain because the client's domain expired and was reported hijacked.
(05) Technology
- Next.js
- TypeScript
- FastAPI
- SQLAlchemy
- PostgreSQL