TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Tracking and storing blog posts From:"Janoff, Steven" <Steven -dot- Janoff -at- ga -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 8 May 2013 16:34:58 -0700
Hi Whirlers,
Wondering if you can help me with what I believe is a tech comm challenge.
A friend of mine has a blog and I am helping him by editing and storing the blog posts and tracking whether or not they are posted/published.
I am trying to figure out a software solution that will help me do the following:
1) Store the original (unedited) version of the post as well as the edited, ready-for-publication version (occasionally there are 2 or 3 edited versions but usually just an original and one edited version)
2) Track whether each post has been edited or not yet edited
3) Track whether each post has been published (posted to the blog) or not yet published
That's it. Currently about 50 or 60 posts in the hopper (about half have been published), and could grow to hundreds.
I don't have any contact with the person who runs the blog site or actually publishes the posts -- I provide the edited posts in raw text form and it goes off from there. For various business reasons we're keeping these roles separate.
I'm thinking some kind of content repository.
I appreciate your thoughts with this.
Thanks,
Steve
PS - My current system is to store the posts in text files and try to organize by folders and also track via draft numbers in the filename but that's a losing proposition and I'm also losing track of which ones have been posted/not posted since I have to check those against the blog. The current system is just not working. I need something clean and efficient. Thanks again.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?
