I’ll be switching from EE to WP too, as soon as I work up enough enthusiasm to get started on it. I think I’ll install a WP blog on one of my other domains first just to kick the tires and play with it a bit, while I figure out exactly WTF I really want to do with ObnoxiousBitch.com…

Glad you’re willing to share that script

Well, I’m pleased with my shift from MT to WP.  The Theme system is not ideal—but its flaws are largely due to the freedom that the platform provides.  Which means it pays to delve into what themes you use and figure out if they provide the support, flexibility, and features you want.

As noted elsewhere, Les, if I can be of any assistance (now that I am off my sickbed), please let me know.

I actually tried WPMU and I found it somewhat confusing to work with. Some of the changes from standard WP—the inability to embed YouTube videos without a separate plugin— also weren’t to my liking. In the end I went with the approach that seemed like it would allow for the maximum amount of plugin and theme compatibility. It doesn’t hurt that WP itself is supposed to eventually support multiple blogs in the future.

If you have lots of blogs you should consider using WPMU, the multi-user version of WordPress, it makes managing multiple blogs much easier, and lets you share user accounts between all blogs.

Les, you can run whatever you want for whatever reasons you want

It bears remembering that EE is a full-fledged content management framework (CMF) that evolved from a blogging tool; Drupal is best suited for a portal/community site, but runs a blog just fine; WP has always been a blogging platform that tries to branch out into CMS territory. Pick your poison, eh.

Supporting content publishers (to put it euphemistically) is an issue I don’t have, but even for EE it’s not uncommon to have developers set up stand-alone entry/edit forms to keep publishers away from the control panel. I personally don’t see a qualitative difference between Drupal’s content creation pages and EE’s SAEF—and WP’s control panel for that matter, although WP’s terminology annoys and confounds me at times.

There are advantages and disadvantages to running multiple platforms, like SEB on Drupal and the rest of your sites on WP. Obviously, it’s twice the learning curve and maintenance, but it also means that not all of your sites have the same security vulnerability at the same time. While I’ll always have a soft spot for Drupal, I don’t know that I would suggest running SEB only on it unless you have concrete plans to make it more of a community site—whatever that may mean. Other than “I have this here hammer, let’s look for a matching nail.”

I have, and continue to, played around with Drupal over the years. My biggest complaint about it is the same one I have with WordPress: The theme system is a nightmare.

That’s not what rules it out for most of the blogs I run, though. What rules it out is the fact that the back-end for it and the terminology it uses is a lot more confusing than what WP has. It’s the Linux of content management systems in that it’s very powerful, but has a steep learning curve.

That would be fine if I were setting it up solely for myself, but I host blogs for both my parents, my sister, my daughter, and a couple of family friends all of whom I’d have to teach how to use Drupal. WordPress is at least closer to what they’re used to from using EE. I could always set them up with WP (I already have one blog converted, the templates worked great) and then use Drupal for SEB, but if I’m going to be supporting WP it’s probably best that I run WP so I know it like the back of my hand.

That’s the logic I’m using anyway.

Webs, three interrelated reasons.

First, I’m turned off by the sheer number of third-party plugins people install for a simple blog. It seems like a maintenance hassle and segues into:

Second, WP’s security track record is abysmal compared to EE and the more third-party stuff you install, the worse it gets.

Third and most importantly, compared to EE WP seems like wearing a straightjacket. WP is a great piece of equipment, provided you’re okay with your arms being locked just so.

Drupal suffers from the first two issues as well, but I can get by with very few pieces of contributed software.

@Robert Grimm

I suppose if somebody would donate professional-quality custom themes, Les might reconsider Drupal

Before you switch, you should consider Drupal. It is more general purpose than WP. You can do nearly anything in it simply by installing a module. You can still have you wiki, though you will probably have to restart it unless there is a module that can import EE wikis. That wouldn’t surprise me since there are modules that can import WP data.

I’ll almost certainly be sharing the templates. I tend to share that sort of thing anyway, but considering the trouble I went through to figure them out there’s no way I’m keeping it to myself.

Les,
I too think it would be a good idea to share those templates. I wouldn’t need them, but other people might find use in them. I’ve been using WordPress ever since I started and found it a joy to use. The changes since first running it are truly impressive. And no matter how far behind I get in updating it doesn’t seem to have a drastic impact on my site which is nice. I have written some plugins and modified themes so if you have questions along those lines don’t be afraid to ask.

Elwed,
I think you should give WordPress another shot. I’m not sure what you don’t like about it, but you may find that the changes since you last looked at it have solved the issue. Maybe it hasn’t, but if it fits your needs I say why not?