Planet Drupal

Syndicate content - aggregated feeds in category Planet Drupal
Updated: 1 day 6 hours ago

Wuinfo: Content as a Service

Sun, 2015-07-26 20:47

As one of Canada’s most successful integrated media and entertainment companies, Corus have multiple TV channels and websites for each channel.

It had been a challenge to have multiple channels' live schedule data displayed on websites. All the data are from a central repository. It became a little bit difficult since the repository is not always available. We had used Feeds module to import all the schedule data. Each channel website keeps a live copy of the schedule data. Things got worse because of the way we update the program items. We delete all the current schedule data in the system and then imported from the central repository. Sometimes, our schedule pages became empty because the central repository is not available.

Pedram Tiv, the director of digital operations at Corus Entertainment, had a vision of building a robust schedule for all channels. He wants to establish a Drupal website as a schedule service provider - content as a service. The service website download and synchronize all channels schedule data. Our content manager can also login to the website and edit any schedule items. The site keeps all the revisions for the changes. Since, the central repository only provide raw data, It is helpful we can edit the scheduled show title or series name.

I loved this brilliant idea as soon as he had explained it to me. We are building a Drupal website as a content service provider. It means we would build a CMS for other CMS websites. Scalability is always challenging for a modern website. To make it scalable, Pedram added another layer of cache protection. We added S3 cache between the schedule service and the front end web servers. With it, schedule service can handle more channels and millions of requests each day. Front end websites download schedule data from the Amazon S3 bucket only. What we did is creating and uploading seven days' schedule data to S3. We set up a cron job for this task. Every day, It uploads thousands of JSON schedule files for different channels in different time zones of next seven days each time.

This setup offloaded the pressure of schedule server and let it serve unlimited front end users. It gives seven days of grace period. It allowed the schedule server to be offline without interrupting the service. One time, our schedule service was down for three days. The schedule service was not affected because we have seven days of schedule data in an S3 bucket. By using S3 as another layer of protection, it provided excellent high availability.

Our schedule service have been up and running for many months without a problem. There are over 100,000 active nodes in the system. For more detail about importing large number of content and building an efficient system, we have some other blogs for this project.

Sites are that are using the schedule services now:

Categories: FLOSS Project Planets

Paul Rowell: Drupal's admin pages can be beautiful!

Sun, 2015-07-26 16:20

So, it turns out the Drupal CMS can be beautiful. I kid you not! Anditko has updated the Adminimal theme with a material skin based on Android Lollipop. I've mentioned Adminimal before, an admin theme that greatly improves the look and feel of Drupal’s CMS, and the latest update takes it that step further into the land of stunning.

Categories: FLOSS Project Planets

Freelock : Drupal on Docker, with a pinch of Salt

Sat, 2015-07-25 11:16

Faster, more secure, more maintainable. Three nice benefits we get from our new standard Drupal server architecture.

This year we're replacing our old "traditional" LAMP stack with an entirely less pronounceable LNDMPS version. We still use Linux, MariaDB and PHP, of course, but instead of Apache we've moved to Nginx, and we've added Docker and Salt.

DrupalDrupal PlanetDockerSaltConfiguration ManagementSecurityPerformanceDevOps
Categories: FLOSS Project Planets

Iztok Smolic: 5 reasons startups should use Drupal

Sat, 2015-07-25 08:30

I like to be technology/platform agnostic, but last couple of years I’ve built everything on top of Drupal. I get this question many times: “Why not using something else?”. My answer is usually: “I became so good at using it, that it only makes sense to me”. I tried to came up with some objective reasons, to […]

The post 5 reasons startups should use Drupal appeared first on Iztok.

Categories: FLOSS Project Planets

OSTraining: How to Create a Glossary View in Drupal

Fri, 2015-07-24 17:36

When you first install the Views module, it comes with several example views.

One of the most popular examples is the Glossary view, which takes a large amount of content and organizes it all by the first letter of the content title. This is useful in a lot of situations, especially when you're creating a directory of businesses or people.

