25ffb8cc734db9cb80fa7272fb9596e5eefe2634
wiki/what-wikis-are-good-for.md
new file mode 100644
index 0000000..dd9dc46
@@ -0,0 +1,35 @@
+---
+visibility: public
+---
+
+# what wikis are good for
+
+wikis are one of the oldest and most enduring formats on the web — and for good reason. they solve a specific problem better than almost anything else: **making knowledge accumulate instead of decay.**
+
+## living documents over static ones
+
+a wiki page is never "done." unlike a blog post or a report, a wiki page is expected to be revised, extended, and corrected over time. this makes wikis ideal for any knowledge that evolves: research notes, project documentation, technical references, team processes.
+
+## collaborative sense-making
+
+wikis lower the barrier to contribution. anyone with access can fix an error, add a link, or extend a section. this means the collective understanding of a group can be captured incrementally, without bottlenecking on a single author.
+
+## structure that emerges organically
+
+wikis let structure develop bottom-up through linking. you don't need to design a taxonomy upfront — you create pages as needed and link them together. over time, a navigable knowledge graph emerges from the connections between pages.
+
+## good use cases
+
+- **research notes** — accumulate findings, link related concepts, build a personal or team knowledge base
+- **project documentation** — keep specs, decisions, and context in one place that stays current
+- **learning journals** — write to understand, revisit and refine as your understanding deepens
+- **worldbuilding** — fiction, games, campaigns — wikis are the native format for interconnected lore
+- **open knowledge** — public wikis let communities build shared references (Wikipedia being the canonical example)
+
+## what wikis are NOT good for
+
+- time-ordered content (use a blog)
+- ephemeral discussion (use chat)
+- polished one-time publications (use a document)
+
+the power of a wiki is that it rewards returning to the same page. if your content is write-once-read-many, a wiki adds overhead without benefit. if your content is write-many-read-many, a wiki is the best tool that exists.
\ No newline at end of file