Runtime API configuration
The frontend reads its API origin at runtime so the same build can run locally or behind a hosted endpoint.
Full-stack product engineering
CubeMint
A commerce workflow built from storefront to payment boundary.
- Role
- Solo developer across product design, Angular, Express, data, payments, and deployment
- Evidence status
- Verified locally; public deployment and security review pending
- Verified
- 2026-07-22
01
Problem and scope
CubeMint is an Angular and Express storefront for browsing, filtering, wishlisting, and purchasing a collection of artisan cubes. The project joins customer-facing interaction design with a MongoDB API, Stripe checkout, image uploads, and containerized delivery.
02
Architecture
Angular storefront
Search, filters, wishlist, cart, admin flows
Express API
Product, authentication, upload, and checkout routes
MongoDB and Stripe
Product persistence and hosted payment boundary
Docker and AWS
Containerized frontend and backend deployment
Text equivalent: the stages above flow from left to right, with each stage passing its result to the next.
03
Engineering decisions
Environment-safe image URLs
Stored image paths are rewritten to the active API origin, preventing an upload host from being permanently baked into the storefront.
Responsive product density
The storefront exposes list and grid controls while adapting navigation, filters, and cart behavior for narrow screens.
04
Verification evidence
- Local API returned 66 MongoDB-backed products.
- Search reduced the visible collection to matching products after its debounce interval.
- Adding Wooden Crate updated the cart count to one and produced a $120 cart total.
- Desktop, mobile storefront, and mobile cart states were captured from the running local application.
$ GET /api/cubes?sort=desc&limit=All&minPrice=0&maxPrice=150
200 OK · 66 products
$ search: Wooden Crate
cart badge: 1 · total: $120.00
✓ storefront and cart verified locally05
Demonstrated workflow
06
Limitations
- The former AWS endpoint is offline, so this release does not claim a live public demo.
- Several uploaded images existed only on the old hosted volume and are missing from the local source copy.
- CORS, JWT handling, uploads, Stripe configuration, secrets, and MongoDB queries require review before public redeployment.
Next step