01
Customer visit
Responsive pages establish age eligibility and present the store experience.
Live business websitePortfolio updated regularly
Production web integration case study
The Chronic Dispensary Website
A production website for an Albany dispensary that turns operational menu and ordering workflows into a responsive customer experience with clear product discovery, store information, deals, and order-ahead paths.
- Environment
- Production website
- Primary workflow
- Browse and order ahead
- Business location
- Albany, New York
- Delivery
- Git-based deployment
My role
Web development, API integration, deployment, iteration
Technology
Next.jsTailwind CSSREST APIsFlowhub workflowsNetlifyGitHub
The challenge
A real problem with practical constraints.
A local retailer needed more than a brochure page. Customers had to understand the store, discover categories and deals, reach the current ordering experience, and find visit information from desktop or mobile while the business retained control of operational inventory and ordering systems.
The response
A working system, not a slide deck.
I built a responsive public website around the customer journey and connected it to live menu and ordering workflows. The experience includes age confirmation, product-category paths, current offers, brand discovery, store details, directions, and clear order-ahead actions.
System design
How information moves through the project.
02
Product discovery
Categories, brands, offers, and calls to action guide shoppers toward relevant products.
03
Ordering boundary
Live menu and ordering workflows remain connected to the operational commerce platform.
04
Deployment
Git-based releases support controlled updates to the public experience.
Engineering decisions
Choices that shaped the result.
These are the tradeoffs I would discuss in a technical interview.
Design around customer tasks
Navigation and calls to action prioritize browsing, ordering, deals, directions, and store details instead of presenting the implementation as a technology demo.
Separate presentation from operations
The public site communicates the brand and routes customers into current ordering workflows while the commerce platform remains responsible for operational menu behavior.
Build for continuous business changes
The structure supports changing offers, categories, events, and store information without rebuilding the customer journey from scratch.
Security by design
- The public website is separated from private vendor configuration and operational credentials.
- Age confirmation is presented before adult-use cannabis content and ordering paths.
- The portfolio documents only public behavior and intentionally omits sensitive integration details.
Outcome
- The project is a live website serving an operating local business rather than a classroom-only prototype.
- Customers can move from discovery to the current order-ahead experience and find location information in a consistent flow.
- The work demonstrates requirements gathering, third-party integration, deployment, and ongoing iteration.
Lessons learned
What I would carry into the next build.
LESSON 01
Production work requires balancing business priorities, vendor boundaries, content changes, and technical constraints.
LESSON 02
A successful integration should feel like one customer journey even when multiple platforms are involved.
LESSON 03
Shipping for a real organization requires careful communication and restraint around private implementation details.
Scope note
This case study describes the public-facing implementation at a high level. Private credentials, vendor configuration, customer information, and sensitive operational details are intentionally excluded.