01
One editor, three ways to work
Click the words and change them. Or drag a block into a column. Or open the HTML. Same page, same file, no separate "advanced version" to graduate to.
- Content: click any heading, paragraph or photo and type over it.
- Layout: drag blocks onto a twelve-column grid, with a separate phone arrangement when you want one.
- Code: the tree view, the HTML of any section, and your own CSS.
- Which tier a person works in is a setting on their name, not a different product.
02
Your real openings, on the page
The availability block reads your actual sites and dates. A visitor sees what is free tonight without leaving to check somewhere else, and the calendar answers the first click instantly because the answer shipped with the page.
- Rates, site map, reviews and a book-direct button read the same live data.
- The numbers are baked in when you publish and refreshed quietly after the page has already appeared.
- Nothing on the page can point at another campground: the block is checked against the sites you own before it runs.
03
Start from the listing you already have
Your ResortTribe directory listing has your photos, your amenities, your rates and your season. We build the first draft of the site out of it, so the first thing you see is your campground, not a blank template.
- Photos come through the image pipeline on the way in.
- Amenities, hours, season, address and phone land in the right blocks.
- Import again later and you get a diff, not a surprise overwrite.
04
Photos you cannot accidentally break the site with
Upload the 5 MB picture straight off the camera. Every image is re-encoded to a size target rather than a quality setting, because the same photo is 48,552 bytes as a wide banner and 85,648 bytes as a tall hero at identical quality.
- AVIF first, with a WebP copy for older phones.
- Quality is searched per image until it fits the budget, instead of guessed once.
- Width and height travel with every picture, so nothing jumps as the page loads.
- Pasting an image address from somewhere else does not get around it: the rule is applied when the page is built, not when the file is uploaded.
05
Publishing that cannot half-happen
Publish writes a complete, finished copy of the site and then points at it. Nothing is ever partly updated, and going back to yesterday is one click because yesterday is still sitting there.
- Every publish is kept as its own version, with the byte sizes it measured.
- Rolling back restores the page and its stylesheet together.
- The published site is plain files on a fast network, with no application server in front of them.
06
Found, and readable to the machines doing the finding
Titles, descriptions, sitemap, robots and the structured data search engines read are generated from what is on the page. An accessibility check runs over the page you actually publish and fixes what it can safely fix.
- Structured data for the campground, the rates, the reviews and the questions.
- A WCAG 2.2 audit with real contrast maths, not a checklist.
- A plain-text summary of the site for answer engines and AI assistants.
07
Analytics and marketing tags, handled honestly
We do not refuse your Google Analytics or your Meta Pixel. They ship in a holder that loads after the page has finished being measured, and maps and videos are a still picture that links out until someone taps it.
- The demo site runs Google Analytics 4 and the Meta Pixel, both verified firing, and still measures 100.
- Before you add a tag we show you what it costs.
08
Other people, and other software
Bring in your daughter to write the copy and your web person to touch the code, each with their own sign-in and their own limits. On Studio, an API token lets your own tools or an AI assistant build pages for you.
- Owner, admin, editor and viewer: four roles, plainly named.
- What someone is allowed to do and what your plan includes are separate questions, and you can see both.
- Single sign-on from your ResortTribe account, so there is no second password.