Centralize Azure Local repo logos and icons in platform

[kristopherjturner]

Summary

Collect the primary logos, icons, banners, favicons, and social-card assets from the Azure Local repositories and copy them into a non-docs asset folder in the platform repository for internal branding/reference use.

Why

Brand assets are currently scattered across individual repositories, most commonly under docs-specific paths such as docs/assets/images, public, or static/img. That makes it hard to find and reuse the current canonical repo visuals when working on portfolio-wide platform tasks.

These assets should live in platform, but not under /docs, because this is an internal source-of-truth and should not be published with the documentation site.

Proposed Approach

Create a root-level folder in platform dedicated to shared brand assets, for example:

• branding/
• or assets/branding/

My recommendation is branding/ at the repository root because it is explicit, easy to discover, and clearly separate from published docs content.

Within that folder, organize assets by repository, for example:

• branding/azurelocal-avd/
• branding/azurelocal-sofs-fslogix/
• branding/azurelocal-loadtools/
• branding/azurelocal-vm-conversion-toolkit/
• branding/azurelocal-copilot/
• branding/azurelocal-training/
• branding/azurelocal-nutanix-migration/
• branding/azurelocal-ranger/
• branding/azurelocal-s2d-cartographer/
• branding/azurelocal.github.io/
• branding/azurelocal-surveyor/
• branding/azurelocal-toolkit/
• branding/platform/
• branding/demo-repository/

Scope

• Inventory repo logos, icons, banners, favicons, and social-card images across the Azure Local repositories
• Copy the relevant assets into a non-docs folder in platform
• Use a consistent naming convention and folder structure
• Add a short internal README describing the source repo and intended asset type if helpful
• Do not move publication paths in the source repos as part of this issue unless a follow-up issue requires it

Current State

Examples already found:

• Many repos store primary brand assets in docs/assets/images/*-icon.svg and docs/assets/images/*-banner.svg
• azurelocal.github.io stores site assets under static/img/ including favicon and social-card files
• azurelocal-surveyor includes a public/favicon.svg

Acceptance Criteria

• platform contains a new root-level non-docs branding folder
• The folder includes the primary logo/icon assets for each Azure Local repo
• Repo assets are grouped consistently by repository
• The destination is outside /docs
• The structure is clear enough to support future reuse for social cards, internal presentations, and repo branding work
• Any intentionally missing assets are documented

Notes

This issue is about centralizing copies of assets in platform, not changing how individual repos currently publish or reference their own assets.