Understanding PageBuilder's Approach

PageBuilder is a dynamic rendering engine that lets editors assemble and edit the ways that content is displayed throughout their site. For many publications, that's a lot of content, across many, many pages.

PageBuilder's approach to handling this diverse array of content is very straightforward. PageBuilder thinks about content in two different ways:

• Pages, which are typically curated and live at a single URI
  • An example of a page might be the homepage, which is a single, curated page that can be accessed through /homepage.
  • An example of a page might be a one-time restaurant guide that is hand-curated by an editor and has a URI of /2016-restaurant-guide.
  • An example of a page might be the News section front, which is accessed through /news, the top stories on which are manually curated by the news editor.
• and Templates, which are typically determined by URL routes and can render many different pieces of content.
  • An example of a template might be an article template, which is set up once by an editor but can render many different articles.
  • An example of content rendered via a template might be the sub-sections of a main site, such as /news/city or /news/politics, which are driven by feeds and are constantly up-to-date with the latest stories.
  • Other common templates include:
    • Search pages
    • Tag pages
    • Author pages

To access your list of pages and templates, simply click the "PAGES" or "TEMPLATES" button in the upper left-hand corner of the main PageBuilder admin. Since your local environment is brand new, you won't see any pages or templates here—yet.