[{"data":1,"prerenderedAt":64},["ShallowReactive",2],{"landing-chrome-en-published":3,"landing-marketing-landing\u002Ffeatures\u002Fdocuments-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,"how_title":33,"not_title":34,"how_points":35,"description":49,"detail_shot":50,"feature_slug":51,"problem_body":52,"output_points":53,"outputs_title":62,"problem_title":63,"meta_description":49},"a2f378fa-1431-4bc6-bec6-299895f2545c","Event document templates | managemyrestaurants.events","Guest paperwork and kitchen paperwork from the same event","Start a 14-day free trial","Not a full document library, and not e-signature. It is reusable templates filled from this event and this client.","landingFeaturePage","Empty for now. Split or two tabs: a guest-facing document and a kitchen-facing document. Same event name in both headers. Show placeholders such as client.name on the template side. No hotel-first headline in the UI chrome.","How you use it","What this is not",[36,41,45],{"_uid":37,"title":38,"component":39,"description":40},"d3871d345ba09c4b","Write the template in the editor","landingStoryPoint","One template for the guest packet, another for the kitchen — or as many as you reuse. The layout can differ. The data should not.",{"_uid":42,"title":43,"component":39,"description":44},"234a4b5d9365f113","Drop in placeholders","Fields such as client name, event date, and totals pull from the event and client record when you generate the document.",{"_uid":46,"title":47,"component":39,"description":48},"f27f08c37a777686","Generate from the event, not from a blank page","Pick the event. The template fills. You edit the exception, not the whole packet.","Write the template once. Placeholders fill from the event and the client. Two layouts can share the data without sharing the look.","Empty for now. Template editor with visible placeholder chips (client.name, event.date) and a preview of filled output. Neutral product UI — not branded for a hotel or a restaurant chain.","documents","Documents are templates that fill from the event and the client. You write the layout once — a confirmation, a kitchen packet, whatever you reuse — then generate it for this booking instead of copying last week’s PDF and hoping the date is right.",[54,58],{"_uid":55,"title":56,"component":39,"description":57},"ddd5fa280240c879","A version the guest can see","Confirmation, menu presentation, event details — filled from the booking, not retyped.",{"_uid":59,"title":60,"component":39,"description":61},"80d4d469c34d1876","A version the kitchen can use","Internal notes, quantities, timing. Same source fields, different template.","What you have when you are done","What this is for",1788634271801]