Final Project Requirements
+5 Theme Section (No Login or Easy Guest access)
You must have a Group Project and/or Theme. Four (4) key interactions are expected.
Data Driven page(s). Technical evaluation expectations require data on Theme pages to be driven by backend, Jinja and usage of Class code in front. DB code or Web APIs are viable options for this requirement. A mix of backend usage is ATTRACTIVE to Teacher.
Something fun for user to do or for user to interact with or user learn from your site.
+5 Individual Section
Individual Section... All projects have an area where individuals have built their own room in site (aka Mini Labs and Digital Portfolio)
Code Modeling... Code structure will include BluePrint organization for Individual Areas.
Individual rooms should retain theme of site and navigation of site. It should be easy to navigate into and out of room without losing orientation.
+5 API Section
Code Requirement... You need to have endpoint(s) working through a REST API.
Crossover sharing of REST API with another project team. Endpoint is required for crossover.
An area where you can see usage of an REST API endpoint from another team. This should be easy to navigate into and out of area which presents this code. Making updates to remote site is HIGHLY encouraged.
+5 Deployment. Section
How it is made. An Area where you can see embedded content that describes 'how it was made'. ie "Readme', 'Scrum Board', Code embed(s).
You must Deploy to Teacher provided hardware and be a part of N@tM requirements.
Quality and Usability of Project
Group Tickets (Progress Technicals found on each individual Ticket)
Final Project Requirements +5 Theme Section (No Login or Easy Guest access) You must have a Group Project and/or Theme. Four (4) key interactions are expected. Data Driven page(s). Technical evaluation expectations require data on Theme pages to be driven by backend, Jinja and usage of Class code in front. DB code or Web APIs are viable options for this requirement. A mix of backend usage is ATTRACTIVE to Teacher. Something fun for user to do or for user to interact with or user learn from your site.
+5 Individual Section Individual Section... All projects have an area where individuals have built their own room in site (aka Mini Labs and Digital Portfolio) Code Modeling... Code structure will include BluePrint organization for Individual Areas. Individual rooms should retain theme of site and navigation of site. It should be easy to navigate into and out of room without losing orientation.
+5 API Section Code Requirement... You need to have endpoint(s) working through a REST API.
Crossover sharing of REST API with another project team. Endpoint is required for crossover. An area where you can see usage of an REST API endpoint from another team. This should be easy to navigate into and out of area which presents this code. Making updates to remote site is HIGHLY encouraged.
+5 Deployment. Section How it is made. An Area where you can see embedded content that describes 'how it was made'. ie "Readme', 'Scrum Board', Code embed(s). You must Deploy to Teacher provided hardware and be a part of N@tM requirements. Quality and Usability of Project