Site Structure
every page on the site, what it's for, and which phase it lands in
Eight pages once the space opens, plus the inquiry confirmation and a privacy page.
The sitemap
| Page | URL | Phase | What it's for |
|---|---|---|---|
| Home | / | 1, rebuilt in 2 | The pitch, the spaces, the primary action |
| The Space | /the-space | 2 | Capacity, dimensions, floorplan, AV, the deck, the video tour, accessibility |
| Catering | /catering | 2 | The in-house kitchen, menus, the bar and outside-caterer policy |
| Weddings | /weddings | 2 | The room described for a couple |
| Meetings & Events | /meetings | 2 | Corporate, nonprofit and community bookings |
| Celebrations & Memorials | /celebrations | 2 | Family milestones and services |
| Rates | /rates | 2 | The rate card, what a booking includes, deposits, the spec sheet |
| Check Availability | /availability | 2 | The inquiry form, the booking process, the FAQ |
| Inquiry received | /availability/thanks | 1 | Confirmation and response-time expectation |
| Privacy | /privacy | 1 | Required by the form. Its own page or a link to MOWP's |
If the phase-1 page goes ahead, it carries a compressed version of all of it, plus the confirmation and privacy pages.
The three phases
Testimonials, photographs of real weddings and a description of how a wedding day runs all need a season of events behind them, and the venue opens without one.
| Phase | When | What lands |
|---|---|---|
| 1 | Optional, undecided | One page, built from renderings |
| 2 | At booking-open | The eight pages above, on renderings and empty-room photography |
| 3 | After the first season | Gallery as a destination, testimonials, real-event photography, the roof deck as its own page if deck-only bookings materialize |
The event-type pages
Weddings, meetings and celebrations could be three sections of one page. They're separate so the same room can be described three different ways without contradiction. A wedding page talks about the deck at golden hour; a meetings page talks about the projector and the parking.
Capacity, rates and policies live on their own pages and are linked from all three. Restating them in three places is three places to update when a number changes. See what has to stay canonical.
They also help in search, but not immediately. See Search.
Where the roof deck lives
A section of The Space, not a page of its own.
The test isn't whether the deck rents separately; separate pricing is a column on the rate card. The test is whether anyone books the deck without the room. Cocktail hours and small receptions would justify a page; a deck that always comes attached to a booking is a section.
Ship it as a section, and split it out in phase 3 if deck-only inquiries arrive.
What has to stay canonical
The site's one structural discipline. Each of these lives in exactly one place and every other page links to it.
| Fact | Lives on | Everywhere else |
|---|---|---|
| Capacity by layout | The Space | Links, or renders a filtered view of the same record |
| What a booking includes | Rates | Links. The Space describes what the room has; Rates defines what a booking covers |
| Catering and bar policy | Catering | Links |
| Deposit, cancellation, insurance | Rates | Links |
| Address, parking and directions | Check Availability | Links. Footer and page badges point here |
| FAQ | One pool in the CMS | Pages render it filtered by topic, never a second hand-written list |
Capacity restated under different layout names, furniture listed on two pages or overlapping FAQ lists are each a number that changes in one place and goes stale in another.
What isn't here
- A blog. Nothing about a venue needs publishing on a schedule, and an abandoned blog is worse than none.
- A calendar of availability. See Scope.
- A team page. One named contact on Check Availability does the job.
- A gallery, until phase 3. Every page carries its own photography, and a gallery destination with no real events in it is visibly thin.
For how these sit in the navigation, see Navigation. For what goes in each one, see Page Outlines.