we primarily consider it a design responsibility to get HTML and CSS work done correctly.”
When we start on new client projects or internal apps, we don't always start the HTML/CSS buildout the same way. Sometimes a client has sketches; sometimes wireframes; sometimes they have a brand/identity in place already - there's a big variety in what materials they come to us with. Likewise, when we start our design process, we don't always use the same exact things we did the last time. Part of this is a result of wanting to constantly experiment and make each time better than the last by learning - and part of it is just the unique style of each designer and their thought process. Regardless of how we got there though, one major pain point was always in the first few days of HTML/CSS building. Would we use a css "framework"? Which one? Should we put a "reset" in place but no framework? Should we start with literally nothing and let the site dictate as we go? Should we...