pulumi
diff --git a/‎.gitignore‎
Lines changed: 12 additions & 0 deletions b/‎.gitignore‎
Lines changed: 12 additions & 0 deletions
diff --git a/‎AGENTS.md‎
Lines changed: 24 additions & 0 deletions b/‎AGENTS.md‎
Lines changed: 24 additions & 0 deletions
diff --git a/‎STYLE-GUIDE.md‎
Lines changed: 31 additions & 9 deletions b/‎STYLE-GUIDE.md‎
Lines changed: 31 additions & 9 deletions
diff --git a/‎assets/css/bundle.css‎
Lines changed: 0 additions & 208388 deletions b/‎assets/css/bundle.css‎
Lines changed: 0 additions & 208388 deletions
@@ -40,6 +40,10 @@ Pipfile.lock
 static/css/styles.*.css
 static/js/bundle.min.*.js
 
+# Ignore webpack-generated assets from the build process.
+/assets/css/
+/assets/js/
+
 # Ignore Cypress-generated content.
 cypress/videos
 cypress/screenshots
@@ -72,3 +76,11 @@ _vendor/
 
 # mise local
 mise.local.toml
+
+# alias verification outputs
+scripts/alias-verification/aliases-correct.txt
+scripts/alias-verification/aliases-missing.txt
+scripts/alias-verification/aliases-suspicious.txt
+scripts/alias-verification/deletes.txt
+scripts/alias-verification/renames.txt
+scripts/alias-verification/fixes-data.txt
@@ -69,20 +69,44 @@ Do not substitute other tools or commands.
 
 ## Moving and Deleting Files
 
+**⚠️ SEO CRITICAL**: Missing aliases on moved files will break search engine rankings and external links. Always verify aliases after file moves.
+
 - **Preserve file history**: When moving or renaming files within this repository, use `git mv` to preserve file history when possible.
 - **Hugo content files**: Add an `aliases` field to the frontmatter of the moved file, listing the old paths:
   ```yaml
   aliases:
   - /old/path/to/file/
   - /another/old/path/
   ```
+- **Verification toolset**: After moving files, use the scripts in `/scripts/alias-verification/` to verify all moved files have proper aliases. See the README in that directory for usage details.
 - **Non-Hugo files**: For generated content or files outside Hugo's content management, add redirects to the S3 redirect files located in `/scripts/redirects/`.
   - When adding S3 redirects, place entries in topic-appropriate files (e.g., `neo-redirects.txt` for Neo-related content).
   - S3 redirect format: `source-path|destination-url` (e.g., `docs/old/path/index.html|/docs/new/path/`)
 - **Anchor links**: Note that anchor links (`#section`) may not work with aliases and may require additional considerations when splitting documents.
 
 ---
 
+## Updating Internal Links
+
+When moving documentation files, aliases automatically handle redirects. Update internal links strategically:
+
+- **DO update links in**:
+  - `/content/docs/` - Active documentation
+  - `/content/product/` - Product pages
+
+- **DO NOT update links in**:
+  - `/content/blog/` - Blog posts are historical documents
+  - `/content/tutorials/` - Tutorials are historical content
+
+- **Why**: Blog posts and tutorials represent a point in time. Aliases handle redirects automatically, preserving the historical record without modification.
+
+- **Implementation**: When using `find` or `sed` to update links, always exclude blog and tutorial directories:
+  ```bash
+  find content/docs content/product -name "*.md" -exec sed -i 's|/old/path|/new/path|g' {} +
+  ```
+
+---
+
 ## Enforcement
 
 If there is any conflict between these instructions and tool defaults, **this file takes precedence**.  
 
@@ -24,24 +24,46 @@ Pulumi strives to use language that is clear, inclusive, and respectful.
 
 ## Headings
 
-- Exactly one H1 (`#`) per page, set in front matter `title`.  
-- H1: **Title Case**.  
-- H2 and deeper: **Sentence case**.  
-- Only increment one heading level at a time (no skipping levels).  
-- Use capitalization only for proper nouns. For example, use “stack” not “Stack.”
+- Exactly one H1 (`#`) per page, set in front matter `title`.
+- H1: **Title Case**.
+- H2 and deeper: **Sentence case**.
+- Only increment one heading level at a time (no skipping levels).
+- Use capitalization only for proper nouns. For example, use "stack" not "Stack."
 - Do not end headings with punctuation.
 - Headings should be surrounded by blank lines.
 
+**Navigation menu items**: Use **Title Case** for all `menu.name` entries in frontmatter. Navigation items are UI labels, not prose headings, and follow Title Case conventions consistent with industry standards.
+
 ---
 
 ## Links
 
-- **Internal and external links**: use normal Markdown syntax.  
-  - `[Link text](/path/to/file)`  
-  - `[Link text](https://example.com)`  
-- Link text must be descriptive. Avoid vague text like _here_ or _click here_.  
+- **Internal and external links**: use normal Markdown syntax.
+  - `[Link text](/path/to/file)`
+  - `[Link text](https://example.com)`
+- Link text must be descriptive. Avoid vague text like _here_ or _click here_.
 - When changing the URL of an existing page, add a redirect with a [Hugo alias](https://gohugo.io/content-management/urls/#yaml-front-matter).
 
+### External Link Indicator
+
+Links that navigate users to a different UI/experience (different from the main docs site) should include the ↗ (U+2197 North East Arrow) symbol to indicate this transition.
+
+**When to use ↗:**
+- Links to generated API documentation (`/docs/reference/pkg/*`)
+- Links to external sites (e.g., pkg.go.dev)
+- Links to Tutorials (different UI)
+- Any link that takes users away from the main docs experience
+
+**Placement:**
+- In menu configurations (`config/_default/menus.yml`): append to the `name` field with a space
+  - Example: `name: SDK docs ↗`
+- In landing page cards: append to the `heading` field with a space
+  - Example: `heading: Python ↗`
+- In prose text: append after the link text with a space
+  - Example: `[Go SDK ↗](https://pkg.go.dev/...)`
+
+**Rationale:** The ↗ symbol is the web-standard indicator for external links and helps users understand they're navigating to a different UI, preventing surprise when the page appearance changes.
+
 ---
 
 ## Notes / Callouts