generate TOC without custom jekyll plugin#25838
Conversation
|
Like I have said numerous times, I'd rather not do this. Using GitHub pages is useless in our case. |
|
This is your opinion, with a project with 60k forks and a maintainer working at github this responsibility may be different. The goal should be to make the setup easy for each contributor, no matter if html beginner, dev expert or theme designer. github pages helps to visualize quick results with a easy setup. This is a request and was just easy to achieve, I've wanted to point this out. ✌️ |
|
Again, it's not my point of view; it's how we use GitHub pages. We have the old docs there too, which aren't present in the branch here. Anyway, I give up on this. To me, all this is futile. Nor have you pasted any numbers from all these changes, positive or negative. Off to @mdo. |
|
📊 Jekyll's build-in Liquid profiler generates: Sadly, custom plugins are not detailed listed. I could only compare the total build time: jekyll-doc branch –
|
3eb4c81 to
d897122
Compare
|
Hey @mdo 👋 Are you interested in this change? Just asking, if it's worth the work to keep it up-to-date with |
9c7e907 to
fe68d72
Compare
|
@mdo: what do you want to do with this one? |
|
@XhmikosR Seems like we should close this one given your ToC work? |
|
Let's leave this open for now. It'll be moot anyway with Hugo. |
6cabb70 to
03bc0d5
Compare
* remove toshimaru/jekyll-toc gem
* use h5 and h6 headlines inside callouts * h5 and h6 by default are excluded by toc generation
* possibly added by false resolving a merge conflict
|
Closing this since we are going to switch to Hugo. Thanks for the patch though. |
toshimaru/jekyll-tocI've checked generation of every site, it works like a charm 👌
This is the final 🏁 PR wich removes custom plugins from
bootstrap docs and enable first-class support for github-pages 🙌
🔗 #25784
🔗 #25319
🔗 #25320
Hope you like it. 🖖
/cc @allejo