Cornershopdev
Restofrontapp
restofront.com
Built for restaurants
Menus, bookings and hours that stay current on their own.
Website factory · system online
The system behind your next local website.
One workspace to scan an existing business, recover what matters, and publish a focused website built for its trade—not another blank template wearing different colours.
Preview before paymentExisting tools staySelf-hostable
factory/run
$cornershop build
sourcerestaurant.example
verticalrestaurant
contentmenu · hours · bookings
themeterroir-editorial
scan
source
shape
schema
match
theme
ship
domain
private previewready to claim
01live niche product
03restaurant theme systems
02verticals in the registry
Products, not presets
One engine. Brands that speak the trade.
Cornershopdev stays behind the curtain. Each niche gets the language, workflows, themes, and domain its customers already understand.
Restaurant theme library
Familiar commerce patterns. Hospitality-specific decisions.
The library borrows interaction conventions diners already know from ordering and booking products, then adapts them to an independent restaurant’s own brand. AI matches the system; it does not invent one on every scan.
Inspect the theme librarypackages/themes/restaurant3 registered
From source to storefront
A pipeline built around the finished thing.
The factory begins with evidence from the business, not a blank canvas. Every stage narrows ambiguity before the owner is asked to review anything.
scan(source)Recover the business
Read the existing site, menu or service list, imagery, hours, contact details, and the tools customers already use.
structure(vertical)Apply the niche schema
Restaurant data becomes a menu. Salon data becomes services and durations. The shared engine never flattens every trade into generic blocks.
render(theme)Match a registered system
AI selects from bounded layouts and tokens built for the business model. It does not improvise fragile production CSS.
publish(domain)Claim, connect, keep current
The owner reviews a private preview, chooses a plan, connects the domain, and keeps the website maintained from one workspace.
The shared core
Small-business software without the generic shell.
Each customer sees a product for their trade. The expensive operational machinery stays shared, typed, and inspectable.
Vertical registry
A trade is configuration, not a fork.
Schema, providers, prompts, templates, vocabulary, and positioning live together. Register a vertical once and the factory knows how to sell and build it.
Shared operations
One data model behind every brand.
Sites, leads, claims, subscriptions, analytics, and domains share the same operational layer without leaking the factory brand into customer-facing sites.
Durable pipeline
Import first. Ask questions second.
A business sees a populated preview instead of an empty wizard. Missing details become a small review task, not a multi-hour setup project.
Open source
Inspect it, extend it, run it.
Next.js, Postgres, durable workflows, and a typed registry. The product is usable as a service and legible as infrastructure.
Pick the vertical. See the result.
Start with the business, not the builder.
Explore the live restaurant product, inspect the registered theme systems, or open the source and build the next trade.