#p5.js Web Editor

This project is currently in development! It will be announced when there is a (public) beta release.

##Development Installation

1. Clone this repostory and cd into it
2. $ git submodule init
3. $ npm install
4. Install MongoDB and make sure it is running
   • For Mac OSX with homebrew: brew install mongodb then brew services start mongodb
   • For Windows and Linux: MongoDB Installation
5. Create a file called .env in the root of this directory that looks like

MONGO_URL=mongodb://localhost:27017/p5js-web-editor
PORT=8000
SESSION_SECRET=whatever_you_want_this_to_be_it_only_matters_for_production
AWS_ACCESS_KEY=<your-aws-access-key>
AWS_SECRET_KEY=<your-aws-secret-key>
S3_BUCKET=<your-s3-bucket>
GITHUB_ID=<your-github-client-id>
GITHUB_SECRET=<your-github-client-secret>

If you don't care about being able to upload media files to S3 or Login with Github, you can drop in the file exactly how it is. Or, if you don't want to do that, just ask me to send you mine. Refer to this gist for creating an S3 bucket for testing, or if you don't want to do that, I can add you to one of my S3 buckets. 6. $ npm start 7. Navigate to http://localhost:8000 in your browser 8. Install the React Developer Tools. 9. Open and close the Redux DevTools using ctrl+h, and move them with ctrl+w

##Production Installation

1. Clone this repostory and cd into it
2. $ git submodule init
3. $ npm install
4. Install MongoDB and make sure it is running
5. Create a file called .env in the root of this directory that looks like

MONGO_URL=mongodb://localhost:27017/p5js-web-editor
PORT=8000
SESSION_SECRET=make_this_a_long-random_string_like_maybe_126_characters_long
AWS_ACCESS_KEY=<your-aws-access-key>
AWS_SECRET_KEY=<your-aws-secret-key>
S3_BUCKET=<your-s3-bucket>
GITHUB_ID=<your-github-client-id>
GITHUB_SECRET=<your-github-client-secret>

For production, you will need to have real Github and Amazon credentions. Refer to this gist for creating an S3 bucket for testing. 6. $ npm run build 7. $ npm run start:prod

###For Production Setup with PM2

1. $ npm install -g pm2
2. $ pm2 start ecosystem.json

##Accessibility Guidelines

Here is guide on how to use the accessible editor

The code for the p5.js web editor adheres to web accessibility standards. The following guidelines will help to ensure that accessibility continues to be a priority as development continues.

Code Structure

• Screen Readers are an assistive technology for vision loss which helps users to navigate a web page. They are able to prioritize content based on the semantic meaning of HTML tags. Therefore, it is important to use specific tags, such as nav, ul, li, section, and so on. div is the least screen reader friendly tag. For example, here is the semantic meaning of the body tag
• All buttons/links/windows need to be accessible by the keyboard ( By tabbing, pressing space etc.)
• In cases where tags are not screen reader friendly, we can take advantage of tabIndex. Using tabIndex ensures that all elements are accessible via keyboard. code example
• When opening a new window or pop up window, ensure the keyboard focus also moves to the new window. code example

Labeling

• When creating button icons, images, or something without text (this does not include an HTML5 <button>), use aria-labels. code example
• All <table>s need to have a summary attribute. This will ensure user is given context to what the table is. code example
• uls and navs menus need to include a title. code example

For more information on accessibility see the teach access tutorial

##Contribution Guide I am currently open to contributors! Email me if you are looking for a task, or look at the open issues and reply that you are working on a task.

The p5.js Web Editor is built on a MERN stack - MongoDB, Express, React/Redux, and Node. For a reference to the file structure format I am using, please look at the Mern Starter and this comment.

This project uses an in-development p5.js interceptor library for accessibility as git submodule. Every time you run npm install, it will update the interceptor to HEAD, so it is important to do this often.

This project does not use CSS Modules, but uses Sass. I like to follow BEM rules for CSS naming conventions, write OOSCSS with placeholders and mixins, and follow the 7-1 Pattern for Sass.

I'm using ES6 and transpiling to ES5 using Babel. For reference to the JavaScript style guide, see the Airbnb Style Guide, React ESLint Plugin.

The ESLint configuration is based on a few popular React/Redux boilerplates. Open to suggestions on this. If in development, you're getting annoyed with ESLint, you can remove it from webpack.config.dev.js in the JavaScript loader, or disable any line from eslint by commenting at the end of the line // eslint-disable-line.

AWS information

This project is currently hosted on an EC2 instance and uses S3 for media hosting.

Backups on the MongoDB are also hosted on an S3 bucket, based on the following gist. The backup script runs nightly via a cronjob at 8AM UTC/3AM EST/12AM PST. Backups are deleted after 30 days.

##Dump of links I'm saving for reference

• https://github.com/brigade/scss-lint
• https://github.com/petehunt/react-howto
• https://github.com/jsbin/jsbin (especially look at the console)
• Need to figure out how to solve the XSS issue, https://github.com/jsbin/jsbin/wiki/Best-practices-for-building-your-own-live-paste-bin
• https://www.npmjs.com/package/express-subdomain
• https://github.com/jsbin/jsbin/blob/master/public/js/render/console.js - the code is a little messy but it might be useful