[semanticist]

Does it spit out a Word document at the end? If not, it's not useful for people who expect to hand data to recruitment companies.

I work for a company that provides CV/Resume parsing services to recruitment companies, and they all want Word documents they can reformat to their house style (and usually anonymise so the employer can't contact the candidate directly) using automated software (either ours or their CRM provider's).

Are you taking structured data from people to generate the resume? Have you considered generating HR-XML which can be passed straight to various CRMs and HR tools?

Do you provide an API to allow multi-board search tools (which we also produce) to search the resumes on your service? Recruitment companies don't want to search your site individually - they want to search everywhere at once.

You're just getting started, but trac's really not a good choice for managing your end-user help! Save it for your developer documentation and get something nicer in there, quickly!

[mikeyg]

It does spit out a word document at the end (if you want one).. The URLs are RESTful. To get a document file out of a resume go to the resume / view you want then do filename.ext.. so http://michael.gregorowicz.praux.com/resume.doc would give you a word document. .txt, text file.. .odt, .pdf, etc!