feat: initial commit

.all-contributorsrc

@@ -0,0 +1,14 @@
+{
+  "projectName": "open-pixel-art",
+  "projectOwner": "twilio-labs",
+  "repoType": "github",
+  "repoHost": "https://github.com",
+  "files": [
+    "README.md"
+  ],
+  "imageSize": 80,
+  "commit": true,
+  "commitConvention": "angular",
+  "contributors": [],
+  "contributorsPerLine": 7
+}

.eleventy.js

@@ -0,0 +1,11 @@
+module.exports = function(eleventyConfig) {
+  eleventyConfig.addPassthroughCopy('styles');
+  eleventyConfig.addPassthroughCopy('assets');
+  eleventyConfig.addPassthroughCopy({
+    'node_modules/nes.css/css': 'assets/nes.css'
+  });
+
+  return {
+    htmlTemplateEngine: 'njk'
+  };
+};

.eleventyignore

@@ -0,0 +1,3 @@
+README.md
+CONTRIBUTING.md
+CODE_OF_CONDUCT.md

.github/config.yml

@@ -0,0 +1,13 @@
+newIssueWelcomeComment: |
+  Thank you so much for opening your first issue for this project! We'll try to get back to it as quickly as possible. While you are waiting...here's a random picture of a corgi (powered by [dog.ceo](https://dog.ceo))
+
+  ![dog](https://dog.ceo/api/breed/images/random)
+
+firstPRMergeComment: >
+  Congratulations to your first contribution to the Open Pixel Art project!
+
+  If you are on the look out for more ways to contribute to open-source, 
+  check out a list of some of our repositories at https://github.com/twilio/opensource.
+
+  And if you love Twilio as much as we do, make sure to check out our 
+  Twilio Champions program! https://www.twilio.com/champions

.github/pull_request_template.md

@@ -0,0 +1,24 @@
+<!-- Thank you for contributing a pixel to the Open Pixel Art project! -->
+
+## Checklist
+
+<!-- Before submitting your pull request please make sure you checked the following tasks: -->
+
+- [ ] I ran `npm test` locally and it passed without errors.
+- [ ] I only edited the `_data/pixels.json` file.
+- [ ] I entered the `username` in the `pixels.json` that I'm also using to create this pull request.
+- [ ] I acknowledge that all my contributions will be made under the project's [license](../../LICENSE.md).
+
+<!-- If you are contributing more than a pixel, please uncomment the part below and fill out the rest of the template -->
+
+<!--
+
+## Description
+
+a short description of your pull request
+
+## Related issues
+
+List any related issues here
+
+-->

.github/workflows/code-review.yml

@@ -0,0 +1,25 @@
+name: Code Review
+
+on: [pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v1
+      - name: Use Node.js 10.x
+        uses: actions/setup-node@v1
+        with:
+          node-version: 10.x
+      - name: npm install, build, and test
+        run: |
+          npm install
+          npm run build --if-present
+          npm test
+        env:
+          CI: true
+      - name: Danger
+        run: npx danger ci --text-only -f
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,64 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+
+# next.js build output
+.next
+
+.DS_Store
+_site

.mergify.yml

@@ -0,0 +1,34 @@
+pull_request_rules:
+  - name: automatic merge on CI success for pixel contributions
+    conditions:
+      - -conflict
+      - 'status-success=Build'
+      - files=_data/pixels.json
+      - '#files=1'
+    actions:
+      merge:
+        method: squash
+        strict: true
+      label:
+        add:
+          - 'hacktoberfest'
+          - 'pixel-contribution'
+  - name: create comment for failed CI
+    conditions:
+      - 'status-failure=Build'
+    actions:
+      comment:
+        message: 'Unfortunately the automatic code review has failed. Please click the details button for more information.'
+      label:
+        add:
+          - 'hacktoberfest'
+          - 'needs-help'
+  - name: add label for review for more than one file change
+    conditions:
+      - '#files>=2'
+    actions:
+      comment:
+        message: 'This PR touches more than one file and has to be revied manually.'
+      label:
+        add:
+          - 'needs-review'

.prettierrc

@@ -0,0 +1,12 @@
+{
+  "semi": true,
+  "singleQuote": true,
+  "overrides": [
+    {
+      "files": ["_data/pixels.json"],
+      "options": {
+        "printWidth": 800
+      }
+    }
+  ]
+}

.vscode/settings.json

@@ -0,0 +1,6 @@
+{
+  "[json]": {
+    "editor.formatOnSave": false,
+    "editor.formatOnPaste": false
+  }
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org