You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(blog): add AKS desktop bare-metal preview post - #6114
Add the approved AKS desktop v0.11.0 bare-metal preview story, following the final post and PR description from #5984.
Cover existing-cluster registration, automatic cluster connect, resource exploration, Projects and AI Assistant, and existing network and access boundaries without claiming cloud feature parity.
Include two same-folder screenshots with descriptive alt text, an accessible YouTube iframe and fallback link, and the final Learn short link.
Reuse will-case and existing tags. Preserve the approved narrative and title, normalize Microsoft Learn links to locale-neutral URLs, and place the truncation marker after the third introductory paragraph.
Validation
npm run typecheck passed.
npm run build passed with unrelated existing missing-truncation and broken-anchor warnings, plus Node.js localStorage experimental warnings.
Verified the draft route, title, video and screenshot references are absent from production HTML, feeds, sitemap, search data and JavaScript output.
Inspected the real Docusaurus development preview: one generated H1, correct author, both screenshots loaded, YouTube player displayed, fallback link present, and iframe title/fullscreen attributes rendered correctly. Playback itself was not tested.
Checked 375 px, 768 px and 1200 px local document viewports: no horizontal overflow; images and video fit the content area.
All 11 unique external URLs returned HTTP 200 after redirects. Both cluster-connect fragments exist; GitHub's issue-creation URL redirects to sign-in as expected.
Visually reviewed both screenshots: no visible credentials, subscription/tenant GUIDs, personal emails or customer-specific identifiers. Registration uses ContosoSubscription; cluster/resource names appear generic/demo-like. No redaction was applied.
Images are unchanged from the approved copies: registration 1098 x 627, 53,985 bytes; Map 1080 x 500, 163,639 bytes. Both satisfy the 1200 px / 500 KB limits.
Approved content remains within the 800-1500-word guideline (approximately 968 whitespace-separated tokens in the source, including Markdown/iframe markup).
Publication hold and review notes
Do not submit or publish yet. The post remains draft: true, excluded from production.
The folder and front-matter date, November 19, 2026, are preparation placeholders, not an approved publication schedule. Confirm and update the date/folder before eventual publication.
The approved 65-character title exceeds the under-60-character guideline. It is intentionally preserved for editorial review.
Reference PR metadata/body and its final merged post were available; review-thread feedback was not available. No further credential access was attempted after the earlier denial.
The reason will be displayed to describe this comment to others. Learn more.
🟡 Changes recommended
The new iframe violates the blog’s MD033 allowlist and will fail the separate Markdown lint check even for a draft post, which the reported build and typecheck do not cover.
The reason will be displayed to describe this comment to others. Learn more.
🔵 Needs a closer look
The YouTube iframe can contact YouTube even after a visitor rejects consent, bypassing the documented opt-in privacy behavior and requiring removal or explicit user-triggered loading.
Once published, this iframe can contact YouTube as it nears the viewport, even after a visitor selects Reject. The banner controls only GA4 (website/src/components/CookieConsent.tsx:19–29), so this player bypasses the opt-in privacy behavior documented in website/AGENTS.md:165–195; lazy loading does not prevent that. Keep only the existing walkthrough link, as suggested below, or create the iframe after an explicit load-video action.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
will-caseand existing tags. Preserve the approved narrative and title, normalize Microsoft Learn links to locale-neutral URLs, and place the truncation marker after the third introductory paragraph.Validation
npm run typecheckpassed.npm run buildpassed with unrelated existing missing-truncation and broken-anchor warnings, plus Node.js localStorage experimental warnings.ContosoSubscription; cluster/resource names appear generic/demo-like. No redaction was applied.Publication hold and review notes
draft: true, excluded from production.