Configuration Example Template 8

From DocWiki

Revision as of 11:37, 20 January 2011 by Sicoughl (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Getting Started..

First Thing to Do - RENAME THIS PAGE and substitute your own title for our generic "Configuration Example Template X" title.

How? Just click Move. Then enter your new title for the page in the To New Title field!


Like some help with formatting your text?
See http://www.mediawiki.org/wiki/Help:Formatting for text formatting guidelines
Click Edit on this (or any other) Cisco Unified Presence article to read the source - and experiment!



Back to Configuration Examples Page: Configuration Examples


Contents

Configuration Example: What To Do when Configuring X and Y

Here’s where you:

  • Briefly outline what your configuration example is about so that users immediately know how relevant the information is to them and whether it’s worth their while to read.

OR

  • Briefly tell the story of a real-world or fictional scenario that sets your configuration example in context for users. Your scenario could illustrate how an existing process works, the problems involved, and the solution that would resolve it – which is basically why you’re providing this configuration example!


Before You Begin Title

Let users know if they need to complete any configuration or have anything in place before they can complete your configuration example. Also consider what your readers already know or should know about this configuration. If it’s helpful for them to know a little more conceptual theory before they configure anything, share that information and put things in context here.


Configuration Procedure

Tell users the steps they need to do to complete the configuration task. You can just describe each step in text, but if you have screenshots to show each step visually, all the better! Either way, it’s best to keep the number of steps in your procedure to between 7 and 9 so as not to overwhelm your reader with too much information in one go – feel free to divide a long example into sub-procedures as you see fit!


Write each step that users need to do to complete the procedure. \\ with or without screenshots

1. Write Step 1

2. Add Step 2..

3. Add Step 3..

4. Finally sum up with a step that tells users how to verify your configuration


Related Topics

If you know of other ‘need to know’ or ‘nice to know’ related topics, give users the links to learn more.

Rating: 0.0/5 (0 votes cast)

Personal tools