Style guides and pattern libraries are a great collaboration and communication tool in cross-functional teams. These tools have many names and variations (see styleguides.io), but in this post I’ll just call them style guides. Essentially they break down the user interface into its component parts, and serve as a resource for new designers and developers to locate existing patterns for further use. Decoupling the UI from application data, and splitting the UI into components often results in a more consistent and efficient UI for users.Read post Style Guide Driven Development with React
Archive for the Open source category
Designing and developing with accessibility in mind is hard. That’s why people have created tools to visualize potential accessibility issues and automate some of the testing tasks. As accessibility is such a huge topic, there’s no one-size-fits-all solution. We need to use multiple tools for testing accessibility, and none of these tools can fully replace human judgment.Read post Accessibility Testing Tools
I’m always trying to find new ways of making the front-end development workflow easier, faster, more structured, and more maintainable. As the web environment is becoming more complex, we need to embrace the tools and use them to help us create a good architecture that allows us to concentrate on the task at hand.
Everyone has his or her own coding style and preferred ways of working. The web evolves rapidly so changing our mindsets and constantly adapting to new ways of thinking and working is a must for front-end developers.
Over the last year or so, I’ve been thinking more and more about how frontend web development processes should be structured in small and large teams. Web projects often have tight deadlines so it’s important to have a structured approach to writing reusable code and testing modular code snippets in an optimized build environment, before deploying code to a testing or staging server.Read post One Web Boilerplate