-
Notifications
You must be signed in to change notification settings - Fork 163
Use Pretzel and Github Pages for Pretzels own doc's. #350
Comments
Nice idea, I wanted to improve the site that is already using github pages on the gh-pages branch but haven't thought of adding the docs. |
I agree to move the generated site source to a It is possible to create and push a commit from AppVeyor, I already do something similar for some of my sites. |
Do you really want to make a repo? Or did you ment folder?
👍 |
Folder, sorry. |
Is github pages enabled? It kinda has to be, cause http://code52.github.io/pretzel redirects to http://code52.org/pretzel/ |
Of course it is cause there it's https://github.com/Code52/code52.github.com |
Which isn't built with pretzel on it's own, what an irony 😆 |
Yep it already is, using the Well, github use Jekyll to generate the site so this is a good opportunity to check the equivalence with pretzel :) |
But as far as i tested if there is a organization gh-page it's not possible to use gh-pages for the repositories :/ |
Well github says that it is possible:
|
To be sure, we just have to modified the gh-pages branch in pretzel repo (like adding an html comment) and see if it appears on http://code52.org/pretzel/ :) |
I don't even know where this comes from 🤷♂️ I just looked into the repo and can't find a clue where this lives or where this does come from... |
I have switched the github pages settings to use the |
Does this work on your side?
seams like it still redirects to the old page? |
The url won't change, github page is configured to serve it to http://code52.org/pretzel/ |
Awesome! |
Apart if we need to use some specific plugins, since github pages use Jekyll it is a good way to check that we have parity with jekyll (at least for functionalities used by the docs). |
We could do some kind of snapshot testing for that? |
That's a good idea, but it will need a thorough followup on each jekyll release. |
It would be cool if we could use GithubPages and pretzel it self to build the documentation.
This way it would be possible to contribute to documentation and help without the need of githubs wiki system.
Proposed solutions:
_docs
(or something similar) and output the site todocs
.The only disadvantage of this is, if we change the documentation, we need to build the site with pretzel and checkin the content's of
docs
folder by hand (or create an automated commit on the current branch on Appveyor, but I don't know if this is possible?)Use a seperate repository like explained by Devon Burriss
But working with
submodules
is so painful...This will address #141
The text was updated successfully, but these errors were encountered: