We up-issued the CogniDox WordPress Blog Plugin this week.
The key change are support for posting online-editable documents from CogniDox and enabling the definition of replacement strings to be applied in posts.
Here's how I used it writing this post:
I created a new document type called "BL" for blog post. Feel free to use any 2 letter suffix that isn't already in use on your CogniDox installation. I made sure to check the Online Editable box which allows me to edit documents of this type using the online HTML editor. I created a new document part, giving it the title "Using the CogniDox WordPress Blog Plugin" and selecting BL as the document type.
Now whenever I select Add Draft or Add Issue, the page will display an Edit Online button next to File to Add, because BL is an online-editable type.
Clicking the Edit Online button launches the rich text editor. I can cut and paste text into the text field. I can add images. I can change the formatting using a range of HTML icons. I can also insert a range of CogniDox metadata types such as the title, part number, version, issuer's name, and more. Here's an image that I uploaded from my PC and saved to the CogniDox server:
As I finish an editing session I save my work with the Store button, which returns me to the add draft (or issue) page. I could at that stage send the document to my colleagues for review along with comments, or notify someone that I've added it. But when I'm ready I save my work using the Add Draft (or Add Issue) button. Repeat as necessary until all those great points and insights are out of your head and written down in the blog post!
I've talked before about some of the practical issues maintaining a blog for a company when more than one person is contributing. In the traditional publishing world there's a concept known as an Editorial Calendar. At it's simplest, that could be a list of article titles, name of author and date required-by. But you can go beyond that to add all sorts of metadata such as the theme, tagwords, target audience, conversion goal and so forth. The blog "commissioning editor" could create a number of CogniDox part numbers, one per blog article, and delegate them to their authors. As each one gets progressed it can be reviewed and ultimately approved for publication.
When this blog post was ready, I promoted my latest draft to an issue and approved it.
From the actions menu on the document details page for my blog article I selected the "Send latest approved version to WordPress" action. It displays the format for me as it will appear on WordPress and if I'm happy with that, I publish.
What we also did this week was extend it slighly for another customer so they can publish news articles. Like many companies these days they've contructed their public website using WordPress as the CMS and there's a section on there for News. Each article has a title, an image and a summary of the article. Click on the title and it displays the full article in a new page. It took a change to the online editor: insert a horizontal line where you want the summary to end, usually at the end of the first paragraph, and it works out how much of the article to display in the summary view and puts the rest into the full body of the article.
Again, an easy and pain-free way to manage an article from inception to publication, with far less danger of sending the wrong version or putting the wrong text with the wrong image.
Anything that streamlines the process of generating content allows more time for actual publishing. And we all know the SEO value of good content.