A Power Pages site is a tree of web pages, each rendered using a web template that defines its HTML structure, with Liquid markup pulling in dynamic Dataverse content.

Web pages

Each page has a URL path, a parent (forming the navigation hierarchy), partial content (the actual body), and a template that wraps that content with shared layout. Pages can also be restricted to specific web roles, controlling who can even see the page exists.

Web templates

A template is a reusable chunk of HTML, often shared across many pages (a product listing template, a case detail template). Templates use Liquid syntax — a templating language similar in spirit to how server-side templating works elsewhere — to loop over data, branch conditionally, and insert values.

{% if user %}
  Welcome back, {{ user.fullname }}.
{% else %}
  Please sign in to view your cases.
{% endif %}

The page designer

The modern Power Pages design studio provides a largely visual, component-based editor (similar in spirit to a website builder) for assembling pages from pre-built components, with the underlying Liquid/HTML still accessible for anything the visual tools don’t cover directly.

Liquid objects you’ll use constantly. {{ user }} (the signed-in portal Contact, if authenticated), {{ page }} (the current page’s metadata), and {% entityform %} / {% entitylist %} tags (which render forms and lists directly from configuration — covered next chapter) cover the large majority of real page-building work.