-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Closed
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationin-developThe fix/feature is present in `develop` branch but not merged into `master` yetThe fix/feature is present in `develop` branch but not merged into `master` yet
Description
I have searched through the issues and didn't find my problem.
- Confirm
What would you like to share?
It would be nice if there was a stricter format on the icon requests. So the icon_request.yml issue template should be updated.
Imo we should add some more required and encouraged fields to fill in:
Required:
- Link to resources (website, github, npm, etc..) (Examples: https://github.com/sveltejs , https://svelte.dev/ , https://www.npmjs.com/package/svelte)
- Link to icons. Official icons should be linked regardless of type, and unofficial if SVG's aren't available from the official ones. (Example: https://github.com/sveltejs/branding)
- Preview of the most important icons (Example:
)
Encouraged:
- List of related tags/categories that the tool falls under (Example:
programming,language) - Alternative names (Example:
go,golang) - Main/primary color. Especially important if the color should be different than the most dominant color in the icons. For example, some tools might have a different primary color than the one most prevalent in the icons. (Example:
#2fff2f)
Additional information
No response
Panquesito7 and lunatic-fox
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentationin-developThe fix/feature is present in `develop` branch but not merged into `master` yetThe fix/feature is present in `develop` branch but not merged into `master` yet