Fix page navigation (#1065)

* fix navigation

* fix links

* move usability to non-functional requirements

* fix links

Author: TessFerrandez

docs/.pages

@@ -3,7 +3,9 @@ nav:
   - Engineering Fundamentals Checklist: engineering-fundamentals-checklist.md
   - The First Week of an ISE Project: the-first-week-of-an-ise-project.md
   - Who is ISE?: ISE.md
+  - Contributing: contributing.md
   - Agile Development: agile-development
   - Automated Testing: automated-testing
   - CI/CD: CI-CD
   - ...
+  - UI/UX: UI-UX

docs/CI-CD/.pages

@@ -12,10 +12,10 @@ Keep in mind that like all software, there is no "right way" to build a user int
 
 The state of web platform engineering is fast moving. There is no one-size-fits-all solution. For any team to be successful in building a UI, they need to have an understanding of the higher-level aspects of all UI project.
 
-1. [**Accessibility**](../accessibility/README.md) - ensuring your application is usable and enjoyed by as many people as possible is at the heart of accessibility and inclusive design.
-1. [**Usability**](./usability.md) - how effortless should it be for any given user to use the application? Do they need special training or a document to understand how to use it, or will it be intuitive?
+1. [**Accessibility**](../non-functional-requirements/accessibility.md) - ensuring your application is usable and enjoyed by as many people as possible is at the heart of accessibility and inclusive design.
+1. [**Usability**](../non-functional-requirements/usability.md) - how effortless should it be for any given user to use the application? Do they need special training or a document to understand how to use it, or will it be intuitive?
 1. [**Maintainability**](../non-functional-requirements/maintainability.md) - is the application just a proof of concept to showcase an idea for future work, or will it be an MVP and act as the starting point for a larger, production-ready application? Sometimes you don't need React or any other framework. Sometimes you need React, but not all the bells and whistles from create-react-app. Understanding project maintainability requirements can simplify an engagement’s tooling needs significantly and let folks iterate without headaches.
-1. [**Stability**](./stability.md) - what is the cost of adding a dependency? Is it actively stable/updated/maintained? If not, can you afford the tech debt (sometimes the answer can be yes!)? Could you get 90% of the way there without adding another dependency?
+1. **Stability** - what is the cost of adding a dependency? Is it actively stable/updated/maintained? If not, can you afford the tech debt (sometimes the answer can be yes!)? Could you get 90% of the way there without adding another dependency?
 
 More information is available for each general guidance section in the corresponding pages.
 

docs/resources/templates/LICENSE renamed to docs/LICENSE

@@ -48,11 +48,3 @@ npm init vite@latest my-app --template react-ts
 # npm 7.x
 npm init vite@latest my-app -- --template react-ts
 ```
-
-## HTML/CSS/JS
-
-> Coming soon!
-
-## Web Components
-
-> Coming soon!

docs/user-interface-engineering/README.md renamed to docs/UI-UX/README.md

@@ -2,7 +2,7 @@
 
 Usability is a topic that is often used interchangeably with user experience (UX), but they are not the same thing. Usability is a subset of UX, focusing specifically on the ease of use and effectiveness of a product, i.e., it is the ease with which users can learn and use a product to achieve their goals. Usability is a key factor in determining the success of a product, as it directly impacts user satisfaction, productivity, and overall experience. A system that is difficult to use or understand can lead to frustration, errors, and ultimately, abandonment by users.
 
-Closely coupled with usability and UX is the concept of accessibility, which you can read more about [here](../accessibility/README.md).
+Closely coupled with usability and UX is the concept of [accessibility](./accessibility.md).
 
 ## Characteristics