edit-wiki

Edit This Wiki

How to add, edit, and maintain content in the PSI Knowledge Base.

---

The Basics

Every page is a .md (markdown) file. If you can write markdown, you can edit the wiki.

Wiki Links

Use [[wiki-links]] for internal references — this is the key difference from regular markdown:

# Regular markdown link (don't use for internal pages)
[Terminology](company/terminology.md)
 
# Wiki link (use this instead!)
[[company/terminology|Terminology]]
 
# Simple wiki link (uses filename as display text)
[[terminology]]

Syntax	Result
[[page]]	Links to page.md, displays “page”
[[page|Display Text]]	Links to page.md, displays “Display Text”
[[folder/page]]	Links to folder/page.md
[[page\#Section]]	Links to specific section

---

Workflow

Step 1: Pull Latest

cd PSI-Wiki-Site
git pull

Step 2: Make Edits

Edit in Obsidian, VS Code, or any text editor.

Step 3: Commit & Push

git add -A
git commit -m "Add new section on X"
git push

The site rebuilds automatically on push.

---

Creating a New Page

1. Choose the Right Folder

Content Type	Folder
Company/product/process info	company/
Step-by-step instructions	guides/
Data schemas, system specs, app docs	reference/

2. Use the Template

---
tags: [relevant, tags, here]
---
 
# Page Title
 
> One-sentence summary of what this page covers.
 
---
 
## Section 1
 
Content here...
 
---
 
## Related Pages
 
- [[other-page]] - Brief description
 
---
 
*Last updated: Month Year*

3. Update llms.txt

Add your new page to llms.txt so AI agents can find it:

- [Your Page Title](path/to/your-page.md): Brief description

---

Page Guidelines

Do

• Use [[wiki-links]] for internal references
• Add tags in YAML frontmatter
• Include a “Related Pages” section
• Keep pages focused on one topic
• Update the “Last updated” date
• Cross-link related content

Don’t

• Duplicate content across pages (link instead)
• Use jargon without defining it (link to Terminology)
• Create deeply nested folders
• Leave orphan pages with no links to/from them

---

YAML Frontmatter

Every page should have frontmatter:

---
tags: [company, terminology]
aliases: [glossary, terms]
---

Common Tags

Tag	Use For
company	Business context, products, processes
reference	Data schemas, system specs
guides	How-to instructions
analytics	Dashboards, metrics

---

Common Edits

Adding a Term to the Glossary

1. Open company/terminology.md
2. Find the right alphabetical section
3. Add: ### Your Term followed by the definition
4. Link to related pages if helpful

Adding a Data Source

1. Open data/data-brain.md
2. Find the appropriate section
3. Add a table row or new subsection

Fixing a Broken Link

1. Search for the broken link text
2. Update to correct path: [[correct/path|Display Text]]
3. Verify by clicking in Obsidian

---

Formatting Reference

Tables

| Header 1 | Header 2 |
|----------|----------|
| Cell 1   | Cell 2   |

Code Blocks

```python
def example():
    return "Hello"
```

Callouts (Obsidian)

> [!note]
> 
> This is a note callout.
 
> [!warning]
> 
> This is a warning callout.

---

Review Process

Small changes (typos, link fixes): Commit directly to the deploy branch. No review needed.

Significant changes (new pages, restructuring):

1. Create a branch: git checkout -b my-changes
2. Make your edits
3. Push: git push -u origin my-changes
4. Create a Pull Request on GitHub
5. Get a review, then merge

---

Tools

Recommended: Obsidian

Obsidian (free) provides live preview, graph view, backlinks, quick switcher (Ctrl+O), and link auto-completion.

Alternatives

• VS Code with markdown preview
• GitHub web editor
• Any text editor

---

Last updated: February 2026