W04: Final Project - Proposal
Description
By now your team should have settled on one idea for your project. This week a more detailed project proposal is required.
The Proposal
Your proposal can take many forms, but should show that you have thought through your idea enough to understand what will be required and that the complexity matches the time available between now and the end of the block.
Your proposal should also show how it will meet the following project requirements:
- Use an external, 3rd party API
- All exposed features should work.
- Should be a combination of static and dynamically generated markup.
- Should incorporate animation.
- Code should show a good level of organization (ES Modules, classes, etc).
- Code should be error free (according to team ESLint rules).
Required sections in the proposal document:
- Overview:
- What is the problem we are trying to solve?
- Why are we doing this?
- Who is the audience?
- List of the major functions of the application. What will it do? List these in as much detail as you can.
- Wireframes of the major views (Mobile and desktop...do the mobile wireframes first!)
- Data sources (External API, etc.)
- Initial Module list
- Colors/Typography/specific element styling
- Schedule to provide yourself mile markers along the way to help you stay on target.
- Link to a Trello board with all the tasks you can think of at this point defined as cards.
Again be
as detailed as possible here.
The Trello board is a living document. It won't be done when you turn it in and it will certainly change. Be as thorough as you can with you planning on possible tasks as you think through the entire application project.
Submission
Submit the proposal document.