Skip to content

chore: move the docs site to shellui-dev/shell-icons-docs - #12

Open
Shewart wants to merge 1 commit into
mainfrom
chore/move-docs-to-own-repo
Open

Shewart wants to merge 1 commit into
mainfrom
chore/move-docs-to-own-repo

Conversation

@Shewart

@Shewart Shewart commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Docs site moved to its own repo

  • New home: the docs site now lives in shellui-dev/shell-icons-docs, with the history of docs/ShellIcons.Docs carried over (git subtree split).
  • Built from released packages: it uses the published ShellIcons.Blazor package instead of a project reference, so the docs always show a released version.
  • Deploys from there: that repo builds a Docker image on every PR and pushes docker.zuluville.com/shell-icons-docs on merge, with its registry secrets kept in that repo only.

Removed here

  • docs/ShellIcons.Docs and its entry in ShellIcons.slnx.
  • .github/workflows/docs.yml, the GitHub Pages deploy; the site is served as a container now.
  • README and RELEASING now point to the new repo.

Breaking changes

None for the packages.

Test plan

  • ShellIcons.slnx builds with 0 warnings; 135 tests pass (57 generator, 44 Blazor, 34 Avalonia)
  • The new repo builds with 0 warnings on ShellIcons.Blazor 0.2.0-alpha; published and run in Production, all 18 pages and their .md versions return 200, llms.txt, agent files and search serve, unknown pages return 404, the icon browser lists 1,555 icons
  • First image workflow run in shell-icons-docs (needs REGISTRY_USERNAME / REGISTRY_PASSWORD secrets to push)

Follow-ups

  • Add the registry secrets to shell-icons-docs, then let it push the image; redeploy on the server
  • Optionally a Portainer webhook so merges redeploy automatically

The site now lives in its own repo with its history, uses the published ShellIcons.Blazor package, and deploys as a container from there, so its deployment secrets stay out of this repo. Removes docs/ShellIcons.Docs, the GitHub Pages workflow and the solution entry; README and RELEASING point to the new repo.

This branch has not been deployed

No deployments
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.

1 participant