[Blog] Minor edits; plus styling

Author: Andrey Cheptsov

mkdocs.yml

@@ -75,7 +75,7 @@ plugins:
       categories_url_format: "{slug}"
       archive: false
       categories_name: Blog
-      categories_sort_reverse: true
+      # categories_sort_reverse: true
   - social:
       cards_layout_options:
         background_color: "black"

mkdocs/assets/stylesheets/cloudscape-docs.css

@@ -1861,6 +1861,7 @@
 }
 .md-typeset :is(h1, h2, h3, h4, h5, h6) a:hover {
     text-decoration: underline;
+    color: inherit;   /* keep the heading color — don't pick up Material's accent (lilac) on hover */
 }
 
 /* Blog excerpt header (author avatars + date · category · read time) removed entirely on the
@@ -1875,31 +1876,13 @@
 }
 
 /* ===== Blog post (article) layout ========================================== */
-/* Blog posts render NO left sidebar (overrides/blog-post.html) — only the article + right rail.
-   The content div carries .md-content--blog (NOT Material's .md-content--post, which is a
-   column-reverse flex meant to pair the post sidebar with the article). It's a CSS hook to widen
-   the article to the same "collapsed left menu" layout as a docs page with the nav hidden: a
-   1280px region (960 body + 40 gap + 280 rail) centered in the viewport. :has() reaches ancestors. */
+/* Blog posts use the same desktop layout as the blog index/category pages: left nav sidebar +
+   article + right rail (On this page, then the relocated post metadata). The content div carries
+   .md-content--blog purely as a hook for that metadata relocation (see .cs-post-meta); layout-wise
+   it now matches a normal page, so no width/sidebar overrides are needed here. */
 @media screen and (min-width: 76.1875em) {
-    .md-main__inner.md-grid:has(.md-content--blog) {
-        max-width: 1280px;
-        margin-left: auto;
-        margin-right: auto;
-    }
-    .md-main__inner:has(.md-content--blog) .md-content {
-        margin-left: 0;
-    }
-    .md-main__inner:has(.md-content--blog) .md-sidebar--secondary {
-        margin-right: 0;
-    }
-    /* Blog posts render the primary nav only so the mobile drawer (burger) has it; on desktop the
-       article spans the full width, so hide the left sidebar here. */
-    .md-main__inner:has(.md-content--blog) .md-sidebar--primary {
-        display: none;
-    }
-    /* No left sidebar → drop the full-height vertical divider drawn at left:280px. Applies to blog
-       posts and to any page that hides the nav (e.g. /terms, /privacy → .md-sidebar--primary[hidden]). */
-    body:has(.md-content--blog)::before,
+    /* Pages that hide the nav entirely (/terms, /privacy → .md-sidebar--primary[hidden]) have no
+       left sidebar, so drop the full-height vertical divider drawn at left:280px. */
     body:has(.md-sidebar--primary[hidden])::before {
         display: none;
     }

mkdocs/blog/posts/state-of-cloud-gpu-2025.md

@@ -4,8 +4,8 @@ date: 2025-09-10
 description: "TBA"
 slug: state-of-cloud-gpu-2025
 image: https://dstack.ai/static-assets/static-assets/images/cloud-gpu-providers.png
-# categories:
-#   - Benchmarks
+categories:
+  - Reports
 ---
 
 # The state of cloud GPUs in 2025: costs, performance, playbooks

mkdocs/blog/posts/state-of-heterogeneous-compute-2026.md

@@ -4,14 +4,16 @@ date: 2026-06-23
 description: "How supply, software readiness, orchestration, and networking shape accelerator choices across NVIDIA, AMD, TPUs, Trainium, and specialized inference systems."
 slug: state-of-heterogeneous-compute-2026
 image: https://dstack.ai/static-assets/static-assets/images/state-of-heterogeneous-compute-2026.png
-# categories:
-#   - Benchmarks
+categories:
+  - Reports
 ---
 
 # The state of heterogeneous AI compute in 2026
 
 Heterogeneous AI compute is becoming harder to ignore. The reason is practical: supply pressure, pricing, and stack readiness are making more than one accelerator path worth evaluating.
 
+<img src="https://dstack.ai/static-assets/static-assets/images/state-of-heterogeneous-compute-2026.png" width="750"/>
+
 This report focuses on accelerator choices behind training and inference workloads: the main patterns, the evidence behind them, how readiness differs across NVIDIA, AMD, TPUs, Trainium, and specialized inference systems, and why orchestration and networking determine whether capacity can be used in practice.
 
 <!-- more -->
@@ -160,7 +162,7 @@ The open question is portability. Ethernet has momentum through [Spectrum-X](htt
 - **Software.** An accelerator path matters only if the model, framework, runtime, kernels, distributed training path, serving stack, containers, and debugging tools are ready enough for the workload.
 - **Orchestration.** Kubernetes and Slurm remain important, but heterogeneous compute needs a higher-level way to provision, place, and operate workloads across fragmented clouds, clusters, datacenters, and accelerator stacks without leaving platform teams to stitch every path together themselves.
 
-## Outside of the scope
+## Out of scope
 
 - Custom silicon controlled by individual hyperscalers or frontier labs. It matters as a supply signal because large buyers can reserve or build capacity outside the public accelerator market, but it is not a generally adoptable path for most teams.
 - Chinese accelerators, including Huawei Ascend and Cambricon. These may be important, especially in China, but comparable public data is limited and hard to verify from outside the region.

mkdocs/overrides/main.html

@@ -228,7 +228,7 @@
 {% endblock %}
 
 {% block announce %}
-<a href="/blog/agentic-orchestration/" target="_blank">Infrastructure orchestration is an agent skill<span class="icon"><svg viewBox="0 0 24 24" width="17" height="17" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M4 12h15"/><path d="m12.5 5.5 6.5 6.5-6.5 6.5"/></svg></span></a>
+<a href="/blog/state-of-heterogeneous-compute-2026/">The state of heterogeneous AI compute in 2026<span class="icon"><svg viewBox="0 0 24 24" width="17" height="17" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M4 12h15"/><path d="m12.5 5.5 6.5 6.5-6.5 6.5"/></svg></span></a>
 {% endblock %}
 
 {# Footer is rendered INSIDE .md-content (above, after the article) — NOT as a full-width sibling —

website/src/components/SiteBanner.tsx

@@ -3,8 +3,8 @@ import { BLOG_URL } from '../routes';
 // Top announcement banner, mirroring the one on the MkDocs docs site. It sits above the top
 // nav; the two stick to the top together (see .site-header). Update the copy/href here when
 // the announcement changes.
-const BANNER_TEXT = 'Infrastructure orchestration is an agent skill';
-const BANNER_HREF = `${BLOG_URL}/agentic-orchestration/`;
+const BANNER_TEXT = 'The state of heterogeneous AI compute in 2026';
+const BANNER_HREF = `${BLOG_URL}/state-of-heterogeneous-compute-2026/`;
 
 export function SiteBanner() {
   return (

website/src/components/SiteNavigation.tsx

@@ -14,12 +14,12 @@ const dstackGithubUrl = 'https://github.com/dstackai/dstack';
 const externalIconAriaLabel = 'External link icon';
 
 // Primary links in the desktop top navigation (plain same-origin MkDocs links). The blog
-// categories are listed individually (Case studies / Benchmarks / Blog) to mirror the docs
+// categories are listed individually (Case studies / Reports / Blog) to mirror the docs
 // header tabs — no "Resources" dropdown.
 const audienceNavItems: Array<{ label: string; href: string }> = [
   { label: 'Docs', href: DOCS_URL },
   { label: 'Case studies', href: `${BLOG_URL}/case-studies/` },
-  { label: 'Benchmarks', href: `${BLOG_URL}/benchmarks/` },
+  { label: 'Reports', href: `${BLOG_URL}/reports/` },
   { label: 'Blog', href: BLOG_URL },
 ];
 
@@ -46,7 +46,7 @@ const productDropdownItems: ButtonDropdownProps.Items = [
 const mobileNavigationItems: SideNavigationProps.Item[] = [
   { type: 'link', text: 'Docs', href: DOCS_URL },
   { type: 'link', text: 'Case studies', href: `${BLOG_URL}/case-studies/` },
-  { type: 'link', text: 'Benchmarks', href: `${BLOG_URL}/benchmarks/` },
+  { type: 'link', text: 'Reports', href: `${BLOG_URL}/reports/` },
   { type: 'link', text: 'Blog', href: BLOG_URL },
   { type: 'link', text: 'GitHub', href: dstackGithubUrl, external: true, externalIconAriaLabel },
   {