Changelog

Editing the text that was already on your site is one thing. Adding something that was never there — a delivery notice, a seasonal announcement, a button pointing at your booking page — was still a request you had to make, and wait for.

There is now a Content blocks section in the back-office. You write a block, in French and in English, with proper formatting: headings, bold, italics, lists and links, plus two things that render in your site's own style rather than a generic one — a callout, for something you want set apart from the surrounding text, and a button that sends visitors to a page you choose. In the editor, callouts and buttons appear as plain neutral markers; their final look is your site's, which is why they never clash with it. Each block is a draft until you publish it, so an unfinished announcement stays invisible.

Blocks go into spots — a small number of positions your site was built with, such as below the hero on the home page or at the top of the menu. Each spot has room for a fixed number of blocks, and you decide which blocks go where and in what order. Unplace a block and it disappears from the page while the text stays safely in the back-office; place it again and it returns.

The limits here are the point of the feature, not a shortcoming of it. You cannot create new spots, move them, or rearrange your site's sections — the spots are decided when your site is built, because where a block sits affects the design and the page's structure in ways a text editor cannot see. No block creates a page, an address, or anything a search engine indexes. A block is a fragment placed inside a page that already exists, and that boundary is what makes the feature safe to hand over without a review step: the worst outcome of a bad block is a paragraph you don't like, which you delete in a few seconds. If you want a new spot, or a new page, that is still a conversation with us — and it should be.

The two languages stay independent. A block published in French with no English text simply does not appear on the English version of your site, rather than showing French to an English visitor. The list tells you which blocks are missing a language, so a half-translated announcement is something you can see rather than something you discover later.

This is an option rather than a default. It is off unless it has been enabled for your restaurant; if you would like it, ask us. You can see it working — the spots a site declares, and what lands in them — in the demo site's component gallery under Features → Content blocks.

Until now, the wording on your site — the line under your name, your About text, the short badge on your photo — was part of the site itself. Changing a single sentence meant asking us, and waiting for the change to be deployed. That was a deliberate choice: marketing copy is written rarely and carefully, and turning every site into an editing tool has a cost. But "rarely" is not "never", and waiting on someone else to fix a typo is not a good answer.

There is now a Site content section in the back-office. It lists a small, chosen set of text fields from your site, each with its own French and English version, and each with a length limit that matches where the text actually appears. You edit one, you save it, and the site shows it — no deployment, no developer, no ticket. If you change your mind, reset puts the original wording back exactly as it was.

What you cannot do is as deliberate as what you can. The list is curated rather than complete: page titles and search-engine descriptions are not in it, because quietly rewriting those damages how you rank in ways that surface weeks later and are hard to trace back. Fields that only accept a couple of words say so and stop you there, because that badge on your photo has no room to wrap. And the original wording is never overwritten — it stays underneath as the floor, so an empty or mistaken edit can never leave a blank space on your site. The worst outcome of a bad edit is text you don't like, which you fix in ten seconds.

The About text also accepts simple formatting — bold, italics, links and lists — and nothing else. No images, no tables, no embedded video. That restriction exists so that what you write is always safe to publish on a public page, without anyone reviewing it first.

This is an option rather than a default. It is off unless it has been enabled for your restaurant; if you would like it, ask us. You can see it working, side by side with the original wording, in the demo site's component gallery under Features → Editable content.

This wave is mostly invisible from the outside, and that is the point. The platform moved onto the current generation of its foundations — a new TypeScript major, a new rich-text engine, a new linter, a new charting library — and every knock-on break was fixed rather than pinned around. Two security advisories were cleared and the dependency audit surface is back to zero. Nothing about the product changed; everything underneath it did.

One fix does change what you see. Checklists in blog posts were quietly losing their checkboxes: the editor's content filter was stripping the very attributes that mark a list as a task list, so every checklist collapsed into ordinary bullets the first time a post was saved — permanently, with no warning. That is repaired, and published checklists now render as real checklists on the guest site, which they never had the styling to do before.

