Building a prototype

Maybe "prototype" isn't the right word for it, but your boss (or your team) asked you to evaluate ScreenSteps and either report back what you discovered, or demonstrate an example of what your company could do with ScreenSteps. So, for lack of a better term, I'll just say you want to build a prototype.

Setting Expectations

This implementation guide is to help you make a basic prototype. Even though you have access to all of the features during the trial, I don't plan on covering all of them - just enough so you can get a feel for how to create visual documentation, and actually make something you can show off.

The plan is to help you do this in about 35 minutes. If it's taking longer than that, just email and let me know you're having a tough time.

Below is a quick rundown of what we'll do, and about how long it should take to do it.

Customize your site (5 minutes)

In this chapter, you'll add a logo, modify the colors of your online knowledge base, and edit some text. While there is a lot more you can do with customizations, we'll just do the basics to make it look nice.

Organize your manual (8 minutes)

You'll provide the structure for your documentation by creating a manual, adding some chapters, and creating a few articles.

Write your articles (15 minutes)

This is where you'll create some content using screenshots, annotations, and written instructions. These won't be grand tutorials - just a few screenshots to give you a feel for what it's like to write articles with ScreenSteps.

You are also going to duplicate a few articles. This activity demonstrates how you can quickly copy your work and reuse it (e.g. for a template), and it will also serve as a way to fill up your prototype knowledge base so you can show it off.

Share your work with your team (7 minutes)

Sharing your prototype is pretty easy - you can send everybody a link to your ScreenSteps website, a link to specific articles, or export everything to PDF and load it to a shared drive or blast it over email. ScreenSteps takes care of all the behind-the-scenes action so you can just focus on creating documentation.

Let's get to work

Alright, let's make a documentation site in 35 minutes... Starting NOW!


Add your comment

E-Mail me when someone replies to this comment