OpenHands/docs/DOC_STYLE_GUIDE.md
mamoodi 844d84d7bb
Release 0.30.0 (#7467)
Co-authored-by: மனோஜ்குமார் பழனிச்சாமி <smartmanoj42857@gmail.com>
Co-authored-by: Xingyao Wang <xingyao@all-hands.dev>
Co-authored-by: Engel Nyst <enyst@users.noreply.github.com>
Co-authored-by: Robert Brennan <accounts@rbren.io>
Co-authored-by: sp.wack <83104063+amanape@users.noreply.github.com>
2025-03-25 18:39:36 -04:00

1.2 KiB

Documentation Style Guide

General Writing Principles

  • Clarity & Conciseness: Always prioritize clarity and brevity. Avoid unnecessary jargon or overly complex explanations. Keep sentences short and to the point.
  • Gradual Complexity: Start with the simplest, most basic setup, and then gradually introduce more advanced concepts and configurations.

Formatting Guidelines

Headers

Use Title Case for the first and second level headers.

Example:

  • Basic Usage
  • Advanced Configuration Options

Lists

When listing items or options, use bullet points to enhance readability.

Example:

  • Option A
  • Option B
  • Option C

Procedures

For instructions or processes that need to be followed in a specific order, use numbered steps.

Example:

  1. Step one: Do this.
  2. Step two: Complete this action.
  3. Step three: Verify the result.

Code Blocks

  • Use code blocks for multi-line inputs, outputs, commands and code samples.

Example:

docker run -it \
    -e THIS=this \
    -e THAT=that
    ...

Referring to UI Elements

When referencing UI elements, use ``.

Example:

  1. Toggle the Advanced option
  2. Enter your model in the Custom Model textbox.