Change Approval Process and Website Ownership

As our organization grows in size, we continue to add more internal services that need to be maintained. The Stevens Blueprint website is one of theses services. Now that the website has been completed, we need an approval process to ensure future changes align with our design principles, organization message, and technical requirements.

In the Software Development space there is the concept of "owning" services. Teams of Software Engineers own a service and are responsible for building new features, maintenance, fixing bugs, and answering questions on that service. This concept should be introduced to Blueprint starting with the Website.

This document introduces a formal approval process for changes to the Website. This ensures that any changes align with the Design principles of the website and are representative of our organization. This also adds accountability to ensure new changes don't break the website and 

The VP of Technology will assemble internal team(s). A PR must at least be approved by a member of this team and a member of the Design Team for it to go through. Bug Fixes can be given priority to only one approval by an owning member.

Design Principles

Tests

Analytics

Tangible Things

Add branch protection that mandates approvals from the respective teams for PR approval.

Discord Channel for #website team and a #public-website channel for any Blueprint members to raise concerns or discussion.