WPx - Writing Program ExtensionWriting ProgramEnglish Department | All Sites... 

Search Business & Technical Writing...  
Web Authoring 355:425
355:425
Home
Syllabus
Sample Projects
Design Resources
Research Resources
 
Draft Assignments
Midterm Prototype
Collaborative Zine
 
 
 
Business & Technical Writing
Home
About Our Program
Certificate Programs
  Technical
  Professional
Teacher Resources
 
 

Tutorial Page

A tutorial page typically means a detailed, step-by-step, how-to guide for some specific activity. But since not every project in this class would need such a page, we approach tutorials as follows:

  • For your Final Project, you may build a tutorial in the sense of anything that instructs your audience — just as if you were doing another Feature article focused on insider tips, background, etc. Note that you may also choose to combine the your tutorial with the Visual page assignment (by simply building a longer page that would fulfill both assignments).
  • For your Collab Zine , you must do a detailed, step-by-by step as explained in the requirements below.

To get started, please review this badly designed tutorial about a good tutorial. Please note that you needn't stifle your natural propensities for being cheeky and witty while being informative.

 

Requirements

1. Subnav functions as a menu for your tutorial's separate parts, which should be either on separate pages or anchor-linked down the page.

2. Minimum content includes at least 500 words and 2 illustrative images (e.g., maps, screenshots, etc.) labelled or highlighted in various ways in order to help break down info relevant to your tutorial.

3. Intro tells users exactly what they're going to do (final result and each step), what they need to know in advance, what they should watch out for, and why they should listen to you (e.g., you've done this before, you're board-certified, you're amusing, whatever).

4. Step-by-steps anticipate users' needs, give them options, use images to show detail and break up text-monotony, and offer troubleshooting tips (or whatever would be analogously appropriate for your topic). You might also occasionally offer links to further detail.

5. Conclusion reviews what should have happened, what users might try next, links to further info, etc.

 

back to top

 

   


Copyright © 2005
Rutgers University Business & Technical Writing
All Rights Reserved
Site Feedback: William Magrino
wmagrino@rci.rutgers.edu