Editing the Wiki

Editing the Wiki

Irregularpedia is a community wiki — anyone with an IrregularChat SSO account can contribute. There are three ways to edit, from quickest to most powerful. Pick the one that fits the size of your contribution.

Looking for something to write?

See Wanted Pages for maintained list of content gaps you can claim. Each one is a scoreboard bounty — you earn points when your contribution merges.

---

Method 1 — In-page editor (quickest)

Best for: fixing typos, adding a paragraph, updating a single page.

You need an IrregularChat SSO account. Join here if you don’t have one.

1. Sign in — click the user icon in the top-right header and log in with your IrregularChat SSO account.
2. Navigate to the page you want to edit. Not sure where to start? The Wanted Pages list has stubs ready for contributors — click any entry, then use Edit this page at the bottom.
3. Click the pencil icon (✏️) next to the page title. A split-pane editor opens with markdown source on the left and a live preview on the right.
4. Make your changes.
5. Click Save — your edit is committed directly to the main branch and goes live on the next deploy (usually within a few minutes).

In-page editor limitations

The in-page editor can only edit pages that already exist. To create a new page, use Method 2 or 3 below. Stub pages (marked “stub — help fill it in” on the Wanted Pages list) already exist in the repo, so you can edit them using the Edit this page button at the bottom of the page.

Keyboard shortcuts

Shortcut	Action
Cmd/Ctrl + S	Save
Escape	Close save dialog

---

Method 2 — GitLab web UI (no local tools needed)

Best for: creating new pages, larger rewrites, submitting a merge request for review before it goes live.

No git client or local setup needed — everything happens in your browser.

Step 1 — Open the wiki folder on GitLab

Go to: https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/tree/main/apps/wiki/src/content/docs

You’ll see the folder structure:

docs/
├── ai-ml/
├── community/
├── cybersecurity/
├── military/
├── privacy/
├── radio/
├── server-guides/
└── ...

Step 2 — Edit an existing page or create a new one

To edit an existing page:

1. Navigate into the correct subfolder (e.g., privacy/)
2. Click the file you want to edit
3. Click the pencil Edit button (top-right of the file view)

To create a new page:

1. Navigate into the correct subfolder
2. Click the + button → New file
3. Name your file with a kebab-case slug and .md extension (e.g., email-anonymity-guide.md)
4. Add frontmatter at the top:

---
title: "Your Page Title"
description: "One-line description for search results"
tags: ["section", "topic"]
---

5. Write your content in markdown below the frontmatter

Step 3 — Commit your changes

Scroll to the bottom of the editor. You’ll see a Commit changes form:

• Commit message — describe what you did (e.g., docs(wiki): add email anonymity guide)
• Target branch — choose one:
  • main — commits directly and goes live on next deploy (fine for small fixes)
  • Create a new branch — recommended for new pages or big edits; lets reviewers check your work first

Step 4 — Open a merge request (if you used a new branch)

After committing to a new branch, GitLab offers to create a merge request. Do it:

1. Add a title describing what the page covers
2. In the description, mention which Wanted Page entry this closes (if applicable)
3. Click Create merge request

A reviewer will approve and merge it. On merge, the scoreboard auto-awards bounty points if the page was on the Wanted Pages list.

---

Method 3 — Obsidian + Git (best for bulk contributions)

Best for: writing multiple pages, working offline, using Obsidian’s graph view to see how pages connect.

See the full guide: Obsidian + GitHub Wiki Workflow

Quick summary:

1. Clone the monorepo:

   git clone https://git.juntogroups.org/irregulars/irregularchat-monorepo.git
   cd irregularchat-monorepo/apps/wiki

2. Open as Obsidian vault:
   In Obsidian → Open folder as vault → select apps/wiki/src/content/docs

3. Install the Obsidian Git plugin (Settings → Community plugins → search “Obsidian Git”) for one-click pull/commit/push from inside Obsidian.

4. Edit or create pages — Obsidian’s graph view shows how your new pages connect to the rest of the wiki.

5. Push and open a merge request:

   git checkout -b docs/my-new-pages
   git add apps/wiki/src/content/docs/
   git commit -m "docs(wiki): add privacy and OPSEC pages"
   git push origin docs/my-new-pages

   Then open a merge request at git.juntogroups.org.

---

Markdown reference

Headers

# Heading 1 (page title — use once)
## Heading 2 (main sections)
### Heading 3 (subsections)

Text formatting

**bold** · *italic* · `inline code` · ~~strikethrough~~

Links

[External link](https://example.com)
[Internal wiki link](/ai-ml/claude-code)

Lists

- Bullet item
  - Nested item
1. Numbered item
2. Second item

Code blocks

```bash
echo "hello"
```

Tables

| Column A | Column B |
|---|---|
| Cell 1 | Cell 2 |

Callouts (Starlight)

:::note[Title]
Informational content.
:::

:::tip[Tip]
Helpful advice.
:::

:::caution[Warning]
Be careful.
:::

:::danger[Critical]
Do not ignore.
:::

Frontmatter (required on every page)

---
title: "Page Title"
description: "One-line SEO summary"
tags: ["section", "topic"]
---

---

Citations

When adding factual claims, cite your sources using footnote syntax:

FlashAttention-2 provides 2-4× speedup[^1].

[^1]: Dao, T. [FlashAttention-2](https://arxiv.org/abs/2307.08691). arXiv 2023.
"Faster Attention with Better Parallelism and Work Partitioning."

This renders as superscript numbers with bidirectional jump links. See Research Citations for the full citation guide.

---

Backlinks are automatic

When you write [Other Page](/path/to/page) anywhere in your content, the Linked from section at the bottom of that target page automatically includes a back-reference on the next deploy. You don’t need to manually maintain “See also” lists on both ends — just add the forward link and the backlink system handles the rest.

---

Getting help

• Questions? Ask on Q&A tagged wiki
• Bugs or broken pages? Open an issue on GitLab
• Full Obsidian workflow: Obsidian + GitHub Guide