What’s Your Workflow for Building a Website?

I think it really depends on what works for you. Some folks build everything at once, while others prefer a more structured approach. If you're not feeling productive, maybe try breaking your tasks into a sequence, like using tools such as Obsidian or GitHub Markdown to plan your workflow and make checklists.

Here’s how I typically do it: First, I gather requirements and have a few meetings to clarify things. After that, I design my database and backend services. I usually find that the frontend can be developed in parallel, provided there's good communication. This way, you minimize surprises and ensure that you have the right data in place.

Honestly, I sometimes tackle features one at a time for complex tasks, but on simpler stuff, I just dive in and code whatever feels right. The key for me is having a solid plan outlined before I start coding — that way I can focus on one piece at a time without losing sight of the bigger picture.

I like to map out requirements and consider edge cases before diving in. Building data structures and establishing procedures for data access follows, and I find this helps reduce rework later on. Once that's settled, I focus on the front end to ensure everything flows smoothly.

Starting with a UI mockup, then focusing on the backend and authentication has always worked well for me. It gives me a safety net to refine things along the way!