Navigation (v2_optimizer._sync_enterprise_navigation + v2-mkdocs.yml):
- "Topic Map" becomes a collapsible hub holding the three orientation
pages — Topic Map (section index), Methodology, Technical Tags — since
they are all about how the portal is structured.
- "Agentic Video Hub" is promoted above Intelligence Digest as a
prominent top-level dropdown, keeping its category subpages.
Video subpages (v2_video_portal):
- Drop the in-page "## Table of Contents" block; it duplicated Material's
native right-column "On this page" TOC (toc.follow), matching how the
topic pages already omit it. The technology ordering list is retained
internally to drive section render order.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Render a weighted "popular labels" cloud at the top of tags.md: every
label is listed alphabetically and sized/coloured by how many resources
carry it (log scale, 6 levels) so the most-used tags read biggest and
warmest. Each label anchors to its section below for jump-to-filter.
- v2_optimizer: emit .v2-tag-heatmap block in _generate_global_tag_index
- v2_elite.css: .v2-heat-1..6 size + warmth ramp (light + slate)
- bump CSS cache-buster to v2.9.39
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Addresses the OpenShift 'lío' (ocp3 deprecated · openshift overview · ocp4
current 29-link page) and groups the Kubernetes distributions:
- OpenShift is now a nested submenu inside the Kubernetes menu (OpenShift ▸ →
OpenShift 4 (current) · Overview · OpenShift 3 (legacy)), so the substantial
ocp4 page is finally reachable. Reuses the AWS nested-submenu mechanism.
- Distros/platforms grouped at the end of the Kubernetes menu: Managed K8s ·
OpenShift ▸ · Rancher · Distros & Alternatives (kubernetes-alternatives moved
here and relabeled). Rancher was already present.
- Switched the 2-column Kubernetes menu from CSS multicol to a deterministic
column-major grid (11 rows × 2 cols) with overflow:visible / max-height:none,
eliminating the sub-pixel balancing remainder that left a faint scrollbar.
Verified in Chrome 148 (Playwright + screenshot): menu renders as a clean 2-col
card with NO scrollbar at viewport heights 768–1080; the OpenShift submenu opens
to the side, stays on-screen, and keeps the parent open. Cache-bust ?v=2.9.38.
V2-only.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Kubernetes dropdown was the only menu tall enough (22 items) to need a
scrollbar (overflow-y on an anchor-positioned popover), which made it open/behave
unreliably compared to the others. Two fixes:
- The Kubernetes menu now uses a 2-column layout (column-count:2), halving its
height (~731px → ~353px) so it shows in full WITHOUT a scrollbar at any
realistic viewport. Multicol is column-major, so reading order is preserved.
- Removed flip-block from the menu position-try fallbacks (kept flip-inline):
the quick-nav is a sticky top bar, so a tall menu flipped above would shoot
off the top of the screen. Menus now always open downward.
Verified in Chrome 148 (Playwright): Kubernetes menu opens with no scrollbar and
stays fully on-screen at viewport heights 700–1080; all 11 menus + the nested
AWS submenu still open correctly; bar stays one row to 1280px. Cache-bust
?v=2.9.37. V2-only.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Full category-driven reorganization of the quick-nav per the agreed taxonomy:
one direct pill (Topic Map) + 11 thematic dropdowns that group related topics
together so every destination has a sensible home.
Digest · Kubernetes (Overview · Docker · Tools · Helm · kubectl · all
kubernetes-* · Managed · OpenShift · Rancher) · Delivery (GitOps · CI/CD ·
DevOps · Argo · Flux · Tekton · Jenkins · …) · IaC (Terraform · IaC · Ansible
· Pulumi · Crossplane · Kustomize) · Cloud (AWS ▸ nested submenu · Azure · GCP
· Serverless · FinOps · Edge · …) · Network · Security · Observability & SRE ·
AI & Data · Dev & Platform · More
- Docker now lives inside Kubernetes; CI/CD + GitOps + DevOps share Delivery;
Terraform + IaC share the IaC menu (as requested).
- AWS is a NESTED submenu inside Cloud (Cloud → AWS ▸ → 8 AWS pages), built with
nested Popover API + explicit anchor() side-positioning (position-area's
horizontal axis isn't honored when the anchor is inside another popover;
left:anchor(right)/top:anchor(top) fixes it). Submenu keeps the parent open;
flip-inline fallback near the right edge.
- Pages may appear in more than one menu where it aids discovery.
- Menus get max-height:82vh + overflow-y for the tall Kubernetes menu.
Verified in Chrome 148 (Playwright): all 11 menus open below + fit viewport; the
AWS submenu opens to the side with the parent kept open; bar stays one row to
1280px. Cache-bust ?v=2.9.36. V2-only.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Audit of fragmentation found only two prefix clusters: aws (fixed in v2.9.34)
and kubernetes. Unlike AWS, kubernetes is well-classified — a rich parent (157
links) with substantial, distinct children (tools 144, networking 64, security
52, monitoring 24, storage 14, autoscaling 13, ...), not 1-3 link stubs. So
NOTHING is merged for kubernetes; this only adds a 'Deep-Dive Topic Pages' hub
to kubernetes.md indexing its 14 substantial sub-pages (Tools · Networking ·
Security · Monitoring · Storage · Autoscaling · Operators · Alternatives ·
Big Data · Tutorials · Backup & Migrations · Client Libraries · Local Dev ·
On-Premise) — purely additive navigation, no merging, no pruning.
Other small pages (pulumi, kustomize, registries, angular, ...) are legitimate
distinct topics, not fragments of a parent, so they are intentionally left
alone. Verified with --render-only; generator-only, CI republishes.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The AWS landing page rendered with only ~3 links because AWS content was split
across ~20 granular pages (Azure/GCP use a single rich page each), and many AWS
sub-pages had just 1-5 links. Two generator changes fix this:
A. Provider hub: aws.md now renders a 'Deep-Dive Topic Pages' index linking to
the substantial AWS sub-pages that remain (Serverless · Storage · Networking
· Security · IaC · Backup · New Features), via a new self.subpage_hubs map.
So the landing is a navigable index instead of a stub.
B. Stub consolidation: the near-empty / junk-drawer AWS sub-pages (<=7 links,
plus 'miscellaneous') merge into aws.md via the existing merge_map mechanism
(aws-miscellaneous, aws-databases, aws-devops, aws-containers, aws-monitoring,
aws-architecture, aws-tools-scripts, aws-messaging, aws-data, aws-training,
aws-pricing). Those slugs are also removed from self.dimensions so the full
pipeline prunes the orphaned pages and auto-syncs the nav.
Verified locally with --render-only: aws.md goes from 3 to 44 links plus the
7-child hub block; V1 (docs/) is untouched by design — it stays the exhaustive
archive and is still read as the merge source. No regenerated v2-docs or
inventory committed (CI republishes per the generator→republish pattern).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
