All Projects → resolvetosavelives → healthicons

resolvetosavelives / healthicons

Licence: MIT License
A collection of open source icons for public health projects.

Programming Languages

typescript
32286 projects
SCSS
7915 projects
javascript
184084 projects - #8 most used programming language
CSS
56736 projects

Projects that are alternatives of or similar to healthicons

Papirus-Nord
Custom colors for folder icons for Papirus Icon Theme!
Stars: ✭ 61 (-83.6%)
Mutual labels:  icons
graphicon
A Vue.js plugin/component to help you manage your icons seamlessly
Stars: ✭ 12 (-96.77%)
Mutual labels:  icons
yaru-remix
My Novice approach for yaru-remix
Stars: ✭ 57 (-84.68%)
Mutual labels:  icons
fate
Browse FontAawesome icons from your shell
Stars: ✭ 26 (-93.01%)
Mutual labels:  icons
ember-add-to-homescreen
📲 "Add to Home Screen" prompt for mobile web Ember.js experiences
Stars: ✭ 23 (-93.82%)
Mutual labels:  icons
foundational-design-system-proto
A prototype for a foundational design system at Shopify
Stars: ✭ 82 (-77.96%)
Mutual labels:  icons
vscode-material-product-icons
Product Icon Theme with Material Icons for VS Code
Stars: ✭ 19 (-94.89%)
Mutual labels:  icons
map-machine
Python renderer for OpenStreetMap with custom icons intended to display as many map features as possible
Stars: ✭ 82 (-77.96%)
Mutual labels:  icons
haiku-icons
Haiku OS icons, exported to HVIF, SVG and PNG
Stars: ✭ 37 (-90.05%)
Mutual labels:  icons
MacAppIconSwitcher
Switches your Mac Application Icons
Stars: ✭ 18 (-95.16%)
Mutual labels:  icons
react-native-fontawesome-pro
Easily use your FontAwesome Pro icons in React-Native
Stars: ✭ 44 (-88.17%)
Mutual labels:  icons
vaadin-icons
Vaadin Icons is a collection of 600+ unique icons designed for web applications
Stars: ✭ 59 (-84.14%)
Mutual labels:  icons
vue-feather
Feather component for Vue.js.
Stars: ✭ 108 (-70.97%)
Mutual labels:  icons
font-apex
Font APEX is an open source icon library from the Oracle APEX team.
Stars: ✭ 85 (-77.15%)
Mutual labels:  icons
reiconify
Convert SVG icons to React components eg.: https://ambar.li/reiconify/md.icons/#/Browse
Stars: ✭ 17 (-95.43%)
Mutual labels:  icons
blade-zondicons
A package to easily make use of Zondicons in your Laravel Blade views.
Stars: ✭ 52 (-86.02%)
Mutual labels:  icons
numix-icon-theme-square
Linux packaging for Numix Square
Stars: ✭ 143 (-61.56%)
Mutual labels:  icons
Bitcoin-Icons
Icons made for Bitcoin applications, free to use.
Stars: ✭ 52 (-86.02%)
Mutual labels:  icons
vue-icon
Maybe it is the smallest vue component that contains all the feather icons
Stars: ✭ 44 (-88.17%)
Mutual labels:  icons
social-logos
A repository of all the social logos we use on WordPress.com
Stars: ✭ 110 (-70.43%)
Mutual labels:  icons

Health Icons Promo Graphic

Health Icons: healthicons.org

Free, open source health icons available for any use

Use for your next commercial or personal project. You don’t need to give credit and you can edit the icons however you want.

Usage

Health Icons is a volunteer effort to create a 'global good' for health projects all over the world. These icons are available in the public domain for use in any type of project.

The project is hosted by the public health not-for-profit Resolve to Save Lives as an expression of our committment to offer the icons for free, forever.

Accessing Icons

Icons are available in several formats and in a few ways:

  • All icons are produced in "outline", "filled", and "negative" styles
  • Each icon is available in SVG and in PNG (48px and 96px)
  • Icons can be downloaded individually via our website, downloaded together in a ZIP file, or accessed under the public/icons folder in this GitHub project.

Icon Requests

Need an icon for your project? Submit a request with an Issue on GitHub using the title "Icon Request: [name of icon]" and we will do our best to respond.

How to contribute

We’d love for you to join our team of volunteer designers and developers!

Get in touch

Join our open Slack channel by emailing [email protected]

Contribute icons

Browse the Figma and contribute icons in the "New icons" section. Please read the code of conduct (below) and the styleguide (in the Figma) carefully before contributing.

Icon Guidelines

Icon Title and Tags in Figma

Each icon should have a title and tags which are added in the “Description” field in Figma. The format is: {title} [{tag1}, {tag2}, {tag3}…, dhis2:{tag}]

Some examples:

donkey icon:
Donkey [Animal, Ass, Farm, Mule, dhis2:donkey]

blood_rh_p icon:
Blood Type RH+ [Blood, RH Positive, dhis2:blood_rh_p]

More details:

  • The “Description” only needs to go on the “filled” version of the icon in Figma
  • Icon titles should be in Title Case with each word capitalized
  • Tags are essentially synonyms or important related words that would help someone find the icon. They could also be alternative uses of the icon, the way a donkey could represent “farm”. If someone searches “blood” or “positive” they’ll see any icons that are tagged with those words. Tags should also be Title Case.
  • The dhis2: formatted tag is a special tag reserved for icons that are in the DHIS2 icon set. This tag should exactly match whatever DHIS2 names this icon.

Code of Conduct

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others’ private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available here. For answers to common questions about this code of conduct, see this FAQ.

Installing and running the website locally

This project uses Next.js.

  1. Check out the repo locally
  2. Run yarn install
  3. Run yarn dev

Importing the latest icon information from Figma

To pull the latest icon information from Figma, update the open-graph images, and update the sitemap.xml:

  1. Copy .env.example to .env.local
  2. Go to your account settings on figma.com and generate a new access token under "Personal access tokens" and copy it to your clipboard.
  3. In .env.local, add FIGMA_PERSONAL_ACCESS_TOKEN="{token-goes-here}"
  4. Run yarn update-icons
  5. If you're committing to a branch on git, make sure to remember to add the newly generated files in the /public/ directory.

MIT License

Copyright © 2021 Resolve to Save Lives

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].