# Design: the redesign, in four mockups The proposed redesign of the site for review: what is wrong now, the two dials (who you are and how much you see), which pages each reader sees, the menu per view, and four mockups built from the live data. > Mockup notes for review, built from the data of release v0.10.9. Not the live site. Admin · design · for review ## The redesign: who you are, and how much you want to see The editor's review of 23 October: the site is right in substance and wrong in form. Too geeky, too much text, a menu that is a site map, and half the screen unused. Four mockups, built from the live data, and the model behind them. The model, in one line Two dials. Who you are sets the layout and the order. How much you want (Focus, Standard, Everything) sets which pages exist for you at all. What you have read gets out of the way. ### The four mockups each is a real page, at full width; resize it to see it stack #### A. Front page: board member, Focus The situation on a dark band, five numbers, three questions for the team, what is new, two pictures. #### B. Front page: security lead, Standard Three columns: reading path and tasks; what changed and the next three actions; the evidence as charts. #### C. A content page: the agencies Answer in one line, every agency on one spectrum, a card each, the evidence table one click away. #### D. The team console Its own menu and layout: board as lanes, releases, agents and what they own. ### What is wrong now #### It reads as a wall of text Long paragraphs and tables first; the picture, if any, comes last. Mockup C turns the agencies page into answer, picture, cards, then the table. #### It does not use the screen Pages stop at 1,080 pixels; on a laptop half the screen is empty. The proposal runs to 1,680 with two or three columns that stack on a phone. #### The menu is the site map Eleven groups and 125 entries, ordered by how the site was built, not by what a reader wants to do. The proposal: four to eight entries, chosen by who you are and how much you want. #### Everyone sees everything A board member meets the vault, the board and the billing model on the way to their answer. The proposal: two dials, who you are and how much of the site you see. #### Read things stay in the way The delta strip is right, but read items still fill the pages. The proposal: read items fade, then leave; they return only when they change. #### The team lives in the reader site The board, roles, keys and telemetry sit in the reader menu. The proposal: a console with its own menu and layout, still public. ### Which pages each reader sees a dark square is in Focus; mid is from Standard; light is only in Everything Part of the site A Curious reader J Board member Q CFO R CISO R Journalist S Security lead D PHP A Security researcher Today front page, what is new, the phone app · 8 pages Your briefing the briefing written for your role · 17 pages Ask questions readers ask, the Sherpa · 14 pages Explained plain-English explainer, glossary · 2 pages What to do playbook, patching, affected systems, check your stack · 6 pages The incident the flaws, timeline, discovery, leak, exploitation, impact, defence · 10 pages The analysis claims, fact-check, numbers, agencies, who says what · 35 pages Risk and compliance risk register, frameworks, stakeholders · 113 pages The code the fix in php-src, the review graph · 3 pages Stories signed articles written here · 7 pages The evidence every source, the vaults, the pipeline, versions · 346 pages The site and the team method, roles, board, releases, admin · 60 pages ### Pages per reader, per view Reader Focus Standard Everything Alex Curious reader 26 64 621 Jordan Board member or executive 26 212 621 Quinn CFO 26 212 621 Robin CISO 153 212 621 Rowan Journalist 422 445 621 Sam Security lead 40 102 621 Drew PHP or platform engineer 33 102 621 Ash Security researcher 383 448 621 Counted from the 621 pages this release builds. #### Who sees the team console Everything view only. It stays public, because how the site is run is part of the story; it just stops being in a reader's way. ### The menu, per view today: 11 groups, 125 entries, the same for everyone Focus Four places. For a board member, a CFO, a website owner. Today Your briefing What to ask Explained Standard The site by task, not by where the data came from. Today What to do The incident The evidence Your briefing Ask Everything All of it, for power users and the team. Today What to do The incident The evidence Risk and compliance Stories Method and data Team console ### Design principles - Use the screen. Up to 1,680 pixels, two or three columns on a laptop, one on a phone; text columns stay readable at 60 to 75 characters. - Answer, picture, detail. Every page opens with its answer in one line, then a picture, then the cards; tables and evidence one click down. - Quiet colour, loud only for status. Ink and paper; red, amber, green and blue only where they mean confirmed, warning, risk or information. - The reader chooses who and how much. Two dials in the top bar, remembered in the browser and in their vault. - Seen things get out of the way. Read items fade, then leave; they return only when they change. - The team has a console. Its own menu and layout, public, out of the reader's path. ### How to roll it out - The editor picks from these mockups and marks them up; this page records the decisions. - The design tokens and the wide grid go into the live stylesheet; every page widens at once. - The top bar with the two dials replaces the menu; the view decides which entries exist. - The front page and the briefings move to layouts A and B, per persona group. - Content pages follow pattern C, starting with the agencies, the numbers and the impact. - The admin pages move into console D. Mockups built by the design agent from release v0.10.9; the brief is on the briefs page. Board items record each step. --- site v0.10.9 · https://php.oct.2026.newsroom.sgit.ai/admin/design/index.html