Billing also changed shape. Subscriptions and invoices are now driven manually by the WebOustaou team rather than through a payment provider, and the parts of the interface that pointed at the old flow are closed off behind an explicit confirmation instead of sitting there half-connected.

Beyond that: rate-limit protection now covers the marketing and demo domains as well as the back-office, missing French wording was restored across the testimonial sections, and a handful of editor and navigation annoyances were smoothed out — most notably a guard that was cancelling its own redirect after creating a menu offer.

Restaurants can now see where guest-site traffic actually comes from. Every visit is tagged with its origin — a QR scan at the table, a direct visit, or a tracked link — and the analytics dashboard gains an origin filter plus a dedicated direct-traffic bucket. A fix in the tracking beacon also makes event capture fully reliable across every page.

The guest site got sharper too: offer pages now handle availability windows and navigation visibility more predictably, and the public site received a full typography and copy refresh — new heading and body typefaces, tighter wording, and positioning that welcomes cafés, food trucks, and independents beyond restaurants alone.

This wave closes the feature roadmap for the beta: version 0.10.0-beta marks the point where the core product is functionally complete. What remains before customer launches is a focused UI polish pass — then the next phase is all about building real customer sites.

WebOustaou now lets restaurants publish a Plat du Jour and richer fixed-price Formules directly from the same workspace. Teams can build structured offer sections, set availability windows, duplicate and reorder entries, and publish dedicated pages on the guest site without custom code.

This wave also upgrades featured products with custom badge labels and optional visibility windows, so a restaurant can spotlight a monthly pizza, a lunch combo, or a seasonal menu item only for the dates that matter. The result is a more promotional, more operationally flexible public menu surface without leaving the core beta workflow.

This wave focused on making WebOustaou easier to fork, safer to ship, and cleaner to tailor. We closed a full audit pass across auth redirects, QR performance, happenings retention, CSP, and capability coverage, while also tightening the public-site and dashboard UX around real screenshots, social cards, hero fallbacks, and footer behavior.

For teams preparing customer forks, the site template now ships with a dedicated forking checklist, more domain-neutral naming, cleaner reusable UI pieces, and a more explicit separation between platform defaults and restaurant-specific content. The result is a beta that is much closer to the next phase: UI and UX tailoring, performance proof, and per-customer finishing work.

WebOustaou now includes Happenings, a lightweight way to promote what's coming to your restaurant — a pop-up tasting, a live-music night, a seasonal festival stall. Create one from the workspace with a title, a short description, a cover photo, and a date, then publish it to your guest site.

Visitors can tap "I'm interested" and leave a name and email in one click, no account or reservation flow required. Every happening has its own list of interested visitors in the workspace, with a one-click CSV export. Happenings is rolling out gradually and is live today on our demo restaurant.

This wave focuses on speed. The admin app now resolves tenant membership, capability checks, and action context through a single consolidated RPC instead of several round trips, and reordering menus, categories, and galleries runs as one atomic set-based update rather than row-by-row writes.

On the public side, the marketing homepage and site template defer their heaviest scripts — the hero demo now loads on click instead of eagerly, and gallery, Turnstile, and validation code split out of the initial bundle — cutting load-blocking work on first paint. All three apps are now pinned to the Paris region alongside the database to shave network latency.

The site template's footer navigation and gallery also gained a dedicated blog entry point, and we closed a round of sign-in reliability fixes for Safari on iOS.

WebOustaou now includes a complete restaurant blog workflow from the back office to the public site. Teams can draft, translate, schedule, tag, and publish posts from the admin app, then show them on the site template with SEO metadata, JSON-LD, and post-view analytics already wired.

This closeout wave also shipped tenant capability gates, dashboard display preferences saved in the database, stronger QR and site-event analytics, and the first in-app performance tooling used to polish the admin experience before the next phase.

The demo portal has been completely rebuilt. You can now explore a live example restaurant site before even creating an account, see what your own site would look like with your colours and logo, and book a guided demo with the team directly from the page.

For a short window, some QR code scans didn't redirect guests to the menu correctly and weren't being counted in scan history. We found the regression, fixed the redirect path, and verified scan tracking is accurate again. If you noticed a dip in your scan numbers around this time, that's why — counts from before the fix may be incomplete.

