Skip to Content

For those of you who haven’t yet tried the new Troubleshooting Guide, here are five reasons why you have to check it out now:

 

  1. It’s problem-oriented – you know what’s wrong, but you don’t know how to fix it – the wizard will guide you step-by-step to find your solution.
  2. It’s interactive and Wiki-based – you won’t need to read thousands of pages to find your way through. You only need to answer a few simple questions and you are there.
  3. We cover the most frequent scenario in the Java server area (that is, startup problems) but we plan to add more content soon. Let us know of areas where you would like to find a solution or if the solution was not what you expected.
  4. We will grant points for each valuable suggestion for content or structure improvement –your feedback is very important for us.
  5. And last but not least, we plan to very soon open the guide for editing to the community – you’ll be able to contribute, shape the guide, and get points for that.

Caught your attention already? Have a quick look at the Troubleshooting Guide and let us know what you think.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Former Member
    Wonderful start ! Documentations are tiring..and structuring stuff in this way is real hard work..

    Kudos and good luck !

    In case of Q/A like the current one , isnt there a chance of too many questions being there once the content increases ? And navigating through content might turn into a nightmare..

    I had recently seen a MindMap model from Chris Wealy for help in webdynpro. It classified topics in a tree.. somethin similar to classify prob areas and then navigating to the FAQ section would be awesome.!

    Lookin forward..

    -Bharathwaj

    (0) 
  2. Richard Hirsch
    Great idea. I just wanted to ask what sort of methodology you used to create the structure of the wiki.

    Are there are any plans to create such wiki-based guides for other products(Visual Composer, etc.) and other decision-making processes (how can I define an Enterprise Service, etc.)

    D.

    (0) 

Leave a Reply