PageWebPro
Make the site. Take the bookings. Get paid. A website platform where the business machinery is part of the product, and where an AI assistant can do the work instead of you.
A website is
rarely the job.
The job is a table booked, a ticket scanned at the door, an order paid for, an enquiry that reaches a person. Most site builders stop at the brochure and sell you four more subscriptions that do not know about each other.
Four logins, one business
Site here, bookings there, tickets somewhere else, payments in a fourth place. Nothing reconciles, and the owner is the integration layer.
Embeds are slow and ugly
Third-party widgets arrive as iframes with their own fonts, their own colours and half a megabyte of script. The page you designed is not the page that loads.
Nothing is scriptable
Editors are built for a mouse. The moment you want an assistant, a bulk change or a hundred locations, you are back to copy and paste.
So the modules are part of the product.
Six modules,
one set of records.
Each has its own settings and its own data, and each renders a widget the published page draws at runtime. They are not add-ons; they are why the platform exists.
Forms
Validation, file uploads, spam protection, stored submissions and an email to a real inbox. The delivery half and the field half are edited separately, so a form can be restyled without breaking where it goes.
Bookings
Restaurant tables, rentals, appointments. Set out what you offer, who or what can do it, and when. Guests book, reschedule and cancel themselves, and you can take the deposit up front.
Tickets
Events with occurrences and tiers, sold through the same cart as products, checked in at the door by QR. Availability is fetched live rather than baked into a cached page.
Shop
Physical, digital and subscription products, a cart, and a checkout that takes iDEAL and cards. Orders land in one place, next to the bookings and the enquiries.
Content
Define a content type, get a listing, a detail template and locale-aware URLs. Translations are scanned and managed per string, with machine translation available for a first pass.
Analytics
Cookieless visitor measurement, first-party, no consent banner required for the basics. You see traffic without handing it to somebody else first.
Three jobs,
start to finish.
Illustrative jobs rather than customer case studies. We do not publish a client's work without their name on it, so these are written from what the product does.
Friday night at a bistro
The site takes bookings all week. On Friday the kitchen sees the covers on one screen, the deposits are already paid, and the two tables that cancelled at four freed themselves up without anyone answering the phone.
The owner logs into one thing, and gets one bill at the end of the month.
A gallery opening, 90 places
Tickets sell on the same page as the prints, in the same cart. On the night they are scanned at the door from a phone.
One list of who is coming, one place the money lands, and no separate ticketing platform taking a cut of a 90-seat evening.
An agency looking after forty client sites
Holiday opening hours need to change everywhere. Instead of opening forty editors, someone asks for it once and gets a screenshot of each site back to approve.
The same afternoon, not the same fortnight.
An editor a
machine can use.
Ask for a change in a sentence and get it, including the work a builder normally hides behind a mouse. This is not a chat box bolted onto an editor. The assistant does the same job an editor does, and you undo it the same way.
Change the opening hours on forty locations, retitle a hundred pages, or translate a whole site, without opening any of them.
It renders the page and sees the result at phone, tablet or desktop width, so it checks its own work before you have to.
Every site keeps a shared set of notes that people and assistants both write to, so the next session starts knowing how this site was built and why.
Pages and layouts, images and fonts, content and translations, forms, bookings, events, products and orders. If you can do it in the editor, it can do it.
The site you are reading was made this way. The pages, the design, the words, the navigation, and the screenshots used to check the layout at each step.
Nothing here used a private back door. If it can build a site like this one, it can look after a customer's.
The heavy editor
never leaves the studio.
The editor never reaches the visitor. What gets served is a plain page, which is why a menu opens quickly on a phone with one bar of signal, and why search engines are happy to read it.
Custom domains sort out their own certificate. Sitemaps look after themselves. The parts most people forget are the parts you should not have to think about.
Pages are light by default. You do not have to buy the score back later with a plugin.
Your own domain on every plan, with the certificate handled for you.
Upload once and every visitor gets the right size, without the page jumping around while it loads.
More than one language per site, with a machine first pass you can correct, and the right version shown to the right visitor.