How The Site Works
Appearance
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] | <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:
- Gather the
.txtguides from the pvme-guides repository. - Format
.txt->.md. - Build the website from the
.mdfiles 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.