Nearly everything you can publish here is a content item. There are eight kinds, and they are built from the same parts on purpose: learn how one works and you have learned most of how all of them work.
The shared content model
Ownership, visibility, engagement switches, archiving, API exposure — the behaviour every item has. Start here.
Relations
Everything that can be attached to an item: releases, media, dependencies, credits, tags, reviews, followers and the rest.
The eight kinds
Mods
A modification for one specific app. Carries install instructions, a licence, and a client/server environment.
Assets
Game development material. Nearly identical to a mod, except the app is optional — an asset can be engine-agnostic.
Servers
A live game server. The only item with a measured half: we query it, and record who is on it.
Apps
A game or program. Everything else files itself under one, and an app decides what its items may look like.
Communities
A user-run organisation that owns servers, mods and articles, and states a minimum age for its spaces.
Collections
A curated list of other items, installable as a set through the app.
Groups
A roster of people — and, unusually, a permission principal that can be granted access to other items.
Articles
Long-form writing, attachable to any of the above or standing alone.
And two things that are deliberately not content items
Parties are play sessions. They are ephemeral, have no long-form body, take no ratings or reviews, and carry their own small counters instead of writing rows into the shared view / favourite / rating tables. A party that lasted eleven minutes should not leave permanent rows in five shared tables. See Parties.
Categories are taxonomy rather than published work — they organise items, they are not items. See Categories and tags.
Reading this section
Each item page is laid out the same way:
- What it is — the one-paragraph answer.
- What only it does — the fields and behaviour that are not shared.
- What can be attached to it — its relations, with links to the page for each.
- Through the API — how to create and edit it programmatically.