Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Information Architecture (Product Documentation) on Confluence

4,016 views

Published on

Confluence as a flexible Information Architecture for Product Documentation and Collaboration. Integrate and optimize your worlds.

Just a snapshot of the many benefits -

Questions, please contact me. :)

Published in: Technology
  • Sex in your area is here: ❤❤❤ http://bit.ly/2Qu6Caa ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating for everyone is here: ❶❶❶ http://bit.ly/2Qu6Caa ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • P.s I am now at AppFusions.com (since April 2010) ... ellen@appfusions.com

    Here's a GREAT post along this theme of 'DocOps' -
    https://answers.atlassian.com/questions/9381297/answers/9382024
    Putting it in play with translations too - at https://wiki.ca.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Nice slide-set. It really covers a lot of the advantages of moving to this model. Two of the companies I studied for my thesis on SME wiki use overcame many of these issues by moving from dedicated documentation systems.

    This presentation didn't really go into any info architecture details for wiki implementation though. Would love to see more about this process.

    Thanks Ellen.

    Stuart French.
    www.DeltaKnowledge.net
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Information Architecture (Product Documentation) on Confluence

  1. 1. Streamline and Optimize Your Information Development (Product Doc, etc.) and Delivery Platform A Flexible Information Architecture Strategy www.customware.net Australia - United States - Malaysia - New Zealand
  2. 2. Highly Flexible to Many Use Cases Copyright © 2001-2009 CustomWare
  3. 3. Eliminate Specialized Skillset Reqt <ul><li>Eliminate high-end documentation application dependency – standard, easy tools, clean copy </li></ul><ul><li>Quicker information development </li></ul><ul><li>Reduced SW costs of niche tools </li></ul><ul><ul><li>FrameMaker ($850/seat) </li></ul></ul><ul><ul><li>Pro online help compilers ($2K - $4K per seat) </li></ul></ul><ul><ul><li>Adobe Acrobat Prof ($200 - $400 per seat) </li></ul></ul><ul><ul><li>Cost of expertise using these tools </li></ul></ul><ul><li>Eliminate ongoing specialized skillset cost/req’t (sometimes hard to find, esp. if PT req’t) </li></ul>Copyright © 2001-2009 CustomWare
  4. 4. More Cost Effective Processes <ul><li>Collaborative team effort info dev’t (w/lead driving strategic direction and guiding input) </li></ul><ul><li>Reduce time-consuming restrictive linear email reviews (and inherent inefficiencies) </li></ul><ul><li>Many hands vs. sole tech writer dependency </li></ul><ul><li>Visible copy vs. stuck on tech writer’s sys, non-transparent evolution, and peer-to-peer emails </li></ul><ul><li>*Anyone* can cross a “t” during process – not only pricey tech writer w/ high-end toolset </li></ul><ul><li>Single-source for Confluence, PDF, Word, XML </li></ul>Copyright © 2001-2009 CustomWare
  5. 5. Flexibility Flexibility… <ul><li>Web-based distribution (provisioned or open) </li></ul><ul><li>Doc templates </li></ul><ul><li>Efficiency macros for extended functionality </li></ul><ul><li>Auto-TOC, simple clean layout, hyper-links </li></ul><ul><li>Multi-media and content distribution support (embed viewable video, .doc, .pdf) </li></ul><ul><li>Context-sensitive help (unique URLs) </li></ul><ul><li>Label tagging for extendibility or rels mgmt. </li></ul><ul><li>Per doc or per release “Space” mgmt </li></ul><ul><li>Auto indexing and advanced searches </li></ul>Copyright © 2001-2009 CustomWare
  6. 6. Supporting “Special Customers” <ul><li>Support OEM branding or unique one-off variations (like “conditional text” need) </li></ul><ul><li>FREE personal version “short” server instances for locked down “view-only” external doc deployment </li></ul><ul><li>Flexible to support unique permission requirements with simple parameter adjustments </li></ul><ul><li>Open for additional collaboration/engagement with customer in *other* non-doc spaces, as needed </li></ul>Copyright © 2001-2009 CustomWare
  7. 7. Controlled Evolved Corporate Asset <ul><li>Develop valuable corporate asset over time </li></ul><ul><li>One place for all documentation vs hidden fileshares, etc. </li></ul><ul><li>Link or search legacy fileshares, as needed </li></ul><ul><li>Searchable content allowing instant and evolving knowledge management system </li></ul><ul><li>Enable outside firewall as SEO platform and ultimately marketing asset (if or when) </li></ul><ul><li>Customizeable themes/layout (CSS) per space/doc </li></ul><ul><li>Extendable as application deployment, as needed (open APIs) </li></ul>Copyright © 2001-2009 CustomWare
  8. 8. Some Examples <ul><li>Atlassian SW Example </li></ul><ul><ul><li>http://confluence.atlassian.com/display/DOC/Confluence+Documentation+Home </li></ul></ul><ul><li>Public site examples: </li></ul><ul><ul><li>http://confluence.atlassian.com/display/CONFEVAL/Live+Confluence+Sites </li></ul></ul><ul><li>CustomWare.net </li></ul><ul><ul><li>http://www.customware.net </li></ul></ul>Copyright © 2001-2009 CustomWare
  9. 9. Dedicated Atlassian Partner <ul><li>Thoughts, questions, or clarifications? </li></ul><ul><li>Ellen Feaheny </li></ul><ul><li>CustomWare Asia Pacific (USA) </li></ul><ul><li>831-247-9417 </li></ul><ul><li>[email_address] </li></ul>Copyright © 2001-2009 CustomWare

×