Here's what the Glossary view looks like:

Categories: FLOSS Project Planets

VM(doh): 6 Reasons Why Drupal 8 is an Exciting Step Forward

Fri, 2015-07-24 16:21

Drupal 8, which has been in beta for a few months now, is causing plenty of excitement. In the beginning, Drupal made confident claims that it would be a major step forward:

Drupal 8 will set a new standard for ease of use, while offering countless new ways to tailor and deploy your content to the Web. Easily customize data structures, listings, and pages, and take advantage of new capabilities for displaying data on mobile devices, building APIs, and adapting to multilingual needs.

Drupal 8 has many new features, and also describes it as having a "leaner, meaner core," an "easier migration process from earlier versions," and "in-place content editing tools." Modules and themes will also become more powerful because of Drupal 8's adoption of OOP (Object Oriented Programming).

1. Creating a Bridge for New Developers

And speaking of the new OOP approach, this new feature might be one of the more exciting aspects of Drupal 8.

It's finally building a bridge to new developers.

Drupal 8 is much more compatible with the programming standards of PHP, and this means that new developers who may not know Drupal very well can still come in with their OOP PHP familiarity and contribute to projects.

Besides adding a wider door through which more developers can pass, Drupal 8 is improving things in all the ways you might expect in our current Age of the Smart Device:

2. Drupal 8 is Actually Mobile-First, Not Just Mobile-Friendly

Drupal 8, not surprisingly, will be mobile-first. It's a good thing too. According to, 80% of Internet users now own a smart phone, and the majority of digital media consumption is now done on mobile devices. Mobile-first is the new standard for web design, and Drupal 8 is embracing that trend. For example, Drupal 8's built-in themes are all responsive, and the administration toolbar is mobile-first.

3. File System-Based Configuration

The new management system makes it easy to switch configuration changes with greater consolidation and versatility (which translates into fewer headaches). Here's how Drupal describes it:

Drupal 8 has a whole new configuration system to store configuration data in a consistent manner. All of your site configuration from enabled modules through fields, contact categories to views, are stored with this system. The system is designed to make it much easier than prior Drupal versions to make changes, export site configuration to files, and import those changes back into the site.

4. HTML 5-Based Markup

HTML 5-based markup means, among other things, native input tools that make it simple to design for mobile. It also means that the output templates have simpler elements. It's definitely a much-needed feature. And they were thorough with it, as their initial list of HTML 5 objectives reveals:

The main goals of this initiative will be to implement HTML5 in Drupal core in a way that will:

  • Have the most benefit for end users.
  • Enable contributed modules and themes to evolve using HTML5.
  • Allow theme developers to control where to use the new semantic elements, and opt out entirely if they so choose.
  • Adding support for the new form elements to Drupal's Form API.
  • Adding new semantic elements in core templates in an appropriate way.
  • Adding ARIA roles to markup to improve accessibility.
  • Simplifying style and script elements.
  • Ensuring input filters and functions accept HTML5 elements.
5. Much Easier Editing

Drupal 8 features a new WYSIWYG configuration, two-column editing, improved draft-saving, and the ability to edit content without reverting to the full edit mode.

6. Drupal 8 Will Speak Your Language

Drupal has its eyes on the global prize, and Drupal 8 is clear evidence of this. It has powerful multilingual features: it has built-in interfaces that can translate anything in the system, it will grab software translation updated automatically from Drupal, and, according to Drupal, it can "build pages with Views language filtering and block visibility."

Powerful indeed.

Contact us or subscribe to our newsletter for more helpful tips and insights about Drupal.

Categories: FLOSS Project Planets

Tim Millwood: Drupal Statistics 2.0

Fri, 2015-07-24 16:15
Since February 2012 I have been the maintainer of the Statistics module in Drupal core. Since then I...
Categories: FLOSS Project Planets

Red Crackle: Adding A Drupal Commerce Product And Product Display

