Leitvia

Documentation menu

Getting started

From a fresh WordPress install to a first page built from Leitvia patterns.

Requirements

  • WordPress 7.1 or later
  • PHP 8.2 or later
  • No other plugin. Leitvia Studio is optional and works with any block theme.

1. Install the theme

Leitvia is not yet listed on WordPress.org. Once it is, go to Appearance, Themes, Add New Theme in the admin, search for Leitvia, then install and activate it. With WP-CLI:

wp theme install leitvia --activate

Leitvia has no build step and no settings page. Everything is set in the site editor under Appearance, Editor.

2. Pick a style

Open Appearance, Editor, Styles. Choose one of the six variations: Warm Editorial, Swiss Editorial or Corporate, each light or dark. Color and typography presets change only one side. Each combination keeps all color pairs at WCAG 2.2 AA contrast.

3. Set up navigation

Edit the header template part and add your pages to the navigation block. Submenus open on click and work with the keyboard. Give the footer a navigation with all main pages, so visitors have a second way to find content.

4. Build a page from patterns

Create a page and choose the template “Landing page (no title)” for pages that start with a hero. Open the block inserter, switch to Patterns and pick a hero, then content, proof and a call to action. Each pattern description says when to use it. Replace the sample text and images with your own.

Avoid two sections with the same layout and background in a row. Alternate dense and airy sections, and use at most one accent-colored section per screen height.

5. Add Studio when you need it

Leitvia Studio follows the same way on the Plugins screen, or with WP-CLI:

wp plugin install leitvia-studio --activate

Studio adds a menu item Leitvia Studio with the Pattern Lab, token sets, the content model and settings. Run the accessibility check of a pattern in the Lab before you use it on many pages. Studio stores its data in core structures, so the site keeps working when you deactivate it.

6. Check your pages

The theme is tested, your content is not. Give every image an alternative text, use one h1 per page and no skipped heading levels, and write link texts that make sense on their own. Then publish the accessibility statement: the pattern “Accessibility statement” gives you the template.