[{"data":1,"prerenderedAt":59},["ShallowReactive",2],{"landing-chrome-en-published":3,"landing-marketing-landing\u002Findustries\u002Frestaurants-en-published":25},{"header":4,"footer":7},{"loginButton":5,"getStartedButton":6},"Log In","Start 14-day free trial",{"companyDescription":8,"product":9,"support":16,"copyright":20,"legal":21},"Plan menus, assign staff, track every task, and auto-generate documents -- from one dashboard where everything connects.",{"title":10,"links":11},"Product",[12,13,14,15],"Features","Demo","Pricing","Blog",{"title":17,"links":18},"Support",[19],"Contact","All rights reserved.",{"privacyPolicy":22,"termsOfService":23,"cookiePolicy":24},"Privacy Policy","Terms of Service","Cookie Policy",{"_uid":26,"title":27,"heading":28,"cta_aria":29,"not_body":30,"component":31,"hero_shot":32,"not_title":33,"description":34,"detail_shot":35,"problem_body":36,"industry_slug":37,"problem_title":38,"outcome_points":39,"outcomes_title":57,"features_heading":58,"meta_description":34},"06b97a1a-e83a-4d9d-a3c0-3cd2c22e1f34","Restaurant event software | managemyrestaurants.events","Private dining and in-house events, on one booking","Start a 14-day free trial","Not a POS, and not inventory. Hotels and banquet halls have their own pages. The homepage is still the overview of the whole product.","landingIndustryPage","Empty for now. Product UI: one restaurant event with client and date prominent; menu, timeline, and documents attached. Private-dining context — tables, not a hotel ballroom. Desktop, light UI.","What this page is not","Birthdays, corporate dinners, and other restaurant events. Put the menu, timeline, tasks, and documents on the event so office, kitchen, and floor are looking at the same plan.","Empty for now. Split frame: left = guest-facing menu or timeline; right = kitchen shopping list or kitchen document. Same event title in both headers. Restaurant service, not a hall wedding.","This page is for restaurant teams who run events in their own dining room. If the office has the email, the kitchen has a spreadsheet, and the floor has a chat screenshot, those pieces can sit on one event instead of three versions of the same night.","restaurants","Who this page is for",[40,45,49,53],{"_uid":41,"title":42,"component":43,"description":44},"ccc6b70d0c6771ae","One event for office, kitchen, and floor","landingStoryPoint","Client, date, and status live on the event. You attach menus, timelines, tasks, and documents when the booking needs them.",{"_uid":46,"title":47,"component":43,"description":48},"7dbbbd27055c5651","A shopping list from the menu you already built","Meals and drinks sit on the event menu. Ingredients roll into a shopping list, so the order is not a second spreadsheet.",{"_uid":50,"title":51,"component":43,"description":52},"fa63ccd44ffa0cc1","Guest paper and kitchen paper from the same fields","Templates fill from the event and the client. The packet for the floor and the packet for the kitchen stay in step.",{"_uid":54,"title":55,"component":43,"description":56},"047bf25787e567fb","A staff login that is not the office file","Kitchen and floor open the event from a staff login. They get the menu and the timing. They do not get the client or the prices.","How restaurants use it","Features you will use",1788634273394]