3 ms·
Yup - it's not that difficult either. This repo of mine is about 90% of the way there (though it doesn't use this library, it uses the same method): https://gi
by swanson 15y ago
Yup - it's not that difficult either.
This repo of mine is about 90% of the way there (though it doesn't use this library, it uses the same method): https://github.com/swanson/lanyon https://github.com/swanson/lanyon
There are some caveats: you need to register an OAuth app to get access to CORS and you have to use basic auth.
- neilparikh 15y agoJust one quick question, why not just make the gh-pages branches in your project the main branch instead of master, so it would show that branch right away when you visit you project. Otherwise, it looks like a great project, and I might use it with my Jekyll blog.
- vinodkd 15y ago+1 to the switch gh-pages comment. Typically 'master' is where the code is and 'gh-pages' is where the pretty docs are. In your case everything is in gh-pages. Either maintain the code in master and "deploy & display" it on the gh-pages branch or just make gh-pages your master. come to think of it, that's what i should do with some of my repos ;)