<commit_before>#<code>[codedoodl.es](http://codedoodl.es)</code>

<code>A showcase of curated creative coding sketches</code>

* [codedoodl.es](http://codedoodl.es)
* [codedoodl.es chrome extension](http://codedoodl.es)

### What is this

What does do

### How to contribute

PR

### Doodle criteria

The purpose of codedoodl.es is a little different to the other code-showcasing sites out there - we want to [... something about them being doodle-y]. In order to maintain consistency with regards to viewer expectation, and [... something about load times], we have laid out some basic entry criteria for each doodle.

Note that the criteria here are more guidelines for the most part - every doodle submitted will be reviewed by a human, and so there will always be flexibility here - we're just trying to create some consistency.

##### Minimum requirements

These are the minimum number of files required for each doodle, these will be used to display / reference each individual doodle on the site / extension.

* <code>index.html</code>

	Every doodle must have a single `index.html` file as an entry point. This file must be situated in the root of the doodle directory, which will located in `/doodles/<author_github_username>/<doodle_name>` as outlined above.

* <code>thumbnail JPEG 300x300 px</code>

	A single 300px by 300px JPEG thumbnail for the doodle must be in the root of the doodle directory.

* <code>manifest.json</code>

	Most importantly - each doodle requires a manifest file which contains all the metadata for the doodle, including doodle information / instructions, author details and tech used. You can manually create this file based on the schema outlined [here](here), or if you use the doodle-creation utility script, the manifest will be automatically generated based on answers you have given.

##### Creative

Blah blah

* <code>hmm</code>

##### Technical

To maintain

* <code>Web-tech only - no plugins</code>

	Blah

* <code>No crazy new tech required (behind flags etc)</code>

	Blah

* <code>Max HTTP requests per doodle</code>

	Blah

* <code>Max pagesize</code>

	Blah

##### No-no's

To create a consistent visual style and user experience, we're restricting the usage of certain [... things]

* <code>no GUI</code>

	Blah

* <code>no branding / logos / explanatory text</code>

	Blah

* <code>no sound</code>

	Blah

* <code>no mandatory user permissions</code>

	Blah

### Roadmap

This is very much a first iteration, we wanted to get something basic released as soon as possible, and are hoping that there will be sufficient interest / engagement from the creative coding community to warrant the future development of more intricate features and functionality, some ideas include:

* <code>Voting system</code>

	Assuming (hoping) that we have enough doodles submitted [... rank]

* <code>Filtering</code>

	Blah

* <code>Additional options per doodle</code>

	Blah

* <code>Additional browser extensions</code>

	Blah

* <code>Browser-extension specific context</code>

	Blah

* <code>User-defined options within browser extenions</code>

	Blah<commit_msg>More documentation<commit_after>#<code>[codedoodl.es](http://codedoodl.es)</code>

<code>\\\\ A curated showcase of creative coding sketches \\\\</code>

[site](http://codedoodl.es) \\ [chrome extension](http://codedoodl.es)

### What is this?

codedoodl.es is community-based collection of code experiments created with web technologies. The aim of these doodles is to exhibit interactive, engaging visual web experiments which only require a short attention span.

This means no loading bars, no GUI, no 5MB 3D models or media files, no page of instructional text, just plain and simple doodles with code.

The site at [codedoodl.es](http://codedoodl.es) houses all of the doodles in one place, and installing the [chrome extension](http://codedoodl.es) will show a new doodle every time you open a new tab.

### How to contribute

The sketches on codedoodl.es are 100% community-sourced. The submission / review / approval process is handled entirely in the open on GitHub - fork this repo, create a doodle, submit pull request, [the reviewers]() will then approve and merge in to the repo.

**[See this guide for comprehensive details on the contribution process.]()**

### Doodle criteria

The purpose of codedoodl.es is a little different to the other code-showcasing sites out there - we want to [... something about them being doodle-y]. In order to maintain consistency with regards to viewer expectation, and [... something about load times], we have laid out some basic entry criteria for each doodle.

Note that the criteria here are more guidelines for the most part - every doodle submitted will be reviewed by a human, and so there will always be flexibility here - we're just trying to create some consistency.

##### Minimum requirements

These are the minimum number of files required for each doodle, these will be used to display / reference each individual doodle on the site / extension.

* <code>index.html</code>

	Every doodle must have a single `index.html` file as an entry point. This file must be situated in the root of the doodle directory, which will located in `/doodles/<author_github_username>/<doodle_name>` as outlined above.

* <code>thumbnail JPEG 300x300 px</code>

	A single 300px by 300px JPEG thumbnail for the doodle must be in the root of the doodle directory.

* <code>manifest.json</code>

	Most importantly - each doodle requires a manifest file which contains all the metadata for the doodle, including doodle information / instructions, author details and tech used. You can manually create this file based on the [schema outlined here](here), or if you use the doodle-creation utility script, the manifest will be automatically generated based on answers you have given.

##### Creative

Blah blah

* <code>hmm</code>

##### Technical

To maintain

* <code>Web-tech only - no plugins</code>

	Blah

* <code>No crazy new tech required (behind flags etc)</code>

	Blah

* <code>Max HTTP requests per doodle</code>

	Blah

* <code>Max pagesize</code>

	Blah

##### No-no's

To create a consistent visual style and user experience, we're restricting the usage of certain [... things]

* <code>no GUI</code>

	Blah

* <code>no branding / logos / additional UI / explanatory text</code>

	Blah

* <code>no sound</code>

	Blah

* <code>no mandatory user permissions</code>

	Blah

### Roadmap

This is very much a first iteration, we wanted to get something basic released as soon as possible, and are hoping that there will be sufficient interest / engagement from the creative coding community to warrant the future development of more intricate features and functionality, some ideas include:

* <code>Voting system</code>

	Assuming (hoping) that we have enough doodles submitted [... rank]

* <code>Filtering / sorting</code>

	Blah

* <code>Additional options per doodle</code>

	Blah

* <code>Additional browser extensions</code>

	Blah

* <code>Browser-extension specific context</code>

	Blah

* <code>User-defined options within browser extenions</code>

	Blah

### Thanks

This project is a [FLUUUID](http://FLUUU.ID) production - we created the site / extension / infrastructure to allow this to happen, but the real thanks goes to the digital artists who have contributed doodles:

[Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]() \\ [Neil Carpenter](http://neilcarpenter.com) \\ [<NAME>]() \\ [<NAME>]()
{'fraction_non_alphanumeric': 0.10615711252653928, 'fraction_numerical': 0.0036218308979642814, 'mean_word_length': 4.230568256041803, 'pattern_counts': {'":': 0, '<': 105, '<?xml version=': 0, '>': 105, 'https://': 0, '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': '6731380', 'n_tokens_mistral': 2426, 'n_tokens_neox': 2242, 'n_words': 991}