- Copy-paste the useful stuff into a GoogleDoc file. Each category has a file.
- In Robohelp, create an HTML file out of each question in a category, and in the navigation tree, bunch all questions of a category under their category.
Saving the GoogleDoc files as Word files, and importing to Robohelp didn't work coz during the Googledoc > Word conversion, the formatting (and hence, the sequence of questions and answers) went for a toss.
- Export Robohelp files as Word files, proofread.
- In Robohelp, incorporate edits of stage 3.
Which means, compare the text line-by-line.
- Generate CHM.
To me, this seems unnecessary labour; stages 2 and 4 are especially wasteful. So, over the past several days, I've been thinking of changing the eBook process so that we can:
- eliminate the duplication of copy-paste at the compilation stage
- do on-going edits
I've come up with the following plan:
- Use a database (simple row-column db) to store data. The db needs to let us:
- Append through a Web-based form. Fields: category_main, category_sub, question, answer 1_name_email_date, answer 2_name_email_date, answer 3_name_email_date etc.
- Search, based on fields
- Define user levels: writer can put and get, editor can put, get and change.
- For compiling, pull the data from the database and append XML tags. Each column is a tag.
- Transform the XML to HTML, compile as CHM. The "category_main" and "category_sub" tags tell us the TOC.
Let's see how it goes. I'll need to research a bit.
Related post: Harvest, separate grain from chaff, release to market