A second question I have then is whether the same EasyBlog Composer editor would make sense, and be able to be used for EasyDiscuss posts, EasySocial stream posts and even Komento comments?

Hello Sean,

Most of those are for web admins, I think you could just write a very simple guide to teach them how to use the built in composer. We have simplified the whole user experience in 5.1 by a lot and it's as simple as clicking on the insert block, and choosing what they want.

From then on, most of it is already guided

Mark,

Thanks for the fast response. I will upgrade to 5.1 early next week. I don't want to do it over the weekend while you all are supposed to be operating on reduced support hours. :-) But, by early next week I will be very happy to switch since my users now get confused by having the EasyBlog interface with the JCE composer. I love JCE but in this case I believe going EasyBlog 100% will be best.

I may use JCE still for other areas like Komento and EasyDiscuss although having only ONE editor throughout all aspects of the web site seems like a really great idea for the future. :-)

Have a great weekend.

Sean

Not a problem at all Sean Since you guys are great in writing articles, perhaps you could cook up a PDF to provide to your users?

I will definitely have to write up something as simple as possible so that I don't have to call the bloggers on the phone and train them individually which is what I end up doing now. :-) Hopefully the new EasyBlog with the Composer will be so simple that I will only have to write a couple short paragraphs. :-)

Sean

Yep, it will definitely be simple In fact, you could start writing by testing on our beta site here, http://beta.stackideas.com

Ok. I am hooked on this new editor. Now I am hoping there will be a way to eventually import my older content into this editor to be able to take advantage of the Blog, Magazine and Grid layouts. :-)

Hello Sean,

Unfortunately right now it's not possible to import from older WYSIWYG editors into the built in editor This is because the built-in editor stores quite a bit of meta data for it to be able to process the content.