For Highland Lantern Kitchen, my fictional San Bernardino restaurant, I would build the story from specific things a customer could understand: a dish, its ingredients and the experience of ordering it. I would avoid filling the page with grand claims that any restaurant could make. The first day would establish a few sample menu items and decide what each photograph should explain. The visual direction would support that information while remaining clearly identified as concept work.
This is an independent educational study, not a client project or reopening announcement. The concept below is fictional. It shows proposed work, not measured business results.
The part we can put on the record
A 2025 newspaper roundup reports Golden Dragon's San Bernardino closure. These IE restaurants closed in the first half of 2025.
Highland Lantern Kitchen is fictional. The historical reference makes no judgment about the former owners, their service, their marketing or the reason for closure. Historical reference: Reported as a winter closure in the 2025 roundup; exact date not established.
A closure or change of use does not tell us whether a website was good or bad. I am not attributing this history to SEO or claiming a different site would have changed it. The useful exercise is to take a customer task from this type of business and work through a fresh design.
The question I would design around
I would place the menu close to the story and give images useful descriptions rather than decorative file names. A short question section would answer practical issues that an operator could verify. On a real project, photographs and testimonials would need to represent the actual business and genuine experiences. For this exercise, I would use clearly labeled illustrative assets and no invented customer endorsements. The design could still show personality without borrowing credibility from a business that did not commission it.
The proposed feature: A fictional restaurant story page with clearly labeled concept imagery, an accessible menu and an operator-editable FAQ based on real customer questions.
EXPLORE THE WEBSITE CONCEPT
Highland Lantern Kitchen
A proposed digital front door built around a customer task in San Bernardino.
An independent business's own photographs and precise menu descriptions communicate more than generic superlatives. A concept can show good presentation without inventing testimonials or a client relationship.
The opening screen would identify the offer, its real location or service area, and the action a customer can actually take. Any hours, prices, availability, or promises would come from the owner before launch.
See how I would check it ↓A fictional restaurant story page with clearly labeled concept imagery, an accessible menu and an operator-editable FAQ based on real customer questions.
Give the customer a clear route into this task, explain what is needed, and confirm what happened. A request must never look like a confirmed purchase, appointment, or reservation when it is only an inquiry.
See where it fits in the launch week ↓What would tell us it is useful?
Test image loading, descriptive text and menu discovery; track contact and order-link actions only after a real, consented launch.
This is a measurement plan. No traffic, ranking, sales, or conversion results have been collected for this fictional concept.
The first seven days, with a defined finish line
I would scope the first release around the customer task above. The schedule assumes the owner has supplied accurate content, approved the offer, and provided the access needed to launch. Custom integrations or a complex application need their own estimate.
- Day 1 · Establish the facts. Confirm the new concept's offer and audience in San Bernardino. Collect permission to use its photos and wording. Keep the historical business separate from the new brand.
- Day 2 · Map the decision. Turn the design question into an outline: An independent business's own photographs and precise menu descriptions communicate more than generic superlatives. A concept can show good presentation without inventing testimonials or a client relationship. Identify what the visitor needs before they act.
- Day 3 · Build the essential pages. Draft a useful home page, an offer or service page, and contact information. Show the Highland Lantern Kitchen identity consistently, with a readable mobile layout.
- Day 4 · Make the task understandable. Prototype and test the proposed feature: A fictional restaurant story page with clearly labeled concept imagery, an accessible menu and an operator-editable FAQ based on real customer questions. Use clear instructions, validation, and an honest completion state.
- Day 5 · Check the basics. Test keyboard use, labels, readable text, image sizes, working links, and a phone-sized screen. Check page titles, canonicals, and crawlable navigation.
- Day 6 · Introduce the real site to Google. Verify the appropriate Search Console property, check the sitemap, and inspect an important URL. Requesting a crawl is not a guarantee of indexing.
- Day 7 · Launch and write down the baseline. Complete the main task once from beginning to end, confirm who receives any request, and record what will be measured next: Test image loading, descriptive text and menu discovery; track contact and order-link actions only after a real, consented launch.
This is a proposed launch plan for a digital foundation. It does not reopen the historical business, create demand, or promise a particular position in search. Read the detailed seven-day launch guide.
The test matters as much as the layout
My final test would ask a reader to describe a sample dish, find how to order and distinguish illustration from evidence. I would check whether images load at appropriate sizes and whether the menu remains useful without them. A future live site could track menu visits and genuine contact actions, with the operator confirming what happens afterward. The first week's achievement would be a clearer restaurant story that leads somewhere useful, not a fabricated claim about sales or search success.
Test image loading, descriptive text and menu discovery; track contact and order-link actions only after a real, consented launch.
A professional web designer should be able to explain these tradeoffs. If the task needs changing data, rules, or a more complex workflow, a software engineer or web application developer may be part of the build. The useful question is whether the work makes the customer's next step clearer and the business's follow-through dependable.
Carry the idea into your own next chapter
The repeatable part is the process: establish the facts, identify a real customer task, build the smallest complete version, test it, and measure what happens. The details should change with the business. For San Bernardino, the lesson in this study is: An independent business's own photographs and precise menu descriptions communicate more than generic superlatives. A concept can show good presentation without inventing testimonials or a client relationship.
Start with Google Search Console · Understand sitemaps and indexing · Read the regional study.