Page Inventory and Version Control
February 8, 2008 12:00 AM
Hi Erin,For version control, we use SVN and the Tortoise SVN client. It works pretty well to maintain version control over each file in our assembly. I'm thinking that isn't what you are asking though. You explicate a common problem. When a change is prescribed, how can I be sure that the change propagates to all areas of content / context. That's a serious challenge that is most often resolved with some simple solutions. For example, your storyboard document could / should have a table tacked at the bottom of the board description for changes. Four columns: Change Description | Date of Chage Request | Date of Change Verification | Verifier's Initials.It may seem painful, but the change needs to start in the planning documents and chain to the developed product. Now, if Lectora had built in facilities for adding 'field objects' on a per screen or per node basis - you could do all of your storyboard planning, execution, and maintenance in one tool. One can dream:)
Discussions have been disabled for this post