<commit_before>---
layout: post
title: "GitHub Pages without the Workflow"
date: 2016-01-29
---

[GitHub Pages with Jekyll](http://jekyllrb.com/docs/github-pages/) is nice.
You just have to store your Jekyll **sources** in a repository `username.github.io`,
where `username` is your GitHub user account,
and you get automatically the **resulting pages** in `http://username.github.io`.
This is achieved thank to the GitHub Pages workflow that runs each time you push your sources to the repository.
At least if the build passes.
If not, you receive an email with the reasons why and no new pages are generated.
However, this process comes with rules that forbid using Jekyll plugins but for authorized ones.
{: .text-justify}

**Note:** I am discussing here about User pages on GitHub Pages.
For Project pages things are a bit different. For example for User pages, pages are on a `master` branch.
For Project pages, pages are on a `gh-pages` branch. See [here](https://help.github.com/articles/user-organization-and-project-pages/).
{: .text-justify}

## Two choices

If you want, e.g., to use the [Jekyll-Scholar](https://github.com/inukshuk/jekyll-scholar) plugin
(to generate pages from `.bib` BibTeX reference files),
you will have either not to use GitHub Pages
(make a simple `my-web-pages` repository and sync your pages with a Web server somewhere else)
or to shortcut the GitHub Pages workflow. This is what we will do here.
{: .text-justify}

This part is based on [Olivier Barais's template](https://github.com/barais/barais.github.io),
itself based on [<NAME>'s template](https://github.com/rudametw/rudametw.github.io).
I chose not to fork their templates here since my site structure is different and I also<commit_msg>presentation<commit_after>---
layout: post
title: "GitHub Pages without the Workflow"
date: 2016-01-29
---

[GitHub Pages with Jekyll](http://jekyllrb.com/docs/github-pages/) is nice.
You just have to store your Jekyll **sources** in a repository `username.github.io`,
where `username` is your GitHub user account,
and you get automatically the **resulting pages** in `http://username.github.io`.
This is achieved thank to the GitHub Pages workflow that runs each time you push your sources to the repository.
At least if the build passes.
If not, you receive an email with the reasons why and no new pages are generated.
However, this process comes with rules that forbid using Jekyll plugins but for authorized ones.
{: .text-justify}

**Note:** I am discussing here about User pages on GitHub Pages.
For Project pages things are a bit different. For example for User pages, pages are on a `master` branch.
For Project pages, pages are on a `gh-pages` branch.
See [here](https://help.github.com/articles/user-organization-and-project-pages/).
{: .text-justify}

## Two choices

If you want, e.g., to use the [Jekyll-Scholar](https://github.com/inukshuk/jekyll-scholar) plugin
(to generate pages from `.bib` BibTeX reference files),
you will have either not to use GitHub Pages
(make a simple `my-web-pages` repository and sync your pages with a Web server somewhere else)
or to shortcut the GitHub Pages workflow. This is what we will do here.
{: .text-justify}

This part is based on [<NAME>'s template](https://github.com/barais/barais.github.io),
itself based on [<NAME>'s template](https://github.com/rudametw/rudametw.github.io).
I chose not to fork their templates here since my site structure is different and I also
{'fraction_non_alphanumeric': 0.09829430471234461, 'fraction_numerical': 0.004625614339404453, 'mean_word_length': 4.389408099688474, 'pattern_counts': {'":': 0, '<': 6, '<?xml version=': 0, '>': 6, 'https://': 8, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4552816', 'n_tokens_mistral': 1034, 'n_tokens_neox': 972, 'n_words': 464}