> I'm ready to help edit the docs, but Mel I'm confused by the > wikifying... is the idea to generate PDFs from the wiki page?
The idea is to use the wikis to edit content (lots of tweaks to text, image selection, rough image placement), then when we're satisfied the content is done and ready to release, freeze it and have one design-oriented person do the layout in SVG and print that SVG to PDF. We'd previously skipped the wiki for the "edit the content" part of that workflow. > then update the SVG? For info, to keep track of changes I usually find > it useful every time I generate a read-only doc such as a PDF to > incude a rev number in the name, e.g. soas-v2-notes.rev02.svg -> > soas-v2-notes.rev02.pdf and then the final published version drops the > ".revXX" while the source keeps the rev number; simpler for others to > be sure which version they have I wonder if it might be worthwhile to have a gitorious repository for marketing materials - it sounds like we're already doing versioning with file-naming, and it might be easier to do with tools intended for the purpose. I don't know if the interface is such that this would actually be pleasant to do for the marketing team (as opposed to a more code-based team) but I can check it out. --Mel _______________________________________________ SoaS mailing list [email protected] http://lists.sugarlabs.org/listinfo/soas
