Servers is a block in Administration, not a section of its own

It is the same KIND of thing as the root location and the databases — this
machine, not the site's content — and a nav row leading to one card was a whole
screen to reach three lines.

Last of the three, because it needs both of the others: a server has nowhere to
run without the checkout and nothing to read without a database.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-29 13:53:39 +01:00
co-authored by Claude Opus 5
parent ca43f7ef86
commit b27969ba57
4 changed files with 42 additions and 61 deletions
+5 -2
View File
@@ -1,5 +1,6 @@
import { RootLocationBlock } from './RootLocationBlock';
import { DatabaseBlock } from './DatabaseBlock';
import { ServersBlock } from './ServersBlock';
/**
* Administration — this plugin's own machinery, not the client's site.
@@ -8,8 +9,9 @@ import { DatabaseBlock } from './DatabaseBlock';
* message; this file decides only which of them exist and in what order.
*
* The order is the order things are needed in: where the site is on this machine, then how to read its
* data. Building `derived/` from `originals/` lives with the folders it acts on, inside Root Location,
* rather than as a section here describing the same two directories a second time.
* data, then the processes that serve it — which need both. Building `derived/` from `originals/`
* lives with the folders it acts on, inside Root Location, rather than as a section here describing the
* same two directories a second time.
*
* ── What used to be here ──
*
@@ -23,5 +25,6 @@ export const AdministrationPanel = () => (
<div className="flex size-full flex-col gap-4 overflow-auto p-5">
<RootLocationBlock />
<DatabaseBlock />
<ServersBlock />
</div>
);