Skip to content

Build and configure website pages

Your website is the one part of BevWerk that strangers see before they decide to visit. Pages (/website/pages) is where you build it.

Managers can use the Published switch in website settings to control whether visitors can see the whole public website. When it is off, the site is hidden from visitors.

If Pages says you’re viewing the last loaded version, choose Reload. You can save again after Pages confirms it has the latest content for this location. If you have unsaved changes on any website tab, Pages asks before reloading, because reloading discards them.

A page is assembled from blocks rather than written as one long document. Each block holds a piece of content, and one of the blocks available to you can embed your live menu — which is what keeps the beer list on your public site tied to what is actually pouring.

That embed is the reason to build the page here rather than elsewhere. A menu pasted into an external site editor is correct exactly once.

Some settings belong to the whole site rather than any single page:

  • Website Title and Default Meta Data (Meta Title, Meta Description) — what search engines and link previews show. These are the words people read before they click.
  • Navigation — which pages appear as a Nav Item, and in what order.
  • Home Page Message — a custom message on the home page, useful for a temporary announcement you do not want to build a whole page for.
  • Social Media — your Facebook Handle and Instagram Handle.
  • Newsletter form URL — paste the HTTPS action URL from your Mailchimp signup form, including its u and id values; it must use a list-manage.com subdomain and the /subscribe/post path. If you collect signups through Toast instead, paste your Toast marketing signup page, such as https://www.toasttab.com/<your-restaurant>/marketing-signup. Leave it blank if you do not use a newsletter form. Do not enter an API key.

A page can be Activated or Deactivated. Deactivating is not deleting: the page and its content stay intact, they simply stop being public.

This distinction is worth using deliberately. A seasonal page, an event that has passed, or a page you are still drafting can all sit deactivated without losing the work, and go live again when the moment comes around.

The page preview renders the same content your visitors will get, including any embedded menu. Content is sanitized before it is stored and again before it is shown, so what survives into the preview is what is safe to publish.