Project review by team

The team carried out a project review asking a number of questions from each other

1. What have you learned/enjoyed
1.1 Fundamentals of HTML and CSS
1.2 GIT
1.3 Collaborating with others
1.4 Getting feedback and a different point of view in PR's

2. What more do you want to learn
2.1 JavaScript
2.2 Complete MDN Learn web development (without the server side for this particular project, see end goals)

3. What are the end goals of the project
- A responsive website that conforms to HTML and CSS recognised standards and supports all users.
- Each contributor completes the MDN Learn web development guide as far as
Server-side website programming
- The project contains one example from each section from the MDN Learn web development guide that can be used as a reference

Area's for improvement
- PR's to apply the following protocol
- Provide a reference to the MDN topic that drives the coding change
- Explain the changes
- Ensure the code is well commented for future contributors to understand the code base.
- More formal approach to review. For example, approvers should respond within 5 days. At least one approval is required before merge.
- Area's that require tutorials/in depth knowledge and wiki
- What IDE to use and the packages to assist with linting and formatting HTML, CSS and javaScript
- Conventions to implement clean, readable, maintainable CSS and javascript
- Responsive standard (i.e. what media queries should we use to support mobile, tablet, Monitor)
- Setup project aspect of the gitbub code-co-op / learning-web-development
- See https://github.com/code-co-op/learning-web-development/projects
- Wiki to document best pratice for using project area (i.e. what to raise, how to document issue, assignment process)