Adopt Keep-A-Changelog
While we do have a [`CHANGELOG`](https://github.com/ForkAwesome/Fork-Awesome/blob/master/CHANGELOG.md), it is not easy to read and understand the changelog as it does not have a well-defined structure. My proposal here is to adopt a structure for the changelog.

https://keepachangelog.com ( [GitHub](https://github.com/olivierlacan/keep-a-changelog) ) defines a [structure](https://keepachangelog.com/en/1.0.0#types) for changelogs that helps to maintain a well-strucured changelog. In fact, our ancestor project - Font-Awesome adopted Keep-A-Changelog when it [moved to Font-Awesome 5](https://github.com/FortAwesome/Font-Awesome/commit/ad8a3004e4ae60a3a46f858e9b36bc1230ff2023#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed) ( right after we forked them :sweat_smile: ).

There are other projects like https://github.com/conventional-changelog that _generates_ a CHANGELOG from `git` metadata, but that would involve enforcing [a particular commit style](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines) and making sure that all commits adhere to that policy.