The Web Project Guide

This episode pairs well with our episode from February with @cathymcknight on selecting a CMS. Between the two episodes, we’ve covered both sides of the equation — the technology, and the people who implement it. Check it out! webproject.guide/podcast/epi…

It’s time for a new episode of The Web Project Guide! This month, @deane_barker and @MrVilhauer talk with @TonyByrne from @realstorygroup about selecting an implementation vendor. What questions should you ask? What’s the process look like? webproject.guide/podcast/epi…

It’s time for a new episode of The Web Project Guide! This month, @deanebarker and @mrvilhauer talk with Elias Lundmark — hosting champion — from @optimizely. What do you need to know as a non-tech person when it comes to choosing a hosting solution? webproject.guide/podcast/epi…

A new episode of The Web Project Guide Podcast is here! @MrVilhauer and @deane_barker chat with @cathymcknight about content management system selection, the idea of "unknown unknowns," and how selection analysts keep vendors honest. IT'S A GOOD ONE! webproject.guide/podcast/epi…

This begins a few months worth of talk about content management systems — first, requirements; then the tools themselves, then the people who implement them. Until then, go ahead and check out this month - and then, subscribe. webproject.guide/podcast/epi…

More than that, it’s a discussion around the need for clear and actionable goals. Requirements aren’t just a checkbox — they’re the manifestation of your project goals, and every requirement you make has a history and a genesis.

It’s time for a new episode of The Web Project Guide! This month, @deanebarker and @mrvilhauer talk with @joekepley about how to translate design and content into something a CMS can understand. webproject.guide/podcast/epi…

We say it every month: we are excited for you to listen. This month, even more so! Like. Subscribe. Ring that bell. See you in your podcast feed. webproject.guide/podcast/epi…

But we’re not here to talk about details and harp on about frustrations. We’re here to celebrate great decision-making. @gregddunlap talks about how many integrations could be left alone, how Drupal handles integrations, and a bit about Google Docs. webproject.guide/podcast/epi…

The fun fact? Of those integrations proposed for an everyday average web project, we’d estimate that about half of them aren’t necessary. They could be solved by a link, or through existing functionality. They could be solved by someone telling a CEO to stop adding requirements.

We’ll be honest: integrations make us nervous. They’re important little pockets of data and functionality that we embed into our site — but they’re also sleeper cells. At any point they could burst. They could become obsolete. They could go rogue.

A new episode of The Web Project Guide podcast — in which @mrvilhauer and @deanebarker speak with @gregddunlap about integrations, Drupal, and the power of Google Docs — just dropped. You could listen, like, and subscribe. webproject.guide/podcast/epi…

We say it every month: we are excited for you to listen. This month, even more so! Like. Subscribe. Ring that bell. See you in your podcast feed. webproject.guide/podcast/epi…

And this month, it’s part of the podcast — our design episode features the master illustrator himself: @sam_otis. @deane_barker and @MrVilhauer chat with Sam about his path from Flash, how to provide feedback, and how to move from print to web. webproject.guide/podcast/epi…

We’re spoiled, because EVERYONE, at some point in time, has to worry about design. If you’re planning on building a website, design is a part of every step — it’s a part of scoping, it’s a part of content, it’s a part of development. It’s everywhere.

We’re spoiled, here at The Web Project Guide, because we never have to worry about design. Because we never have to worry about a designer. We’ve got one — it’s @sam_otis.

We are excited for you to listen. And, you should do just that! @escmum is charming and wonderful and an absolute blast. Like. Subscribe. Ring that bell. See you in your podcast feed. webproject.guide/podcast/epi…

The biggest key to this kind of work? It's knowing that content work is hard. It takes more than knowledge about grammar: it takes a lot of intense conversations, defined strategy, and a willingness to push back. And tea. A lot of tea.

Here's something that is very good: our JUST-DROPPED episode of The Web Project Guide Podcast with @escmum, in which @deane_barker and @MrVilhauer chat about content design, accessibility, and turning big organizations toward big change. webproject.guide/podcast/epi…

This was a very fun thing to record with @MrVilhauer and @deane_barker, so you should go LISTEN TO IT!