The ScreenSteps Online Knowledge Base Everything you need to know about ScreenSteps
Blue mango logo white 250
  • Table of Contents
  • Contact Us
ScreenSteps Documentation » Creating a Software Manual With ScreenSteps » Before You Start

Topics

  • 1. Creating Your Content 3
    • 1.1 Before You Start
    • 1.2 Create a Manual and Stub Out Your Lessons in ScreenSteps
    • 1.3 Add Lesson Content
  • 2. Publishing Your Manual 2
    • 2.1 Things to Consider Before You Publish
    • 2.2 Exporting Your Manual
  • 3. Tips For Keeping Your Manual Useful 2
    • 3.1 Keeping Your Manual Relevant
    • 3.2 Keeping Your Manual Up To Date

Quicklinks

  • Downloads
  • View forums
  • Submit a help request
  • Contact us
  • Retrieve a lost license key

Last Updated

Jan 22, 2011

Other Resources

  • ScreenSteps Desktop & Workgroup

  • ScreenSteps 2.9
  • ScreenSteps Workgroup
  • Customizing HTML Templates
  • ScreenSteps: Tips & Tricks
  • Creating Word Templates
  • Publishing to Blogs & Wikis
  • ScreenSteps Live

  • ScreenSteps Live
  • Setting up a New Admin, Editor or Author on ScreenSteps Live
  • ScreenSteps Live Support Client
  • Integrating ScreenSteps Live With Other Services
  • Collaborating on ScreenSteps Live
  • ScreenSteps Live Remote Authentication
  • ScreenSteps Live API
  • API Examples
  • Implementation Guides

  • Creating a Software Manual With ScreenSteps
  • Creating a ScreenSteps Live Support Site
  • Zendesk and ScreenSteps Live
  • Help Scout and ScreenSteps Live
  • FAQs

  • FAQs

Comments

0 comments for this lesson

  • Next: Create a Manual and Stub Out Your Lessons in ScreenSteps

Before You Start

Whether this is the first software manual you have ever created or you are a seasoned documentation pro, understanding a little about how ScreenSteps works will help you write documentation that gives you better results in less time.

Here are few key principles for working with ScreenSteps.

Talk About How, Not What

ScreenSteps is designed to help you focus most of your time on teaching tasks. Your users will find it much useful if you explain how to accomplish real world tasks with your application as opposed to explaining what all the screen are and what the buttons do.

If you start most of your articles with the title "How do I..." then you will find that your documentation will become much more task-based and more useful to your readers.

Create Content in Small Chunks

ScreenSteps is designed to create content in small chunks. We call them lessons. Instead of having a few long lessons, you should have many short lessons. Short lessons are easier to write and easier for your customers to read. A good rule to follow is to keep your lessons to somewhere between 5 and 15 steps. If they get longer than that then you should think about splitting the lesson up.

Remember - Users Won't Read Your Documentation, They Will Reference It

Users aren't going to read your documentation from beginning to end. They are going to reference it. That is another reason it is good to break up your documentation into small chunks. It makes it easy for your users to quickly scan your table of contents to find the information they need. It also makes it easier for you to point your users to the exact section of your documentation that will answer their question.

Don't Skimp on the Pictures

ScreenSteps is designed to help you add pictures to your documentation. Don't skimp! Take lots of pictures. This will add clarity to your documentation and your users will really appreciate it.

  • Next: Create a Manual and Stub Out Your Lessons in ScreenSteps

Comments (0)

Add your comment

E-Mail me when someone replies to this comment
Blue Mango Learning Systems © 2012