> ## Documentation Index
> Fetch the complete documentation index at: https://vr-it-services-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> The six built-in front-page sections used when no page builder is active.

# Default sections

# Default sections

When your homepage is **not** built with a page builder, the theme renders six built-in sections. These are the fallback, not the recommended way to build a homepage.

![Screenshot: the default front page rendering hero, features, testimonials, pricing, CTA and blog sections](https://mintlify.s3.us-west-1.amazonaws.com/vr-it-services-pro/images/screenshots/default-sections-full-page.png)

## When these sections appear

The theme checks in this order:

1. If **Settings → Reading** shows your latest posts on the front page → it renders the **blog index** instead
2. If a static front page is set, the theme checks whether that page is builder-owned
3. Builder-owned with content → the builder's content, nothing else
4. Not builder-owned, or empty → **these six sections**

**How to use them deliberately**

They are a genuine safety net. If Elementor is deactivated or a front page loses its Elementor
data, your homepage still shows a complete, styled page rather than a blank screen. That is the
design intent.

## The six sections

### 1. Hero

> **Contains**
>
> An eyebrow label, a large headline, supporting copy, two call-to-action buttons, and a stat card.

> **Editing**
>
> `template-parts/section-hero.php` in a child theme.

### 2. Features

Four feature cards, each with an inline SVG icon, a heading, and a short description. The section carries the `#features` anchor — which is where the default header CTA button points.

> [!WARNING]
>
> **The feature card copy is placeholder text**, and two of the four cards share the same description. Rewrite all of it rather than adapting it.

### 3. Testimonials

Quote cards with attribution. Sample quotes only — replace them, and only use quotes you have permission to publish.

### 4. Pricing

Three pricing tiers with feature lists, carrying the `#pricing` anchor.

### 5. Call to action

A closing banner linking to your contact page. The destination comes from the **Secondary CTA URL** setting, so it is configurable without touching code.

### 6. Blog preview

Your three most recent posts, rendered by a separate query. If you have no published posts, this section is empty or hidden.

![Screenshot: the default sections rendered on the front page](https://mintlify.s3.us-west-1.amazonaws.com/vr-it-services-pro/images/screenshots/default-sections-sections.png)

## Why use these instead of a builder?

There are a few situations where the built-in sections are the better choice.

> **You do not want to install a page builder**
>
> The sections need no plugin at all. A site with the theme's own front page loads fewer assets than one built in Elementor.

> **You are writing all the content in code**
>
> If you are building a static marketing page anyway, editing a template part is more direct than assembling sections in a builder.

> **You are evaluating the theme**
>
> Activate the theme on a scratch site and you immediately see what it looks like with content in it, before making any decisions.

## Why most people will not use them

> [!WARNING]
>
> **The copy is hardcoded and generic.** Every headline, paragraph, testimonial, and price is written into the template files. There is no Customizer control for any of it. Making these sections yours means editing PHP in a child theme — which is a different skill from what a Customizer-based theme is for.

If you want a marketing homepage you can edit without code, use Elementor and the [demo pages](/templates/demo-pages.md). If you want no plugin at all, these sections are a reasonable starting point, edited in a child theme.

## Editing the sections

> [!WARNING]
>
> **Never edit these files in the parent theme.** They will be overwritten on the next update. Create a child theme first — see [Child themes](/developers/child-themes.md).

The section files live in `template-parts/`:

```text theme={null}
template-parts/section-hero.php
template-parts/section-features.php
template-parts/section-testimonials.php
template-parts/section-pricing.php
template-parts/section-cta.php
template-parts/section-blog-preview.php
```

Copy any of them into your child theme at the same relative path, edit your copy, and the parent theme's version is ignored. See [Template files](/developers/template-files.md).

**Hide a section instead of deleting it**

Wrapping a section's markup in a `false` conditional keeps the file present but stops it
rendering — easier to re-enable later than deleting the file.

## Customizing the CTA destination

The closing call-to-action section uses your **Secondary CTA URL** setting, so you can repoint it without code.

**Appearance → Customize → Vara SaaS → Layout → Secondary CTA URL**

## Related

> **[Child themes](/developers/child-themes.md)**
>
> Required before editing any section file.

> **[Demo pages](/templates/demo-pages.md)**
>
> The richer alternative with Elementor.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.