Archive for WordPress
My wife told me about this tragic story of a Southern Baptist pastor being killed in Illinois … and when I saw his name I remembered I had interviewed for a story a couple years ago when I was communications director for Midwestern Baptist Seminary.
Please keep his family and church in your prayers.
I can’t tell you how excited and blessed I am to be given this opportunity here at Church Communications Pro and to be able to explore new territory! I have all kinds of ideas jumping around in my head but I know that I am going to have to pace myself and learn some new skills and take time to do this right. I am going to share a bit of what I envision happening here at some point:
- Great interviews and Q & A Sessions with some really cool people from a variety of church backgrounds, visions, and skills. I love learning from others in the trenches and hope this will be a sweet addition.
- Pre-designed and Open Source products such as sermon branding kits, blog headers, website skins, connect cards, and more. I have stuff I have been working on for some time as well as have a few talented designers who will be contributing their stuff as well.
- Guest writers who will contribute excellent articles in their area of gifting or skill sets.
- Consulting for churches
- Sponsorship opportunities and additional resources
These are just a few ideas that I have, but what I am requesting is feedback from you, the Church Communications Pro readers. What are your suggestions for improving or building upon the foundation here? What would be beneficial for your church or ministry? How can I make CCP even better? Please think about providing your two cents to me personally or responding here in the comment section. I really appreciate it!
Raj at Performancing has a nice post about using WordPress as a content management sytem.
He lists these benefits as reasons to use WordPress as a CMS:
- Undated URLs — Change the permalink structure. Click on the “Options” tab then “Permalinks.”
- Posts vs pages — On most of the sites I do with WordPress, the permalink structure looks pretty much the same for posts and pages.
- Contact forms — I use Chip’s contact form and love it … I think I’m getting more response from people as you don’t have to copy and paste an email address, etc.
- About Us page
See also how to finetune your WordPress blog with this excellent article.
You might also check out the whole series on using WordPress as a content management system I did recently …
Check out this rockin plugin for your WordPress-driven blog or church website called Really Simple Site Map.It lists every post and page you’ve ever published and a solution to a more polish sitemap than the Google Sitemap Generator plugin (which still rocks).
I get dizzy looking at it … lots of sleepless nights!
[Found via Weblog Tools Collection]
Update: Lorelle of the famous and insanely useful Lorelle on WordPress blog stopped by to correct some things about this post. She gave me an education … and I’m just honored she stopped by! Here’s what she said in the comments that I don’t want you to miss:
Just a little clarification is needed here. There is a LOT of confusion between the terms “sitemap” and “site map”.
A “site map” is a listing of your blog posts on your blog, like a table of contents. This is what the poorly named “Really Simple Sitemap” does. It should be “Really Simple Site Map”.
A “sitemap” is a hidden XML file that is read by Google, Yahoo, and other search engines as a guide to all your blog posts. It isn’t “readable” by humans since it is inside a bunch of code. That’s what the Google Sitemap Plugin does. That’s correctly named.
You might want to fix your post to correctly label what does what. You offer such great information, I’d hate to see this confusion be perpetuated.
Thanks and keep up the great work.
If you’ve been following my Using WordPress to Run Church Websites series, then I need to add an additional plugin that allows you to easily put a contact form on your church website.
Here are two plugin options that automate the form and process: