Content (Portability) is King Transcription

Geeks and God Episode 132 - July 2010

Pre-Intro

Welcome to the July 2010 edition of The Geeks and God Podcast. This month, we'll talk about

  • Calls to Action
  • Blogging with Posterous
  • Going Live; what do da as you move your Drupal Website from development to live.

Intro

Welcome, everyone, to the Geeks and God Podcast, hopefully we can talk about something that will help you out in your church or ministry.

South East LinuxFest / DrupalCamp SC

For show notes:

Posterous

Use Ed’s audio from February as a starting point for this topic.

I’ve never really used Posterous that much, but I do have an account. I just got their June newsletter the other day, and there are several updates since Ed recorded this piece a few months ago.

  • Posterous is aggressively updating their ability to import blogs and photos from other web services, especially those that have recently shut down, or are in the process of doing so. posterous.com/switch
  • Users can now add pages to their Posterous site, like “About Me” or a place to post contact information.
  • They’ve updated to a pretty nice looking rich media editor.
  • Their system now supports mobile versions of your blog.
  • They added several new themes, and - this is cool - they’ve added support for TypeKit so you can select custom fonts. (That could spin off into it’s own discussion. Maybe we should talk about font support on the web as an update to the sIFR podcast Matt and Bob did a couple of years ago. You know, there’s a problem with sIFR - it doesn’t work on the iPad.) fontsquirrel.com

Calls to Action

On the BoagWorld web design podcast (which, sadly, is coming to an end, or at least going on hiatus) Paul Boag frequently advocates the concept that every website should have an immediately recognizable call to action, and that every page of the website should lead users to completing that call to action. Given that as a premise, what calls to action should a church website contain, and how should pages lead users to that call to action? How effective is the church at following this model, and how could we improve?

Hans commented on the forum post that the #1 call to action is to facilitate communication. That’s true, but not exactly the focus of the question. By call to action, we’re talking about what immediate next step we want our users to take, either from the website or - more specifically - from that specific page.

(10 techniques post.) http://boagworld.com/design/10-techniques-for-an-e...

Drupal Spotlight: Going Live - Part 1 of 2

Check out (and contribute to) http://www.drupal-check.org/ for more tips!

  1. Set up a regular backup procedure
  2. SEO Checklist module
  3. Make your passwords easy to remember, hard to guess.
  4. Check & comment your code following Drupal Coding Standards
  5. Validate your HTML and CSS
  6. yslow FireFox plugin
  7. Delete any test content
  8. Remove any unused custom or contrib modules and themes
    • Disable unused modules admin/build/modules/list
    • Uninstall unused modules admin/build/modules/uninstall
  9. Disable unused regions in .info file
  10. Enable core Throttle module
  11. Install the Boost module
  12. Check the filesystem, remove any .tar, .PSD
  13. Delete unused Imagecahe folders. default/files/imagecache/[imagecache preset name]

Wrap Up

Be sure to give us feedback by

As always, we’d like to thank to our sponsor, MustardSeedMedia.com and also thanks to Bob Christenson and Matt Farina for their continued support of this podcast.

Note: This Transcription Currently Incomplete