I agree with staunch. It's important you know whether you're doing it for the end result or to learn a new stack. If it is the end result train yourself to not

I agree with staunch. It's important you know whether you're doing it for the end result or to learn a new stack. If it is the end result train yourself to not care about the details. Keep the tech minimal and all the design choices should be centered around one question - "Will this help me ship?" I had the same issue of getting bogged down by technical details, so when I was developing my side product (https://discoverdev.io https://discoverdev.io) I ensured everything I do will be geared towards shipping it! I hadn't developed a frontend app before so I kept it simple, just HTML and CSS - no JS, no framework.