Restaurant Thomas

Restaurant Thomas is the public website for a restaurant and catering business. The project covers the visitor-facing site, the catering entry points, local service pages, and the technical work needed to keep the site fast, findable, and easy to use.

The site has two jobs. It should help normal visitors find the restaurant information they need, and it should help catering visitors reach the right offer path without digging through the wrong page.

What it does

• Shows restaurant information, seasonal details, and public service pages.
• Gives catering visitors a visible path to offers and inquiries.
• Supports local service pages for city-based catering searches.
• Keeps pages indexable without depending on a database at runtime.
• Adds consent-aware analytics and better tracing for inquiry submissions.
• Improves performance so public pages load with more headroom.

Recent work

The June work improved both the public site and the operational handoff. The catering entry was restored to places where visitors expect it, confirmed Biergarten season details were exposed publicly, and event visitors were routed more directly to the catering offer.

The local catering pages were made indexable without database runtime dependency. That makes the pages safer for static delivery and easier for search engines to crawl. Service-city SEO content was refreshed, and translation artifacts were cleaned up so public pages read better.

There was also practical infrastructure work. Inquiry submissions are now easier to trace in Vercel logs, and the site gained PageSpeed headroom. Analytics were enabled in a way that respects consent instead of forcing tracking too early.

Value for users

For visitors, the value is clarity. They can find restaurant information, understand catering options, and reach the right inquiry path faster. For the business, the value is a site that can bring in local demand while still being easier to operate and debug.

Current direction

The current direction is a cleaner public funnel. Restaurant visitors should not be confused by catering pages, and catering visitors should not get lost in restaurant-only content. The site should keep improving search coverage, speed, and inquiry quality.

Public boundary

This page covers public website behavior. It does not include private inquiry contents, analytics identifiers, customer records, or internal business reports.