Tagged Development

While it’s amazing how easy it is for an experienced Drupal 7 site builder to get around using the Drupal 8 UI, the same is not true for writing code for D8. As has been made clear for years now, Drupal 8 is very different inside. Many of the hooks we know and love have gone away, most procedural code has been replaced with interfaces, classes, and methods, and there are scads of YAML (Yet Another Markup Language, .yml file extension) files that wire everything together. How does a developer get her/his footing in this slippery new landscape?

Blocks in Drupal 7 are pretty useful but, in practice, larger sites often have requirements that core blocks can't support like placing the same block in different regions for different content types. I’m happy to see core blocks have been improved in Drupal 8 to be much more practical and powerful.

We are excited to be headed to BADCamp this week! We are ready to rock UC Berkeley with our sessions, trainings, and amazingness! ... all capped off with a Drupal 8 Multilingual (D8MI) Sprint.

It took me a while, but the *nix command line won me over. The turning point came when I discovered the true potential of grep (which gets its name from globally search a regular expression and print).

I focus on frontend development, so this blog will use frontend examples with CSS, but in reality grep can be used for so much more. Grep is a great way to save time spent searching and better use that time doing.

Why Use the Corresponding Entity References Module?

Corresponding Entity References (CER) is a very useful module if you have two entity references that talk to each other. If you update one entity reference, CER does all the work to make sure the other entity reference reflects that update. It makes it easy to quickly associate entity references without having to edit two entities.

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.

Thank you to our guest author, Brian Degnan, PhD. for contributing his experience after a battle with Rackspace, Fileconveyor, Drupal, Linux, and inodes. :)

Lindsay, Aimee and Kristen will be representing the Hook 42 team at DrupalCon Austin this summer. Aimee & Kristen have been to several DrupalCons but this will be Lindsay's first and we'll celebrate her birthday when we're there. Woot!