Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature to allow editors to provide descriptive metadata for taxonomy terms #1858

Closed
hughbris opened this issue Feb 5, 2018 · 2 comments
Closed
Labels

Comments

@hughbris
Copy link
Contributor

hughbris commented Feb 5, 2018

I'm going to look into whether I can figure this out. It was "suggested" by a question in Slack a few days ago.

Could we provide a way to show a custom page for specific taxonomy terms? Presently, a route like animals:cats will typically show a list of items matching that term. (It's still a bit magic to me, but it seems the Page class populates the page's collection with page items matching the term(s)). We would want the page showing that list of matching pages to be able to show extra information about the term (a paragraph about cats, for example).

@hughbris
Copy link
Contributor Author

hughbris commented Feb 5, 2018

In practical more general terms, this means providing a mechanism to expose extra information about the term to the templates. Populating the term tree should be sufficient to achieve this.

For sourcing the metadata, I am going to look at using a filesystem pattern similar to those used for media metadata, media thumbnails, and language files. So a file like user/pages/taxonomy/animals/cats.md might contain our info in YAML frontmatter and Markdown. It could also be 'user/taxonomy...oruser/config/taxonomy...`

@hughbris
Copy link
Contributor Author

hughbris commented Feb 8, 2018

Been thinking about the modifications required for this to work. It's pretty much an extension to the taxonomy class with few or no changes to existing code. Apart from its discreetness, am thinking I'll build this as a plugin to start with because:

  • too much uncertainty over fitting new code in with existing core "architecture" and style
  • I know major changes are afoot for G2 taxonomy

Comments on this direction welcome of course, but I would appreciate if this isn't closed in a rush while I explore that option more fully :)

@mahagr mahagr closed this as completed Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants