Updates and changelogs
Per-game release notes, written once and read everywhere.
Where they show
Updates lists everything across the network, newest first.
app.titanite.family/updates/<game> narrows it to one game, and a game's own
page carries the same entries.
They are one set of records with several views, so a note written for a game appears on the game's page without anybody copying it there.
Writing one
Group staff with edit rights on the game write them on the site. There is no Discord command for this and no file to commit.
Bodies render markdown: headings, lists, quotes, bold, italic, code and links.
Write your list with one bullet per line. A bullet long enough to wrap is still one bullet, and the parser follows the line breaks you actually typed.
Pictures and video
An update can carry extra media beyond the game's own artwork: images, and YouTube video by id.
Video is YouTube only, by decision. Nothing loads from YouTube until somebody presses play, which matters on the Updates page where dozens of entries sit on screen at once.
Images can be uploaded straight from the edit form. There is no need to ask a developer to commit a file.
What replaced what
The front page used to carry four updates written into the code, so changing them meant a developer and a deploy. Now anybody with edit rights on a game can post one.
When you are stuck
My update is not on the Updates page
Check the game it belongs to. An update for a game whose group has withdrawn from the network is hidden along with everything else that group owns.
My list turned into one long paragraph
An old fault, fixed. If you still see it, the body was saved by a version that flattened a wrapped bullet. Re-type the list and save again.
The video shows a grey box
The YouTube id is wrong, or the video is private. Paste the id on its own rather than an embed or a share link with tracking on the end.
An image I replaced still shows the old one
Discord and browsers cache pictures by address. Upload the new one rather than overwriting at the same address, or add ?v=2 to force a fresh read.
I opened an update, changed nothing, saved, and it looks different
Report it. Opening and saving must never change a body, and if it did, the parser has a fault worth fixing rather than working around.