Skip to content

Front matter meta should override .meta.yml defaults  #6914

@rachel-rigdon-sp

Description

@rachel-rigdon-sp

Context

I am adding a Discourse comments section to our documentation. I've set the .meta.yml to comments: true and placed it in our docs/ folder, which successfully applied the comments.html override with the Discourse code to all pages in the folder.

However, there are some pages within the folder (like our main index.md) that we don't want comments on.

I've tried excluding them using meta formatting at the top, like:

--- comments: false --- 

I've also tried comments: hide and comments: exclude on the individual page, to no avail.

Description

Make the front matter you set on individual pages override the defaults in the .meta.yml

Related links

Use Cases

Author's:

  • Have more fine-grained control over which pages should include/exclude comments, tags, and blog configurations by prioritizing the front matter over the .meta.yml defaults.
  • Be able to include/exclude features without creating a hook.

User's - Will only see features that are useful for specific pages, which can declutter docs and direct focus to the right content.

Visuals

No response

Before submitting

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue reports a bugresolvedIssue is resolved, yet unreleased if open

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions