Skip to content

fix: use the ShellUI logo as the NuGet package icon - #43

Merged
Shewart merged 2 commits into
mainfrom
fix/package-icon
Oct 9, 2026
Merged

Shewart merged 2 commits into
mainfrom
fix/package-icon

Conversation

@Shewart

@Shewart Shewart commented Oct 9, 2026

Copy link
Copy Markdown
Contributor

Neither package set PackageIcon, so nuget.org showed the default icon for ShellUI.CLI and ShellUI.Components. src/ShellUI.Components/icon.svg was an unused placeholder.

  • assets/icon.png is the ShellUI >| dot mark on a dark rounded tile, 256 px, which reads on nuget.org's light and dark themes
  • Directory.Build.props sets it as PackageIcon and packs it once for both packages
  • assets/icon.svg is kept as the source
  • src/ShellUI.Components/icon.svg is removed

Both packages now ship icon.png with <icon>icon.png</icon> in the nuspec.

Shewatipa Tseisi added 2 commits October 6, 2026 10:23
Neither package set PackageIcon, so nuget.org showed the default icon, and src/ShellUI.Components/icon.svg was an unused placeholder. assets/icon.png (the dot mark on a dark tile) is now the icon of ShellUI.CLI and ShellUI.Components, with assets/icon.svg as its source.
nuget.org renders Markdown only and accepts images from raw.githubusercontent.com. assets/readme-logo.svg is the brand tile at 64 px (ink on light, paper on dark), drawn with md-files brand/generate.py; it shows once this branch is on main.
Copilot AI balanced review requested due to automatic review settings October 9, 2026 18:14

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@Shewart
Shewart merged commit 99d30a5 into main Oct 9, 2026
1 check passed
@Shewart
Shewart deleted the fix/package-icon branch October 9, 2026 18:18
Shewart added a commit that referenced this pull request Oct 13, 2026
Release notes and version references for 0.4.0-alpha.2.

**In this release** (already on main):
- #48: the Tailwind CLI is downloaded once per machine and run from
there, so projects hold no binary; downloads survive slow connections;
`init` carries on if the download fails; `.shellui/` is git-ignored;
`update` moves older projects onto the shared CLI
- #46: `update` installs new dependencies and keeps files you changed
(`--force` to overwrite); `remove` finds layouts and custom paths; the
package `TimePicker` value fix; `color-scheme` for light and dark
- #44: `shellui-theme.css` no longer 404s when linked directly
- #43: NuGet package icon and README logo

**This PR**
- `Directory.Build.props`: suffix `alpha.2`
- Docs name stable `0.3.4` and prerelease `0.4.0-alpha.2` (README,
VERSIONING_STRATEGY, CLI_INSTALLATION, CLI_SYNTAX, FAQ, QUICKSTART);
stable-docs links point to `v0.3.4`
- The version fallbacks in `VersionHelper` and `ComponentMetadata`
(still `0.3.0` on main) are now `0.4.0-alpha.2`
- `docs/RELEASE_NOTES.md`: the 0.4.0-alpha.2 section, plus the 0.3.4 and
0.3.3 sections from `release/v0.3`; `scripts/extract-release-notes.sh
0.4.0-alpha.2` extracts it

**Release checks** (on `9c7cfac` plus this commit)
- Release build has 0 warnings, and all 334 tests pass
- A 0.3.4 project updated with the packed alpha.2 CLI: targets
refreshed, the 112 MB project copy of Tailwind removed, 54 components
updated, the edited `AppSidebar` kept, 5 new dependencies installed,
builds 0/0
- A fresh Identity app, `init --yes --dashboard 02` then `add auth-01
data-table chat qr-code time-picker`: uses the shared Tailwind CLI and
builds 0/0; `.shellui` holds only its `.gitignore`
- All 93 direct targets together in `my-app` build 0/0 on net8.0, net9.0
and net10.0, with no project copies of the CLI
- The packed `ShellUI.Components` in a browser: `window.ShellUI` loads,
TimePicker shows its value, dark mode sets `color-scheme` (including the
native date input), Popover closes on Escape, Command runs `Action` then
`CommandSelected`, no console errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants