LucidCMS

Lucid is nice, I like the abstraction they did in the templates, no mixing of PHP and html.

Is that what passes for a subtle hint in Florida?

Until LucidCMS supports a customizable URI structure and RSS feeds, it certainly wouldn't work for our needs. But it seems to be a nice start in the right direction.

WYSIWYG editing is not really tied to any CMS or Blog.

Picking a WYSIWYG editor:
1. Shop for the editor that works best with your browser
2. Look for a system that uses this editor
3. Try out the system and see how it incorporated the editor
4. Then start entering content, all types of content and see how the skin parser deals with the instructions.

The most popular content editors that you can tag onto a project work great in one browser but give fits in others. Some work great on Windows but have issues on Linux or OSX and vice-versa. Some even slow down your editing session if you happen to be on low end equipment, so if you post from somewhere other than your private P4/G4, be patient.

Now, that's one way to deal with content but it's not portable, and I'll tell you why.

The most portable of content is just plain text, it's universal, it can be fed to any system. Adding formatting instructions to your posts makes them only portable to systems where those same instructions exist, like the bbcode in this post. An editor just wraps your content with instructions, some of the fancier ones make posts into unreadable mounds of text.

There's two types of content in a normal post, text and images. Image placement and formatting can be handled with a few lines of CSS, you can carry those lines with you to the next system. In your posts, your images are wrapped by  <divs>, image on the left with text wrap to the right and the opposite.

Systems come, systems go, make your content portable.