Final pass internal-developer-portal-platform-self-service-actions article

Author: webstackdev

_TODO.md

@@ -307,6 +307,7 @@ src/content/articles/internal-developer-portal-platform-self-service-actions/pdf
 />
 
 <List
+  startNumber={2}
   classes={{
     wrapper: "sm:ml-6 sm:mr-12 mb-6",
   }}

src/content/articles/internal-developer-portal-platform-self-service-actions/index.mdx

@@ -16,20 +16,23 @@ Last month I watched a developer spend three days getting a PostgreSQL database.
 
 And yet the outcome was identical to not having a portal at all - the same tickets, the same meetings, the same waiting.
 
-That's the portal-versus-platform distinction that trips up most organizations. A portal __indexes__ things: it aggregates links, surfaces documentation, shows who owns what. A platform __does__ things: it provisions infrastructure, creates repositories, grants access. The portal tells you how to request a database. The platform gives you a database.
+That's the portal-versus-platform distinction that trips up most organizations. A portal _indexes_ things: it aggregates links, surfaces documentation, shows who owns what. A platform _does_ things: it provisions infrastructure, creates repositories, grants access. The portal tells you how to request a database. The platform gives you a database.
+
+<Highlighter>Self-service actions are what transform a directory into a platform.</Highlighter> Without them, you've built a prettier wiki.
 
 <Callout type="warning">
 If your "platform" requires developers to read documentation and file tickets to get things done, you've built a directory, not a platform. Platforms execute workflows. Directories point to workflows that humans execute.
 </Callout>
 
-Self-service actions are what transform a directory into a platform. Without them, you've built a prettier wiki.
-
 ## The Portal Maturity Model
 
 Most internal developer portals evolve through predictable stages. Understanding where you are helps clarify where to invest next - and where most organizations get stuck.
 
 <List
-  variant="check-icons-list"
+  variant="chevron-list"
+  classes={{
+    wrapper: "sm:ml-6 sm:mr-12 mb-6",
+  }}
   items={[
     {
       lead: "Level 1: Directory.",
@@ -51,7 +54,11 @@ Most internal developer portals evolve through predictable stages. Understanding
 />
 
 <Table
-  variant="vertical-column-delineation-table"
+  variant="grid-and-accent-header-table"
+  fullWidth={false}
+  classes={{
+    tbody: '!text-content',
+  }}
   content={{
     figure: "Portal maturity levels.",
     thead: {
@@ -158,7 +165,7 @@ The YAML is straightforward, but the design decisions matter. Notice the sensibl
 Five principles separate good actions from frustrating ones.
 
 <List
-  variant="check-icons-list"
+  variant="numbered-with-background-list"
   items={[
     {
       lead: "Obvious outcomes.",
@@ -191,24 +198,28 @@ The best self-service actions feel like filling out a form to order something on
 
 Approvals are where self-service platforms regress into ticket systems. The instinct is understandable - production changes are risky, expensive resources need oversight, compliance requires audit trails. But if every request routes through a manual approval queue, you've just built Jira with a different skin.
 
-The solution is __policy-based approval routing__: define rules that auto-approve low-risk requests while routing high-risk ones to the right approvers. Most requests should flow through automatically. Approvals become the exception, not the rule.
+The solution is _policy-based approval routing_: define rules that auto-approve low-risk requests while routing high-risk ones to the right approvers. Most requests should flow through automatically. Approvals become the exception, not the rule.
 
 The dimensions that typically matter:
 
 <List
-  variant="check-icons-list"
+  variant="badge-list"
+  classes={{
+    titleClass: "block w-full text-center",
+    wrapper: "sm:ml-2 mb-6",
+  }}
   items={[
     {
-      lead: "Environment-based:",
-      text: "dev auto-approves, production needs sign-off",
+      title: "Environment-based:",
+      lead: "Dev auto-approves, production needs sign-off",
     },
     {
-      lead: "Cost-based:",
-      text: "under $100/month auto-approves, over $500 needs finance",
+      title: "Cost-based:",
+      lead: "Under $100/month auto-approves, over $500 needs finance",
     },
     {
-      lead: "Risk-based:",
-      text: "standard operations auto-approve, IAM changes need security review",
+      title: "Risk-based:",
+      lead: "Standard operations auto-approve, IAM changes need security review",
     },
   ]}
 />