Your project should fulfill the following requirements:
-
Use a CSS framework other than Bootstrap.
-
Be deployed to GitHub Pages.
-
Be interactive (i.e., accept and respond to user input).
-
Use at least two server-side APIs.
-
Does not use alerts, confirms, or prompts (use modals).
-
Use client-side storage to store persistent data.
-
Be responsive.
-
Have a polished UI.
-
Have a clean repository that meets quality coding standards (file structure, naming conventions, follows best practices for class/id naming conventions, indentation, quality comments, etc.).
-
Have a quality README (with unique name, description, technologies used, screenshot, and link to deployed application).
Presentation to address the following:
-
Elevator pitch: a one minute description of your application
-
Concept: What is your user story? What was your motivation for development?
-
Process: What were the technologies used? How were tasks and roles broken down and assigned? What challenges did you encounter? What were your successes?
-
Demo: Show your stuff!
-
Directions for Future Development
-
Links to the deployed application and the GitHub repository
Metric | Weight |
---|---|
Technical Criteria | 25% |
Concept | 10% |
Deployment | 20% |
Repository Quality | 10% |
Application Quality | 15% |
Presentation | 10% |
Collaboration | 10% |
This project is graded based on the following criteria:
-
Satisfies the following code requirements:
-
Application uses at least two server-side APIs.
-
Application uses client-side storage to store persistent data.
-
Application doesn't use JS alerts, prompts, or confirms (uses modals instead).
-
Application uses a CSS framework other than Bootstrap.
-
Application is interactive (accepts and responds to user input)
-
-
Application should be a unique and novel idea.
-
Your group should clearly and concisely articulate your project idea.
-
Live URL: https://mhutchbot.github.io/Project-One/
-
Application GitHub URL: https://github.com/MHutchbot/Project-One
The following gif shows the application's appearance and functionality:
-
Repository has a unique name.
-
Repository follows best practices for file structure and naming conventions.
-
Repository follows best practices for class/id naming conventions, indentation, quality comments, etc.
-
Repository contains multiple descriptive commit messages.
-
Repository contains a quality README file with description, screenshot, and link to deployed application.
-
Application user experience is intuitive and easy to navigate.
-
Application user interface style is clean and polished.
-
Application is responsive.
- There are no major disparities in the number of GitHub contributions between group members.
Each member is required to submit the following:
-
The URL of the deployed application.
-
The URL of the GitHub repository.