Add icon set metadata manifests#37
Conversation
Establish machine-readable descriptions and accepted/rejected metaphors for micron icons so AI tools can select the correct on-brand icon.
|
✅ Deploy Preview for red-hat-icons ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Keep a single root-level index file instead of a manifests directory, per icon metadata layout guidance.
Keep a root icons.yaml that describes each set and points to per-set manifests under src/, starting with curated microns metadata. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Tracking issue for this work is now #38 (moved from design-skills#25). Skills stay out of scope here. |
coreyvickery
left a comment
coreyvickery
left a comment
There was a problem hiding this comment.
@marionnegp Done with my review.
…tion Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
These files will need to be exported in package.json so they are included in the package and get versioned with releases. This way, an agent could access them via node_modules and read the content, which may differ per version. I'll add a Suggestion comment on package.json with the necessary format.
On second thought, we are also going to need a build process (in build.ts) to copy them into the generated set folders, e.g., ./microns that gets created. Then the exports in package.json will just work given the glob exports/*
When you have the file names finalized, let me know, and I can do this part.
github-project-automation
Bot
moved this from In Progress 🟢
to Review 🔍
in Red Hat Design System
…tadata.yaml Co-authored-by: Cursor <cursoragent@cursor.com>
coreyvickery
changed the title
… paths Co-authored-by: Cursor <cursoragent@cursor.com>
coreyvickery
left a comment
coreyvickery
left a comment
There was a problem hiding this comment.
My review part 2.
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
|
@coreyvickery I made a few small changes in addition to removing the Figma-only icons. Any icons listed in the YAML should be available/shipped. If they're in Figma-only, then we'd want to include them in the release (as we update the YAML) and make them available anyway. |
4 participants
Part of #38
Summary
icon-sets.yamlat the repo root as the index for all icon sets (use cases, size ranges, manifest paths)src/microns/metadata.yamlwith curated per-icon descriptions, accepted uses, and rejected usesmetadata.yamlfiles forui,standard, andsocialsets, pending curationicon-sets.yaml; per-set manifests aresrc/<set>/metadata.yamlStructure follows the agreed layout: one root index YAML, then one per-set manifest beside the SVG sources under
src/<set>/. Skills stay out of this repo and can point at these manifests.Test plan
src/<set>/metadata.yaml) are the naming we want