📎 Webclip
Fullstack Project Planning
The article argues that fullstack projects go more smoothly when planning is broken into separate parts. It lays out a sequence that starts with scope and database modeling, then moves through API planning, backend work, wireframing, component planning, frontend work, and testing.
Reading notes#
- Define the project scope first, including whether it needs backend and frontend parts, user authentication, or third-party APIs.
- Decide which database to use, which models are needed, and how those models relate if the database is relational.
- Plan the API endpoints after the database is set up, including CRUD coverage, query parameters, public access, and protected routes.
- Choose the backend stack and host the API before building it.
- Test backend code as it is built, and use tools like Postwoman, Postman, or Insomnia to check endpoints manually.
- Make wireframes or sketches before frontend coding, since this makes the build easier and helps with UI libraries like Material UI or Bootstrap.
- Break frontend sketches into components if using a component-based framework like React, and identify containers, stateful components, and a single source of truth.
- Plan frontend stack choices, styling, consistency, mobile-first design, and accessibility before and during the build.
- Write frontend tests as you go, cover edge cases, and think through how the UI handles errors.
- Share the project for user testing if possible, since other people may catch missed edge cases or suggest improvements.
