The community has a page, and the page is its invite

A fourth About page, `Join Discord`, sitting between the author and the ask:
what is this, who made it, where is everyone, how do I help. Like its three
siblings it is written markdown under assets/pages, reads nothing and
transmits nothing, and keeps a CLI face — `meshterm discord`.

It is short on purpose. The invite link, and the code for it in a `qr` fence,
because on a PicoCalc there is no clipboard and the code is how a link leaves
the screen at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Opus 5 committed 2026-09-02 08:38:44 -04:00
1 parent 155c0b5b21
commit 6fc4e7afc9
6 files changed
+74 -15

No files matched your search

+11 -1
View File
@@ -1,6 +1,6 @@
"""The About MeshTerm pages: the app, the person who wrote it, and how to help it along.
Three read-only pages hung under the main menu's *About MeshTerm* section — the one
Four read-only pages hung under the main menu's *About MeshTerm* section — the one
section that names a subject rather than a doing, because "what is this thing, and who
made it" is a question the other five can't answer. Each opens as a full screen, scrolls
if the terminal is short, and is left with Esc; nothing here touches the radio or the
@@ -72,6 +72,15 @@ def about_author() -> MarkdownDoc:
return _page("author")
def join_discord() -> MarkdownDoc:
"""The *Join Discord* page: the invite link, and a QR of it to point a phone at.
A page rather than a popup because there is nothing to decide — it is a link, and on
a headless console the QR *is* how the link gets off the screen.
"""
return _page("discord")
def support_project() -> MarkdownDoc:
"""The *Support MeshTerm* page: what keeps it going, and how to chip in.
@@ -166,6 +175,7 @@ __all__ = [
"AboutPage",
"about_author",
"about_meshterm",
"join_discord",
"open_about_page",
"support_project",
]