-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
How to enable by default for all pages #116
Comments
I'm just a casual user, but I had the same sort of issue. Setting defaults:
-
scope:
path: ""
type: "integrations"
values:
toc: true If this doesn't help, it might be worth setting up a separate repo with a minimal use-case, to make sure it isn't something outside this plugin that is messing with things. Looking at the code you linked to, you seem to be missing the required
source: https://jekyllrb.com/docs/configuration/front-matter-defaults/ Not sure if that is mesing anything up but it might be worth fixing. |
@Potherca this worked! Thanks a lot for this ❤️ |
Hey @Potherca :) Thanks for helping out 😉 |
* Remove features from test_files * Modify description * {% toc %} tag / toc_only filter * Move "Default Configuration" to the customization section * Add _config.yml * Refine English * Add " Alternative Tools" * Update TOC * Update README.md * Update TOC again * Add "Enable TOC by default" closes #116
I've added Enable TOC by default section to README. 👍 https://github.com/toshimaru/jekyll-toc#enable-toc-by-default |
Hi! Thanks for the plugin! How is it possible to enable this by default for all pages? Here's a PR where I'm trying to enable this for some pages https://github.com/home-assistant/home-assistant.io/pull/13572/files.
In short:
{% toc %}
since this is applied in an aside.toc: true
is defined in the_config.yaml
defaults .Still, the ToC doesn't appear. If I set it explicitly in a page's frontmatter, it works, but I want to avoid that though since there are 1000+ pages this should be applied to.
Any help would be appreciated, thanks!
The text was updated successfully, but these errors were encountered: