We love sharing our knowledge about Drupal, technology, and beyond.
Learn from our blog
The purpose of this blog post is to tell others how in one week I went from fruitlessly searching the Issue Queue, to contributing to Drupal 8 while interacting with core contributors...and how you can too! I did this by triaging Issues that had the Novice Tag with the help of Drupal Mentors and I documented the process along the way. There are a ton of Issues left to triage and core contributors need your help!
Building a multilingual site in Drupal 7 requires a lot of patience and a lot of special-purpose modules. Checkout my Multilingual Module Madness presentation from DrupalCon Portland if you want to learn more! ;)
Intro of the Padawan Contributor
Which ones are strategic to my growth:
Any of the sessions that are welcoming to newcomers or involve best practices are strategically important for my growth. One advantage of being new, is every session can lead me to grow.
Prepping for DrupalCon Austin sprints: Sprint leads, component maintainers, experienced contributors & mentors, update core issue queues this week!
With new responsive websites, it's more important than ever to look at your site at different widths. But this can be time consuming and repetitive. Also, you may want to see how your dev site compares to your live site - for example "Did this small change I made to the css on one page change much on other pages?" Again, time consuming to do by hand. Luckily for us, here comes Wraith to the rescue!
The Hook 42 team had a great time at Stanford Drupal Camp this weekend. Kristen and Aimee presented two sessions each and four other members of our team attended, Lindsay, K2 (Kristin), Marc, and Marc's 15 year old son Dean. It was the first Drupal camp experience for the extended team and they enjoyed the great topics, beautiful facilities, and the welcoming community. Many thanks to the Stanford Drupal community for hosting such a great event!
There comes a time in every Drupal developer's day when they realize they really don't need a field on some content type or other entity. Maybe it was a field holding temporary data while you did a migration or maybe a feature was removed or maybe things have been rearchitected to use a non-field approach.