You are currently browsing the category archive for the ‘Wordpress’ category.

Previously I looked at how to add simple maps to your church website, but for a wordpress site this was complicated, because of the artificiall nature of the directory structure if the site is using re-written URLs. Basically a plugin was required.

Now Google has provided another mechanism for including maps that can be inserted simply by embedding them in pages. All that is needed is to copy some HTML code and paste into your church’s webpage.

You need to login to your account on Google and click on ‘Maps’, then ‘My Maps’ to get started. When you are happy with the map, you can click the ‘emded this in a webpage link’ on the right hand side. If your map is of a church in the UK, then I recommend signing into Google from Google UK, as I had problems otherwise.

You can add other features easily to the map, such as other important points nearby to the church. For example, car parks and travel facilities (trains, buses etc.). This become clickable, and can contain other helpful information.

You can see it in action on my church’s website.

A WordPress plugin has been released to bring bible verses in blog posts to life, by linking them to eBible.com and also showing the verse as a ‘tooltip’ via the title tag.

There is a demo blog which shows the plugin in action.

Like other plugins, you drop it into the wordpress plugin folder, but before it works you need to complete the options screen. Most importantly is the eBible.com API key that you need. You can get a free one here.

Read the rest of this entry »

I have finally got round to embedding a google map of the location of the church on our church website. This is a much better solution than just scanning a map from a roadatlas and uploading it (which breaks copyright law) or linking visitors to external sites, which may mean you lose those visitors.

I used the wordpress plugin called GeoPress. It is simple to set up once you have signed into Google and obtained an API key (Google Maps API registration). (Note: enter your blog url as the GoogleMaps URL).

Then you can add maps to any posts or pages, but most importantly for church website, to the map and directions page.


Related: Easy Google maps embeded on your church website, without the need to use a WordPress plugin.

The WordPress.com state package is now available for all wordpress blogs as a plugin. And the stats that are collected are displayed in the same place as the WordPress.com blog(s) that you have. You can get the plugin from WordPress.org

WordPress.com statistics are certainly not as sophisticated as some packages (such as Google Analytics), but they are easy and quick to understand. Also, it will not interfere with other statistics packages, such as Mint, Google Analytics, and Statcounter.

And for people like me with a church website on WordPress.org and another blog (this blog) on WordPress.com, it is very convenient to have the statistics in the same place.

For church websites, the main reason they want to use flash is for impact. It can look really professional. However as mentioned before the main downside is accessibility.

But if all you want is fancy rotating graphics, perhaps a bit of AJAX can help?

Tim Hyde has modified one of his wordpress themes and incorporated JonDesign’s SmoothGallery. It looks fantastic and mimics the flash clickable gallery seen on many large church websites. But best of all it is fully accessible, with changing title, alt, etc. attributes for the elements.

A guest post on Church Marketing Sucks briefly discusses using RSS or other feeds to provide information to church members. For instance different types of news and announcements. If your church runs their church website on wordpress then this makes it easy to do as each category has its own feed, so that as long as you post different types of news to different categories subscribers can follow them independently.

For instance on this website we have the category ‘church humour’, which is located here:

churchblogger.wordpress.com/tag/christian-humour/

And the RSS feed is located here;

churchblogger.wordpress.com/tag/christian-humour/feed/

It is found simply by adding /feed/ to the end of the URL. Fancy an atom feed? Just append /feed/atom/ to the end. If you do this to a post rather that to a category post list (as above) you will have the RSS feed (or atom feed) for the comments to that post. (And by default these comment feeds come prefixed with ‘Comments on:’, in the feed title so that in a feed reader it is clear it is a comment feed. For example:

churchblogger.wordpress.com/2007/02/11/fitting-in-at-church/

Becomes:

churchblogger.wordpress.com/2007/02/11/fitting-in-at-church/feed/

But there is a problem, and it is to do with privacy. The CMS post suggests prayer requests, but many of these with be of a confidential nature. They cannot just be posted on a public website for all to see. Even if you do not tell ‘outsiders’ what the feed URL is, you cannot keep it private for ever, as your church members will use bloglines or another feed reader to subscribe or google will find it.

One solution is to use the wordpress password-protected post feature, setting a password. These posts appear in the feed, but without the content. Church members can then go to the website and type in an agreed password.

The only thing to consider is that it makes the church look uninviting and closed to outsiders if when they visit the church website to see many password protected posts. The best option here would be to stop entries in this category appearing on the front page loop.

Feeds are very powerful and with wordpress as your content management system for the church website, management of them is made easy.

Following on from an earlier post on styling your church website which suggested in more than one place to edit CSS, it is perhaps necessary to explain the CSS editing process and what you can do to make it easier.

But what is CSS? Here are some resources;

For more practical help in editing CSS you may want to look at an excellent article by Lorelle on building a sandbox for theme development. She describes a technique for speeding up the CSS editing process and ensuring all elements are styled. (This is not the same however as the sandbox theme though I wrote about in a previous post).

My only advice is to dig in and try. You may get frustrated, but don’t give up. And when you think you are happy be sure to test and retest your work on a range of systems and browsers.

Archives