At Nav we are sometimes asked to provide resumes prior to a project engagement. We've tried various methods for managing these documents. Each method meets the same fate as any other content management/document management problem meets: If the owner of the content does not have an effortless way to publish the content, the content stagnates.
What better place to serve these documents than each employee's internal blog? Radio will upstream any file placed in the Radio directory structure. So, we can just drop the resume into our internal-only category and it will get upstreamed to our blog server. Next, you need to provide a link to the document. One way to do this without managing a category-specific template is to create a #navigatorLinks.xml file in your category folder and then customize it by including a link to the resume. I cleaned up mine further by eliminating the links to my public blog categories with a summary category called "Public Site". (I learned this technique through this thread).
Now, I can keep my internal resume up-to-date and accessible to anyone who needs it. Yet another piece of knowledge I can manage through a single interface--Radio.
12:53:46 PM 
|
ZopeMag, the only Magazine devoted exclusively to Zope, is looking for freelance writers. [