Skip to content

Contributing

The documentation is written by the people who make missions. If you figured out how to set something up and it took you more than ten minutes — write it down, and the next person will spend one.

You need a GitHub account. Every change is reviewed and appears on the site within a few minutes after that.

  1. At the bottom of the page click Edit page — GitHub opens its source file.
  2. Make the change.
  3. Click Commit changes…, briefly describe what you changed, then Propose changes and Create pull request.
  1. Open the right folder in the repository: the reference is in reference/.
  2. Click Add file → Create new file.
  3. Name the file in Latin letters with hyphens — the name becomes the page address: reference/kill-zones.md → /reference/kill-zones/.
  4. For a reference page, copy the template into it and fill it in.
  5. Submit a pull request, as with an edit.
  1. Open the src/assets/ folder in the repository.
  2. Click Add file → Upload files and upload the image. The file name — in Latin letters and meaningful, for example freezezone_settings.png.
  3. Insert it into the text with a path from the page:
    • from a reference page (reference/…) — ![What's on the screenshot](../../../assets/freezezone_settings.png);
    • from other pages — ![What's on the screenshot](../../assets/freezezone_settings.png).

Pages in en/ sit one level deeper, so they need one more ../.

The image is compressed during the build, and on the site it opens full size on click.

Write in Discord or open an issue: what’s wrong, what’s missing, what question is left. Someone will make the change for you.

  • Reference — one page per thing a mission maker sets up: a component, an entity, a setting. Example: Groups and slots.
  • Common mistakes — “I did this and it doesn’t work, because…”. Everything asked in Discord more than once goes here.
  1. Russian is the primary language. An English page is a translation of the Russian one, at the same path in the en/ folder. If you edited a Russian page, you may leave the English one alone: an “outdated translation” notice appears on it by itself, and npm run i18n lists every page that is behind.
  2. Write plainly and to the point — like a good technical manual. No slang and no jokes, but no officialese either: not “this component performs the blocking”, but “the component blocks”. Address the reader directly and use the imperative in instructions: “place”, “enable”.
  3. Name fields the way the editor does, with the code name next to them: “Countdown Seconds (m_CountdownSeconds)”. That way the reader finds the field in Workbench instead of guessing what you translated.
  4. Show rather than retell. A screenshot with the field circled on it replaces a paragraph of description.
  5. Name the mod version if the behavior appeared or changed in a specific version.
  6. Not sure — write it anyway, but add a “Needs verification” block. An incomplete page is more use than a blank one.
  7. Explain edits to someone else’s text. Found a mistake — fix it and write in the pull request what you changed and why.

Pages are written in Markdown. Besides the usual headings, lists and tables, these come in handy:

Link to another page — an address from the site root with a trailing slash: [Zones](/reference/zones/), on English pages [Zones](/en/reference/zones/).

Path to a prefab or config — as a link that opens the file in Workbench: ~EchoLobby for the mod’s files, ~ArmaReforger for vanilla ones:

[`Prefabs/Zones/EH_Polyline_KillZone.et`](enfusion://ResourceManager/~EchoLobby:Prefabs/Zones/EH_Polyline_KillZone.et)

Callout blocks:

:::note
Additional information.
:::
:::tip
A useful tip.
:::
:::caution[Needs verification]
What exactly needs to be checked.
:::
:::danger
Something that can break the mission.
:::

Order in the menu is set at the top of the file:

---
title: Title
description: One sentence about the page
sidebar:
order: 5
---