As most of you probably already know, Lullabot is a completely distributed company. All of our employees work remotely from wherever in the world they live in whatever style best suits them. Many of us work from home, some prefer coffee shops, and others seek out coworking spaces. We've been doing this since 2006 and it has worked really well for us.
We've built an amazingly talented team and we've worked on some amazing projects. It has been a challenge to figure out how to scale culture and manage interconnectedness as we've grown to nearly 50 employees. We've also had to invent solutions to many issues such as healthcare and benefits, recruiting, taxes, payroll, and management styles – which are easier at conventional brick and mortar companies. But despite any difficulties, we're convinced that this is the future of work.
So on January 28th, we're going to gather several of the leading companies focused on distributed/remote work for a roundtable discussion-style conference that we're calling Yonder. It's a 2 day invitation-only event – limited to 25 attendees – happening in San Diego, CA.
We've already got some high-profile companies represented. Do you work at a distributed company or as part of a remote team? Pass along the word about Yonder. Do you lead a distributed company or team? Visit Yonder.io and request an invite.
Let's get together and compare notes.
In the world of content strategy, spreadsheets are a critical tool for planning and communication. In particular, content types are often defined and refined in spreadsheets before they're committed to code or CMS configuration.
Large-scale Drupal sites often maintain a separate "staging" server to test and preview changes before they're released to the public. If you're working on a smaller project, though, it can be useful to give a few trusted testers access to a few pages of the site. In those situations, the Protected Pages module might be just what you need.
Part of the Drupalize.Me team, Addison Berry, Joe Shindelar, Kyle Hofmeyer, and Joe Fender, gets on today's episode to talk about our new site launch, and the long road it took for us to get here. We talk about the reasons we decided to upgrade the site, and share some of the big changes we made, and the biggest issues we've faced getting the job done.The long road from Drupal 6 to 7
In this episode Addison Berry is joined by Miro Dietiker and Christophe Galli to talk about the Translation Management (TMGMT) project. Multilingual sites are complex beasts, and in addition to getting things wired up to allow translation, you also need to get the site translated into the languages you need.How do you keep track of your site's translation needs?
After a fall hiatus, Insert Content Here is back for a second year of content strategy and digital publishing goodness!
In episode 19, Jeff Eaton and Harvard's Mike Petroff talk about the recent redesign of the Harvard Gazette on Wordpress, the challenges of serving a large university's communications needs, and trends in social publishing and visitor interaction.Balancing multi-channel communications with the needs of a 400-year-old university
Let's look at an example. We want to display the weather of a given city in our website. This involves:
By the time most large Drupal sites have been around for a year or two, they've accumulated a menagerie of content types. Articles, press releases, product pages, reviews, biographies, landing pages, home pages, promo rotators, photo galleries, and more litter the list of content, and making sure they're treated consistently can be a problem.
Last week a number of us went to beautiful Prague, Czech Republic to immerse ourselves at DrupalCon. The city was amazing, and the conference was a blast. In this episode Addi, Kyle, Juampy, and Micah share their experiences, favorite sessions and news, and give a general rundown on how DrupalCon Prague turned out. We also have a bit of a discussion on European versus US DrupalCons, and talk about some other events that are coming up. Importing Data With Migrate and Drupal 7
This year's European DrupalCon took the community to the beautiful city of Prague, in the Czech Republic. From September 23rd to 27th, Drupal users and contributors from around the world gathered for training, code sprints, heated technical discussions, and a peek into what's coming in Drupal 8.
The Magic Module consolidates a number of these useful tools into one place.
I recently got a new Mac and needed to configure it as a local web server for the many Drupal sites I work on. I used to use MAMP for this, but lately have been using the built-in functionality that comes on a Mac instead. MAMP is easy to install, but it creates a duplicate version of PHP and a duplicate version of Apache. That takes up space on my machine and occasionally causes trouble when some operation uses the wrong version of PHP because of confusion about which installation should take precedence.
For this episode, Addison Berry is joined by Nate Haug and Jen Lampton to talk about their new project, Backdrop, which is a fork of Drupal. This is a shocking move in the community, and has generated a lot of questions and concerns. We talk about the motivation behind the fork, who's working on it, and ask about the negative impact this can have on the community. We asked on Twitter and Facebook for what questions folks had, and we got a ton of responses. Addi asks these questions to Nate and Jen, directly from the voices in the community.
Insert Content Here listeners may have spotted last week's firestorm of blog posts and tweets about the Content Strategy Forum in Helsinki, Finland. Held once a year, it draws hundreds of CMS, content strategy, and marketing folks: this year's event was no slouch.
Have you needed to change all occurrences of a domain, filepath, or text string within your site? Normally this would involve a lot of planning and custom queries. Drush Search & Replace fixes that problem.
Warning! This is a very powerful drush extension. If used incorrectly it can actually destroy data integrity or cause data loss which can not be reverted. Please test on development environment, backup your site, and use at your own risk.
Welcome to the third part of our series on writing Views query plugins! In part 1, we talked about the kind of thought and design work that needs to be done before coding on the plugin begins. In part 2, we went through the basics of actually writing a query plugin. In this final chapter, we will investigate some enhancements to make your plugin more polished and flexible.
Let's face it, sometimes Drupal 7's default field markup is less than ideal. While whipping up a quick field template file might seem trivial to some, you can quickly find yourself in a maintenance nightmare managing template code for content types with many fields. The Semantic Fields module solves that problem nicely.