Steep learning curve

[smolijar]

Hello @carloscuesta 😎!

I think we are at the edge of seeing Gitmoji too difficult to start with. When trying to implement it in my team, I have noticed some people are discouraged to use it, because they are overwhelmed by the amount of emojis available.

Having continuous requests for very specific emojis (e.g. #175 ), we can predict the situation to get even worse.
How do we prevent gitmoji from becoming too complex to use or perhaps make getting started with gitmoji easier?

When trying to convince someone to try using it, I tried to simplify it. In my eyes there are major overlaps (not a bad thing). E.g. there are many symbols for specific bug fixes. So I tried to explain them, there are several basic symbols you can use.

Maybe it would be nice to simplify the emoji in hierarchy, so that users can gather their head around more swiftly.

I tried to propose a way of grouping the emojis into hierarchy, supported by "types" from conventional commits (which might help some users coming from there).

image

This is but a draft, but I think that once we agree on that, it's just a matter of appealing presentation.

The problem has been addressed in #347

[SkyaTura]

I like the idea of nesting the emojis, or at least adding fields for parent emojis, and use them to generate cheat sheet markdowns as shown by @szepeviktor in #314

[Simek]

If you don't know - apart of Gitmojis website there is also a CLI (https://github.com/carloscuesta/gitmoji-cli) which helped a lot in our team at the beginning of switching to Gitmojis commits.

I know it may be not an ideal solution for everyone but it was created with intention which is rised here:

This project provides an easy solution for using gitmoji from your command line. Gitmoji-cli solves the hassle of searching through the gitmoji list. Includes a bunch of options you can play with! 🎉

[smolijar]

This issue is about the complexity of the system. Making a complex system more accessible via a tool does not reduce complexity. I know about the CLI and I was using it when I started with Gitmoji and it helped me indeed. The problem is that this kind of tool might be a no-go for some teams because of conflicts with their existing workflow.
I might have been misunderstood, the problem is not the tooling. The problem is that Gitmoji is a vague recommendation to write commit messages, but to get started, you kind of need a tool to begin with.

[carloscuesta]

I think we already argued about this in #345. The concept is about simplicity and giving the idea to users to use emojis on GitHub commits