-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
WIP: Initial Askama Book #332
Conversation
Thanks for your work! I guess this might make things easier to navigate. I'll take some time to play around with this. |
No worries! Let me know if I can help. I forgot to mention: I envisage this could be hosted with github pages or similar. |
Sorry for the slow cycle, but I really like the look of this. It seems like a big improvement compared to the linear documentation in the crate root. I suppose we should really prune the crate root docstring now as well as maybe make the README a bit more concise (in particular, link to the Debugging and Troubleshooting section in the book instead of having it inline). Would you mind doing that? Also, I'd like to tweak the order of the book's chapters to list Debugging before Configuration. |
I've flipped the order for the the summary/table of contents. In terms of referring to the book, did you have a URL In mind you want to host it on? Or should it simply just link to the markdown document in the |
I was going to set up GitHub pages after this merged. |
(Fixed the clippy issue on master.) |
So it should appear at https://djc.github.io/askama/ I guess (I don't have any experience with GitHub Pages yet, so will need to figure out how to make that happen from this). |
This has been merged. |
Ah all good. Apologies I didn't get to it sooner! I'm glad to see it's released though! |
As per twitter convo, here is a PR with an initial mdbook version of the documentation with a lot of the content copied from API inline docs.
You can view this with:
I'm not sure if this is an approach you'd like to take, and so examples could possibly be put back into the API doc itself. I have just found when using other templates (such as tera), it's good to have a reference that is searchable.