Skip to main content

​
Page templates

Vara SaaS ships one page template, plus the option to add your own. Screenshot: the Page Attributes panel in the page editor showing the Template dropdown

​
Page Builder Full Width

Admin path: Edit a page → Page Attributes panel in the sidebar → Template Selecting Page Builder Full Width switches that page to a bare content canvas. This is the template assigned to the four imported demo pages.
Assign it to a page with content. With no content, the page renders as an empty canvas with just the header and footer. The theme will automatically generate a homepage layout for a front page using this template if it finds none, but that behaviour is specific to the front page.

​
Choosing between the two options

​
Creating your own template

Any PHP file in a child theme with the right header becomes a selectable option.
  1. Create a file at wp-content/themes/your-child-theme/templates/landing.php
  2. Add the template header as three comments at the very top of the file
  3. Add your markup below it
get_header() opens <main id="site-content"> and get_footer() closes it. Your template must not open another <main> — two main landmarks on one page is exactly the accessibility bug this theme works to avoid. Check your markup if the page looks visually correct but fails an accessibility audit.

​
How templates map to pages

WordPress picks a template using its standard hierarchy, which Vara SaaS follows.
A page’s assigned template overrides the hierarchy for that page. page.php still governs pages left on Default Template.
Screenshot: a diagram of the WordPress template hierarchy used by the theme

​
The fallback template

index.php is the last resort. It renders a plain container with an optional sidebar and a simple post list.
index.php uses an h1 for every post title. On an archive rendering ten posts, that is ten h1 elements — an inconsistent heading outline compared with the theme’s other archive templates, which correctly use one h1 in the hero plus h2 and h3 in cards.It rarely renders in a normal install, because home.php, archive.php, and search.php cover those cases. But it can render if a plugin registers a custom archive the theme does not handle, and it would fail a heading hierarchy audit. If you build a child theme, replacing index.php with a correct outline is a worthwhile fix.

Template files

What each template renders, and how to override it.

Demo pages

The pages that ship with the theme.