The operational problem
Customers needed to know what could be ordered, starting price, lead time, pickup, deposit, allergens, and how to share a custom idea without a long message exchange.
A custom-cake website that makes products, starting prices, policies, real work, and the order-request process understandable.
Why this system exists
A structured inquiry reduces avoidable back-and-forth while keeping the creative conversation personal and preserving the owner's final quote and availability decision.
The site organizes the client's real photography, products, prices, policies, gallery, order guide, and inquiry form around the way custom orders are actually handled.
How the work moves
- Browse products
- Understand price and policy
- Share date and idea
- Owner confirms availability and quote
- Deposit confirms date
- Approve final photo
- Pickup
What shaped the solution
Photography, baking work, products, policies, and brand belong to Cakes by Hibaq.
What I owned
Designed
Product, price, policy, gallery, and order information architecture
Developed
Next.js routes, order form, responsive media, metadata, and schema
Integrated
Inquiry delivery and public deployment
Collaborated
Owner intake, policy clarification, product details, and media selection
Decisions that carried the work
Structure the inquiry, keep the quote human
The form collects the date, item, flavour, and idea, while the owner keeps final control over availability, design, and price.
Verified outcome
Live product, price, gallery, policy, and order routes.
Structured inquiry tied to the owner's actual quoting and pickup workflow.
Responsive image and short-video system built from client media.
What I will not overclaim
The portfolio describes Ayub's website and workflow contribution only.
Verified from the current repository, owner-intake documents, asset audit, and public site.