Skip to Content
Contributing
Report an error
Open in ChatGPTOpen in Claude

Contributing to FiveM documentation

FiveM Docs is an independent community reference, not the official Cfx documentation. The source repository for this website is currently private. Public visitors cannot fork it or open pull requests and issues there. A GitHub “Edit this page” link would therefore not work.

Contribute to the official Cfx documentation

The official FiveM documentation repository  is public and accepts contributions under its own guidelines.

  1. Check the official contribution instructions  and existing issues.
  2. Fork citizenfx/fivem-docs, edit the relevant Markdown file, and validate code examples against the actual runtime or official source.
  3. Open a pull request to the official repository with reproduction steps, tested commands and references.

Contributing upstream improves the official documentation; it does not automatically update this independent website. Refer to the source coverage directory to see how we map official topics and where our independent explanations differ.

Maintainer workflow for this site

Invited collaborators with access to the private repository should follow AGENTS.md and the project’s existing tests. Keep changes small, document client/server context, and avoid claiming that mock tests certify in-game behavior. Public readers can report corrections through the separate FiveM Docs feedback tracker . The website source remains private.

Editorial responsibility and corrections

This independent reference is maintained by Livvux . Use Report an error on any article to open a prefilled public correction form . A GitHub account is required and reports are public. Include the exact FiveM Docs URL, the incorrect statement, a primary source or minimal reproduction, and the artifact/resource version involved. Do not send keys, player identifiers or private server logs. The private repository is not a public issue tracker. For an error in the official Cfx documentation itself, use the upstream contribution workflow above.

What a source review means

A visible Source review note identifies the date, primary references and scope of a documentation review. Reviews may use automated assistance; the label does not assert a named human sign-off, compatibility with every game artifact, or successful execution inside FiveM. Dates change when the article is substantively reviewed or corrected, not automatically on each deployment.

We distinguish source contracts, syntax/automated tests, database experiments and actual client/server captures. Examples should identify their context, prerequisites, expected result, error paths and limits. A mock native or passing website test is not a real two-client ownership test. Historical API names and Legacy/Enhanced differences stay explicit. Corrections should keep existing working URLs, preserve useful references and avoid unsupported performance or search-ranking claims.