docs: consolidate documentation into README

- update list of contributors
- scaffold README structure and TOC
- move development docs into README
- scaffold sections for quickstart/customization
- update local development/quickstart documentation
- move and update wordpress docs section
- move and update structure docs to README
- move generator docs to README
- move plugins docs to README
- move custom blocks docs to README
- fold CSS docs into project structure
- move deployment docs into README
- follow GitHub conventions for contributing/code of conduct guides
- give a more detailed description of the starter template
- use relative path links to repo
- add details about what to change for a new project
- add details about docker deployment
- remove image of limited usefulness
- fix typos, missing link, and broken image
- fix outdated references

Author: dustin-jw

.env.example

@@ -1,13 +1,14 @@
 # Database Environments
 MYSQL_USER=example_user
-MYSQL_PASSWORD=
+MYSQL_PASSWORD=example_password
 MYSQL_DATABASE=example_database
 MYSQL_HOST=db
-MYSQL_ROOT_PASSWORD=
+MYSQL_ROOT_PASSWORD=example_root_password
 
 # Set `WP_ENV` to `yourLastName-local` (ex. `smith-local`).
-WP_ENV=sparkuser-local
+WP_ENV=example_user-local
 
 # This will replace localhost URLs in the DB on exports, and be replaced by localhost URLs on imports
-# Relace "example.com" with your domain name (or the domain name for a staging environment)
+# Replace "example.com" with your domain name (or the domain name for a staging environment)
+# This needs to be consistent between team members for DB imports/exports to work correctly
 SITE_URL=https:\\/\\/example.com

CODE_OF_CONDUCT.md

@@ -0,0 +1,36 @@
+# 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, gender identity and expression, level of experience, nationality, personal appearance, race, religion, marital status, color or sex (including pregnancy, sexual orientation, or gender identity).
+
+## 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.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing
+
+Hey! You're thinking about contributing? That's awesome! You're awesome. Don't know where to start? The best place to get started is visiting our [issues][issues] to see if there are any you'd like to tackle.
+
+Here's a few things you should know before you submit your PR:
+
+1. The purpose of this project is to make getting up and running on a WordPress project quick and simple. By design, it has minimal styles and functionality.
+1. All contributions must follow our [code of conduct](code-of-conduct.md)
+
+## Steps to submit a PR
+
+- Clone/Fork the repo
+- Install dependencies: `npm install`
+- Install plugin dependencies `npm run plugins:install`
+- Start the development process `npm start`
+- Ensure linters pass: `npm run lint`
+- Ensure tests pass: `npm test`
+- Make changes and then make sure the linters and tests still pass
+- Push your branch/fork and [submit a PR][pr]
+- Assign a [sparkboxer][contributors] to review your PR
+
+## Commit Style
+
+We use [Conventional Commits][conventional commits] on this project. Commit messages must be prefixed with a valid commit type and the commit type cannot be prefixed with any additional text.
+
+Supported commit types include `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, and `test`.
+
+Valid example:
+
+```sh
+feat: add new linting rule for ...
+```
+
+Invalid examples:
+
+```sh
+feature: add new linting rule for ...
+```
+
+```sh
+:sparkles: feat: add new linting rule for ...
+```
+
+ℹ️ See the [Conventional Commits][conventional commits] page for further details on available commit types and how to handle breaking changes.
+
+[issues]: ./issues
+[pr]: ./compare
+[contributors]: ./graphs/contributors
+[conventional commits]: https://www.conventionalcommits.org/en/v1.0.0/