<commit_before># Dev.Opera

Repository for source code of new Dev.Opera

## How to setup environment

1. Install Jekyll, Sass and all needed gems by running `gem install jekyll sass kramdown stringex`.
2. Download and install [Node.js](http://nodejs.org) with default installer options.
3. Clone project by running `git clone <EMAIL>:operasoftware/devopera.git`
4. Run `npm install` inside `devopera` folder
5. Run `npm install grunt-cli -g` to install Grunt globally
6. Run `grunt` to build Dev.Opera inside `_site` folder

There are two modes of development available:

1. If you're developing some feature or article, run `grunt watch` and all your changes will be generated automatically every time you save any Jekyll template or Sass file. As quick as possible. To stop watching changes press `Ctrl C`.

	- If you’ve just saved any of `styles/*.scss` files, watcher will compile and copy styles to `_site/styles` folder in a few moments without full build process.
	- If you’ve saved any of `.md` or `.html` files, compilation could take up to 60 seconds, which is sad but there’s nothing we can do.
	- Please file an issue if you need the same quick watcher for anything else: scripts, images, etc.

2. If you need to build production version of Dev.Opera, run `grunt` and everything will be not just builded inside `_site` folder, but also compressed and optimized. Just once.

## Notes

- All instructions are for Unix (OS X, Linux, etc.) because Jekyll is not compatible with Windows.
- You may require write access for all commands mentioned above. Type `sudo`, space and command if needed.
- To launch Jekyll server open _another_ console instance or tab and run `jekyll serve`.<commit_msg>Proper nested MD list<commit_after># Dev.Opera

Repository for source code of new Dev.Opera

## How to setup environment

1. Install Jekyll, Sass and all needed gems by running `gem install jekyll sass kramdown stringex`.
2. Download and install [Node.js](http://nodejs.org) with default installer options.
3. Clone project by running `git clone <EMAIL>:operasoftware/devopera.git`
4. Run `npm install` inside `devopera` folder
5. Run `npm install grunt-cli -g` to install Grunt globally
6. Run `grunt` to build Dev.Opera inside `_site` folder

There are two modes of development available:

1. If you're developing some feature or article, run `grunt watch` and all your changes will be generated automatically every time you save any Jekyll template or Sass file. As quick as possible. To stop watching changes press `Ctrl C`.
	- If you’ve just saved any of `styles/*.scss` files, watcher will compile and copy styles to `_site/styles` folder in a few moments without full build process.
	- If you’ve saved any of `.md` or `.html` files, compilation could take up to 60 seconds, which is sad but there’s nothing we can do.
	- Please file an issue if you need the same quick watcher for anything else: scripts, images, etc.
2. If you need to build production version of Dev.Opera, run `grunt` and everything will be not just builded inside `_site` folder, but also compressed and optimized. Just once.

## Notes

- All instructions are for Unix (OS X, Linux, etc.) because Jekyll is not compatible with Windows.
- You may require write access for all commands mentioned above. Type `sudo`, space and command if needed.
- To launch Jekyll server open _another_ console instance or tab and run `jekyll serve`.
{'fraction_non_alphanumeric': 0.0686217008797654, 'fraction_numerical': 0.005865102639296188, 'mean_word_length': 4.183890577507599, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6827117', 'n_tokens_mistral': 957, 'n_tokens_neox': 929, 'n_words': 528}