Search Results for "posh-git-master"

...GitHub pages uses Jekyll natively, so when I make documentation, I typically look for Jekyll templates. Why? Using Jekyll means that I can use markdown, and allow for users to easily contribute, and build automatically just by way of pushing to a master branch (or general GitHub pages). I’ve liked MkDocs in the past, but it required me to use a special renderer. I also felt limited in my ability to customize it. The same is true for MkDocs material. It’s absolutely gorgeous, but was not suited for my GitHub pages and customization needs. For this reason, I’ve spent some time creating a custom Jekyll template that is (almost) as beautiful and includes all the features that I might want.

This plugin automagically does the entire the letsencrypt process for your gitlab-hosted Jekyll blog! GitLab CI setup such that when you push to master (or your preferred branch), your changes are deployed live. Automate letsencrypt renewals for Gitlab pages.

A Liquid tag plugin for Jekyll that renders a version identifier for your Jekyll site sourced from the git repository containing your code. Great if you want to display the version of your project on your site automatically each time your site is built. Identify and highlight the build of your project by calling the tag from your Jekyll project.

To start your own blog, simply git clone the repository on GitHub. You could also press the "fork" button on GitHub. Then you will need to edit the _config.yml file at the root of repository. To add your own posts, add a file to the _posts directory which has the name year-month-day-title.md.