Fri, 2015-07-24 15:49
This article is the first in a tutorial series that teaches beginners how to configure a Drupal Commerce site. Follow this series to gain a basic understanding on how to build online stores of your choice. The focus of this specific article is on installing Drupal Commerce on an existing Drupal installation and then adding a product and displaying it on the site. By the end of this article, you will be able to create a basic product page in Drupal with an “Add to cart” button.
Categories: FLOSS Project Planets frontpage posts: RMS, Free Software Movement and Drupal... NYCcamp

Fri, 2015-07-24 14:23

So, what happened???.... The FreeScholar in me got really tired of hearing developers that are excited about some proprietary solutions/tools that happen to work with Drupal. Some of these solutions are being touted as the way to go in the future. I believe that our community has no shortage of genius, creative minds and brilliant ideas, so I encourage us all to think deeply about the tools we use and our personal freedoms.

About 2 months ago, I invited Richard Stallman to our monthly meetup at MIT. I wanted him to meet the Drupal community and take a look at how we work together on projects that are dear to our hearts, helpful to our communities and good for society- we make things happen. He gave a short lightning talk about free software and hardware, then we had a Q and A with him. Many of us got a better understanding of what his mission is and how we can be a part of the educational outreach for Learning to explain how free software is key to autonomy, privacy and human rights, is a big help for the movement.

Next, I invited RMS to NYCcamp... On Saturday July 18th, he gave the keynote speech to a packed house at the United Nations - After the keynote and standing ovation, he connected with the Aegir team and began a discussion on web hosting platforms and free server tools which led to a larger group convening at a strategy session with the Aegir team lead, Chris Gervais and RMS. They led an engaging round table discussion with about 30 people -

What an excellent time - your voice and thoughts are needed, let's free our future with free software as the foundation.

I love Drupal almost as much as I love freedom.

Categories: FLOSS Project Planets

Red Crackle: Drupal Commerce Tutorial - Create your first e-commerce store

Fri, 2015-07-24 14:07
In this series of tutorials, you will learn how to create a Drupal Commerce site from scratch. You will learn how individual modules in Drupal Commerce suite fit together to build an e-commerce store, irrespective of whether you are selling products, services or subscriptions.
Categories: FLOSS Project Planets

Mediacurrent: Solr Integrations with Drupal Sarnia Module

Fri, 2015-07-24 13:52

Every day, companies and organizations with lots of content are weighing the pros and cons of adopting Drupal. Often, this decision takes the form of “to what extent should we adopt Drupal” - meaning whether an organization will want to move toward managing all, or possibly only some of its content in Drupal. Having chosen some form of the latter (as practical concerns often warrant), organizations and their technical teams must delve into the territory of integrating Drupal with third party or sometimes proprietary data sources.

Categories: FLOSS Project Planets

Blink Reaction: My First Drupal Commit - Part One

Fri, 2015-07-24 12:46
Contributing to Drupal from a Junior Developer’s Perspective


Here at FFW, we are acutely aware that Drupal is an open-source environment, and as such, we appreciate the many thousands of hours that volunteers have put into its development. So, when developers at FFW are between projects, we are encouraged to do "contrib" work, meaning we find open issues in the Drupal issue queue, solve them, and get them pushed out into the community. Until very recently in my year at FFW I was on a single project for one of our largest clients. When I finished my engagement on that project, and before I started another one, I found myself with some free time and the opportunity to work on my first Drupal commit! This is a fantastic company culture and policy, everybody wins because of it, and I feel lucky to work here. At any given time, we always have someone doing contrib work, mainly with Drupal 8 core. It helps us learn as individuals, helps the presence and reputation of our company, and of course helps Drupal, which is the reason we’re all here, and the reason you’re reading this blog series.

That being said, this will be a post about how to contribute and the process involved. There will no (or very few) code examples. There are plenty of resources online for that. Rather, this is for the novice to intermediate Drupal developer who’s ready to give back to Drupal for the first time and doesn't quite know where to start.

