WikilyWIKILY
All games8 Wikis · pick your game
8
Menu

Documentation

Tables and rows

Updated 2026-08-13

Two hundred weapons, each with damage and a picture. Written as two hundred separate pages, that is two hundred chances to format a number differently.

A table is the alternative: keep the facts once, in rows and columns, and let pages read from it.

What a table is

A table has columns, the facts you keep, and rows, one per thing. Each column has a type: text, number, date, yes/no, picture, or JSON for a nested list.

A table is a grid: the columns are the facts you keep about every entry, and each row is one entry. Empty cells are normal - not every enemy has a boss phase.
Empty cells are normalMost tables have columns only some entries use. That is what conditions exist for.
One column names the entryPage titles, pickers and automatic addresses are built from it, so keep it short, unique and stable.

Add a table

  1. Open your wiki and click Manage.
  2. Go to Media, then the Data tab.
  3. Click New table and upload a CSV or JSON file, or paste the data in.
  4. Check the detected column types, fix any it got wrong, and give them readable names.
  5. Save.

Spend a minute on the column names. You will see them in every inspector, picker and condition from now on, and “Health” reads better than “hp_val” every time.

Re-uploading later replaces the rows and keeps the columns, which is how a table stays in step with a game patch without anything else needing an edit.

Connect a page to a row

A page becomes data-driven by being bound to one row. The page keeps its own address and its own writing; the row supplies the facts.

Binding connects one page to one row. The page keeps its own address and its own writing; the row supplies the facts, and every block that reads a column gets that row's value.
  1. Open the page in the editor.
  2. Open the Binding panel.
  3. Choose the table, then the row this page is about.
  4. Click Bind to row.

From then on, blocks that read a column draw this row’s values, and the editor shows them while you work rather than after you publish.

A page for every row

Binding one page at a time is fine for a handful. For a whole table, generate them:

  1. Go to Media to Data and open the table.
  2. Click Generate pages.
  3. Choose the address they live under. enemies/ gives you enemies/grunt, enemies/assassin, and so on.

Each generated page is bound to its row automatically. They start empty, which is the moment to give them all one design at once. See One layout for every entry.

When the columns change

A re-upload can rename or drop a column. Blocks reading the old name do not error, they render empty, which is the worst way to find out.

So the table has a drift screen listing every block still pointing at a column that no longer exists, across your pages and the shared layout.

Repoint itAim the block at the new column.
Remove itDelete the block that has nothing left to read.
Mark expectedSome blocks legitimately read a different table.

Check it after any re-upload that was not a straight data refresh. Five minutes there beats a reader telling you a stat block has been blank for a month.

Correct a single value

Sooner or later one row is wrong. You do not have to edit the file and re-upload: a bound page’s editor has a Row data panel that edits that row’s values directly.

Those edits are overrides. They sit on top of the uploaded data, so a re-upload replaces the source and your corrections are applied again on top.

Everything that reads the row sees the corrected value: pages, lists, the editor’s preview.