MOWP 2026 Docs

Automatic Behavior

what the site handles on its own, on save, on publish and on a schedule

Some of the site's work happens on its own, on save, on publish and on a schedule.

Addresses and redirects

  • An address is built, not typed. A page's address comes from its parent and its slug. Change either and the address changes with it.
  • Moving something published leaves a forwarding rule. Pages, news posts, events and campaigns all do this, marked Added automatically in the Redirects list. Published pages underneath a moved page move too, and each leaves its own rule.
  • Campaign rules are temporary. Campaign addresses come back around. Everything else forwards permanently.
  • Moving back clears up. The rule a move left is removed, and deleting something removes the automatic rules pointing at it.
  • Two things can't hold one address. A page, campaign or redirect that would collide with something already there is refused at save, with a message naming what's in the way.

Drafts, versions and publishing

  • A draft is a 404 to the public. It takes a CMS login or a share link to open one.
  • A share link lasts 14 days. It needs no login, and opening the page in the editor mints a fresh one.
  • Draft views are marked. A band sits across the bottom of the page, and signed-in staff also get the editor pill in the top bar.
  • Every save keeps a version. Who saved it, and when.
  • Every save clears the cache. Pages, posts, events, campaigns, dining centers, redirects, forms, navigation and site settings. There's no flush step.

Headings, images and files

  • Heading levels come from where a block sits. Never from a setting. Rich Text offers h2 to h4 and nothing else.
  • An image needs alt text to save. The Decorative — nothing to describe tick is the other answer, and renders an empty alt.
  • Uploads are resized on the way in. Thumbnail and card versions, with the media list showing each file's type in plain words.
  • SVGs are read before they're stored. One carrying a script or an event handler is refused with a message saying so.

Search and sharing

  • Every page has a share image. The one uploaded to the page wins, then the default in Site Settings, then a generated card carrying the organization's name.
  • The canonical address is the page's own. There's no field to override it.
  • Hide from search engines marks the page noindex. On pages and campaigns, and it drops the page from the sitemap too.
  • Structured data is emitted only where the facts exist. The organization, breadcrumbs, news posts, events, dining centers with their opening hours, FAQs and job openings. An event with no venue or start date emits none.
  • The sitemap, robots.txt and site search rebuild from what's published.
  • The SEO panel stays quiet unless something's wrong. No meta description, a title or description long enough to be cut off in a result, a share image under 600 by 315, or the page hidden from search.

Forms

  • Every form carries a hidden field that bots fill in and people don't. A submission that fills it is accepted and thrown away.
  • Turnstile checks the visitor where an admin has switched it on, verified on the server rather than in the browser.
  • The server validates against the stored form, not against what the browser sends. Required fields are enforced, choices are checked against the stored options, and anything the form doesn't define is dropped.
  • Five submissions a minute from one visitor, then the form stops accepting.
  • A notification email goes to the address in Site Settings as each submission arrives.

Refreshes and expiry

  • Dining center addresses are geocoded on save, and again whenever the address changes. An address that can't be found says so in the sidebar with the date, and Lat and Lng can be typed in by hand.
  • Opening hours are written into a sentence from the schedule.
  • Job openings are read from Paycom every six hours, full descriptions included. When Paycom can't be reached the block serves the last set it read.
  • Affiliation marks stop showing the day after they expire.
  • A campaign that has ended forwards to the donation page.

The CMS dashboard works its launch checks out fresh on every visit rather than reading back a list somebody ticked. Going Live covers what it looks for, and what still needs a person.

On this page