NomadNet page formats

MeshChatX serves pages from a Mesh Server page node and displays them in the Nomad Network browser. Pages are fetched with the Nomad path convention /page/.

Supported filenames

Extension	Role
.mu	Micron markup (NomadNet default)
.md	Markdown with GitHub-flavored features via the renderer
.txt	Plain text with escaped HTML and preserved whitespace
.html	Static HTML with CSS only (see security below)

If you add a page without a recognised extension, the server stores it as .mu. Filenames with other extensions (for example .exe) are rejected when saving through the API.

Plain text (.txt)

Content is HTML-escaped and shown with pre-wrapped whitespace. There is no Markdown parsing on .txt pages.

Markdown (.md)

Not the same engine as chat. Conversations use the lightweight MarkdownRenderer in the messaging UI. Nomad .md pages use marked with GFM-oriented rules plus sanitisation. Features and edge cases can differ between the two paths. Automated tests cover both.

Authoring tips:

• Use ATX headings with a hash and a space before the title, for example # Title, ## Section, #### Subsection.
• Fenced code blocks keep indentation.
• Off-mesh http and https links in rendered content are removed or restricted so the preview cannot drive external navigation without mesh-style URLs.

HTML (.html)

• JavaScript is not executed. script tags and event-handler attributes are stripped.
• External resources are blocked where possible. @import and url(…) pointing at http://, https://, or protocol-relative URLs are removed from CSS.
• Embedded