Merge pull request #259 from EqualifyEverything/v1

V1

Author: bbertucc

.gitattributes

@@ -1,9 +1,13 @@
+/.ddev
+vendor/
+*.log
+.github
+.vscode
 .DS_Store
 .vscode
+/assets
 login/
-config.php
 config-server.php
-vendor/
 test/
 _dev/
 _private/
@@ -15,3 +19,7 @@ node_modules
 package.json
 package-lock.json
 .phpunit.result.cache
+.env-**
+.env
+cron.log
+composer.lock

.gitignore

@@ -7,9 +7,9 @@ We welcome any comments, questions, or feedback on our site. If you notice aspec
 This project is committed to delivering an excellent user experience for everyone. Equalify's user interface is structured in a way that allows those of all abilities to easily and quickly find the information they need.
 
 ## Ongoing Efforts to Ensure Accessible Content
-Equalify uses the Web Content Accessibility Guidelines (WCAG) version 2.1 as its guiding principle. As we develop new pages and functionality, the principles of accessible design and development are an integral part of conception and realization.
+Equalify uses the Web Content Accessibility Guidelines (WCAG) version 2.2 as its guiding principle. As we develop new pages and functionality, the principles of accessible design and development are an integral part of conception and realization.
 
-We continually test content and features for WCAG 2.1 Level AA compliance and remediate any issues to ensure we meet or exceed the standards. Testing of our digital content is performed by our accessibility experts using automated testing software, screen readers, a color contrast analyzer, and keyboard-only navigation techniques.
+We continually test content and features for WCAG 2.2 Level AA compliance and remediate any issues to ensure we meet or exceed the standards. Testing of our digital content is performed by our accessibility experts using automated testing software, screen readers, a color contrast analyzer, and keyboard-only navigation techniques.
 
 ## Summary of Accessibility Features
 - All images and other non-text elements have alternative text associated with them.
@@ -18,4 +18,4 @@ We continually test content and features for WCAG 2.1 Level AA compliance and re
 - Forms are associated with labels and instructions on filling in forms are available to screen reader users
 
 ## Project VPATs
-To request a conformance report using the Voluntary Product Accessibility Template (VPAT), please [submit an issue on Equalify's Github repo](https://github.com/EqualifyEverything/equalify/issues/new).
+To request a conformance report using the Voluntary Product Accessibility Template (VPAT), please [submit an issue on Equalify's Github repo](https://github.com/EqualifyEverything/equalify/issues/new).

.htaccess

@@ -0,0 +1,34 @@
+# Contributing
+Equalify code is first and foremost inclusive. We invite everyone, no matter their experience, to contribute to Equalify.
+
+This document outlines how we maintain an inclusive code-base, open to all contributors.
+
+## Keep Code Easy-to-Understand
+
+Any coding language can become complicated quickly. We want to keep our code easy to understand so that even beginners can know where to jump in. Clarity is achieved by keeping two rules:
+
+### Rule 1: Work Procedurally
+
+Procedural programming works with the basic Accessibility premise of well-ordered content (for more, check out [Mozilla’s discussion on “Proper Semantics”](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/HTML#good_semantics)). We know that’s different than many software projects that value Object-oriented programming, but we have enjoyed the fact that many new-to-PHP users understand our code easily.
+
+### Rule 2: Name Clearly
+
+Lots of code comments often mean that functions and variables are not named. We value explicit naming of functions and variables instead of adding lots of comments about what the functions or variables do.
+
+## Write in PHP
+
+PHP became our programming language of choice after building early prototypes in Python and JavaScript. We didn’t choose Python because it wasn’t familiar to many website developers we started working with. We didn’t choose JavaScript because promoted working in a way that worked against screen reader users. We always remain open to change if that means making our platform’s code more accessible to users.
+
+## Avoid Frameworks
+
+New frameworks must save us time without adding new barriers for contributors. Under that creed, we find ourselves going back to coding solutions in basic PHP instead of adopting frameworks. 
+
+## Be Efficient, But Not At Expense of Clarity
+
+Remember: we are an accessibility platform. We want to be fast and agile. That said, we’ll gladly trade a small efficiency to be more clear to our contributors. We think the smartest solutions are both super efficient and super understandable.
+
+## Act Without Dogma
+
+Of course, all of our ideas are up for debate! Please create a pull request to let us know of any new ideas. We’re excited to evolve into the most inclusive platform to have ever shaped the internet.
+
+Cheers!