META — PAGE ABOUT AGPEDIA

Style Guide

This style guide outlines the writing principles for Agpedia.

General principles

Technical level and accessibility

Write for a reader who is intelligent and broadly educated, but has no prior knowledge of the topic. The goal is not to simplify — it is to be clear. Technical depth and accessibility are not opposites: a well-written technical article is both precise and followable.

Names across languages

Article prose is written in the language of that article's version. Non-English names (relative to the article's language) appear in parentheses after the name used in the prose on first use, not woven into the running text.

Translations

Each page has a canonical language: the version that is the reference for that page. It starts as the language the page was first written in. Any editor can change it, for example when most active editors of the page work in another language.

Headings

Lead section

Numbers

Dates

Links connect articles and help readers navigate to related topics. Use them to aid understanding, not to decorate prose.

Images

An image helps readers recognise a subject and understand it faster. Every article should have at least one image when a relevant, freely licensed one exists.

Slugs

Words to watch

Avoid the following language patterns, which weaken verifiability or mislead readers:

Available in

Discussion

No threads yet.

Sign in to start threads and post replies.