You can now see what we're working on and what's coming next — online ordering, a POS system, floor tablets, customer accounts, and an AI phone agent. The roadmap is available directly from our site. Your feedback and priority votes are welcome to shape what comes next.

A documentation centre is now available online. You'll find step-by-step guides for setting up your site, managing your menu, understanding your QR stats, and much more. Articles are available in French and English, and are updated regularly as new features ship.

A simple contact form appears on your customer site. Visitors can message you directly — group reservations, menu questions, general feedback. You get an instant email notification, and messages are also viewable from your dashboard.

Customer sites now automatically generate the structured SEO tags (Schema.org Restaurant, LocalBusiness) that help Google surface your venue in local results and on Google Maps. Your address, hours, cuisine type, and phone number are indexed with no manual setup needed.

Add ingredients and allergens to each dish directly from the dashboard. They appear automatically on your customer site, with the regulatory icons for all 14 major allergens. Guests can filter the menu by their intolerances, and you stay compliant with EU food information regulations.

Track how many times each of your QR codes has been scanned, from what type of device, and which days see the most activity. This helps you know whether a table QR is actually being used or whether it needs to move. Date charts coming very soon.

Invite your staff into your management workspace — a trusted server, a floor manager, a business partner. Everyone logs in with their own account, and access can be revoked at any time. No more sharing a password or leaving everything unmanned when you're away.

Customer sites now load significantly faster thanks to intelligent caching of menus and content. Pages display in under a second for most visitors, even under high traffic. Updates from the dashboard remain instant — the cache refreshes automatically as soon as you save a change.

A cookie management banner now appears on all customer sites for visitors based in the European Union. Preferences are remembered, the banner doesn't reappear on every visit, and no third-party trackers load before explicit consent is given. Compliant with CNIL and EU cookie guidelines.

Every guest site now ships with the legal pages French restaurants are required to publish: mentions légales, a privacy policy, and a cookies page, pre-filled with your business details. One less thing to draft yourself before going live.

Generate QR codes from the dashboard and point them at any page on your site: menu, homepage, a special event. You can change the destination at any time without reprinting the QR — handy for seasonal menus or one-off promotions. The QR is ready to download in high resolution for print.

Guests can now send you a message directly from your site's contact form, delivered straight to your inbox. We also shipped branded 404 and error pages, so a mistyped link still feels like part of your restaurant's site instead of a generic dead end.

Every customer now gets a dedicated guest-facing website, forked from the same production-ready template: a clear header and hero, and full menu browsing down to individual product details and photos. It's fast, mobile-first, and ready to customize for your branding.

Guests can now see your opening hours, find you on a map with one tap for directions, and check whether you're open right now — right from your site's homepage. The open/closed status updates automatically from the hours you set in your dashboard, no manual flipping required.

You can now click through a full WebOustaou site before you ever talk to us. The interactive demo at demo.weboustaou.fr shows a real restaurant's menu, hours, and contact page, built with the same components every customer site uses. Explore it on your phone first — most guests will.

If you have more than one location, you can now manage them all from the same account: each has its own site, its own hours and its own menu, completely independent. One login to see and edit everything.

Set your exceptional closing days directly in the workspace — public holidays, summer break, renovations, annual closure. The open/closed status on your site updates automatically on the day, with no manual switch or risk of forgetting.

Upload and organise your dish photos directly from the workspace. They appear on your site immediately, optimised for fast loading on mobile. No FTP or developer needed — drag, drop, done.

Darius Pizza becomes the first restaurant to use WebOustaou in production. Their site is live, their menu updates in real time from the workspace, and customers are already ordering from the tables. A real restaurant, real customers — the best test there is.

You can now update your menu, reorder categories and change your opening hours without touching a single line of code. The WebOustaou management workspace works from any browser — desktop, tablet or phone — and changes appear on your site within seconds.

The first version of the restaurant website goes live. Menu, photos, opening hours, a map to find the place — everything a customer looks for when they land on your site, designed from day one to load fast on mobile. This is where it all started.