tag line

What is ScreenSteps Live?

We get a lot of questions about what ScreenSteps Live is. Here are some examples:

“Is it .Mac for ScreenSteps Lessons?”

No.

“Is it just a file sharing service?”

No.

“Is it a blog for ScreenSteps Lessons?”

No. But we did say that once which was a bad marketing move on our part - completely the wrong category to put ScreenSteps Live in.

And our favorite:

“Why would I need ScreenSteps Live when I can already export lessons as HTML or post them to my blog?”

The answer to that takes just under 5 minutes and can be seen in the video below.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

ScreenSteps 2.1.1 Released - Blog Pages and Confluence Posting

Last night we released version 2.1.1 of ScreenSteps Standard and Pro. Here are some of the highlights:

  • Text undo has been improved.
  • You can now post ScreenSteps lessons as pages on WordPress, TypePad or Movable Type blogs.
  • In ScreenSteps Pro you can now post to a Confluence wiki.

A couple of other minor fixes and improvements that you can read about in the release notes.

You can download the latest updates by selecting Help > Check for Updates in ScreenSteps or by downloading it here.

You can also watch a quick video of posting a lesson to Confluence below.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

The ScreenSteps Live API Developer Guide

The ScreenSteps Live API uses REST to retrieve manuals from your ScreenSteps Live account via xml.

Urls

The request urls are pretty simple. Currently the following requests are supported:

/api/manuals Retrieve a list of all public manuals for an account
/api/manuals/:manual_id Retrieves the table of contents for a single manual. The manual id can be the id number for a manual or the permalink that you set up on ScreenSteps Live.
/api/manuals/:manual_id/lessons/:lesson_id Retrieves the content of a lesson in a manual. Also retrieves basic information about the manual (title, and id) as well as the title and id of the next and previous lessons in a manual.

By default only public manuals will be retrieved. If you wish to retrieve a manual that is protected then you can add the “?show_protected=true” parameter to the end of the url.

Required Headers

The following headers are required when making a request:

Date The current time and date in http format (e.g. Fri, 11 Jul 2008 18:24:47 GMT).
Content-Type Should be set to “application/xml”
Authorization This is the authorization string that you will need to compute for each request (explained below)

Authorization String

Read the rest of this entry »

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

ScreenSteps Live API Beta

We are very excited to announce the beta of the ScreenSteps Live API beta. What does this mean? Now you can upload and manage all your lessons at ScreenSteps Live but embed the content into your own website, web app or desktop application. To help you see the potential we have created a couple of screencasts, one demonstrating the API with some PHP example code and another demonstrating a Rails plugin we have developed that makes integrating ScreenSteps Live content into your Rails app almost effortless.

You can get the PHP code example and Rails plugin at our GitHub site:

Currently the API is in beta. We have setup an example account for you to play around with if you like. The details for this are in the screencasts. If you have a ScreenSteps Live and would like to have the API enabled for you please drop us an email at info at screensteps dot com and we will get you setup.

Here are the two screencasts:

PHP Example Code

Full Size Video

Ruby on Rails ScreenSteps Help Plugin

Full Size Video

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

Posting to Drupal

With the release of version 2.1 we have had a number of requests about whether or not ScreenSteps can post to Drupal. Since Drupal has an API for posting blog entries you can. I’ve posted a lesson on how to configure Drupal and ScreenSteps: Posting to Drupal. I’ve also included the lesson with this post.

There was a small code change that I had to make to Drupal in order for categories to work. I explain the change in the lesson and have filed a bug report that you can review here if you are interested: http://drupal.org/node/280685.

Read the rest of this entry »

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

ScreenSteps Gets 5-Cow Rating From Tucows

Just wanted to let you know that last week ScreenSteps received a 5-cow rating from Tucows.com. Those aren’t easy to come by so we were quite excited. The best part: we got 7 out of 7 for our documentation. It would have been pretty embarrassing if we hadn’t.

Tucows

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

Simplify Your Documentation

In this post I am going to show you a very simple way to get your documentation done using ScreenSteps. Your results may be a little different than what you are used to but if you follow this approach you will find that your manual will be much easier to create and much easier for your users to read.

You can also see a video that covers the same information here.

Answer Questions

What is the purpose of your manual? In most cases the purpose of the manual is to make it so that your user does not have to email or call you to find out how to do something. That really is the point, but few manuals are written with this in mind. I see a lot of manuals that talk about the philosophy of a product or the architecture behind it. I personally have never had a tech support email or call come in that asked me about the philosophy, the design or architecture of a product. Tech support calls usually start with "How do I …?"

Well, if we are trying to decrease support requests with our documentation then we should probably answer the questions that our customers have. The good news is that actually makes your documentation a lot easier to create.

To show you how to do this I am going to create a manual on how to use WordPress. Now, I am not going to actually complete the entire manual but I will show you how I would scope things out. Once you have things scoped out in ScreenSteps it is actually very easy to go back and fill in the lessons you have outlined.

Create a New Manual

First I will create a new manual in ScreenSteps.

And give it a name.

Now I have a manual with nothing in it. To get things started I am just going to write down the questions that people might ask. Each question will be a new lesson. I don’t really need to do any planning at this point. I am just going to write down the questions as I think of them. (Note: You may prefer to do this in your favorite outline application first but I will show it in ScreenSteps).

To do this in ScreenSteps just select the New Lesson icon.

