8 Commits (cfbe339df0940492995dbb343d3cb86d64c4daf0)

Author	SHA1	Message	Date
nexxo	cfbe339df0	Die Seitenleiste fragt zuerst, ob etwas auf dich wartet ... Achtundzwanzig Eintraege in sieben Gruppen, und „System" war der Platz fuer alles, was sonst nirgends hinpasste: Mail-Einrichtung neben einem Rechtsdokument, neben den persoenlichen Kontoeinstellungen, neben der Mitarbeiterverwaltung — und ganz unten die Seite, die sagt, was liegt. Der Betreiber hat es so beschrieben: „offene Punkte ist der letzte Punkt, dann Rolle drueber und Einstellungen wieder drueber". Zwei Regeln ordnen es jetzt. Was man einmal einrichtet, verlaesst die Leiste: neun Seiten liegen als Kacheln hinter EINEM Eintrag (admin.setup), gruppiert nach dem, was sie einrichten. Keine dieser Seiten wurde angefasst — sie behalten Route, Berechtigung und Inhalt, es aendert sich nur der Weg dorthin. Damit ist der Umbau rueckholbar. Und die drei Seiten, auf denen etwas WARTET, stehen ganz oben, mit einer Zahl daneben: das ist die Frage, mit der man eine Konsole oeffnet. Stoerungen sind aus „Betrieb" nach oben gezogen und Zahlungsprobleme aus „Geld" — umgezogen, nicht verdoppelt. Bei null faellt die Plakette weg, der Eintrag bleibt: eine Seite, die verschwindet, sobald nichts offen ist, ist genau dann nicht erreichbar, wenn man nachsehen will, ob wirklich nichts offen ist. Zwanzig Eintraege statt achtundzwanzig, jede Seite genau einmal. Zwei Dinge, die beim Verschieben kaputtgegangen waeren: * Die neun verschobenen Seiten standen nicht mehr in console(). Damit war auf ihnen KEIN Eintrag markiert (Codex R15, P2) und currentLabel() lieferte null — die Brotkrume haette dort nur noch „Konsole" gesagt. Zwei Stellen, eine Wurzel: die Kachelliste ist nach Navigation::setup() gewandert, wo beide sie lesen, und isCurrent() haelt die Tuer markiert, solange man dahinter steht. * Die Versionszeile im Fuss stand als toter Text da, waehrend die Seite mit dem Aktualisierungsknopf in die Einrichtung gezogen war. Gemeldet vom Betreiber: „man sieht es nicht, ohne genau hinzuklicken." Sie ist jetzt der Weg dorthin — und sagt in der Akzentfarbe, wenn etwas wartet. Wartet nichts, bleibt sie grau: eine Zeile, die immer ruft, ruft nie. Die drei Zahlen liegen fuer eine Minute im Zwischenspeicher. Diese Leiste rendert auf JEDER Konsolenseite; ohne das waeren es vier Abfragen je Seitenaufruf — eine Abgabe, die man erst sucht, wenn die Konsole zaeh ist. Achtzehn Zusicherungen, darunter die, auf die es ankommt: keine der achtundzwanzig Seiten von vorher ist verlorengegangen. Die Liste steht im Test ausgeschrieben und nicht aus der Repository-Geschichte gelesen — ein Test, der sich seine Erwartung aus demselben Repository holt, das er prueft, prueft nichts. Entwurf: docs/superpowers/specs/2026-08-04-konsolen-seitenleiste-design.md Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-04 02:51:35 +02:00
nexxo	c0f83ab957	Seitenleiste neu geordnet: Betrieb trug zwoelf Eintraege aus drei Themen	2026-08-02 00:29:14 +02:00
nexxo	3a4324fb6f	Give people a way back in, and put the URL in English ... ── The hole ──────────────────────────────────────────────────────────────── There was no password reset. Fortify's feature was commented out, so there was no link on the sign-in form, no page and no route — a customer who forgot their password was locked out of their own cloud until somebody opened a shell. On a product whose selling point is that you can ring somebody, that is a support call a week and an embarrassing one. Two pages of ours under Fortify's route names (R1/R2), because with views off Fortify registers only the POST endpoints. The mail is a Mailable in this product's design rather than the framework's MailMessage: somebody who has just been locked out is exactly the person a phishing mail is aimed at, and a message that looks nothing like the rest of our post is one they cannot check — ours carries the footer that names our domains. Three decisions worth stating, each with a test: The answer is identical whether the address is known or not. "No account with that address" turns the form into a way of finding out who is a customer. The reset kills every other session. Whoever knew the old password may still be signed in somewhere, and a reset that leaves them there has fixed nothing. It does NOT sign the visitor in. The link arrived by email, and a mailbox somebody else can read would otherwise be a session somebody else gets. ── /sicherheit → /security ───────────────────────────────────────────────── R13: paths are English. Mine was not. The old path stays as a permanent redirect because it has already gone out in mail footers. ── One wordmark ──────────────────────────────────────────────────────────── "Sometimes it says Cloud and sometimes it does not" — correct. It was on the footer, the placeholder and the maintenance screen, and absent from the header, the sidebar and the sign-in plate. The product is called CluPilot Cloud; that is the name on the invoices and in every mail, so it is now the name everywhere. The console sidebar takes the small size so the lockup, the ADMIN badge and the close button still share one line (R18). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-29 16:50:29 +02:00
nexxo	17a6fabcc2	One wordmark, one typeface, and the address the server actually issues ... Reported as "logo and font are different everywhere" — maintenance page, customer panel, console, homepage. They were. Counting them up: the site header set the name in ink at -0.02em, the sidebar split it into "Clu" plus an orange "Pilot", the sign-in plate set it white at a third size, the customer two-factor page set it in MONO with no mark at all, the error pages and the placeholder each inlined their own — and the maintenance screen had no wordmark whatsoever. Nine surfaces, seven ideas of the brand. There is one now: resources/views/components/ui/brand.blade.php. Mark plus wordmark in one piece, in ink, with an optional muted "Cloud". No orange half — that made the accent a permanent fixture instead of something used sparingly. The four places that cannot use a Blade component (the two self-contained pages, the error layout, the mail layout) inline it and are held to the same shape by a test. The typeface. The console loads IBM Plex through Vite; the 503 page has no stylesheet at all, so the maintenance screen — the one page shown when somebody is already worried — was rendering in the system sans. It declares the fonts itself now. And the bold weight was missing from public/fonts entirely: the placeholder and the error pages both asked for ibm-plex-sans-latin-700-normal.woff2, which was not there. A @font-face pointing at nothing fails silently, which is why nobody noticed. The error pages carried the same two faults the placeholder shipped with: an empty gradient tile where the mark belongs, and `gap` on an inline-flex row spacing "Clu", "Pilot" and "Cloud" apart as three separate words. And the price sheet promised "Adresse auf clupilot.cloud" — a domain the company does not own — while provisioning was issuing addresses under whatever CLUPILOT_DNS_ZONE says. It is assembled from that setting now, the same reason the prices are read from the catalogue rather than typed into the page. welcome.blade.php removed: Laravel's leftover, reachable from no route. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-29 14:30:44 +02:00
nexxo	3fadaa14b0	Merge credentials and infrastructure into one Integrations page ... Zugangsdaten and Infrastruktur split the same subject by storage mechanism — SecretVault vs App\Support\Settings — instead of by what each field configures, which is not a distinction an operator setting up Stripe or DNS should have to know or care about. One page now, grouped by integration: Zahlungen (Stripe), DNS (Hetzner), Monitoring, VPN/WireGuard, SSH-Identität. A secret and a plain setting sit side by side within a section; the difference stays visible — a vault entry is write-only and shows only an outline, a setting shows its value in full — as a property of the field, not a reason for a separate page. Both storage mechanisms are unchanged underneath: this is a presentation change, not a data migration. The vault keeps its own gate (secrets.manage + a recently confirmed password); plain settings keep theirs (hosts.manage alone). Reachable with either capability, since the two are no longer two pages a role happens to see one, both, or neither of — every section and every save action still checks its own capability server-side. admin.secrets and admin.infrastructure redirect here permanently rather than 404ing a bookmark. The nav entry that replaces both is visible to either capability — Navigation's capability field now accepts an array meaning "any of these", not only a single ability. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-29 01:49:39 +02:00
nexxo	bda61ca560	Pin the sidebar header and footer so only the nav list scrolls, and shorten two action labels that wrapped	2026-07-28 20:52:12 +02:00
nexxo	435a202fdd	Match the panel to the approved template, measured rather than assumed ... The panel had been built by reading the template and believing the result. Every round of review found the same class of defect, so this round the template was rendered in a browser and measured with getComputedStyle, and the implementation measured the same way — two number columns instead of an opinion. That immediately settled a disagreement: a review of the template's SOURCE said the metric grid used a 20px gap. Rendered, it is 14px. The measurement wins. Brought to the template's figures: label 11.5px (it was 11px in three separate places, which is how it drifted — it is now one .lbl rule), value tracking -0.02em, unit weight 450, metric row 6px above and 14px between, page head centred with a 14px gap, grid gap 14px, columns switching at 1101/561px and the h1 at 901px to match the template's own breakpoints, ring 62px, bar 5px. The shared button now takes its height from min-height (40px) rather than vertical padding, at 14px/600 with 0 18px padding and a 10px radius — a button keeps its height whatever sits inside it, icon, spinner or bare text. Also here, from the same round of review: - The chart's blue border was Tailwind's own `ring` utility colliding with a component class of the same name. Renamed to `.metric-ring`. This was dismissed once as a screenshot artefact; it was real. - Page titles lost the `sm:text-3xl` (40px) an earlier bulk edit had appended to 23 of them. The template's h1 is 30px. - The users table has its actions back — edit, suspend, lock and delete — for every seat that is not the owner, with the owner refused in the action itself and not merely hidden in the markup. DemoCustomerSeeder writes one complete customer as real rows: instance, subscription, six seats across four roles, a backup, current-period traffic and thirty days of samples with a deliberate wobble and one day at 286/288 checks. Nothing in the panel is drawn from a fixture any more, so anything missing shows up as missing. Removing the demo is one deletion. Verified: 607 tests, and a Codex comparison of the two measurement sets — "a person would call them the same design", the only difference a 1px gap. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-27 17:08:05 +02:00
nexxo	6376f5e9fa	One design system for every surface ... The console was a second product. admin-tokens.css held a complete dark set — its own surfaces, its own orange, its own status triad — so every shared component had to work in two worlds, and the two halves of the application drifted apart in ways nobody could see from inside either one. That file now carries density and nothing else: smaller type, tighter rows, tighter corners. Colour comes from one place. The tokens themselves are rebuilt around what the redesign settled on: - Radii scaled to object size (9/11/16/22) instead of one value everywhere, which is what made the interface read as a design-system specification rather than as a product. - Warm, broad, low shadows. A neutral grey drop shadow belongs to a different design language and reads as cold on this ground. - --accent-press, which several rules already referenced and nothing defined. An undefined var() does not make a browser skip the declaration; it computes to , and for background-color that is transparent — the accent button lost its fill on hover and left white text on white. - No serif. A serif headline is what made every page read as a document, which is the impression the whole redesign exists to remove. --font-serif now points at the sans so nothing breaks while call sites are cleaned up. The two shells are one shell with two configurations, and both finally have a mobile navigation: the sidebar used to simply disappear below 900px, leaving no way to move around the application at all on a phone. The customer dashboard is bound to real records — instance, seats, traffic, backups, contract — instead of the fixtures it shipped with. Where something is not measured, storage consumption, it says what was contractually agreed rather than inventing a figure. This is the sheet a customer forwards to their auditor. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-07-27 16:03:47 +02:00