The purpose of ChurchC.ms is to find and report on every CMS that focuses on Churches. We’ve finished posting each one that we can find, and are organizing them by tier. A tier is a subjective distinction that delineates different levels of ChCMS, primarily based on size and time on the market.
Check this out: WP Unite is a simple system which allows you to manage multiple WordPress blogs in a single interface and admin panel.
It’s got some additional features like analytics that give it that extra “punch” that was, functionally-unnecessary but very nice.
It’s free for the first two blogs and then paid for more after:
This is Part 4 of The Complete Guide To Writing a WordPress Widget Series.
By now, we’ve read through the WordPress API, stubbed out our plugin, worked through the requirements, and come up with some paper napkin sketches of our administration panel.
At this point, we’re ready to begin implementing the plugin. For this iteration, we’re going to focus on getting a functional administration panel working.
This is Part 3 of The Complete Guide To Writing a WordPress Widget Series.
At this point, we’ve got enough code written such that we can begin implementing certain aspects of our widget.
As mentioned in a previous series, iterative development is a great way to develop your projects (and it’s part of my preferred development methodology) so we’re going to be applying that to developing our Tweet It widget, too.
In this iteration, we’ere going to be working on the administration panel. Specifically, we’re going to outline the requirements of the administration panel, develop the look and feel, and then refactor some of the code.
This is Part 2 of The Complete Guide To Writing a WordPress Widget Series.
The process of creating WordPress widgets is relatively straightforward regardless of what functionality you’re building. That is to say that thanks to the WordPress API, there’s a standard way to put together a widget
But before jumping into writing code, it’s important to understand how to navigate and to use the available resources for WordPress-based development.
In this post, we’ll take a quick look at the WordPress Codex and then put together some skeleton code that we’ll use throughout the remainder of this series to create our plugin.
Osmek is honestly a pretty neat idea: A “new” kind of CMS, it’s built entirely in the cloud so it’s readily available wherever you are. A nice interface, a powerful set of APIs to use, you might end up liking it a bit too much.
It’s free (for smaller systems) and will cost you if you scale:
Check out the UI as well as this demo of building a blog: