I recently saw Paul Lewis’ screencast demonstrating how trivial it can be to fix a particular kind of performance issue caused by scrolling. I knew the problem looked familiar and I realized it was happening right in my front yard, on the Four Kitchens homepage. Read on to see how easy it was to diagnose and fix.
In this issue: We’re taking Minneapolis by storm for Twin Cities Drupal Camp, Matt wrote an overview of the new launch of TWiT.tv; plus, dreaming computers, why the Pope hates the internet, What is Code, and more.
Do you ever watch This Week in Tech with Leo Laporte? If you don’t maybe now is the time to start. Last week, Four Kitchens helped TWiT with the launch of their new content API based on Drupal 7, with a headless website that is the first of many new TWiT apps sure to be appearing.
This week a team of Web Chefs is heading to the fair city of Minneapolis to share knowledge and be inspired by the community at Twin Cities Drupal Camp. If you plan on attending the Camp stop by to say “Hi!” at our sponsor table and make sure you don’t miss our Headless Drupal training and these great Web Chef sessions!
In this issue: We launched TWiT.tv! Twin Cities Drupal Camp is happening next week and we can’t wait for it; plus, TripMode might be just the tool for you, Device Metrics, a kitty library, and wiki inspiration from the team at Slack.
We’re happy to be offering our popular Introduction to Headless Drupal class free of charge for Twin Cities Drupal Camp attendees! Do you want to manage content in Drupal but use something else to deliver it to your users? This is the class for you.
I recently had a significant webfont problem on some client work and had to really sink my teeth into the problem to resolve it properly. I found some great resources that helped me fix it in no time. Hopefully they’re as useful to you as they were to me.
In this issue: celebrating Web Chef birthdays, more Webperf Wednesdays from Chris Ruppel; plus, SlackBots for beginners, the arrival of Instant Articles, and playing Screentendo.
On average, we break our own CSS every week and a half. It's pretty common across all web projects - most people just don't know it. It seems we all need a system that will tell us when we break our CSS.
Two weeks ago web chef emeritus Ian Carrico and myself had the pleasure of of both training and speaking about frontend performance at DrupalCon LA. I’d like to describe our free, open source training materials a bit to entice you to try them, and perhaps start building awareness of performance within your team.
- 1 of 42
- next ›