The thing that's so great about open source software, and the way Drupal contrib in particular works, is that anyone can contribute, regardless of past experience. Take me for example, I've made a career of Drupal for the past five years, but have never given back until now. Shame on me! There's no certification you need in order to contribute, no permissions, just an account at and a willingness to learn. And don't worry – like I did at first – you can't break anything. The contrib and approval process is sophisticated enough that only correct, community-approved patches will get committed. There's nothing to fear, so…

Let’s Get Started

First I'll summarize the steps you go through to contribute, then I'll dive into each one, pointing out tips and gotchas along the way. So, at its most basic level, contributing goes like this:

1.     Find an issue you would like to, and are able to, contribute to.

2.     Download the latest Drupal core to your local machine. I’ve been working on Drupal 8 core issues, so that's where we’ll start.

3.     Create a new branch, and download and apply patches that already exist for the issue, so you're working from the most recent version of the code.

4.     Complete your work locally.

5.     Create a patch and an interdiff (more on that later) and upload them to the issue.

6.     Await the automated testing results and recommendations or approval from the community.

7.     Repeat steps 4 through 6 until your work is approved and your patch is ready.

8.     Get a commit in Drupal core!

I know it sounds like a lot, but once you do it a few times it will become easier and faster. Put it this way: my first patch took me almost a day to complete. Now I can create and upload one in a few minutes. Like anything else, the more you do it the faster (and more confident) you get. And it is so worth it to learn this process. I can’t overstate how excited I was when I got my first commit into core! In Monday’s post I’ll get deeper into each step of this process.

DrupalBest PracticesDrupal PlanetDrupal TrainingLearning SeriesPost tags: DrupalContributeDrupal Community
Categories: FLOSS Project Planets

Drupal Watchdog: Managing Video Content in Drupal

Fri, 2015-07-24 12:06

When faced with the task of managing videos in Drupal, the number of available solutions might seem overwhelming. Where should you store the videos? What is the difference between CDNs (content delivery networks), cloud storage services, and hosted video solutions? Which Drupal modules should you use with which service?

Drupal Modules

By using some of the most popular modules for video handling, you can quickly set up a reliable video solution:

  • Media module Although not specialized for video, this widely used module can be combined with others; some cloud services have their own modules integrated with the Media module, too.
  • MediaElement module The MediaElement module provides an HTML5 (or Flash fallback) player. With the MediaElement module you can stream video to mobile devices as well. The player can integrate with your responsive theme.
  • Video module The Video module can handle video upload, transcoding, and playing; generates thumbnails; and can deliver videos from cloud systems.
Content Delivery Networks

CDNs are largely distributed systems optimized for delivering content to end-users, over the Internet, with high availability and performance. For video content, they are often coupled with a transcoding server.
They can be expensive, but are a good choice for improving performance and delivering content for high-traffic websites. As the data centers are distributed, they will be faster than the usual hosting providers for most visitors to your site. Also, contemplate using a CDN if you already have a transcoding server.

The CDN module provides easy Content Delivery Network integration for Drupal sites. It alters file URLs so that files are downloaded from a CDN instead of your web server.

Cloud Storage Services

Cloud storage services aren’t optimized for delivering rich media content on high traffic sites, but can be a cheaper alternative to CDNs – if you don’t have a huge number of videos and your site traffic isn’t very high.

Categories: FLOSS Project Planets

Mpumelelo Msimanga: Stop Spam By Disabling Drupal Visitor Registrations

Fri, 2015-07-24 09:00
Stop Spam By Disabling Drupal Visitor Registrations

For sites that do not need to have user registrations. The most effective way to prevent registration spam is to disable visitor registrations. If you need users to register to post comments, consider using use third party chat applications like Disqus and Livefyre.

Categories: FLOSS Project Planets

Tim Millwood: Drupal 8  & Composer

Fri, 2015-07-24 07:20
Over the last few weeks I’ve been spending a lot of time with Drupal 8 and Composer. This has meant...
Categories: FLOSS Project Planets

Drupal @ Penn State: The future of Drupal under the hood

Thu, 2015-07-23 22:36

I’m in the middle of several Drupal Camp / Con’s (any event over 1000 people is no longer a “Camp” but that’s for another time) and it’s occured to me: I can no longer learn by going. Now, this is learn in the traditional sense of what I used to go to Camps for (been coming to camps for 8 years now).

Categories: FLOSS Project Planets

ThinkShout: Four Things You Can Learn About Content Strategy...from Mad Max

Thu, 2015-07-23 20:00

George Miller has a vision of the future. Judging by the non-stop mayhem and desolation that is Mad Max: Fury Road, if I had the same vision, I wouldn’t sleep very much. As a piece of action cinema, however, Fury Road succeeds on every level. I couldn’t look away – but the second time I saw it, I was surprised by the number of carefully rendered details I missed the first time. I want to see it again.

After you emerge into the sunlight and finally manage to blink after two hours of wide-eyed apocalyptic rapture and think about Fury Road as a piece of content produced by a distributed team that had an audience in mind, there are plenty of lessons we can take away from it.

It takes time to make great content

Miller first tried to make Fury Road in 2001, took it up again in as a live action film in 2011, and wrapped photography in 2013. The movie itself didn’t come out until mid-2015. Typically, Hollywood calls that sort of timeline "development hell", and it presages an Ishtar-scale flop.

When you consider recent successes like The Lego Movie (4 years in production) and the fantastic Boyhood (12 years in production), it’s clear that, with the right people involved, movies benefit from allowing directors to realize their vision. Expand that to books and music, and the quickly-created masterpiece is the clear outlier.

To think that your organization can churn out content that best serves its mission without careful thought and robust process, then, would be a mistake.

There’s a long-standing notion that people don’t read on the Internet, backed up by careful research. I believe people don’t read on the Internet because, by and large, the available content is crap.

When you think about your own habits, though, haven’t there been at least a few pieces you’ve read almost word for word? I certainly absorbed the New Yorker’s recent terrifying article about how the Cascadia Subduction Zone is going to reduce Portland to the set of the next Mad Max. And ESPN’s Outside the Lines regularly produces content I read carefully – because they’re well-written pieces about topics that interest me.

Research shows that people who read for pleasure read more carefully. As Slate’s Michael Agger points out, even Jakob Nielsen, one of the founders of "People don’t read on the Internet", believes people will read content that interests them:

Nielsen's idea is that people will read (and maybe even pay) for expertise that they can't find anywhere else. If you want to beat the Internet, you're not going to do it by blogging (since even OK thinkers occasionally write a great blog post) but by offering a comprehensive take on a subject (thus saving the reader time from searching many sites) and supplying original thinking (offering trusted insight that cannot be easily duplicated by the nonexpert).

That sounds to me like the very definition of great content – and great content takes time to produce. I’m not talking about three-levels-of-bureaucratic review time, but about putting effort and craft into your explanations of what your organization believes is important to the world, be it through written word, a video, a podcast, or even just an image.

That can seem overwhelming, particularly when most nonprofits don’t have a cadre of trained writers on staff. There are plenty of tools out there to help you. Editorial calendars. Page tables and content templates. (Yes, content strategy, when it comes to implementation, involves a lot of spreadsheets.)

But it comes down to this: Don’t try to do too many things well. Try to do a few things better than everybody else.

You’re never going to bring everybody on board with your cause, so writing for the masses may not be the most effective strategy. Take time to create at least some content for those who care enough to read it.

Technical infrastructure should be so good, it renders itself invisible

If you take the time to produce great content, you want to make sure it’s displayed in the best possible light – and by that, I mean your users shouldn’t notice the technology at all.

Fury Road benefits from a huge number of practical effects: things look like they’re blowing up because they are, not because some computer rendered its idea of what an explosion should look like. But almost every shot was still digitally enhanced. This allowed Miller to create the impression of large crowds:

Fury Road also makes extensive use of compositing to expand its visual palette:

When you’re actually watching the film, however, the "How did they do that?" gives way to breathless enjoyment of the chase. The movie feels real because the effects are integrated so well, they become part of the story instead of superseding it.

The same has to be true of your technology platforms.

Nobody cares what email platform you're using if the contents are interesting and easy to absorb – but they will notice broken HTML. And your constituents aren’t coming to your website to ogle its features, they’re coming for the content. If they notice the underlying functionality, then your technology is not serving your mission.

Stay true to your vision

When you think about it empirically, Fury Road should not have succeeded with a mainstream audience. It’s a two-hour chase scene. Its nominal hero’s face is obscured by a mask for almost half the film’s run-time. Its night scenes were filmed in bright daylight. It prominently features a tanker truck full of breast milk. And yet it has grossed nearly $400 million worldwide.

Fury Road succeeds because it stays true to its director’s vision. George Miller knew what he wanted – the entire film was storyboarded and the cast largely worked without a script – and put exactly that, and only that, on film.

By Google’s count, Fury Road has roughly 3600 spoken words. Even a relatively action-oriented movie like Jupiter Ascending has nearly 9000 – largely because it’s burdened by the presumed need to explain what’s going on to the audience through background exposition:

Your planet is just now entering its genetic age. You understand very little about something which is a vital part of our reality. In our world, genes have an almost spiritual significance. They are the seeds of our immortality. When the exact same genes reappear in the exact same order, it is for us what you would call reincarnation.


Fury Road doesn’t care about telling you what’s going on or why it’s happening, just that it is. Why doesn’t Furiosa have an arm? How did Immortan Joe come to control all the water? It doesn’t matter in the visceral thrill of the chase. We trust Miller because we know he’s thought through all of the backstory and decided it didn’t matter here. He’s right. And cutting the movie to its barest bones serves his vision perfectly.

All that to say: If you produce content for a nonprofit, you have a built-in advantage because you have your Mission, Vision, and Values as touchstones. You know the backstory about why your organization does the work it does, and that can – and should – inform every piece of content you produce.

Think about the story you’re telling in terms of narrative arcs. Most of the content you produce, while illuminating some aspect of your Mission, Vision, and Values, can’t tell the entire story of your work. Instead, capture the interest of your audience, delight them with carefully crafted, finely honed content, and link back to the bigger picture. Hyperlinks were created before content strategy was even a phrase, but they allow us to lay out our story in pieces, tied back to a central narrative.

Prepare for the haters

The Internet is pretty great at disseminating information. Now that it’s easy for anybody and everybody to post their opinions in a public forum, our access to information is limited more by our imaginations than the media gatekeepers of old who decided what story should land on the front page.

The Internet has both improved public discourse – and degraded it. Because here’s the thing: if you have an opinion, it’s almost guaranteed that somebody out there has an opposing point of view. While these used to be confined to local conversations, when you post that opinion online, they can find you. They will find you.

Social media has been great for nonprofits in terms of community building and direct interactions with constituents. But it has also allowed the haters to find each other. What might have been a marginal response to your organization’s work in the past becomes amplified by technology.

In the case of Fury Road, that response was a call for boycott from a group of "meninists". (I know! I had no idea that was a thing, either.)

After the movie came out, noted misogynist Aaron Clarey wrote some pretty hateful things on his blog: "Let us be clear. This is the vehicle by which they are guaranteed to force a lecture on feminism down your throat… This is the Trojan Horse feminists and Hollywood leftists will use to (vainly) insist on the trope women are equal to men in all things, including physique, strength, and logic."

You can read the entire article if you need a little anger in your day, but Clarey ends with a Call to Spitefulness: "So do yourself and all men across the world a favor. Not only REFUSE to see the movie, but spread the word to as many men as possible."

