GithubHelp home page GithubHelp logo

simple-icons / simple-icons-website Goto Github PK

View Code? Open in Web Editor NEW
248.0 248.0 25.0 5.01 MB

The website for Simple Icons: SVG icons for popular brands

Home Page: https://simpleicons.org

License: Creative Commons Zero v1.0 Universal

Pug 24.63% JavaScript 60.37% CSS 14.73% Shell 0.04% Dockerfile 0.23%
icons icons-website website

simple-icons-website's Introduction

Simple Icons

Simple Icons

Over 3100 Free SVG icons for popular brands. See them all on one page at SimpleIcons.org. Contributions, corrections & requests can be made on GitHub.

Build status NPM version Build status
Number of icons currently in the library Number of users active in our Discord server Backers and sponsors on Open Collective

Usage

Important

We ask that all users read our legal disclaimer before using icons from Simple Icons.

General Usage

Icons can be downloaded as SVGs directly from our website - simply click the download button of the icon you want, and the download will start automatically.

CDN Usage

Icons can be served from a CDN such as jsDelivr or Unpkg. Simply use the simple-icons npm package and specify a version in the URL like the following:

<img height="32" width="32" src="https://cdn.jsdelivr.net/npm/simple-icons@v11/icons/[ICON SLUG].svg" />
<img height="32" width="32" src="https://unpkg.com/simple-icons@v11/icons/[ICON SLUG].svg" />

Where [ICON SLUG] is replaced by the slug of the icon you want to use, for example:

<img height="32" width="32" src="https://cdn.jsdelivr.net/npm/simple-icons@v11/icons/simpleicons.svg" />
<img height="32" width="32" src="https://unpkg.com/simple-icons@v11/icons/simpleicons.svg" />

These examples use the latest major version. This means you won't receive any updates following the next major release. You can use @latest instead to receive updates indefinitely. However, this will result in a 404 error if the icon is removed.

CDN with colors

We also provide a CDN service which allows you to use colors.

<img height="32" width="32" src="https://cdn.simpleicons.org/[ICON SLUG]" />
<img height="32" width="32" src="https://cdn.simpleicons.org/[ICON SLUG]/[COLOR]" />
<img height="32" width="32" src="https://cdn.simpleicons.org/[ICON SLUG]/[COLOR]/[DARK_MODE_COLOR]" />

Where [COLOR] is optional, and can be replaced by the hex colors or CSS keywords of the icon you want to you use. The color is defaulted to the HEX color of the icon shown in simpleicons.org website. [DARK_MODE_COLOR] is used for dark mode. The CSS prefers-color-scheme will be used when a value is specified. For example:

<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/gray" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/hotpink" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/0cf" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/0cf9" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/00ccff" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/00ccff99" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/orange/pink" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/_/eee" />
<img height="32" width="32" src="https://cdn.simpleicons.org/simpleicons/eee/_" />

Node Usage Node

The icons are also available through our npm package. To install, simply run:

npm install simple-icons

All icons are imported from a single file, where [ICON SLUG] is replaced by a capitalized slug. We highly recommend using a bundler that can tree shake such as webpack to remove the unused icon code:

// Import a specific icon by its slug as:
// import { si[ICON SLUG] } from 'simple-icons'

// For example:
// use import/esm to allow tree shaking
import { siSimpleicons } from 'simple-icons';
// or with require/cjs
const { siSimpleicons } = require('simple-icons');

It will return an icon object:

console.log(siSimpleicons);

/*
{
    title: 'Simple Icons',
    slug: 'simpleicons',
    hex: '111111',
    source: 'https://simpleicons.org/',
    svg: '<svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">...</svg>',
    path: 'M12 12v-1.5c-2.484 ...',
    guidelines: 'https://simpleicons.org/styleguide',
    license: {
        type: '...',
        url: 'https://example.com/'
    }
}

NOTE: the `guidelines` entry will be `undefined` if we do not yet have guidelines for the icon.
NOTE: the `license` entry will be `undefined` if we do not yet have license data for the icon.
*/

