Ok, so here are the contestants:
Typo – Ruby on Rails, not as fully-featured but growing.
Drupal – Very cool looking, lots of plug-ins and features.
WordPress – Lots of people are moving this way, but I hear some complaints as well. I love the wealth of plug-ins.
Community Server is pretty much out of the running in my mind, I don’t like the bloat-factor (all I need is a blog) and I don’t like the license it’s released under. (some of my favorite software is the result of “code forking or derivative versions”)
I will be trying each of these out over the next couple weeks and try to make a decision, right now I am leaning towards Typo.
-James
{ 11 comments }
If you’re interested in a .NET blog engine, there’s still Subtext (soon to be released). We have a few very nice looking skins.
(http://micahdylan.com/) and much better comment spam handling than .TEXT.
Oh, AND we can import .TEXT. I’m putting the finishing touches on the UI for that right now. But the SQL script has been and currently is 100% finished.
Don’t forget SingleUserBlog
http://markitup.com/Posts/PostsByCategory.aspx?categoryId=bc1e0ae5-7908-452d-a936-f296ba379f23
It’s coming along nicely and is now .Net 2.0
> don’t like the bloat-factor
Ouch James, that hurts. I think you should really re-evaluate this unless you’ve actually installed it.
First of all you won’t find this to be true. Much as the the design for ASP.NET 2.0’s Membership, Role Manager, and Personalization features Community Server segments all of its functionality so you can run ‘just blogs’. For exmaple, blogs.msdn.com or gearlog.com are two great examples of sites running Community Server blogs. Granted Community Server is designed for > 1 blogger/user.
I will add it to the running and give the install a shot, but the license is what really bugs me even more than the other issues. If I am correct I can’t even get MetaBlogAPI support without buying the commerical license and an add-in?
-James
Metablog API is not a paid add-on, it never has been. With v1.0, it wasn’t included with the release because it wasn’t ready in time (I believe), but it was in with v1.1 and is with v2.0. Metablog API is such a basic feature it would be like selling someone a car without any tires if we didn’t include it.
What about dasBlog? I’m using it for nearly two years without a problem.
I hear you about the license. Wish they included more options with the community license. I hear even IP blocking is now a paid add-on.
Have a look at my single blog site running off of CS. There is no bloat…
Thought I’d mention that Typo is included in the Instant Rails download, so it’s extremely simple to get set up. http://rubyforge.org/projects/instantrails/
I’ve got CS running on my blog, linked above, and will definitely agree with the bloat factor. It’s nice having the galleries tied into an app, but for 1.1 they still are too different to make it feel like one site.
Hopefully when I upgrade my personal site to 2.0 it’ll get better, but I still miss the .Text days
Comments on this entry are closed.