permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs
commit 19b4abd9864377f68c406fee3e3234893490191f
parent f78c65bd5870ed1aeb5612e79851dff5abc57202
Author: doriane <doriane@web>
Date:   Wed, 21 Jan 2026 19:24:55 +0100


Diffstat:

Madd_the_starter.mdwn | 2+-


1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/add_the_starter.mdwn b/add_the_starter.mdwn
@@ -12,7 +12,7 @@ than scale.
 
 - Begin with a recurring rhythm (weekly, monthly) — consistency beats ambition.
 - Try to keep the language and terms you use accessible —  allow first time visitors to gradually dive into the topic
-- Use simple means to organise and communicate: one poster, one shared document, and make use of the permacomputing.net infrastructure (a.o. web hosting and chatroom for your group) and code of conduct. See https://permacomputing.net/onboarding/
+- Use simple means to organise and communicate: one poster, one shared document, and make use of the permacomputing.net infrastructure (a.o. web hosting and chatroom for your group) and code of conduct. See [[onboarding]].
 - Choose a format that feels accessible for your gatherings — informal meet-ups over rigid workshops.
 - Let organisational logistics develop over time, as more people join in. Trust that your understanding of what kind of work, documents, and tools are needed, will become more clear gradually.