<commit_before>= JBake AsciiDoc Quickstart

The JBake AsciiDoc Quickstart project is all you need to deploy your blog or website hosted on GitHub with content based on AsciiDoc. This project combines the power of AsciiDoc with JBake as a publishing framework on top of GitHub's publishing infrastructure.

== Directions

The goal of this procedure set is to configure a Travis job to listen for commits on the _jbake_ branch, automatically "bake" the website using JBake, and push the generated content to the _master_ or _gh-pages_ branch, depending on configuration.

== {counter:directions}. Configuration

There are some variables you need to edit in the `pom.xml` file:

  <github.site.repositoryName>USERNAME.github.io</github.site.repositoryName>
  <github.site.repositoryOwner>USERNAME</github.site.repositoryOwner>
  <github.site.branch>master</github.site.branch>

- If you want to use GitHub's Personal Pages, the generated content for your website will have to be published on the `master` branch, your repo has to be named `username.github.io` and it will be available at http://username.github.io.
- If you want to use GitHub's Project Pages, the generated content for your website will have to be published on the `gh-pages` branch, your repo could have any name (you might want to rename the fork, from `jbake-asciidoc-quickstart` to `blog` for example) and it will be available at http://username.github.io/jbake-asciidoc-quickstart or http://username-github.io/blog, depending on the repository name.

You might want to add a `src/jbake/content/CNAME` file with a custon domain that has CNAME DNS record poiting to `username.github.io`. That way you could access your website at http://www.username.com/ or http://www.username.con/blog, depending on your configuration.

For this to work you can just create a file with the domain name:

  $ echo "www.username.com" > src/main/jbake/assets/CNAME<commit_msg>Added links to README<commit_after>= JBake AsciiDoc Quickstart

The JBake AsciiDoc Quickstart project is all you need to deploy your blog or website hosted on GitHub with content based on AsciiDoc. This project combines the power of AsciiDoc with JBake as a publishing framework on top of GitHub's publishing infrastructure.

== Directions

The goal of this procedure set is to configure a Travis job to listen for commits on the _jbake_ branch, automatically "bake" the website using JBake, and push the generated content to the _master_ or _gh-pages_ branch, depending on configuration.

More information:

- JBake: http://www.jbake.org
- AsciiDoc: http://www.asciidoc.org

== {counter:directions}. Configuration

There are some variables you need to edit in the `pom.xml` file:

  <github.site.repositoryName>USERNAME.github.io</github.site.repositoryName>
  <github.site.repositoryOwner>USERNAME</github.site.repositoryOwner>
  <github.site.branch>master</github.site.branch>

- If you want to use GitHub's Personal Pages, the generated content for your website will have to be published on the `master` branch, your repo has to be named `username.github.io` and it will be available at http://username.github.io.
- If you want to use GitHub's Project Pages, the generated content for your website will have to be published on the `gh-pages` branch, your repo could have any name (you might want to rename the fork, from `jbake-asciidoc-quickstart` to `blog` for example) and it will be available at http://username.github.io/jbake-asciidoc-quickstart or http://username-github.io/blog, depending on the repository name.

You might want to add a `src/jbake/content/CNAME` file with a custon domain that has CNAME DNS record poiting to `username.github.io`. That way you could access your website at http://www.username.com/ or http://www.username.con/blog, depending on your configuration.

For this to work you can just create a file with the domain name:

  $ echo "www.username.com" > src/main/jbake/assets/CNAME
{'fraction_non_alphanumeric': 0.07378296146044624, 'fraction_numerical': 0.0, 'mean_word_length': 4.556338028169014, 'pattern_counts': {'":': 0, '<': 15, '<?xml version=': 0, '>': 17, 'https://': 0, 'lorem ipsum': 0, 'www.': 8, 'xml': 2}, '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': '5670733', 'n_tokens_mistral': 1097, 'n_tokens_neox': 1058, 'n_words': 506}