<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Anton Lychkouski</title>
    <description>The latest articles on DEV Community by Anton Lychkouski (@menuonstudio).</description>
    <link>https://dev.to/menuonstudio</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4250962%2F83541e7d-5a21-4e44-8a24-e4f620f4d8cb.png</url>
      <title>DEV Community: Anton Lychkouski</title>
      <link>https://dev.to/menuonstudio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/menuonstudio"/>
    <language>en</language>
    <item>
      <title>A restaurant website needs a maintenance workflow, not just a launch</title>
      <dc:creator>Anton Lychkouski</dc:creator>
      <pubDate>Wed, 18 Nov 2026 04:55:27 +0000</pubDate>
      <link>https://dev.to/menuonstudio/a-restaurant-website-needs-a-maintenance-workflow-not-just-a-launch-4gip</link>
      <guid>https://dev.to/menuonstudio/a-restaurant-website-needs-a-maintenance-workflow-not-just-a-launch-4gip</guid>
      <description>&lt;p&gt;A café website can look finished on launch day and become unreliable a week later: a price changes, a dish sells out, or opening hours shift. The difficult part is keeping the information current.&lt;/p&gt;

&lt;p&gt;I work on &lt;a href="https://menu-on.com/main?lang=en" rel="noopener noreferrer"&gt;Menu-on&lt;/a&gt;, a managed menu website service for cafés and restaurants. Our approach is to include website administration and updates to the content supplied by the venue, alongside hosting and support.&lt;/p&gt;

&lt;p&gt;Here is a practical checklist for anyone building this kind of product.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Decide who owns each update
&lt;/h2&gt;

&lt;p&gt;The venue supplies and confirms the facts: prices, ingredients, allergens, opening hours and availability. The website operator publishes those changes. Make that handoff explicit; a nice editor alone does not establish who is responsible for the information.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Keep the public address stable
&lt;/h2&gt;

&lt;p&gt;A table QR code, a Google Maps website button and a social bio should lead to a page that can be updated without printing a new code. Check both the destination and the language after changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Test the menu as a guest
&lt;/h2&gt;

&lt;p&gt;Use a phone. Can you find a dish, understand the price, switch language and locate the venue without zooming or guessing? For a bilingual menu, check that descriptions and essential details remain consistent between languages.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Separate interest from completed transactions
&lt;/h2&gt;

&lt;p&gt;Menu views and clicks on a booking button help explain visitor interest. They do not prove completed reservations or sales. Name those events clearly so the restaurant does not mistake a click report for revenue.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Make the service boundary visible
&lt;/h2&gt;

&lt;p&gt;For Menu-on, we create a personalised preview and transfer the supplied menu before a subscription begins. Ongoing service covers hosting, administration, support and content updates. The current subscription is €45 per month or €199 every six months. This is a managed service; the value includes the work after launch.&lt;/p&gt;

&lt;p&gt;You can see the &lt;a href="https://menu-on.com/main?lang=en" rel="noopener noreferrer"&gt;English service page and request a free preview&lt;/a&gt;. Business contact: &lt;a href="mailto:hello@menu-on.com"&gt;hello@menu-on.com&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I represent Menu-on. This article was drafted with AI assistance.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
    </item>
  </channel>
</rss>
