Skip to content
360 linesCodeBlameRaw
1/**
2 * sudo's navigation, and the roadmap for what g1t is building in house:
3 * its own CRM and back office, in place of bought ones. Each item is a
4 * real page. One marked `soon` renders a placeholder that says what it
5 * will do and why, so staff can see where sudo is going (routes.ts makes
6 * a route for each). No Workers or React imports, so it can be tested
7 * under Node.
8 */
9
10/** The icon a sidebar item shows; components/shell.tsx draws each one. */
11export type NavIcon =
12 | "overview"
13 | "workspaces"
14 | "enterprises"
15 | "reach-out"
16 | "people"
17 | "invoices"
18 | "prices"
19 | "credits"
20 | "usage"
21 | "stripe"
22 | "costs"
23 | "abuse"
24 | "incidents"
25 | "inbox"
26 | "view-as"
27 | "announcements"
28 | "staff"
29 | "audit"
30 | "requests"
31 | "overages"
32 | "velocity"
33 | "invites"
34 | "aliases"
35 // Sections
36 | "customers"
37 | "spend"
38 | "revenue"
39 | "platform"
40 | "support"
41 | "team";
42
43/** What a page that is not built yet says about itself. */
44export type Roadmap = {
45 /** What it will do and why, two to four sentences. */
46 summary: string[];
47 /** What it will have, one line each. */
48 plans: string[];
49 /** Something staff should know now, such as where to go meanwhile. */
50 meanwhile?: { text: string; to?: string; link?: string };
51};
52
53export type NavItem = {
54 label: string;
55 /** Where it lives. A `soon` item's page is the placeholder. */
56 to: string;
57 icon: NavIcon;
58 /** One line, shown on hover. */
59 about: string;
60 /** Other paths under which this item is the current one. */
61 also?: string[];
62 /** Not built yet: the page says what it will be. */
63 soon?: Roadmap;
64 /** A number the sidebar shows beside it while it is above zero, such as requests waiting. */
65 count?: NavCount;
66};
67
68/** The numbers the sidebar can show, read by root.tsx on every page. */
69export type NavCount = "waitlist" | "incidents";
70
71export type NavCounts = Partial<Record<NavCount, number>>;
72
73/** What a page or a folded section shows beside it: its items' counts, added up. */
74export function countFor(items: Pick<NavItem, "count">[], counts: NavCounts): number {
75 return items.reduce((sum, item) => sum + (item.count ? (counts[item.count] ?? 0) : 0), 0);
76}
77
78/**
79 * A section of the sidebar: a row with an icon that opens to its pages,
80 * as GitLab and Vercel fold theirs. One with no title is top-level links.
81 */
82export type NavGroup = { title: string | null; icon?: NavIcon; items: NavItem[] };
83
84export const NAV: NavGroup[] = [
85 {
86 title: null,
87 items: [
88 { label: "Overview", to: "/", icon: "overview", about: "The business at a glance: this month, the last six, and who needs a word." },
89 { label: "Reach out", to: "/reach-out", icon: "reach-out", about: "Who is worth a word now, and who on the team has it." },
90 ],
91 },
92 {
93 title: "Customers",
94 icon: "customers",
95 items: [
96 { label: "Workspaces", to: "/workspaces", icon: "workspaces", about: "Every workspace, who owns it, and how it pays." },
97 { label: "Enterprises", to: "/enterprises", icon: "enterprises", about: "Customers paying for several workspaces with one bill." },
98 {
99 label: "Invites",
100 to: "/invites",
101 icon: "invites",
102 about: "The waitlist, every invite, more invites for a person or workspace, and who invited whom.",
103 count: "waitlist",
104 },
105 {
106 label: "Aliases",
107 to: "/aliases",
108 icon: "aliases",
109 about: "Names that lead to a workspace, such as g1t to flagon-io. Staff set them; customers cannot.",
110 },
111 {
112 label: "People",
113 to: "/people",
114 icon: "people",
115 about: "Everyone with a g1t account, across the workspaces they belong to.",
116 soon: {
117 summary: [
118 "Every person with a g1t account, not just the workspaces they belong to. Support starts from a person far more often than from a workspace: someone writes in from an email address, and staff need to find them, see which workspaces they own or belong to, and what they did lately.",
119 "It gives sales a view of contacts as well as accounts: the owner who signs, the engineer who brought g1t in, and who to ask when a workspace goes quiet.",
120 ],
121 plans: [
122 "Search by username, email or name, across every account",
123 "A person's page: their workspaces and role in each, sign-ins, verified email, two-factor status",
124 "Contacts on a workspace: who is the buyer, who is technical, who to bill",
125 "Merge duplicate accounts, and resend or change a verification email, each recorded",
126 ],
127 meanwhile: { text: "Search a workspace by an owner's username or email on Workspaces.", to: "/workspaces", link: "Workspaces" },
128 },
129 },
130 ],
131 },
132 {
133 title: "Spend",
134 icon: "spend",
135 items: [
136 {
137 label: "Requests",
138 to: "/requests",
139 icon: "requests",
140 about: "Owners asking for a higher limit or help with a month: answered within one business day.",
141 },
142 {
143 label: "Overages",
144 to: "/overages",
145 icon: "overages",
146 about: "Workspaces well past their typical month, what caused it, and goodwill credits.",
147 },
148 {
149 label: "Velocity",
150 to: "/velocity",
151 icon: "velocity",
152 about: "Who is spending fastest right now, against their usual hour, and any spikes.",
153 },
154 ],
155 },
156 {
157 title: "Revenue",
158 icon: "revenue",
159 items: [
160 {
161 label: "Invoices",
162 to: "/invoices",
163 icon: "invoices",
164 about: "Every invoice g1t has sent, to workspaces and enterprises.",
165 },
166 {
167 label: "Plans & prices",
168 to: "/prices",
169 icon: "prices",
170 about: "The price book: what each meter costs g1t and what it sells for.",
171 soon: {
172 summary: [
173 "The price book, edited in sudo instead of in code. Every metered unit (sandbox seconds, builds, app requests and CPU, app-months) has what it costs g1t and what g1t sells it for, and the price follows the cost with a markup.",
174 "Changing a markup or a plan's price is a decision finance makes and should be able to make safely: previewed against last month's usage, with a date it takes effect, and recorded with who made it and why.",
175 ],
176 plans: [
177 "Each meter's cost, markup and price, and where the cost came from (Cloudflare's list price or its bill)",
178 "Edit a markup or a plan's monthly price, with a preview of what last month would have charged",
179 "Schedule a change for the start of a month, so no one is charged mid-month on a new price",
180 "Every change in the history the public pricing page already shows",
181 ],
182 },
183 },
184 {
185 label: "Credits & refunds",
186 to: "/credits",
187 icon: "credits",
188 about: "Every credit staff have given (promotional, goodwill, refunds), what was used, and each month by kind.",
189 },
190 {
191 label: "Usage explorer",
192 to: "/usage",
193 icon: "usage",
194 about: "What customers used, sliced by meter, model, repository and day.",
195 soon: {
196 summary: [
197 "What customers used, across every workspace, sliced any way: by meter, repository and day. It answers the questions that come up in a sales call or a cost review: who uses the most sandbox time, and what a customer spends per pull request.",
198 "Billing records every run and sandbox second with its cost and charge already. This puts it in front of the people who need it, without a query.",
199 ],
200 plans: [
201 "Charged, cost and margin over any range, for everyone or one customer",
202 "Group by meter, model, task, repository or workspace; compare two periods",
203 "The heaviest workspaces this month, and how fast each is growing",
204 "Export to CSV",
205 ],
206 },
207 },
208 ],
209 },
210 {
211 title: "Platform",
212 icon: "platform",
213 items: [
214 { label: "Stripe", to: "/stripe", icon: "stripe", about: "Billing's Stripe keys, webhook, and the events Stripe sent." },
215 {
216 label: "Costs & margin",
217 to: "/costs",
218 icon: "costs",
219 about: "Where g1t's money goes, with what it gave away kept apart; on Bill & pricing, Cloudflare's bill, drift and the price book.",
220 },
221 {
222 label: "Abuse & fraud",
223 to: "/abuse",
224 icon: "abuse",
225 about: "Sandboxes stopped for looking like mining, and disputes and declines.",
226 },
227 {
228 label: "Incidents",
229 to: "/incidents",
230 icon: "incidents",
231 about: "Declare and run incidents, schedule maintenance, and publish postmortems on status.g1t.sh.",
232 count: "incidents",
233 },
234 ],
235 },
236 {
237 title: "Support",
238 icon: "support",
239 items: [
240 {
241 label: "Inbox",
242 to: "/inbox",
243 icon: "inbox",
244 about: "Customers' messages, beside everything about who sent them.",
245 soon: {
246 summary: [
247 "Customers' email and in-app messages in one queue, each beside everything sudo knows about who sent it: their workspaces, what they pay, their limit, their last invoice, and the notes sales kept. Support answers faster when nothing needs looking up.",
248 "Built in house so a conversation can become an action without leaving it: a credit, a billing link, a note on the workspace.",
249 ],
250 plans: [
251 "Assign, snooze and close conversations; see who is answering what",
252 "The sender's workspaces, plan, limit and recent invoices alongside",
253 "Saved replies, and links that open the right page in g1t",
254 "Response times by person and by week",
255 ],
256 },
257 },
258 {
259 label: "View as customer",
260 to: "/view-as",
261 icon: "view-as",
262 about: "See g1t as a customer sees it, audited and time-limited.",
263 soon: {
264 summary: [
265 "See g1t exactly as a customer sees it, to reproduce what they describe. Read-only by default, it is the most sensitive thing staff can do, so it is built to be safe first.",
266 "Every session will be audited and time-limited: it needs a reason, it ends on its own, the customer's own audit log says that g1t staff looked, and nothing can be changed or any secret read while viewing.",
267 ],
268 plans: [
269 "Start a session with a reason (a support conversation or a note); it ends after 30 minutes",
270 "Read-only: no pushes, no settings, no secrets, no billing changes",
271 "A banner on every page while it lasts, and a record in the customer's audit log",
272 "Only roles allowed to, and a list of every session for review",
273 ],
274 },
275 },
276 {
277 label: "Announcements",
278 to: "/announcements",
279 icon: "announcements",
280 about: "Banners and notices for customers: incidents, maintenance, changes.",
281 soon: {
282 summary: [
283 "Tell customers what they need to know, from one place: a banner for an incident or maintenance, a notice about a price change, an email to the owners of the workspaces a change affects.",
284 "Notices can go to everyone or to a slice (owners on an enterprise, workspaces near their limit), with a start and an end, and a record of who sent what.",
285 ],
286 plans: [
287 "Banners in g1t with a start, an end, and a severity",
288 "Email to owners of chosen workspaces, previewed before it goes",
289 "Price-change notices with the notice period the terms require",
290 "A history of everything announced",
291 ],
292 },
293 },
294 ],
295 },
296 {
297 title: "Team",
298 icon: "team",
299 items: [
300 {
301 label: "Staff & roles",
302 to: "/staff",
303 icon: "staff",
304 about: "Who is staff, and what each role may do.",
305 soon: {
306 summary: [
307 "Who is g1t staff and what each of them may do. Today everyone in STAFF_EMAILS may do everything; as the team grows, roles should match the work: sales can see accounts and keep notes but cannot credit, support can make billing links and small credits, finance can change terms and issue refunds.",
308 "Access still decides who gets in. Roles decide what they can do once there, and every refusal is recorded like every change.",
309 ],
310 plans: [
311 "Roles (sales, support, finance, admin) with the permissions each grants",
312 "Per-role limits on money: the most a credit can be without a second person",
313 "Assign roles by email, recorded, with the date each was given",
314 "A second person's approval for comped terms and large credits",
315 ],
316 },
317 },
318 {
319 label: "Audit log",
320 to: "/audit",
321 icon: "audit",
322 about: "Every change made in sudo, by whom, across every customer.",
323 },
324 ],
325 },
326];
327
328/** Whether a section holds the page at `pathname`, so it is drawn open. */
329export function holdsCurrent(group: NavGroup, pathname: string): boolean {
330 return group.items.some((item) => isCurrent(item, pathname));
331}
332
333/** Every item, in sidebar order. */
334export function navItems(nav: NavGroup[] = NAV): NavItem[] {
335 return nav.flatMap((group) => group.items);
336}
337
338/** The items not built yet, each with the placeholder page routes.ts makes. */
339export function soonItems(nav: NavGroup[] = NAV): (NavItem & { soon: Roadmap })[] {
340 return navItems(nav).filter((item): item is NavItem & { soon: Roadmap } => item.soon != null);
341}
342
343/** The item for a path, if one is its page. */
344export function soonFor(pathname: string, nav: NavGroup[] = NAV): (NavItem & { soon: Roadmap }) | null {
345 const path = pathname.replace(/\/+$/, "") || "/";
346 return soonItems(nav).find((item) => item.to === path) ?? null;
347}
348
349/**
350 * Whether `item` is the current page at `pathname`: its own path or one
351 * beneath it. `/` is current only on itself.
352 */
353export function isCurrent(item: Pick<NavItem, "to" | "also">, pathname: string): boolean {
354 const path = pathname.replace(/\/+$/, "") || "/";
355 return [item.to, ...(item.also ?? [])].some((prefix) => {
356 const base = prefix.split("?")[0];
357 if (base === "/") return path === "/";
358 return path === base || path.startsWith(`${base}/`);
359 });
360}