Closed marioseixas closed 11 months ago
You have to build your pelican blog locally, and upload only the HTML to your GitHub repo. GitHub will happily show your generated HTML.
You can even have two branches, one where you keep your sources, and one where you keep the generated HTML, if you really want to store the sources in the same repo. Or you can just open another repo for the sources.
You have to build your pelican blog locally, and upload only the HTML to your GitHub repo. GitHub will happily show your generated HTML.
You can even have two branches, one where you keep your sources, and one where you keep the generated HTML, if you really want to store the sources in the same repo. Or you can just open another repo for the sources.
Thanks!
I saw your git repo but seems that your sites are not made as you explained above.
Anyone has github repositories that did as above to maintain a site/blog?
This repo has just HTML (and of course CSS and other related files): https://github.com/DIPlib/diplib-docs It's served at https://diplib.org/diplib-docs/
I just re-build the web site locally, git commit
and git push
to update the website. It's not Pelican, but how the HTML was generated is irrelevant. What matters is that it's generated locally and pushed to GitHub, GitHub is not using Jekyll to generate it.
Perfect, thank you so much!
I'm trying to migrate my github pages blog (https://github.com/marioseixas/marioseixas.github.io) from jekyll to m.css but seems that github pages only support jekyl. not pellican, right?
If so, what are the alternatives to host a blog based on m.css that has it's files on a github repository and cannot be built via github pages?
Thanks in advance
Build error: