Style Guide for Artemis Project Web Site Documents

This document provides guidelines for writing style and content that you should consider when preparing a document for the Artemis Data Book. Please refer to the HTML Formatting Guide for guidelines on HTML coding styles to be used in creating a document for the Artemis Project Web Site.

Your document might require some variation from this style guide, but please follow these guidelines as closely as you reasonably can. Using this style guide:

• gives the ASI documents a consistent look and feel.
• makes it easier for the ASI Web Team (and you!) to review and update your document.

This style guide will change as different situations arise, so be sure to check this document regularly for updates. If you have any questions or concerns, drop a line to the ASI Web Team at <asi-web@asi.org>.

Writing Style and Content

Most of the material published on the ASI Web Site will deal with technical matters. For this type of material, use a moderately formal essay or technical paper format.

Some material, such as the Frequently Asked Questions and Frequently Raised Objections, requires a more conversational tone. Adapt your writing style to fit the material.

Use the active voice in your writing. Say "Use the active voice in your writing," not "The active voice should be used in your writing."

Use simple words. If a 5-cent word does the job, don't use a 10-dollar word! You don't want to come across as talking down to the readers, nor do you want readers to scratch their heads wondering what you're saying.

Avoid social issues unless they are directly relevant to the Artemis Project. This is not a forum for personal crusades.

Use graphics where needed to communicate your message. Do not use graphics strictly for effect; they require too much download time and produce excessive loading on the web server.

When listing data, always list the English units first, followed by the metric equivalent in parentheses.

Lists (Numbered and Bulleted)

• to describe a particular procedure where the sequence is important, such as how to contact the Artemis Society, or how to join a particular task committee.
• to keep the information organized - for example to allow the reader to refer to the information in a separate communication.
• to make it easier for the reader to keep track of his place in the list.
• to indicate order of importance. If you're describing the five most important features of a spacecraft system and wish to list them in order of importance (1=most important, 5=least important), a numbered list is appropriate.
• when the number of items is itself important.

Use bulleted lists if the order of items in the list does not matter.

Copyrighted Material

If you use copyrighted material other than by reference, or a brief citation within the doctrine of fair use, be sure that:

• You obtain written permission to use the material.
• Any stipulations regarding copyright statements and usage restrictions are followed.
• You cite the source in your document.

This document is updated from time to time to reflect current Artemis Society policy and practice. Please check frequently for updates.