Nodes

Public graph

Created about 9 hours ago, updated about 9 hours ago · Owners: Root

ID29537

What it is. A node explains one idea well enough to be read on its own. It has a title, a body in Markdown, and links to its parents and children. It can carry math (written in LaTeX), figures, tables and references found by DOI or arXiv ID.

Why one idea. Small nodes can be reused wherever an idea is needed, improved without touching their neighbours, and owned by the people who wrote them. A node that tries to explain three things is better as three nodes.

What comes with it.

  • History: every saved change is a version, with a title and, on public nodes, a description of what changed and why. Versions can be compared word by word.
  • Talk: a page for questions, disputes and discussions about the node.
  • Owners: on the public graph, the people who decide what changes in it (see Who owns what).
  • Files: attachments such as PDFs and images.

How it is built. A node is a database record with its content, its author's handle and its visibility; its versions are kept in full, so nothing is ever lost. Search indexes its text, and, where it is switched on, its meaning.

Limits. A node has one title and one current text; alternatives live in forks and proposals until their owners decide.


Read on

  • A node's page: What a node's page shows: where it sits, its text and who made it, its parents and children, and the tools around it.

Under the hood

  • Nodes, edges and versions: How a graph is stored: nodes with Markdown text, typed edges between them, and a version for every commit.
See in the graph Search below

Parents1More general nodes this one belongs to

Children22 nodes that explain it further