Sounds like your going to have to if you want it to take up less time.

For instance, I'm dead set against the wiki being used as a database
like this. It's not meant for collaborative writing and is the wrong
tool for the job. Even a google doc spreadsheet would be more structured
as you could export it.
  
I'm not sure about now, but when I last looked in to Google Docs (prior to using a wiki) it had some limitations, file size if I remember rightly, which meant we couldn't open a new document with the necessary images in the document. Also using Google Docs would mean inviting proof-readers to each document which is a bit of a pain, unless this has changed...

Get together some scripts to generate svg xml based on your data, then
you a hop away from just re-editing it in place instead of copying and
pasting.

Your also on track to be able to feed it into html.
  
I have no idea about that stuff and, since we're volunteer based, if people don't volunteer, I can't magic them (but I wish I could!)  :/

Ultimately what you want is a way for all your writers and collaborators
to contribute and for there to be a very minimal set of editing tasks
that join everything together.
  
Absolutely, but there doesn't seem to be a good set of tools available at the moment. Most CMS apps are either missing something or just do what we do now (ie: wiki).

Last thing we want is one bloke doing all the work manually and getting
the right tools together is just as much about saving your future time
True, but I can only work with what I have I'm afraid...   :/

-- 
Ronnie Tucker

[email protected]
www.RonnieTucker.co.uk

Fb: facebook.com/profile.php?id=585438496
TWITTER: twitter.com/ronnietucker
MSN: [email protected]

Registered Linux User # 456627
Registered Ubuntu User # 18227
-- 
ubuntu-marketing mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-marketing

Reply via email to