Blog
At Rangle, we believe in sustainable development practices. This is not only reflected in our lean and agile approach to meeting our clients’ needs, but also in our emphasis on individual and team happiness. We express this at the organizational level through things like communities of practice, workshops, lunch & learns, and organization-wide surveys, but also at the individual level through one-on-ones.
Andrew Kumar, Director of Platform Strategy at Contentful, and Bertrand Karerangabo, Vice President of Digital Strategy at Rangle share a wide-ranging look at CMS platforms—where they’ve come from, where they’re going, and how to deliver top value to your digital customers now.
A DesignOps practice, despite what the name may imply, has wider company benefits beyond the confines of the design team.
The purpose of a design system is to serve the needs of a team, not just an individual designer. You know that creating a design system creates speed, but it’s not simply about the compound effect of cutting down on designer’s grunt work—a design system also removes burdensome communication blockers, and adds speed to the work of the overall agile team, including developers, quality practitioners, and marketing/merchandising teams.
The purpose of a design system is to serve the needs of a team, not just an individual designer. You know that creating a design system creates speed, but it’s not simply about the compound effect of cutting down on designer’s grunt work—a design system also removes burdensome communication blockers, and adds speed to the work of the overall agile team, including developers, quality practitioners, and marketing/merchandising teams.
Since 2015, Rangle has been working with Google on tools and resources for developers, including our Angular Training Guide , to be released in a new edition on June 30. In partnership, we introduced Augury, the most-used tool for debugging, profiling, and inspecting Angular applications with Google Chrome. Augury is a tool that visualizes your code, helping developers understand what Angular is doing, without digging through source code. It’s an excellent tool for new Angular developers, but equally useful for experts in the framework.
Are we still talking about MVC? Isn't it dead already, with UML and waterfall? We want to soar through the cloud, create lambdas, use modern stacks, integrate with top-of-the-line libraries, the latest and the greatest — not something from a dust-covered book written a long time ago, in a galaxy far, far away. I hear you, young Padawan, but give me a few minutes of your time, and I'll explain how those two intersect, and how you can sit on the shoulders of giants.
In the course of three years of consulting and problem solving for companies with existing design systems, one fact has become (at times, painfully) obvious: Design systems are hard to get right.