Jump to content

How The Site Works

From PvME Wiki
AI-assisted additive formatting; current PvME source words, order and media preserved
 
Update source attribution; preserve PvME guide content
 
Line 45: Line 45:
</div>
</div>


<div class="pvme-source-attribution">[https://pvme.io/about/workings/ PvME source] · PvME contributors · [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA 4.0]. AI-assisted formatting; source wording retained.
<div class="pvme-source-attribution">[https://pvme.io/about/workings/ PvME source] · PvME contributors · [https://creativecommons.org/licenses/by-nc-sa/4.0/ CC BY-NC-SA 4.0].
</div>
</div>

Latest revision as of 02:34, 16 November 2026

How The Site Works

Full process on Github, and in short:

  1. Gather the .txt guides from the pvme-guides repository.
  2. Format .txt -> .md.
  3. Build the website from the .md files using MKDocs Material.

Limitations

First and foremost, the guides on the website are always up-to-date with the PvME Discord Server.

This is because both are using the .txt guides from the pvme-guides repository.

With that being said, the .txt formatting is primarily aimed at Discord which can lead to some content showing incorrectly:

  • References to social Discord exclusive channels (#pvm-help)
  • Mentions of $linkmsg

I try to stay ahead of this by adding formatting rules that exclude or change Discord-only content.

If you find any formatting issues, please message me on Discord (Pleb#0025) or create an issue on Github.

PvME source · PvME contributors · CC BY-NC-SA 4.0.