-
Notifications
You must be signed in to change notification settings - Fork 384
Converting to mdbook #53
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
Conversation
Fix title typo Add missing posts to the directory
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.
I tested it and I assume this PR might be outdated due to feature additions to mdbook
. I added a book.toml
in #111 and it basically does the same without any changes to the repository structure (besides the additions of a Readme.md
file for each subfolder/subcategory). So imho we could close this and continue work in #111 @marcoieni , your thoughts?
I close this in favor of #111 since I think that a lot of the work done for this PR is not required anymore with newer versions of mdbook. |
As discussed in issue#6, this PR tries to add rendering and testing support for the project with mdbook.
To maintain the current structure of the project while playing nicely with mdbook's building system, a dirty script was added into the project. Currently, just type
cargo run render
in the shell, the rendered pages would be ready for publishing in a subdirectory calledbook/
. Check it out on gh-pages.Currently two problems remains:
cargo run test
would fail,Hopefully both problems would be gone after their related PRs being merged into master.
Related: #51 #43