<commit_before># Static Site Generators Listing

[![Build Status](https://api.travis-ci.org/bevry/staticsitegenerators-list.svg?branch=master)](https://travis-ci.org/bevry/staticsitegenerators-list)

A comprehensive listing of static site generators with some minimal meta data about them.

**[View the listing](https://github.com/bevry/static-site-generator-comparison/blob/master/list.yaml) | [Edit the listing](https://github.com/bevry/staticsitegenerators-list/edit/master/list.yaml)**

**[View the website](http://staticsitegenerators.net) | [View the website source](https://github.com/bevry/staticsitegenerators-website)**


## Contributing

### Requirements for additions

There are generally three types of Content Management Systems:

1. Dynamic Servers (e.g. WordPress, Ghost, DocPad, Harp) — these allow you to have re-render on every request abilities
2. Flat File CMS (e.g. Yellow, Techy) — these allow you to write your content as files
3. Static Site Generators (e.g. Jekyll, DocPad) — these generate a static website from your input that you can deploy anywhere

Currently, this listing is only for projects that are either a Flat File CMS and/or Static Site Generator, but not for projects which are only Dynamic Servers (such as WordPress and Ghost).

### Adding a static site generator

Accepted project fields:

* `name` - the project's name
* `github` - the location of the GitHub repository
* `license` - the project's license (or lack of license), see [license types](https://github.com/jaspervdj/static-site-generator-comparison/blob/master/list.yaml)

Other fields are automatically collected from the GitHub repository but if the project does not have one you can use the following fields:

* `website` - the project's website if they have one
* `language` - the project's language (note, if the entry is closed-source, use "Web" or "App")
* `description` - the project's description
* `created_at` - the project's creation date in "2010-10-20T13:46:08Z" format (not needed if the project has a GitHub repo)

Example:

``` yaml
- name: "Amazing"
  github: "octocat/amazing"
  license: "MIT"
  website: "http://theamazingstaticsitegenerator.com"
  language: "Go"
  description: "The most amazing static site generator yet."
  created_at: "2010-10-20T13:46:08Z"
```

## License

This listing is released into the public domain.<commit_msg>Update repo location in readme<commit_after># Static Site Generators Listing

[![Build Status](https://api.travis-ci.org/bevry/staticsitegenerators-list.svg?branch=master)](https://travis-ci.org/bevry/staticsitegenerators-list)

A comprehensive, partially automatically generated comparison of static site generators with some minimal meta data about them.

**[View the listing](https://github.com/bevry/staticsitegenerators-list/blob/master/list.yaml) | [Edit the listing](https://github.com/bevry/staticsitegenerators-list/edit/master/list.yaml)**

**[View the website](http://staticsitegenerators.net) | [View the website source](https://github.com/bevry/staticsitegenerators-website)**


## Contributing

### Requirements for additions

There are generally three types of Content Management Systems:

1. Dynamic Servers (e.g. WordPress, Ghost, DocPad, Harp) — these allow you to have re-render on every request abilities
2. Flat File CMS (e.g. Yellow, Techy) — these allow you to write your content as files
3. Static Site Generators (e.g. Jekyll, DocPad) — these generate a static website from your input that you can deploy anywhere

Currently, this listing is only for projects that are either a Flat File CMS and/or Static Site Generator, but not for projects which are only Dynamic Servers (such as WordPress and Ghost).

### Adding a static site generator

Accepted project fields:

* `name` - the project's name
* `github` - the location of the GitHub repository
* `license` - the project's license (or lack of license), see [license types](https://github.com/bevry/staticsitegenerators-list/blob/master/list.yaml)

Other fields are automatically collected from the GitHub repository but if the project does not have one you can use the following fields:

* `website` - the project's website if they have one
* `language` - the project's language (note, if the entry is closed-source, use "Web" or "App")
* `description` - the project's description
* `created_at` - the project's creation date in "2010-10-20T13:46:08Z" format (not needed if the project has a GitHub repo)

Example:

``` yaml
- name: "Amazing"
  github: "octocat/amazing"
  license: "MIT"
  website: "http://theamazingstaticsitegenerator.com"
  language: "Go"
  description: "The most amazing static site generator yet."
  created_at: "2010-10-20T13:46:08Z"
```

## License

This listing is released into the public domain.
{'fraction_non_alphanumeric': 0.10388247639034627, 'fraction_numerical': 0.013011542497376705, 'mean_word_length': 4.82640586797066, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 12, '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': '3446032', 'n_tokens_mistral': 1450, 'n_tokens_neox': 1359, 'n_words': 532}