I upgraded to the latest version and it answers my every prayer hanks for this awesome plugin, and now it can be shown/hidden as need be, which makes a huge difference. Sorry I blogged this before trying the new version, I musn’t have had it installed on UMW Blogs, so that’s my bad.

Also, I appreciate the warning about editing themes, I know there’s risk involved, but we have a pretty tight leash over who can, and who cannot edit these themes. So, in the end, I am not too concerned about the risks, though I guess this is why backups come in handy.

Why thank you, we learn from the best of the open folks like yourself. And I have to say that going through each tab on the backend of UMW Blogs was an important process for me getting to think about the interface. It was a necessary labor to remind myself of the fact that this stuff isn’t necessarily as easy and intuitive as I sometimes believe. More than that, the narrative bumps which I kept in the screencasts) suggest the idea you point out here beautifully, my own issues with telling the story mark the spaces in the interface that need to be worked on, or at least explained more clearly. Doing these screencasts in the rough, as I have, has been really important for tracing where this application exceeds, and where it doesn’t.

Thanks for the kind words, Bill, always appreciated. (here we go being nice again )

You guys are Rock Stars for the work you are doing, and for making it available.

RE: “these screencasts helped me see some of the obstacles I had been overlooking for people who are coming to this application fresh” — amen to that. One of the beautiful things about creating documentation is that you can see where the user gets bogged down — it’s usually exactly the same place where you (the docs writer) struggle with how to organize/explain the process.

Thanks for this — it’s a great resource.