Eighteen sections, one guild

Most guild platforms ship the same shape: a forum, a calendar, a roster, sometimes a Discord widget. The shape rarely changes. We outgrew it years ago, kept layering tools on top of tools, and ended up running a coordination problem instead of a guild. The rebuild collapses everything back into one place that we own.

The interesting decision was scope. We ended up with eighteen sections in the sidebar, and every one of them earned its place by replacing a Discord channel, a stale spreadsheet, or a shared note someone was tired of maintaining. Nothing on the site exists because a guild site is supposed to have it. Things exist because something used to live somewhere worse.

Fleet is the easy example. Members run ships. Ships used to live in a pinned Discord post, three abandoned spreadsheets, and the heads of two officers. Now they live in a typed table that fills its own technical fields on save. Planning a multi-ship op went from a ten-message thread to a filter on a roster.

Treasury is the harder example. Two tables for income and expense would have shipped faster. Instead every entry carries a category, an optional link to the operation that produced it, and a creator. Those categories took ten minutes to define and saved more time than the rest of the build, because they let any officer answer 'how much did mining make us last quarter' without opening a spreadsheet.

The temptation when you are the only admin during a build is to skip the admin UI and edit the database directly. Resist it. Every section that started members-first and admin-second had to be revisited the moment a real admin needed to do anything in bulk. Build the admin shape first, derive the member view from it. That lesson cost a month and applies to almost every internal tool I have ever shipped.

The thing I am proudest of is invisible. Public routes are rate limited at the edge. Admin writes pass through an audit log. Every form validates twice. None of it shows in screenshots. All of it is there because the previous site failed in exactly the ways a site fails when none of those things exist.

What I will not do is turn this into a public hosted product. There are guild platforms that already do that. This one is for our guild, written by a member, owned by us, accountable to no one else. That accountability boundary is the entire point.