If you need to iterate over all icons, use:

import * as icons from 'simple-icons';

TypeScript Usage Typescript

Type definitions are bundled with the package.

import type { SimpleIcon } from 'simple-icons';

PHP Usage Php

The icons are also available through our Packagist package. To install, simply run:

composer require simple-icons/simple-icons

The package can then be used as follows, where [ICON SLUG] is replaced by a slug:

<?php
// Import a specific icon by its slug as:
echo file_get_contents('path/to/package/icons/[ICON SLUG].svg');

// For example:
echo file_get_contents('path/to/package/icons/simpleicons.svg');

// <svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">...</svg>
?>

Third-Party Extensions

Extension Author License Simple Icons Version
Angular module Angular @avmaisak v6.18.0
Blazor Nuget package Blazor @TimeWarpEngineering
Blender add-on Blender @mondeja
Drawio library Drawio @mondeja
Drupal module Drupal Phil Wolstenholme
Figma plugin Figma @LitoMore
Flutter package Flutter @jlnrrg
Framer component Framer @LitoMore
Hexo plugin Hexo @nidbCN
Home Assistant plugin Home Assistant @vigonotion v7.14.0
Hugo module Hugo @foo-dogsquared
Java library OpenJDK @silentsoft
Jetpack Compose library Jetpack Compose @DevSrSouza v4.14.0
Kirby plugin Kirby @runxel
LaTeX package LaTeX @ineshbose
Laravel package Laravel @adrian-ub
Leptos crate Leptos @Carlosted v9.14.0
Miro app Miro @LitoMore
Python package Python @sachinraja v7.21.0
Raycast extension Raycast @LitoMore
React package React @wootsbot
Ruby gem Ruby @thepew
Solid package Solid @x64Bits v9.0.0
Stream Deck icon pack Stream Deck @mackenly
Svelte package Svelte @wootsbot
Vue 3 package Vue @wyatt-herkamp
Vue package Vue @noahlitvin
Webflow app Webflow @diegoliv
WordPress plugin WordPress @tjtaylo v4.25.0

Important

From our next scheduled major release (v12, releasing on May 26, 2024), we will begin removing third-party extensions from the above list that are not up to date with at least our previous major release.
For example, when v12 is released, we will remove any extensions that don't support v11.0.0 or higher.
Please create a PR to update the version number of your extension in this README following each update of your extension.

Contribute

Information describing how to contribute can be found in the file CONTRIBUTING.md

Contributors

simple-icons-website's People

Contributors

