Years ago, I didn’t understand what designing websites for accessibility really meant. I thought that accessibility guidelines would only benefit a few users, that they would introduce unsatisfying design limitations, and that following them would take more time and money.
You want to refresh the look of your site. You have the approval from your stakeholders, the budget and resources, and goals for the new design. But how do you actually kick off a design project?
Last year was a wonderful one for Alley. We accomplished a lot—so much so that we had to take a month or two to bring it all together for this post! Here are some of the highlights.
Many of Alley’s publishing clients use Brightcove’s video platform with custom plugins to handle more complex ads and analytics functionality. Here’s how to fit it into a local development workflow.
We first launched our in-browser prototyping platform, Huron, eight months ago and it’s become instrumental in streamlining our design and development process. We’re proud to announce our latest version (2.1.1) is now available on npm as an open-source tool.
Alley Interactive partner and chief strategy officer Brad Campeau-Laurion recently spoke at LoopConf about Alley’s internal code review process. Brad explained how Alley’s company-wide code review mandate helps boost collaboration within the development team while also ensuring high standards and quality control for all projects.
Consider a hammer. You don’t have to think about where to hold it, or which part is supposed to strike the nail. It’s not a perfect device — you might still whack your thumb — but it’s pretty intuitive.
A spectre is haunting the open source CMS community—the spectre of Medium.
In a complex application, many components will need to manage both data access and internal state. Where it really gets tricky is when we need to know something about components that are nested in the tree, or data needs to persist across components or states. For example, we may want to make our router aware
At Alley, we frequently design sites that require any given component to appear in a variety of contexts. A visual style guide allows us to view the site not as a series of pages, but grouping of reusable components. Ultimately, this simplifies and standardizes the way our designs communicate. In addition, it jumpstarts future components