-
Notifications
You must be signed in to change notification settings - Fork 2
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
Support menu text attribute #3
Conversation
Hey @alwaysblank Can this be merged into staging so I can test https://app.zenhub.com/workspaces/hm-playbook-607442e6aab6bf000ecd201d/issues/humanmade/hm-playbook-theme/472? Anything holding this up? |
@CoreyBenefiel This wasn't merged in because of the following:
In my opinion I think you could probably merge all the PRs on this repo and things will be fine, but I wouldn't recommend doing some without having an engineer look at the points mentioned above first. |
Hi, @CoreyBenefiel and @alwaysblank, as far as I remember, the plugin needed to be tested and confirmed it does the job for the new Playbook design. Then the initial PR #1 should have been reviewed and merged, but that never happened 🤷♂️. Since the plugin is not used anywhere else, I think it's save to merge everything into |
The pointer of this repo was set to the branch The change that this PR includes affects only using a menu title if editor specified it.
https://github.com/humanmade/hm-table-of-contents-plugin/pull/3/files I tried testing this feature to see if it does the job. Could not find it in a walk-through and could not also find any information about how to test it. @CoreyBenefiel could you describe how can I test the |
@MiguelAxcarHM Did you look at the relevant PR on the playbook theme repo? https://github.com/humanmade/hm-playbook-theme/pull/472 Without that merged, this PR won't do anything. |
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.
It works as expected.
Absolutely smashed this one out of the park @alwaysblank @MiguelAxcarHM. I expected I would need to manually remove the content menu block from individual pages over time, but I can see this feature not only works for new content but also works for legacy content AND deprecates the block. Awesome! Thank you. |
This adds conditional support for defining a "menu title," i.e. a different title for the heading that will be used in other locations (i.e.e a ToC or the local nav widget).