Store

Source catalog: mypageRelease checks documented

Eyewear Brand

Lumen Eyewear is a designer eyewear studio in Seoul — hand-finished Italian acetate and Japanese titanium frames, with prescription-ready and polarised lens options for every face.

g-shop-eyewear.preview.mypage.dev

Loading interactive demo…

This is the real app, live — click around and try it.

About this template

Eyewear Brand gives you a storefront that looks premium — catalog, product pages, cart, checkout, and an order admin. Payments are scaffolded and ready to connect; everything else works today.

Lumen Eyewear is a designer eyewear studio in Seoul — hand-finished Italian acetate and Japanese titanium frames, with prescription-ready and polarised lens options for every face. The starter is copied as editable source, so you can change the design, content, data model, and workflows instead of being locked to a static demo.

Key highlights

Editorial storefront

A catalog and product pages that make your goods look premium.

Cart & checkout

A complete purchase flow, ready to connect to real payments.

Order management

An admin view to see and manage orders as they come in.

Mobile-first shopping

Smooth browsing and buying on any device.

Features & capabilities

A complete starting point for editing, verification, deployment, and independent source ownership—not a screenshot-only design.

Complete page architecture

Every page is wired and navigable — not just a homepage. Routing, layouts, and states are already in place.

Responsive foundation

Built with mobile and desktop breakpoints; run the browser audit with your final content before launch.

Restyle in one line

Colors, type, and spacing are wired together, so one line of intent restyles the whole app — no editing element by element.

Found on Google

Your main pages load as real HTML, so search engines and link previews see real content — not a blank page.

Data architecture matched to the workflow

Database-backed starters use real queryable tables and row-level policies; presentation-only starters do not invent a database dependency.

Explicit access boundary

Private workflows include sign-in, role checks, and row policies; public starters keep the core journey open instead of pretending login is configured.

Functional form patterns

Starters that include contact, booking, or signup flows wire validation and submissions to their schema. Test the final workflow before launch.

Theme-ready design tokens

Brand color, spacing, radius, and surface tokens can be changed consistently from the theme panel; rerun contrast checks after your final palette change.

Accessibility checks included

Semantic markup is the baseline, and the browser audit reports WCAG A/AA issues that still need attention.

Modern build pipeline

Vite produces revisioned assets, while the browser and performance gates show what still needs optimization.

Edit by conversation

Change copy, layout, or color by describing it — "make the hero bigger", "use a warmer tone". No code required.

Your code, exportable

Built in an isolated sandbox, verified before you see it, and yours to export anytime. No lock-in.

This template compared with a typical paid starter

What matters	mypage	Typical paid starter
Price	0 AI credits to fork; AI work is metered	Subscription and usage terms vary
Your code	Independent source export + GitHub sync	Git/export support depends on product and plan
Customization	Prompt, visual, theme, or source editing	Editing surfaces vary by product
Backend	Project database + policy gate when included	Managed backend options are common
SEO	SSR/prerender route and metadata gate	Rendering and metadata support varies
Time to live	A built preview without local setup	Most AI builders also provide hosted previews

Who this is for

Makers and brands selling a small, curated catalog
Founders launching a direct-to-consumer product
Shops replacing a clunky marketplace listing
Anyone who wants a branded store, not a template mall
Artists and creators selling prints or merch
Pop-ups and drops that need a store fast

Best use cases

Sell your products

List a catalog, take orders, and manage them from one admin view.

Launch a DTC brand

Give a single product the premium, focused page it deserves.

Take pre-orders

Validate a product with real orders before you scale inventory.

Own your storefront

Replace a rented marketplace with a branded store you control.

What you can build

A full storefront

Catalog, product pages, cart, and checkout with an order admin behind it.

A single-product page

A focused, premium page for one product with buy flow and proof.

A pre-order or drop

Take real orders for a limited run and manage them as they arrive.

Getting started

Use This Template
Click "Use template" to create your own copy of Eyewear Brand. mypage copies the source, applies any included migrations, and builds a preview without using AI credits. Build time varies by template and capacity.
Customize Your Brand
Change colors with one-click themes built on design tokens. Visual Edits can update mapped static text, classes, and uploaded-image paths; data-bound or conditional elements direct you to chat or Dev Mode instead of risking a broken edit.
Add Your Content
Replace the sample content with your own writing, products, and photos. Tell the AI what to change in plain language, or use Dev Mode for precision. Successful AI, manual, and supported visual changes create checkpoints so you can return to a known state.
Connect Your Data
When this starter includes a database, its migrations and row-level policies are applied to your project. Test final roles, forms, and launch data before publishing. Payments, login, and notifications use connectors that must be configured explicitly.
Go Live
Publish a verified revision to a real URL. Hosting, TLS, and server-side rendered pages are handled by the deployment path. New edits are built as candidate revisions, so a failed build does not replace the active one.

Data & launch checklist

This starter includes 2 project-scoped database tables: products, orders. Review the final data and role policies before publishing.
Production flows use these explicit connector boundaries:
- payments — Configure server-side Stripe credentials, allowlisted Price aliases, and the signed webhook. Test pending, paid, duplicate, expired, refund, and failure paths; a browser redirect is never proof of payment.
- shipping — Add an AfterShip key and the allowed carrier mapping. Test a real or test tracking number, unknown carriers, provider errors, and quota limits before presenting a delivery state as current.
- maps — Add the server-side map provider key and allowed origins. Verify geocoding success, quota exhaustion, provider failure, and the no-key fallback without exposing the credential to the browser.
- notify — Configure server-owned recipient templates and the selected email or Korean messaging provider, including its signed delivery webhook. Test success, retry, bounce/failure, scheduling, and cancellation without accepting a browser-selected recipient.
- auth — Built-in email/password identity is wired. Create verified test accounts, assign least-privilege roles, and prove anonymous, member, staff, and admin access before launch. Social login remains optional provider work.
Replace sample content and images, check every route at mobile and desktop widths, and resolve all browser, accessibility, security, and performance findings before going live.

Conclusion

That's Eyewear Brand — an editable source project rather than a static screenshot. Fork it, review the generated routes and policies, make it yours by conversation or code, run the browser audit, and publish a verified revision when you're ready. The export is independently buildable, so you can take the code with you.