Skip to content
Type something to search...
Taxo Theme Documentation

Hide Pages And Sections

There are several ways to hide content in Taxo. The right one depends on whether you want the change on one page, one collection item, or the whole site.

1. Hide A Shared Section Everywhere

Edit the shared section Markdown file and set enable: false.

src/content/sections/english/cta-section.md
enable: false

Use this when the section should disappear on every page that uses it.

2. Hide One Item Inside A Section

Many section lists also support enable: false at the item level:

list:
- enable: true
title: "Basic"
- enable: false
title: "Enterprise"

This pattern appears in sections such as:

  • pricing cards
  • FAQ items
  • team members
  • features

3. Hide A Menu Item Only

If the page should still exist but should not appear in navigation:

{
"enable": false,
"name": "Pricing",
"url": "/pricing/"
}

4. Hide A Single Page From Production

Set draft: true in that page or collection entry:

---
title: "Privacy Policy"
draft: true
---

For collection entries such as blog posts, services, and case studies, Taxo filters draft items out in production.

5. Hide An Entire Collection Temporarily

If you set draft: true in a collection -index.md, Taxo will hide the list page and related generated pages in production.

Examples:

  • src/content/blog/english/-index.md
  • src/content/services/english/-index.md
  • src/content/case-studies/english/-index.md

6. Hide A Section On Only One Page

Do not set the shared section file to enable: false if the section should stay visible elsewhere.

Instead, edit the page file and remove that render call:

src/pages/[...lang]/index.astro
<HeroSection />
<FeaturesGrid />
{/* Remove or comment out this line for this page only */}
<ServicesSection />

7. Use Page-Level Section Overrides

Some inner pages pass section data from frontmatter into shared components. That lets you disable a section only on that page:

src/content/team/english/-index.md
teamSection:
enable: false

This works because TeamSection.astro merges page overrides with the default section content.

Quick Rule Of Thumb

  • Want to hide it everywhere: change src/content/sections/...
  • Want to hide it from menus only: change menu.*.json
  • Want to hide one page in production: use draft: true
  • Want to hide it on just one route: edit the page file or use a page-level section override