Skip to content
SolidRusT.ai

Documentation Style Guide

This guide helps contributors write documentation that is clear, consistent, and helpful for developers using SolidRusT AI.

Be Concise

Developers want quick answers. Get to the point.

Be Accurate

Test all code examples. Verify API details.

Be Inclusive

Avoid jargon. Define technical terms.

Be Practical

Include working examples for every feature.

Address the reader directly with “you” and “your”:

DoDon’t
”You can configure the client…""Users can configure the client…"
"Your API key is…""The user’s API key is…”
DoDon’t
”The API returns a response""A response is returned by the API"
"Configure your environment""Your environment should be configured”
DoDon’t
”Run this command""You might want to consider running"
"This feature requires…""It should be noted that this feature…”

Every code example should be:

  • Runnable - Copy-paste should work
  • Complete - Include all imports and setup
  • Realistic - Use practical use cases
from openai import OpenAI
# Initialize client with SolidRusT AI endpoint
client = OpenAI(
base_url="https://api.solidrust.ai/v1",
api_key="YOUR_API_KEY" # Replace with your key
)
# Make a chat completion request
response = client.chat.completions.create(
model="vllm-primary",
messages=[
{"role": "system", "content": "You are a helpful assistant."},
{"role": "user", "content": "Hello!"}
]
)
# Print the response
print(response.choices[0].message.content)

For API endpoints, provide examples in multiple languages:

Terminal window
curl https://api.solidrust.ai/v1/chat/completions \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "vllm-primary",
"messages": [{"role": "user", "content": "Hello!"}]
}'
---
title: Clear, Descriptive Title
description: One sentence explaining what this page covers.
---
Introductory paragraph explaining the topic and why it matters.
## Prerequisites
List what the reader needs before starting.
## Main Content
Step-by-step instructions or explanations.
### Subsection
Break complex topics into digestible sections.
## Examples
Working code examples demonstrating the concept.
## Next Steps
Link to related documentation.
---
title: Endpoint Name
description: Brief description of what this endpoint does.
---
## Endpoint
`POST /v1/endpoint`
## Request
### Headers
| Header | Required | Description |
|--------|----------|-------------|
| Authorization | Yes | Bearer token |
| Content-Type | Yes | application/json |
### Body Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| param1 | string | Yes | Description |
| param2 | number | No | Description (default: 10) |
### Example Request
[Code examples here]
## Response
### Success Response (200)
[Example response JSON]
### Error Responses
[Error codes and descriptions]

Use callouts to highlight important information:

  • Use sentence case for headings
  • Don’t skip heading levels (h2 -> h4)
  • Keep headings concise
  • Use bullet points for unordered items
  • Use numbered lists for sequential steps
  • Keep list items parallel in structure

Use tables for structured data like parameters or comparison:

Column 1Column 2Column 3
DataDataData
  • Use descriptive link text
  • Link to related documentation
  • Avoid “click here” or bare URLs
DoDon’t
See the authentication guideClick here
Learn about rate limitshttps://docs.solidrust.ai/guides/rate-limits
import { Card, CardGrid } from '@astrojs/starlight/components';
<CardGrid>
<Card title="Title" icon="rocket">
Card content
</Card>
</CardGrid>
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs>
<TabItem label="Tab 1">Content 1</TabItem>
<TabItem label="Tab 2">Content 2</TabItem>
</Tabs>
import { Steps } from '@astrojs/starlight/components';
<Steps>
1. First step
2. Second step
3. Third step
</Steps>

Before submitting documentation:

  • All code examples are tested and working
  • API details match actual behavior
  • No placeholder text or TODOs
  • Links work correctly
  • Follows this style guide
  • Builds without errors (npm run build)
  • Grammar and spelling checked

Have questions about the style guide? Open a discussion.