Now let's get back to the subject of the challenges with building software. This will help us see the power and reason for a library like this. One of the biggest issues we faced was getting the designer and developer workflow to please both sides of a project team. As we worked with designers over the years, they often expressed frustration dealing with spaghetti code and confusion caused by building design markup around our coding logic. At the same time, developers like me were frustrated when designers would move stuff around to make the page look right and break my programming logic. It became apparent that what we needed was for us to separate.
What type of separation? This didn't mean the designers getting rid of the developers or the other way around. What we needed was a way to write the code so there were far less issues and conflicts. The logic should be collected in one place and the presentation in another. We have CSS and other things that help with this goal...