Introducing ReUI:Open-source UI components and apps built with React, Next.js and Tailwind CSS
Browse ReUI

Regression path where Keenicons are completely removed.


The use of Keenicons has been a significant enough burden that I'm here to ask how does Metronic suggest we regress them completely from the codebase. We want them completely nonexistent and removed.

You might ask why.

1. They are much too playful, too immature, and doesn't instill professionalism inside our types of applications.

2. They are not named friendly enough for a find and hopefully regress/replace all back to fontawesome (which is annoying to say it nicely).

3. I'm not sure who asked for a set of custom Keenicons but its a new dependency and a new set of icons our designers and dev's are completely out of awareness on and this alone taken away HOURS if not weeks now in explanation, or in designer time having to find suitable replacements and in turn having dev's replace and all the back and fourth there.

4. Keenicons preferably would never be Metronic's first choice in icon set. Especially not used inside of any demo as default. If someone chooses to use Keenicons then cool but being forced upon them again has taken away a significant amount of time from day-to-day business.

We get you want to use your icon set, but this is not ideal for any SaaS we build. Its enough of a hinderance we need to know your suggested route to regress them completely on each new Metronic update. We do not want to do deal with the stress of these icons on our business with each new update to your product. We need something official as a path to regress them as soon as possible and revert to a solid icon set light Fontawesome.

Thanks


Text formatting options
Submit
Here's a how to add some HTML formatting to your comment:
  • <pre></pre> for JS codes block
  • <pre lang="html"></pre> for HTML code block
  • <pre lang="scss"></pre> for SCSS code block
  • <pre lang="php"></pre> for PHP code block
  • <code></code> for single line of code
  • <strong></strong> to make things bold
  • <em></em> to emphasize
  • <ul><li></li></ul>  to make list
  • <ol><li></li></ol>  to make ordered list
  • <h3></h3> to make headings
  • <a></a> for links
  • <img> to paste in an image
  • <blockquote></blockquote> to quote somebody
  • happy  :)
  • shocked  :|
  • sad  :(

Replies (5)


I can totally understand the frustration with Keenicons, especially when they don't align with the professional tone required in SaaS applications. The back-and-forth between designers and developers to replace them is a time sink that no business can afford to repeat with every update. Ideally, an official guide to remove Keenicons and revert to a more standard, recognizable set like Fontawesome would be a great help. We need info on how to effectively manage this regression with minimal impact, ensuring smoother transitions in future updates without compromising on design or functionality.



I’ve been diving into various ways to simplify business operations and came across some interesting insights on the benefits of streamlined company registration. When setting up a new business, especially internationally, it’s crucial to consider not just the registration but also banking aspects. For instance, if you’re eyeing Seychelles for your company’s base, integrating the registration process with a bank account can save a lot of hassle. I found a resource that made this process incredibly smooth and straightforward here It’s definitely worth checking out if you’re exploring efficient ways to get your business up and running. You can find more about it here.



Hi Regarding the portion where it is marketed as a Rails starter kit, I would have to disagree. Because Ruby on Rails handles assets in a particular way, maintaining the framework should entail modifying the Assets Pipeline as well. How to load and bundle CSS and JS files using sprockets, stimuli, and hotwire...
https://devs.keenthemes.com/question/how-to-for-rails-development geometry dash
The HTML bundle's offerings are identical to those found in the Quick Setup documentation. Static outputs must be produced using the same gulp/Webpack build procedure, and it is not at all connected with Rails pipelines.



Hi Bryan,

We take your point. This is definitely something to discuss with the team, let's see what we can do.
As an option we may consider creating a conservative style of the same set. Do you think this will be a solution?
On a distance it's good to have our own icon set, since we listen customers feedback and add necessary icons.

Best regards,
Bob



Hi,

Thank you for taking the time to provide feedback on KeenIcons.

Since the launch of our KeenIcons set, we have received overwhelmingly positive feedback from the community.

One of the things that makes them so special is that they're now placed as normal font icons with a few lines of HTML elements rather than large SVG code. This makes the page's HTML code much lighter, which can improve performance.

Metronic is built to be customizable and the KeenIcons set is not the only choice since you can use any of the other available icons(Fontawesome, Duotune(the old icon set, Bootstrap Icons, or your custom icon set) in your project.

We're currently working on the next version of KeenIcons, and we'll be adding a lot of new icons and improvements to existing ones.

Regards.


Text formatting options
Submit
Here's a how to add some HTML formatting to your comment:
  • <pre></pre> for JS codes block
  • <pre lang="html"></pre> for HTML code block
  • <pre lang="scss"></pre> for SCSS code block
  • <pre lang="php"></pre> for PHP code block
  • <code></code> for single line of code
  • <strong></strong> to make things bold
  • <em></em> to emphasize
  • <ul><li></li></ul>  to make list
  • <ol><li></li></ol>  to make ordered list
  • <h3></h3> to make headings
  • <a></a> for links
  • <img> to paste in an image
  • <blockquote></blockquote> to quote somebody
  • happy  :)
  • shocked  :|
  • sad  :(
Text formatting options
Submit
Here's a how to add some HTML formatting to your comment:
  • <pre></pre> for JS codes block
  • <pre lang="html"></pre> for HTML code block
  • <pre lang="scss"></pre> for SCSS code block
  • <pre lang="php"></pre> for PHP code block
  • <code></code> for single line of code
  • <strong></strong> to make things bold
  • <em></em> to emphasize
  • <ul><li></li></ul>  to make list
  • <ol><li></li></ol>  to make ordered list
  • <h3></h3> to make headings
  • <a></a> for links
  • <img> to paste in an image
  • <blockquote></blockquote> to quote somebody
  • happy  :)
  • shocked  :|
  • sad  :(