Recently I have been spending my spare time working on rewriting SimpleStateManager. The project already had a pretty robust series of unit tests however I wanted to improve this further by adding a few more. In addition to adding new tests, I wanted to improve how the tests were being run.
So tonight I spoke at Untangle the Web about how we can untangle the way we go about building and designing a responsive site by putting our content first and then ensuring were able to deliver that content as fast as possible by building for performance.
In my last post I looked at how we could prioritise content based on the type of device. The first post was only part of the puzzle you need to complete to build an awesome responsive experience, it’s probably worth pointing out that each post is standalone and doesn’t assume any knowledge from a previous post.
Recently I have spoken at a few events about how we can start to reimagine how we design and build our responsive sites, focusing on two areas; content and performance.