Sections & Page Overrides

Sections & Page Overrides

Files: src/content/sections/english/ (and french/), page content files · Skill level: Beginner to edit, light code to add or move

A section is one full-width block of a page: a banner, a services list, an FAQ. Consultiz has three kinds:

docs/section-ownership.md in the theme lists every section component, its kind, its content file, and the pages that use it. How Consultiz Works explains the idea in full; this page is the practical reference.

Change A Section Everywhere

Edit its file in src/content/sections/english/ (and french/). Some files have comments that list their options. Change values, keep the keys and indentation.

Hide A Section

• Everywhere: set enable: false at the top of its section file.

• On one page: add its block to that page’s content file with enable: false:

  newsletterSection:
    enable: false

• On one page, for good: delete its line in the page’s route file in src/pages/[...lang]/.

Don’t delete a section’s content file while a route still uses the section.

Change A Section On One Page

Add a named block to the page’s content file, with only the keys you want to change. Objects merge key by key, lists replace the whole list, "" clears a value, and [] clears a list.

customersSection:
  title: "Our partners"

newsletterSection:
  title: "Tax deadlines and updates, once a month"
  submitLabel: "Sign up"

Copy the block name exactly. A misnamed block is ignored without an error. Values inside a correctly named block are checked by npm run astro-check and the build.

Page Blocks By Page

Each page reads a fixed set of blocks. A block only works on a page that renders that section.

Reusable Section Catalog

Every reusable section, its default content file in src/content/sections/<language>/, and the pages that show it. Variants of the same kind of section (two banners, three testimonial sliders) are separate components; see Section Variants.

Banners And Introductions

Services, Industries, And Solutions

Proof And People

The testimonial sliders read their quotes from src/content/testimonial/english/-index.md (the home and home2 lists).

Some sections have no page in the demo (for example the services slider, the process steps slider, and the video testimonial slider). They are listed in Section Variants.

Client Logos And Rating Badges

The demo client logos are invented wordmarks, and the rating badges (“4.9, based on 12,456 reviews”) use a neutral icon, /images/icons/rating-badge.svg. Both are samples to replace or remove:

• Logos: the list in src/content/sections/english/partner-marquee.md (src, alt, and an optional href), and the servicePartners list in src/content/homepage/english/tax-accounting.md. Only show clients who agreed to it.
• Ratings: googleReview in partner-marquee.md and in the servicePartners block, rating in about-centered.md, the rating in feedback-section.md and testimonial-video-showcase.md, the icon of each quote in src/content/testimonial/english/-index.md, the ratings in solutions/english/-index.md (detailDefaults), and intro in careers/english/-index.md (rating, reviewText, ratingUrl, ratingLogo).

Show a rating only if your firm really has it on a review platform. Then use that platform’s own logo as the icon (icon, iconAlt, or ratingLogo), your real score and review count, and a link to your profile there (url or ratingUrl, which also accept a page path on your site). Otherwise set enable: false (for example googleReview: { enable: false }) or remove the block.

Articles, FAQ, Contact, And Calls To Action

Site-wide files in the same folder: home-header.md (Header), footer-newsletter-grid.md (Footer), cookie-consent.md (Cookies & Analytics), and company-page.md, which holds the content of the /company/ page.

Preview Sections In Lists

Sections that preview a collection (solutions, articles, portfolio, industries, team) take options.limit:

This is separate from the page size of the collection’s own list page.

Add A Section To A Page

This is a small code edit in the page’s route file:

1. Import the component at the top, between the --- lines:

   import FaqCentered from "@/components/sections/faq/FaqCentered.astro";

2. Place it where you want it, inside <Base>:

   <FaqCentered />

3. To give it page-specific content, pass a block from the page file. Use a block name the page’s schema already knows (see sectionsSchema in src/sections.schema.ts):

   <FaqCentered content={entry?.data?.corporateFaq} />

Building a brand-new section is a developer task: follow section 5 of NEXTJS-TO-ASTRO-GUIDE.md in the theme (component, Markdown defaults, schema, route).