User Story Board - Copy this React, Tailwind Component to your project

Final Project User Stories & Wireframes Final Project Architecture It's time to think about what you are going to be building. You'll have to develop an entire product, prepare a presentation & demonstrate the product and the idea to family, friends and hiring partners. This project should be started after you have taken the class about Agile Development because you will have to create User Stories and a Kanban Board. 📝 Instructions Start the project using the academy's Full-Stack boilerplate that contains Front-End and Back-End all together. Add all your user stories into the repository's issues, as it will be the main repository for your project specs. Please create a Github Kanban Automated Project with the KANBAN columns: Backlog, Todo, Doing, Done. Now add the issues into the project as cards and plan for your first iteration. Technological Requirements for the project Several Pages (for example: Home page, Login Page, Profile Page, etc.) User authentication (Login + Signup + Forgot Password). Custom made API with Authentication. 3rd party API integration (embeds and iframes don’t count); it has to be a back-end integration. React.js application using Flux and React Router. Anything else the student wants to add. Methodology Requirements The project must have between 3 - 4 team members. Start by doing the wireframes and user stories and adding them into your repository's issues and projects (you have to deliver them). Create all the user stories with acceptance criteria. Use a Kanban board for follow up on Github Project Boards. Building the Wireframe A great way to polish your user stories is to draft off all your application wireframes. Please create all the wireframes for your application's Minimal Viable Product (MVP). Steps Start by building a sitemap. Then do the wireframe of your home page. Continue drawing on the most important pages. Every time you draw a page, identify and highlight the re-usable parts to convert them into components. Try to re-use everything all the time. The less code, the better! Keep it simple!