Homepage & Page Overrides
Taxo uses both shared section content and page-specific settings. Once you know which layer controls what, editing becomes much easier.
The three layers are:
- shared section content in
src/content/sections/ - page-level frontmatter in
src/content/.../-index.md - page composition in
src/pages/[...lang]/...
Shared Section Content
Homepages and many inner pages use shared Markdown files like:
src/content/sections/english/hero-section.mdsrc/content/sections/english/faq-section.mdsrc/content/sections/english/cta-section.md
If you change one of those files, every page using that section changes too.
Pages That Support Local Section Settings
Some pages pass frontmatter data into shared section components. Common examples are:
- FAQ page passes
faqSection - Contact page passes
contactSection - Team page passes
teamSection - Blog list page passes blog index data into
BlogLayout - Case studies list page passes index
optionsintoCaseStudiesListSection
FAQ example
faqSection: badge: "Frequently Asked Questions" title: "How Can We Help You?" searchPlaceholder: "Search Here..."Team example
teamSection: enable: true limit: falseIf A Frontmatter Block Does Not Change The Page
Some content files include example frontmatter blocks that only work when the page template uses them.
For example, the Services index file includes a servicesSection block, but
the Services list page does not use that block directly. If a frontmatter
change does not appear on the page, check the page file in
src/pages/[...lang]/ to see which section data the page uses.
Best Practice
- Want a global section change: edit
src/content/sections/... - Want a page-specific heading/search/limit override: edit the page’s
-index.md - Want to change which sections appear at all: edit the Astro page file