https://github.com/cemwebdev/piconss
A developer focused icon library
https://github.com/cemwebdev/piconss
frontend-library icons javascript
Last synced: 11 months ago
JSON representation
A developer focused icon library
- Host: GitHub
- URL: https://github.com/cemwebdev/piconss
- Owner: CemWebDev
- License: mit
- Created: 2024-10-11T16:03:41.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-11-22T18:21:02.000Z (over 1 year ago)
- Last Synced: 2025-04-04T16:42:33.289Z (12 months ago)
- Topics: frontend-library, icons, javascript
- Language: JavaScript
- Homepage: https://cemwebdev.github.io/piconss/
- Size: 291 KB
- Stars: 6
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# piconss
### A collection of customizable SVG icons for dark, light and default.
## Table of contents
- [Installation](#installation)
- [Usage](#usage)
- [Available Icons](#available-icons)
- [Contributing](#contributing)
## Installation
You can access piconss icons via **unpkg** or use them locally by cloning the repository.
You can use piconss directly in your HTML or JavaScript applications without any installation:
```html
```
## Usage
You can customize the icons using different themes. Currently, the available themes are:
`default`
`light`
`dark`
To use a specific icon, just provide the correct path as shown below:
```html
```
## Using with unpkg
Add the following link to your HTML or MD file to use icons from unpkg:
```html
```
## Available Icons
Below is a list of all available icons in the piconss library:
| Icon Name | Icon Image |
| -------------- | ------------------------------------------------------------------------------------- |
| `angularjs` | 
|
| `aws` | 
|
| `azure` | 
|
| `babel` | 
|
| `blender` | 
|
| `bootstrap` | 
|
| `c` | 
|
| `clion` | 
|
| `cpp` | 
|
| `csharp` | 
|
| `css3` | 
|
| `dart` | 
|
| `django` | 
|
| `docker` | 
|
| `dotnet` | 
|
| `electron` | 
|
| `expressDark` | 
|
| `expressLight` | 
|
| `figma` | 
|
| `firebase` | 
|
| `flask` | 
|
| `flutter` | 
|
| `gatsby` | 
|
| `git` | 
|
| `github` | 
|
| `go` | 
|
| `graphql` | 
|
| `haskell` | 
|
| `html5` | 
|
| `intellij` | 
|
| `java` | 
|
| `javascript` | 
|
| `jenkins` | 
|
| `jest` | 
|
| `jira` | 
|
| `jquery` | 
|
| `julia` | 
|
| `jupyter` | 
|
| `kotlin` | 
|
| `less` | 
|
| `linux` | 
|
| `markdown` | 
|
| `matlab` | 
|
| `mocha` | 
|
| `mongodb` | 
|
| `mysql` | 
|
| `nextjs` | 
|
| `nodejs` | 
|
| `numpy` | 
|
| `nuxtjs` | 
|
| `opencv` | 
|
| `perl` | 
|
| `php` | 
|
| `postcss` | 
|
| `postgresql` | 
|
| `postman` | 
|
| `prettier` | 
|
| `prisma` | 
|
| `pycharm` | 
|
| `python` | 
|
| `pytorch` | 
|
| `r` | 
|
| `reactjs` | 
|
| `reactrouter` | 
|
| `redux` | 
|
| `ruby` | 
|
| `rust` | 
|
| `sass` | 
|
| `scala` | 
|
| `sketch` | 
|
| `sqlite` | 
|
| `svelte` | 
|
| `swift` | 
|
| `tailwindcss` | 
|
| `tensorflow` | 
|
| `threejsDark` | 
|
| `threejsLight` | 
|
| `typescript` | 
|
| `unity` | 
|
| `unrealengine` | 
|
| `vscode` | 
|
| `vuejs` | 
|
| `webstorm` | 
|
## Contributing
We appreciate your contributions to piconss! To contribute, follow these steps:
1. **Fork the repository:**
Go to the [piconss repository](https://github.com/CemWebDev/piconss) and click the "Fork" button.
2. **Clone your fork:**
After forking, clone the repository to your local machine using the following command:
```bash
git clone https://github.com/your-username/piconss.git
```
3. **Create a new branch** Create a new branch where you can make your changes. Use a descriptive branch name:
```bash
git checkout -b my-new-feature
```
4. **Make your changes** Make the necessary changes or additions to the icons or code.
5. **Commit your changes** After making your changes, commit them with a clear and concise message:
```bash
git add .
git commit -m "Add new icon for xyz"
```
6. **Push to your fork:** Push your changes to the branch on your fork:
```bash
git push origin my-new-feature
```
7. **Submit a pull request:** Go back to the original repository and create a pull request from your branch. Be sure to provide a clear explanation of the changes you've made.