actions-user avatar andre601 avatar andygol avatar anilseervi avatar dependabot[bot] avatar developstorm avatar dylvaz avatar ericcornelissen avatar github-actions[bot] avatar jorgeamadosoria avatar litomore avatar mondeja avatar ms0503 avatar oneminch avatar petershaggynoble avatar priyansh32 avatar renovate[bot] avatar sachinraja avatar sh-cho avatar simple-icons[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

simple-icons-website's Issues

Lazy load icons on website

Kind of issue

  • Improvement
  • Bug
  • Other, namely:

This issue concerns

  • The NPM Package
  • The Packagist Package
  • The website
  • Other, namely:

Description

With over a 1000 icons I think it might be a good idea to implement the lazy loading of icons on the website. That is, when the page is first loaded we load a limited amount of icons (say 250) and when the user scrolls down we (gradually?) load more icons.

Some things to keep in mind/that should be tested thoroughly:

  • How will this work with the different sorting methods (colour vs. alphabetical)
  • How will this work with searching
  • More...?

Add link pointing to simple-icons-website repository

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

I miss a link that takes you to the web repository (this repository), as long as it does not confuse with the main repository. Do you see it too meta? Maybe it could be "hidden" at the end, like the Twitter share button ... ๐Ÿค”

Update grid item layout

Kind of issue

  • Improvement
  • Design
  • Bug
  • Other, namely:

Description

This issue tracks various suggestions for redesign to grid items. Other suggestions can be provided as comment here or as a separate issue.

  • As per this comment (and more feedback): move or remove the logo in the background of grid items.
  • As per this comment: make the color more prominent in grid items.
  • As per this comment: reduce the size of grid items as much as possible (even if #17 is added).

Improve website search

Kind of issue

  • Improvement
  • Bug
  • Other, namely:

This issue concerns

  • The NPM Package
  • The website
  • Other, namely:

Description

Currently the website search performs poorly on some strings, not weighing exact matches high enough. For example, when you want to find Facebook by searching for "fa" it is preceded by the less accurate match "Fnac" (and several others):

image

I have implemented a somewhat better search algorithm here:

This search algorithm is based on the one described in this blog post, without some of the more fancy stuff. The bonuses/penalties for matching letters in specific positions have been tweaked based on our needs, putting more value on exact matches and on matches from the start of the string.

The big downside is that there is no easy way to filter out poor matches, because the score of each match depends on the length of the pattern and the length of the searched string. It could potentially be tweaked to better do this, but I don't have the time to do that right now.

Ideally we would implement this, or another search algorithm, on the website to give better search results.

CONTRIBUTING.md - npm install should be replaced with npm ci

As the title says, this will prevent contributors from writing to package-lock.json when installing dependencies and make the contributing experience just a tab bit better ๐Ÿ˜ƒ.

Some info on npm ci:

The new npm ci command installs from your lock-file ONLY. If your package.json and your lock-file are out of sync then it will report an error.

It works by throwing away your node_modules and recreating it from scratch.

Beyond guaranteeing you that you'll only get what is in your lock-file it's also much faster (2x-10x!) than npm install when you don't start with a node_modules.

Use consistent iconography

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Currently, the iconography is a bit inconsistent, the icons for ordering were custom made for the old website; the dark/light/system mode icons are taken from Feather Icons (the system one is custom-made based on Feather Icons icons); and for #47 we need a "legal" icon which Feather Icon's does not seem to have.

In the table below I aim to create an overview of some icon packs that I'm familiar with and whether or not they have each icon. The most obvious finding, it doesn't look like any icon pack provides "sort by color" or "sort by relevance" ๐Ÿ˜“

Icons Font Awesome Feather Icons iconsvg Heroicons Phosphor Icons System UIcons Material Design Icons
Light mode Yes Yes Yes Yes Yes No Yes
Dark mode Yes Yes Yes Yes Yes No Yes
Light/Dark mode No? No? No? No? No? No Yes
External link Yes Yes Yes Yes Yes? Yes? Yes
Copy to clipboard Yes Yes Yes Yes Yes Yes Yes
Legal Yes No No Yes No No Yes
Sort alphabetically Yes No No No? No? No? Yes
Sort by color No? No No No No No Yes?
Sort by relevance No? No No No No No Yes?

[Suggestion] Add "Icon detail" view

โ„น๏ธ If you're interested in this feature, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

As per this comment, add an "icon detail view". This would display a particular icon at a larger size and potentially give download options such as #31, #32, #33 for that particular icon, as seen in this example mockup.

I'm not sure how useful this is. The larger icon can be nice, but if that is the only benefit I'm not sure something like the mockup below is suitable. The icon-specific download options can be nice, but I would expect that everyone would nearly always want the same download option for all icons.

What it may allow us to do is things like:

  • Show everything that is already in the card (the SVG, color, brand guidelines URL, license name & URL)
  • Show aliases (simple-icons/simple-icons#4797)
  • Show the SVG source URL
  • Show the brand website URL
  • Show if the icon will be removed in next versions
  • Link to milestone and pull request of icon removal, if will be removed in next versions
  • Option to copy the brand name
  • Option to copy the brand slug
  • Option to copy the font class
  • Option to copy the font code point
  • Option to copy the entire SVG (even though that is already possible)
  • Option to copy the path data
  • Option to copy code to use in NPM
  • Download svgs in the brand color (#32)
  • Show the icon in a variety of sizes (#40)
  • More? (Suggestions are welcome)

Add instant search / search shortcut

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

We can make searching easier on the website by adding either of the following:

  • Automatically start searching when the user starts typing (letters or numbers) anywhere on the website.
  • Add a key/key combination to focus the search input. This could be Ctrl+f but unless we support exact search I think we should keep support for browser search.

I personally like the former. Any opinions from others (@simple-icons/maintainers)?

Add a CSS reset

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely: refactor

Description

We should consider adding a CSS reset (e.g. Reset CSS by Eric A. Meyer) to the website to improve consistency across browsers.

To anyone looking to work on this, please be sure to remove duplicated styles from existing CSS rules.

Add link to CDNs

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Currently the website has external links to GitHub, NPM, and Packagist. We should also add link for - at least - the CDNs we promote in the documentation.

Tabbing order confusion

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely: a11y

Description

Currently, tabbing through the website really only works if you're using the default ordering (alphabetical). If either colored ordering or relevance ordering (when searching) is used, tabbing through the grid items will result in jumping all over the page.

This is because the visual re-ordering of the grid items is achieved using the flexbox order property and dynamically assigned CSS variables. The idea behind this approach, when it was implemented, was to leverage the GPU to do the re-ordering.

Unfortunately, this is a minor (?) problem for accessibility and if performance isn't too bad when shuffling the elements around to preserve a sane tab ordering we should change the implementation.

Redundant Building in Verify Action

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely: CI

Description

It looks like dependencies are reinstalled and website is re-built in "Test Website" action. Therefore, it seems unnecessary to set "Build website" as a precondition for "Test Website", or maybe the whole "Build website" is an unnecessary test (already covered by other ones).

Burger icon for responsive menu

Currently the menu has no responsiveness other than wrapping itself to fit the screen.
We should add a burger menu to hold all menu items as it is standard for responsive apps.

The only concern I have is with how to deal with the modal for extensions in this case.

[Suggestion] Universally choose download type

โ„น๏ธ If you're interested in this feature, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Improvement
  • Bug
  • Other, namely:

Description

Following an idea that appeared in this redesign proposal we may consider updating the website so that the user can choose what kind of files they want to download (currently SVG or PDF) and than have single download button in grid items to download the brand logo in that format.

This has two potential benefits:

  • If we provide support for more formats (e.g. PNG and JPEG), the buttons may no longer fit in the grid item, requiring us to redesign the grid items to accommodate many buttons.
  • If there is just one button to download the icon, it is less likely the wrong button is pressed.

It also has some potential benefits

  • As this is maybe not super common, the user may not find out that they can change the type of file that will be downloaded. Which is a shame if they're not looking for the default.
  • It may be non-trivial to support this for users without JavaScript. Though, we may choose to generate one page for downloading SVGs and one for PDFs (and one for whatever we wish to support) and change the button to choose the type into a link to that page.

This issue relates to #25 as it would probably lead to a redesign of the grid items, since multiple download buttons are no longer needed.

Choose a default ordering

โ„น๏ธ If you're have an opinion regarding this discussion, please leave a โค๏ธ if you prefer ordering by color and a ๐Ÿš€ if you prefer ordering alphabetically. Also, feel free to leave a comment if you have more to add to the discussion


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

This is a pretty simple discussion. For context: the original website always ordered the icons by color by default. The redesign currently orders the icons alphabetically by default. (In both versions, changing the ordering once will store that locally and restore that ordering when you revisit the page).

So the question is, which ordering should we use in the redesign. I see one obvious argument for either solution:

  • Alphabetically: Makes logical sense, is probably more useful if you're looking for a specific brand.
  • By color: Looks better, as the colors flow nicely throughout the page.

If you believe you have a good argument in favor of either, feel free to leave a comment (or add a ๐Ÿ‘ to a comment with that argument).

For those that don't want to try it out manually, here are two screenshots with a preview for both options (as of v4.8.0 of simple-icons):

Alphabetical ordering Color ordering
image image

Support "forced" color scheme for non-JS users

Kind of issue

  • Improvement (when JS is disabled)
  • Bug
  • Other, namely:

Description

Similar to #34, if JavaScript is disabled the user can only use the system default color scheme, whereas with JavaScript you can always choose dark mode or light mode. (forcefully overriding the system default). We could support using a specific color scheme other than the system default for non-JS users by generating a versions of the website where each color scheme is the default and converting the buttons to choose the color scheme into links to the respective page for non-JS users.

I think we should support this, provided we can do so with minimum effort for keeping the two versions of the page in sync when the .pug source is changed. E.g. by somehow instructing the default color scheme in the webpack configuration, and than just generating both versions.

Some blacks are not correctly ordered when ordering by color

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

When ordering by colour the ordering is a bit off as some black colors are displayed at the top, before the reds, while most blacks are displayed all the way at the bottom, following the whites.

Ideally, we find some sort of solution for this ordering problem. Unfortunately, in general there isn't necessarily a good solution for sorting colors. There will always be some cutoff point and it will probably never be perfect.

However, with some effort we may be able to improve the current situation. Two (possible) goals:

  • Group all "blacks" and "whites" at the end.
  • Have at least the ordering above the fold look "as expected".

Anyone looking to work on this issue, share any suggestions, research, or previews you can ๐Ÿ™‚

Example

Below is an example of what ordering by colour looks like - using v4.8.0 of simple-icons. As you can see "GitHub" and "DS Autombiles", which have dark grey colours, appear before "The Spriters Resource" which is red, i.e.

#181717 #1D1717 #BE3939

image

Some icons are missing from the website

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Some icons (the copy, copied, external link, and legal icons) are currently not being rendered. Testing some recent commits, it seems to be due to a dependency update introduced in #91.

Add AAAA (IPv6) records for simpleicons.org

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Github now supports IPv6 for Github Pages - https://github.blog/changelog/2021-09-30-enabling-ipv6-support-for-github-pages/

Could you add AAAA (IPv6) DNS records to simpleicons.org, so the website is served over IPv6 for users on ISP's that offer IPv6.

2606:50c0:8000::153
2606:50c0:8001::153
2606:50c0:8002::153
2606:50c0:8003::153

From step 5 in https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site

Website header links "GitHub" and "About" are nearly identical

Kind of issue

  • Improvement
  • Bug
  • Other, namely:

Description

Currently the GitHub link on the website links to:

https://github.com/simple-icons/simple-icons

And the About link on the website links to:

https://github.com/simple-icons/simple-icons#readme

The difference being:

- https://github.com/simple-icons/simple-icons
+ https://github.com/simple-icons/simple-icons#readme

I think it's worth considering removing one of the two. My suggestion would be to remove the About link and possibly change the GitHub link to:

https://github.com/simple-icons/simple-icons#readme

Discussion and suggestions are welcome ๐Ÿ™‚

Support both alphabetical and colored ordering for non-JS users

Kind of issue

  • Improvement (when JS is disabled)
  • Bug
  • Other, namely:

Description

Currently, if JavaScript is disabled, the user only has alphabetical ordering available. We could support color-based ordering for non-JS users by generating a second version of the website where color-based ordering is the default and converting the buttons to choose the ordering method into links to the respectively ordered page for non-JS users.

I think we should support this, provided we can do so with minimum effort for keeping the two versions of the page in sync when the .pug source is changed. E.g. by somehow instructing how the icons should be ordered in the webpack configuration, and than just generating both versions.

Dependency Dashboard

This issue provides visibility into Renovate updates and their statuses. Learn more

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

  • Update all dependencies (JamesIves/github-pages-deploy-action, autoprefixer, babel-jest, husky, jest)

  • Check this box to trigger a request for Renovate to run again on this repository

[Discussion] Update controls design

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

These are suggestions for changing the design of the controls.

  • Move color mode buttons away from the other controls.
  • Omit borders, e.g.:
    preview no brders
  • As per this comment, grouped buttons, e.g.:
    preview grouped buttons

Add compact layout

โ„น๏ธ If you're interested in this feature, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Following the original design, a "compact layout" mode can be added to the website. The end-design may differ from what is displayed there, it is just a guideline.

[Suggestion] Replace header link text by logos

โ„น๏ธ If you agree with this design idea, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Related issues: #27

Currently, the website header contains three links to external platforms (and an about link), namely: GitHub, NPM, and Packagist. These links are in text, but it is common for such links to be icons - and so did many redesign mockups in simple-icons/simple-icons#980.

So the question is, should we replace these text links by icon links? I think I would be in favor of this as I think it looks better, it is arguably easier to parse an image than it is text. On the other hand, it is usually recommended to use text for accessibility - though workarounds for that exist.

Alternatively, we could also choose to have both text and icons, hiding the text in some kind of compact mode.

Consider design for link to DISCLAIMER.md

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely: requirement

Description

Add a link to the DISCLAIMER.md of the project - depends on simple-icons/simple-icons#4912.

In #74 we were not necessarily happy about the design aspect of the link to the disclaimer, but we merged it in in the interest of having some link while we figure out the design. This ticket now serves to keep this topic alive and potentially discuss the design of the link to the disclaimer.

Add link to report outdated icons

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

We should make it easier for users to report outdated icons in an effort to keep our collection up-to-date. Based on discussion (see below) we think the link should basically just point to the Icon update template as (a) this reduces the chances (prevents?) of someone creating many issues quickly in an automated way, and (b) while prefilling details such as the brand name is nice, it doesn't add to much value to the UX while adding a lot of HTML (at least one element per icon = at least 1900 elements).

Removing color sorting

  • Feature
  • Bug
  • Design
  • Other, namely: feature removal

Description

Color sorting is a feature present in the website that provides very little value.
Considerations:

  • It is a subjective sorting criteria that can't be applied in a deterministic way to an array of elements (such as the icons) due to colors being a multidimensional value.
  • It offers little help to the user to find a particular icon or to search for related icons. The order in which colors are presented says nothing to the user.
  • As sorting it has no purpose, since being at the beginning or the end of it means nothing for the icon: the relationship between colors can't be modeled in terms of one dimension.
  • The existence of the feature forces the website to support it moving forward in any aspect the code needs to support. Example, the discussion here: #34 , where support for color sorting is required for non JS users. In this sense, a feature that is already merely (and subjectively) cosmetic is in practice requiring work to be maintained without offering much in the way of value to the user base.
  • The removal of this feature would simplify the interface, reduce the weight of the HTML file by removing all --color-order
    attributes, and would remove the color-sorter dependency from the project.
  • Not carrying this feature forward opens the possibility for different features to be added, like grouping by category or bulk downloading (#42). While these can be added without removing color sorting, it would be a better tradeoff to take one feature out and add another, at least regarding source code size.

If we can get consensus, I can remove this feature myself.

Add structured data

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Add structured data to the website. This could make the results in e.g. Google a bit nice when searching for "Simple Icons".

Any opinions on whether we should add this (@simple-icons/maintainers)?

Improve rendering with `content-visibility:auto`

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely: Improvement

Description

The new grid layout looks great and renders well but we could, potentially, improve the rendering further by using content-visibility:auto on the grid items along with contain-intrinsic-size, assuming it doesn't interfere in any way with the lazy loading of the SVGs.

Some further reading:

Inconsistent Formatting in Header Links

Kind of issue

Design

Description

Brand names in the header are inconsistently formatted. I would assume, given they're titles or brand names, that they should be capitalized as below, except when stylized a certain way:

  • Main Repository (currently 'main repository')
  • npm (correctly formatted, name is stylized lowecase)
  • Packagist (currently 'packagist')
  • jsDelivr (correctly formatted)
  • UNPKG (currently 'Unpkg')
  • Legal Disclaimer (currently 'Legal disclaimer')

[Suggestion] Download a collection of icons at once

โ„น๏ธ If you're interested in this feature, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

As per this comment: add functionality to allow users to select an icon to be included a "collection", and then have the ability to download all the icons in the collection at once (probably as .zip). It could be nice to provide download options such as #31, #32, #33 for the collection (without it affecting anything else), similar to #43.

As per this comment the benefits of this are not super clear, as it takes up space in the UI while most users probably only download a handful of icons when visiting the website...

Clearing the search bar directs to wrong URL

Kind of issue

  • Improvement
  • Bug
  • Other, namely:

Description

Visiting https://ericcornelissen.github.io/simple-icons-website, if I type something into the search bar and then clear it (clicking on the small "x") it somehow redirects me to https://ericcornelissen.github.io instead of back to https://ericcornelissen.github.io/simple-icons-website (while still displaying the website correctly ๐Ÿค”).

Therefore after clearing the search bar, downloading an icon fails, as the "SVG" button no longer points to https://ericcornelissen.github.io/simple-icons-website/icons/42.svg but now to https://ericcornelissen.github.io/icons/42.svg.

Tested on Chrome (89.0.4381.6) on Ubuntu (20.10).

[Suggestion] Add indicator for "current letter" when ordering alphabetically

โ„น๏ธ If you're interested in this feature, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

As per this comment, add an alphabetical indicator of where in the grid of icons you are - not present when ordering is by color or by relevance. For example. as seen in the mockup below โฌ‡๏ธ

An argument against this is that it is kind of redundant and may compete with the search functionality (i.e. users may try to search manually by scrolling to the right first letter and looking for an icon manually).

preview

Alternative styling for brands with #FFFFFF as color

Kind of issue

  • Improvement
  • Bug
  • Other, namely:

Description

Currently, the .grid-item of brands with an (almost) white brand color look a little bit off, e.g., as of writing this, Zulip:

Non-white White
image image

Similarly, in dark mode brand with an (almost) black brand color look a little bit off:

Non-black Black
image image

This could be improved, though I'm not sure how to change the styling ๐Ÿค”

Support more query parameters

โ„น๏ธ If you're interested in this feature, please leave comment or add a ๐Ÿ‘


Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

As per this comment add more query parameters than just the one for the search parameter. E.g.:

  • ?colorscheme=(dark|light|system): This loads the website with a specific color scheme. As the color scheme is also stored in localStorage I don't think this should be added to the URL automatically. Instead it may be added to link new users to the website in a specific color scheme. For existing users - those with a preference stored - the color scheme in the URL should be ignored.
  • ?ordering=(alpha|color|relevance): This loads the website with a specific ordering of the icons. As the ordering is also stored in localStorage I don't think this should b added to the URL automatically. Instead, it may be added to link new users to the website with a specific ordering. FOr existing users - those with a preference stored - the ordering in the URL should be ignored.

Slow render while using mobile data.

Kind of issue

  • Feature
  • Bug
  • Design
  • Other, namely:

Description

Suggestions:

  • Make search bar functional while loading other icons.
  • Lazy load would save much time on First Load (recommended for slow connection regardless device screen width)

Steps to recreate the issue:

  • Select 2G/3G on mobile
  • Open the website
  • It'll stuck the loader on 75% for a few minutes.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.