Here you can see that I have a list of questions that a user might ask. Now, as I look at these, some, like "How do I Upload a File?" are pretty easy to answer in just a few steps. But some, like "How do I Install WordPress?" might take a little more explanation.

For my next step I am going to organize these a bit. Some of the questions I will split into new multiple lessons to make them a little easier to create. I personally hate creating long lessons. They are a pain to make and boring to read.

Lessons Reorganized

Here you can see how I have reorganized things a bit. I have created a couple of sections (1) and have organized the lessons underneath each section (2).

Fill in the Lessons

Now, all I need to do is go back and fill in the lessons. Since the lesson title is a question it is really easy for me to decide what I need to do. I just need to create a lesson that answers the question. Once I am done, I might rename the lessons a bit. For example, I might change "How do I Upload a File?" to "Uploading a File to WordPress" but that is largely a matter of personal preference.

Conclusion

That is pretty much all their is to it. Try it out for yourself. I think that you will find that in afternoon you can have some pretty complete documentation that will be easy to create, easy to read and will be easy to update in the future.

If you want to get really fancy, then try this with ScreenSteps Live. Then, whenever a customer asks a question that you didn’t cover in your manual you can just add the answer to your online manual. We have been doing that for about 6 months now and it has worked really well.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

What’s New in 2.1

ScreenSteps 2.1 is finally released! It has taken awhile but we think that you are really going to like this update. I just wanted to highlight a few of the key enhancements in ScreenSteps 2.1, namely:

  • The Post to Blog feature
  • Improved PDF output
  • Improved PDF manuals

Post to Blog

One of the most exciting things about 2.1 is the new Post to Blog feature. You can now post to your WordPress, TypePad or Movable Type blog. Just go into your ScreenSteps preferences, create a new web account, choose the account type and you will be all ready to post lessons instantly to your blog. You can even choose which category you would like your post to appear in, or publish the lesson as a draft. If you like to create tutorials for people we think that you will find this to be a great way to get your lessons out.

IMPORTANT: If you were using the 2.1 beta you will want to update your blog templates to the new defaults. You can see how to do that here: Updating Templates

Improved PDF

We have also dramatically improved the PDF quality. In previous versions of ScreenSteps some images could appear a little blurry. In 2.1 this has really been improved. Look at these two PDF files. See the examples below.

Old PDF Output

Notice the blurriness in the header image and the screen capture.

2.1 PDF Output

Here you can see how much clearer the PDF export is.

Improved PDF Manuals

For users of ScreenSteps 2 Pro we have also really improved PDF manuals. In ScreenSteps 2.0 you could export a PDF manual but the cover page and table of contents looked a little shabby.

In 2.1 you can now add an image and footer to your title page and the table of contents now has better formatting and page numbers.

Title Page

Here you can see the new options for the title page. You can now add a footer and image.

Improved Table of Contents

This is the new PDF table of contents. The formatting has been cleaned up and page numbers are now included.

Conclusion

There are also a lot of bug fixes and small improvements. We hope you like all of the additions.

You can download the latest version by selecting “Check For Updates” from the Help menu in ScreenSteps or by going to our Downloads page.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

Redesign Coming to ScreenSteps Live

Sometime in the next week or so we will be pushing some changes to ScreenSteps Live that we wanted to let you know about. The changes are mostly cosmetic but we have also reorganized some of the menus to make things a little easier to get to.

New Tabs

We have changed the main navigation to tabs. We thought that this would make the navigation a little easier to understand.

Admin Tab

You will also notice that the "Account" tab has been renamed to "Admin". This tab only appears to admin users on your account. We have also re-organized the settings under the new "Admin" tab. This is where you can do your bulk editing of Lessons, Manuals, Comments, Readers, Groups and Users. You will notice that the account settings are no longer in this section.

Settings

You can now get to the settings here.

Settings Tab

When you click on "Settings" (1) you will now see a new "Settings" tab (2). Here you can edit your profile, account settings, and, if you are the owner of the account, your plan and payment details.

Plan and Payment Settings

Here you can upgrade/downgrade, update your billing information as well as cancel your account.

Other Stuff

We have also improved the screens for creating new users, groups, readers, etc. We hope that you like the new look!

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail

Document the Experience

When describing how to write documentation in ScreenSteps Greg and I often tell people to create task-based lessons. You think of a task that the user needs to accomplish and you show them how to do it. I’ve been thinking about this lately and while accurate, I don’t think this description fully communicates how ScreenSteps should be used.

So here is another stab at it- Document the experience.

People should use ScreenSteps to create documentation centered around the experiences the user will have with the software. Imagine different scenarios that the user will find themselves in. What questions will they have? What will they want to do?

When you sit down to write documentation consider the following:

  • What questions will the user ask the first time they launch the software?
  • What tasks will the user want to accomplish with the software?
  • What questions will the user ask the first time they use a particular feature?

If you begin your documentation with a list of questions that a user might ask then you can sit down and create lessons that respond to those questions. What ends up happening is that you write documentation that is really useful to the user because you are showing them how to get something done.

In addition, if you are a software developer you will find that by using this approach your application will go through a refining process. As you ask questions and document the software step-by-step you will find things that don’t quite work as they should or a workflow that could be improved.

Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • del.icio.us
  • Slashdot
  • Technorati
  • TwitThis
  • e-mail