Designing new icons for EOS-icons
If you are sending a new icon to EOS-icons, please make sure your SVG is compliant to all the rules defined at:
Code contributions to EOS-icons
If you are about to open a PR in EOS-icons, please make sure you read the following instructions that will give you the overview you need to understand the project in depth:
https://gitlab.com/SUSE-UIUX/eos-icons/wikis/How-to-contribute-to-EOS-icons
Conventions and rules for JS, CSS, and others:
Javascript conventions we follow at EOS:
- https://gitlab.com/SUSE-UIUX/eos/wikis/Writing-standard-JS-code
- https://standardjs.com/rules.html
- https://gitlab.com/SUSE-UIUX/eos/wikis/code-commenting-standards
CSS conventions:
- https://gitlab.com/SUSE-UIUX/eos/wikis/Writing-standard-scss-code
- https://gitlab.com/SUSE-UIUX/eos/wikis/SCSS-structure
- https://gitlab.com/SUSE-UIUX/eos/wikis/code-commenting-standards
How to name your branches:
Investigations and team decisions
Semantic releases [only for core team members / upstream]
Here are the rules to follow for release purposes: Guidelines
Important
When we release it is necessary to purge the CDN cache so that anyone using the CDN with @Latest or without any specific version doesn't have any conflict getting the new icons when we release. The endpoint is:
https://purge.jsdelivr.net/npm/eos-icons@latest/dist/css/eos-icons-outlined.css https://purge.jsdelivr.net/npm/eos-icons@latest/dist/css/eos-icons.css
Migrations guidelines
Changelog for a smooth migration to v4