Skip to content

Don't make draft/future/expired pages of branch nodes recursively disabled #11809

@bep

Description

@bep

This will be a breaking change for some, but it's meant well -- the current behaviour of special handling taxonomy pages is confusing and less flexible than it could be.

Currently, when we draft a taxonomy page (or e.g. mark it to be published in the future or it's expired):

categories/_index.md:

---
title: "The Categories"
draft: true
---

Content.

We hide the entire tree from /categories and down.

The original intent/semantics of draft was to delay publishing of that particular page/content, so with this change we make kind=taxonomy work the same as sections. So, we say:

  • For regular pages (leaf nodes) and term pages, the Page it's just removed/ignored.
  • For home, section, taxonomy
    • we keep the Page node to make the page tree fully navigable.
    • the Page is not rendered and not in any page collection.
    • but you can reach it with site.GetPage (and the taxonomy in site.Taxonomies).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions