content

Producing relevant, up-to-date online content is a challenge for content managers everywhere. The bigger your content output and the more stakeholders you have involved in the process, the harder it is to keep track of whatever is being created, edited, and published. If this is your use case, what you need is a clear, easily manageable content publication workflow.

We all recognize bad information architecture when we see it on a website. There are some signs that the creators didn't do a great job in terms of content structure and organization:

• Confusing menu labels
• Haphazard topic organization
• Critical information and actions jumbled in with general news and marketing copy
• Site searches that return useless, obsolete information

While it's frustrating to come across these issues on someone else's website, it feels much worse when we realize we've made those mistakes ourselves.

Since the start of lockdown in March, you’ve probably seen way more live streams on social media than you ever had before. These are taking places on platforms like YouTube, Instagram, and Facebook Live.

We recently got a question at a training from an attendee whose organization has been doing more live streams on Facebook. They also use Drupal’s built-in Media module and were wondering how they could embed their recorded live streams from Facebook onto their Drupal site. In today's tutorial, I outline two different methods for pulling this off.

It’s a new year, and one of your resolutions might be keeping a more minimalist lifestyle. A few years ago, I read Marie Kondo’s book about the benefits and practice of keeping things tidy. And it planted a seed in my mind about how this applies to content. And in particular, your content strategy. How can we apply the same techniques that result in a well-organized drawers and closets to well-organized content hierarchy and navigation? How can they guide your next content audit?

Sometimes, we find issues with content that are not anticipated by the planning process since they don't show up by looking at sample content or discussing the major use cases of the site. By looking at real content during the data import phase, these issues can be dealt with at an early stage in the development process.

Building a comprehensive information architecture for a content-heavy website can be a challenge. Luckily, Drupal is great for rapid development and by building content types early on, it's easier to discover issues with either the content, design, or architectural decisions.

Every project we do at Evolving Web has a content import component. Whether the content consists of legacy data sources or a single CSV file with freshly written text, we usually have enough content to consider writing one or several import scripts to import it into Drupal.