Before doing anything make sure you get your UX design team/designer/person responsible for what it looks like to finalise the design. Full specs required for

Before doing anything make sure you get your UX design team/designer/person responsible for what it looks like to finalise the design. Full specs required for fonts, colours, sizing, padding, accessibility labels etc before a single line of code is written is the optimal situation, but not always realistic - get as much as you can agreed first. This is because from experience designers et al like to fiddle around with things a lot before it is "done" so don't waste time coding before the specification is ready. Once you have a stable design/specification to work from you can start - I like to plan out the DOM before writing any code to avoid the excessive "firing arrows" the author struggles with. I generally try to code up the raw HTML first, then progressively add CSS afterwards. I avoid CSS frameworks like tailwind/bootstrap wherever I can as they get you started quicky yes, but in the long run make it harder to get exactly what you want (see previous remake a out designers liking to fiddle)