Blog editor group test part 3
Interim results:
- w.bloggar
- ecto
- zempt
BlogJet doesn’t get a ranking because it is a WYSIWYG editor and, therefore, a fundamentally different beast.
Add comment May 8th, 2005
Archive for May 8th, 2005
Blog editors group test part 2
I am half way through the group test of offline blog editors which I started yesterday (in between drawing up a site map and wireframes for a client site). So far, so good - I am writing this in w.bloggar, having tried Zempt and Ecto.
Each has strengths and weaknesses, which I will summarise in a future post. For now, here are the criteria for the test:
-
Is the editor easy to set up? I want to be able to instal the editor, hook it up to my WordPress and Typepad blogs and go. Plain English instructions are always welcome
-
How does the editor cope with two blogs and multiple posts? Does the editor recognise the difference between a draft and a published post? Is it easy to select between my two blogs and multiple posts? Can I edit a published post?
-
How easy is it to write and edit posts? Can I style text as quickly and easily as with the WP and TP’s online editors? Does the editor play nicely with Textile or Markdown ? Can I add in my own XHTML tags? Can I assign multiple categories to a post?
-
Does the editor work properly? I know these things are shareware or even freeware, so the developers can’t spend time testing every damn thing, but if I can’t do all the basics without errors and alert boxes, then it’s game over.
-
Does it feel right? I want to be objective because I will be making recommendations to clients based on this test, but most of all, I have to be happy with my choice.
Right - this is in w.bloggar with Markdown - let’s see what this looks like… ?
Update: The answer to that question was pretty darn great, until I decided to amend this post with my next editor - BlogJet. BlogJet loaded the Textile markup into it’s WYSIWYG editor and stripped out all the line breaks, leaving - stone the crows - one great big paragraph. I went back into w.bloggar, which is my favourite so far, and re-Textiled this post.
I must confess to a hand coder’s in-built aversion to WYSIWYG, so I don’t see BlogJet coming out on top for my purposes. To be fair, everything else about BlogJet looks good, so I may well end up recommending it to clients who don’t want to dirty their hands with markup.
Add comment May 8th, 2005