Open
Conversation
Owner
|
Sorry, left this out. Completely unsure what to do about this. I do like the idea of moving to markdown, and maybe moving them back to the main tree. Tried pandoc instead, but that requires way more scripting that current gh-pages to get anything usable. Github apparently has some Jekyll integration but it's not clear it's going to be any better. Merged into https://github.com/arsv/perl-cross/tree/mkdocs for now. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MkDocs is a great tool, see http://www.mkdocs.org
write the documentation source (Markdown) in
masterbranch:mkdocs.yml
docs/*.md
generate & push the generated stuff (HTML, ...) in
gh-pagesbranch:$ mkdocs gh-deploy --clean
see the result in my fork at https://fperrad.github.io/perl-cross/