We had a case where on some views we needed to print the header above the exposed filters and on others we needed to print the header after the exposed filters. Here's my simple solution.
Linking patterns allows us to give our users a real feeling for how the website is going to work, on real devices, which things like InVision can never do. Here's some simple approaches.
A simple request: we need an 'Add to Calendar' widget to add our events to Google Calendar, iCal, and Outlook. Simple (once I had completed it!).
Anyone who knows me as a front-end developer, knows how much I dislike InVision (though really, it's all those type tools - Zeplin, SketchCloud, Figma, etc). I might keep a little archive of my tweets about it here.
I have a card component with a title, image, text, and link. How come all my card variants are inheriting all the values from the default one? Short answer, you don't. It's a feature, not a bug.
What would make for a first-class, enterprise-ready, front-end development team?
Responsive images in PatternLab get a bit of a bad rap sometimes, because they are tricky to have in PL and Drupal. Here's my "easy way" of achieving it.
Yes, I know, there's more than one way to integrate PatternLab with Drupal. Here's how I create a card component and map it to Drupal.
Let's revisit my recent post and see if we can come up with more user-friendly names for PatternLab items.
I'm sometimes asked for an overview of my general approach to PatternLab. Simple: put everything for each component in the same directory!