-
Couldn't load subscription status.
- Fork 305
Add support for title_category #517
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
Conversation
e0932ca to
9f378ad
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks really good. I appreciate the documentation and test updates here as well. I left one suggestion. Let me know what you decide to do with the suggestion and I can proceed from there.
Thanks for contributing! ❤️
Co-authored-by: Matt Rogers <mattr-@github.com>
Co-authored-by: Matt Rogers <mattr-@github.com>
|
Should we proceed with the merge @mattr-? |
|
@jekyllbot: merge +minor |
|
Thank you for the merge @mattr-! Do you think that it's a good idea to release v2.9 to rubygems.org now? There were a few other features and improvements added to this gem since the last release in 2022 and a new release would make them more easily accessible downstream. |
|
There will be a release at some point soon-ish. I'm in the middle of reworking the release processes for nearly all of our gems, so it might be awhile longer. |
This PR is best described by the diff of the changes to
docs/advanced-usage.mdit includes.Personally I need it for a website that serves multiple longer texts divided into pages, like books divided into chapters. The currently generated
<title>and title SEO tags just aren't enough, they are lacking the crucial indication that some pages are parts of larger entities, but smaller than the entire website. I also think that it will be useful for other structured texts like documentations where the context of each page is important.