Never mind that everything that happens in Fury Road serves the story, not a philosophy. The plot, such as it is, hinges on the escape of five women from captivity. As director George Miller puts it, "Initially, there wasn’t a feminist agenda... I needed a warrior. But it couldn’t be a man taking five wives from another man. That’s an entirely different story. So everything grew out of that."

He’s supported by Chris Hansen, the director of the film and digital media division at Baylor University: "We’re used to women being in the background, not men. But Miller isn’t doing it as a statement, he’s doing it because that’s what the story calls for."

Because the story your organization is telling supports and builds upon your Mission, Vision, and Values, somebody, somewhere is going to assume you are trying to diminish them in some way. And they will spew their hatred like a firehose.

As part of your content strategy, you need to be prepared for reactions to the information you put out into the world. Carie Lewis, Director of Communications Marketing for the Humane Society of the United States, knows too well that "When sensitive topics come up, trolls come out in droves, and misinformation spreads... In today’s world, the only thing you can do is have a crisis plan in place for what to do if/when you get attacked. Because you just never know what the internet is going to glom onto."

The producers of Fury Road ended up benefitting from the "men’s rights" backlash because it stirred up a controversy that made people want to see the movie even more. We probably can’t hope for that.

Carie notes that, "Internal education is key. Help your staff navigate the waters with social media policies and trainings to protect them as well as the organization."

The HSUS has standards and procedures for responding to negative publicity, and those have been documented. Carie says, "It’s important for us to be honest while at the same time not drawing unnecessary attention to the issue... We develop talking points that address the issue but don’t get into internal details. They get routed through PR, membership, social media, and the executive offices."

Building on that, The HSUS tries "to respond to everyone who comes to us on one of our social media channels with a legitimate question or concern, and within 24 hours. That means all questions unless it's someone we know is just trying to stir up trouble. There are some people who live to cause trouble and that you will never win over. You have to know when to stop, and when to not even start. That comes with time and experience."

As a final word of advice, Carie offers that "One thing I see a lot is organizations trying to talk over the issue. We learned the hard way that approach just doesn’t work; people will see right through you and it will only make matters worse."

Your mission should be at the heart of the content you produce. When that’s the case, it will be easier to defend the work you do – and it will energize the people already passionate about your work.

Everybody wants to be loved, but the prospect of online backlash shouldn’t stop you from crafting great content that articulates the reasons you do the work that you do.

Now go see the movie already!

Thanks to Ivan Boothe and April Lambert for their edits and additions.

All images copyright 2015 Warner Bros. Pictures.

Categories: FLOSS Project Planets

DrupalCon News: Training Spotlight: Translate Your Web Site in One Day

Thu, 2015-07-23 15:44

Do you need to translate a website but don't have the time or money to pay someone to do it? This training will provide you with an overview of internationalization (i18n), localization (l10n), multilingual issues, and translation basics using the Lingotek Translation module. You will also receive mentored help translating a copy of your Drupal website (or a different one, if you'd rather).

Categories: FLOSS Project Planets

OSTraining: Find the Node ID of Drupal Content

Thu, 2015-07-23 14:35

Several times, our members have asked about finding the Node ID of individual pieces of Drupal content. The Node ID is the primary key in the database for Drupal content and it's useful in many situations.

If you don't have the Pathauto module installed, this information is easy to find. By default, the Node ID is directly in the URL of the content.

However, if you have the Pathauto module enabled (as most sites do) the Node ID can be hard to find. Here's the solution ...

Categories: FLOSS Project Planets

Cheeky Monkey Media: Resistance is Futile!

Thu, 2015-07-23 10:00

Back in June of 2014, the monkeys headed for Austin, Texas. We stormed the Drupalcon with adventure gear, and a few clever and even controversial tee shirt giveaways. One of the most popular tee shirt was the "We are Drupal - Resistance is Futile" tees.

We have brought it back for you in a free wallpaper version. Feel free to download the zip file (a whack of various sizes are available). We hope you enjoy, and feel free to spread the word.

Download Wallpaper


Categories: FLOSS Project Planets