What types of icons should be included in devicon? #353
Replies: 7 comments 5 replies
-
Here are my thoughts on the above questions:
Yes, I think we should. While programmers might not directly use these tools, we might use the products created by these tools. Also, a lot of tech jobs closely collaborate with "semi-tech" jobs, like web designers. I feel that these closely coupled jobs are a part of the tech industry too and their tools can be a part of Devicon. For example, in web development, you might work with images that were created in Photoshop. Knowing Photoshop and other image manipulation apps are also considered a huge asset or even a requirement. Therefore, it makes sense to have Photoshop in Devicon.
We should stop at more "general" products. Word and Google Calendar can be used by anyone from any industry, therefore they are not development tools. A good way to differentiate these products is to look at their customer base. If it's built specifically for tech jobs or for closely-coupled jobs in mind, we should accept it. For example: 3D modelling apps and sound editing softwares can be seen as its own fields. These tools are built for 3D modelers and sound engineers in mind. While their products can be used in game development, the fields are not as closely coupled as web designers and web developer. Therefore, their icons should not go into Devicon. I do admit sometimes this is tricky, such as Slack and LinkedIn. Therefore, we might have to take things on a case-by-case basis. If many people sees it as an an essential part of the tech industry (like Slack and LinkedIn), we can accept them.
I think we should not have them in our repo. While these companies contribute a lot to the tech industry in terms of innovation, they are not tools or languages. However, if their name is also a development tool then we can accept them. So Google, the browser, should be accepted but Google, the company, should not. Facebook, the social media site, should not be accepted but its tools (React and GraphQL) should be. Of course, we can make exceptions and add companies to the repo if that's what our users want. However, they are so different from our current definition that they warrant their own repo. |
Beta Was this translation helpful? Give feedback.
-
I've contributed with some icons and have been in this discussion before, in my opinion:
As a full stack web developer focused on front end, i think that at least the ones i've added, belongs to
This is tricky as well cause you can programmatically create documents or templates that can help you to accomplish some tasks i.e. create a commercial At the same time, there are some tools that can provide you with functionalities that are related to a technology that might not be as related as some would want. In the case of google calendar, they provide an Taking another example, the case of
I think that they should be accepted, because as i mentioned with the google calendar example, some of them provide tools that are related to the area. Think about when you sign up on a new page or ecommerce, you can find a google or facebook, even twitter signup. And in most cases if not in all, the branding is the same. As more examples, facebook provides pixel that's used like G-Analytics or even the business part, digital marketing and more services that are used nowadays by many digital marketing agencies or ecommerce business as part of their job. Companies you mention like Airbnb have developed a lot of packages or useful libraries used today like ConclusionI think that this is a wide topic and the use of tools in the definition gives a gateway to many possibilities. In my point of view, a tool is something that you can use to make your work easier and as soon as a product accomplish this, it fits in the definition. You can add an indirect tools section to solve this, or a lab section just like material-ui, and depending on the use and acceptance of an icon, decide if it's worth it or not. At the end, the decision of which icons someone can add will be yours. Greetings 😃 |
Beta Was this translation helpful? Give feedback.
-
My 2¢
I think that's a really hard line to draw, if you do accept them. There are other alternatives that are doing something similar to what devicons does (like simpleicons).
There are probably a lot more here than it's worth keeping up with, keep the focus narrow and you have more time to spend on what really matters to deliver quality (which by the way, I think you've done).
Again, there are plenty of sources for these types of icons. Stay focused, and you will deliver the quality that people need from you. EDIT Another point of view, playing my own "devil's advocate"... You could always break those out into other repositories if you do so choose to keep them, giving weight and importance to them in a slightly different perspective. |
Beta Was this translation helpful? Give feedback.
-
I appreciate the discussion since this is a community driven project. As previous participants of this discussion pointed out it's pretty hard to draw the line since you could say that any tool you are using when you develop software (web, mobile, desktop, ,...) is a "software development tool". If you bring it to the extrem: A whiteboard in your office could be seen as a "related product for software development". I think that devicon should accept icons which are directly related to software development. If a company (f.e. Google) decides to provide languages or tools for developers f.e. In my opinion we should focus on tools and technologies which are made for software developers. Like in the origin description of this repository:
To quote @Thomas-Boi:
I would extend this description to not only web developers but software developers (which includes mobile, web, desktop). When taking about game development it's a little tricky but I admit to have a conversation on specific icon level (f.e. should we add Unity engine?) |
Beta Was this translation helpful? Give feedback.
-
Hi all, I'm very glad to see everyone's thought on this discussion so far. They are essential to Devicon and it helps maintainers like us to make this repo better for everybody :) So far, here are the things that stood out to me based on the current discussion:
Regarding game engines, I think that we should accept them because:
That being said, game development is a slippery slope. This is a category that we will need to look at on a case-by-case basis. So here is what we will do going forward:
That is all, I look forward to see more comments :) Cheers, |
Beta Was this translation helpful? Give feedback.
-
Hi, 1. The element you want to see added to Devicon must be at a minimum popular (because adding an icon for 2 people will increase the weight of the font unnecessarily).2. The element must fall into at least one of the category of the Allowed or Need Approbation section below:Allowed
Need ApprobationFor these categories we need also to see why it's related to development before accepting.
Not Allowed (not exhaustive)
For me defining categories simplifies the approval process for a new icon to the project, and it avoids the frustration of not knowing the "rules" for the users. Let me know that you think 😊 |
Beta Was this translation helpful? Give feedback.
-
Hello Comunity I’m looking for the Talend logo (ETL tool) and do you know if it is in the repo or if it exists in another one? |
Beta Was this translation helpful? Give feedback.
-
Hello guys,
We would like to ask all of you to help us narrow down the goals of Devicon. Currently, we think that the definition is too broad and sometimes, we don't know whether an icon belongs to our repo.
Here is Devicon's current definition:
Also, our name Devicon is "dev icon" shorterned together :). Basically, this means that we want icons that focuses on technological development languages and tools.
For languages, these includes but are not limited to:
For tools, these includes but are not limited to:
The above examples are some cases where the icons clearly belongs to our repo. However, there are some categories where we don't know for sure, such as:
What we want to discuss with you guys:
Should we accept tools that are indirectly related to tech development? While we already have some icons in our repo (Slack, Photoshop, Trello, . . .), do you think that they belongs here? Should we continue accepting them?
If we do accept tools that are indirectly related to tech development, how indirect should the connection be before we stop accepting it? Microsoft Word or Google Calendar can be used for tech jobs, should we accept icons from these tools?
What count as tech companies? While Google, Facebook, Amazon, . . . are clear big tech companies, do Netflix, Uber, and AirBnB count? Should we even accept icons about these companies in the first place?
Those are the main questions that we can think of for now. If you guys have any questions you would like to bring up, please let us know and we can add them to the discussion list.
Looking forward to the discussion :)
Beta Was this translation helpful? Give feedback.
All reactions