-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 can I have different "Edit this page" URL for each page #150
Comments
Hi! What you can try:
---
BookEditPath: your/path/here
---
And then if you plan to migrate fully to hugo - remove this change after. |
Also. I thought for some time to add nested menu support. Maybe that would solve your problem. There are 2 menus: |
So I just added it to master. But then realised that it would not solve your problem with collapsing menu 😞 So overwriting template I guess is the option. |
@alex-shpak thanks for your fast responses and supporting this project. It's awesome that you do that. Menu nesting is not a direct solution but it's cool that hugo-book supports it now 👍 I really don't want to patch my local copy of the theme. I simply build another customized site generator on top of hugo and hugo-book where I iterate each markdown file and add edit link on them. I can try to look at it & send a PR if you think hugo-book should natively support something like |
Well, you don't need patch theme itself but overwrite template with Hugo.
In this case you need only to watch theme changes for that specific file. As for adding |
There are also |
Thanks for all explanation, I learnt a lot today. I loved the solution with inject templates 👌. It seems to be the cleanest way, and makes the theme very extensible 💪. I decided to have the buttons on the top, right before the page content. I see that there's an I got it working by adding |
Cool 👍 I also added |
|
Background
hugo-book
metadata. In the end the script creates ready-to-gocontent/
andstatic/
folders.What I'm trying to achieve
Problem
BookRepo
andBookEditPath
The text was updated successfully, but these errors were encountered: