📝 Update CHANGELOG.md

- added formatting notes for releases
- added notes for PEP0440 styling guide
- added additional notes for conversion to semver terminology

Author: ZenithClown

CHANGELOG.md

@@ -1,3 +1,57 @@
-# Changelog
+<h1 align = "center">CHANGELOG</h1>
 
-All notable changes to `pkg-name` will be documented here. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+<div align = "justify">
+
+All notable changes to this project will be documented in this file. The format is based on
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [PEP0440](https://peps.python.org/pep-0440/)
+styling guide. For full details, see the [commit logs](https://github.com/sharkutilities/pandas-wizard/commits).
+
+## `PEP0440` Styling Guide
+
+<details>
+<summary>Click to open <code>PEP0440</code> Styilng Guide</summary>
+
+Packaging for `PyPI` follows the standard PEP0440 styling guide and is implemented by the **`packaging.version.Version`** class. The other
+popular versioning scheme is [`semver`](https://semver.org/), but each build has different parts/mapping.
+The following table gives a mapping between these two versioning schemes:
+
+<div align = "center">
+
+| `PyPI` Version | `semver` Version |
+| :---: | :---: |
+| `epoch` | n/a |
+| `major` | `major` |
+| `minor` | `minor` |
+| `micro` | `patch` |
+| `pre` | `prerelease` |
+| `dev` | `build` |
+| `post` | n/a |
+
+</div>
+
+One can use the **`packaging`** version to convert between PyPI to semver and vice-versa. For more information, check
+this [link](https://python-semver.readthedocs.io/en/latest/advanced/convert-pypi-to-semver.html).
+
+</details>
+
+## Release Note(s)
+
+The release notes are documented, the list of changes to each different release are documented. The `major.minor` patch are indicated
+under `h3` tags, while the `micro` and "version identifiers" are listed under `h4` and subsequent headlines. The legend for
+changelogs are provided in the detail pane, while the version wise note is as available below.
+
+<details>
+<summary>Click to open Legend(s) Styilng Guide</summary>
+
+  * 🎉 - **Major Feature** : something big that was not available before.
+  * ✨ - **Feature Enhancement** : a miscellaneous minor improvement of an existing feature.
+  * 🛠️ - **Patch/Fix** : something that previously didn’t work as documented – or according to reasonable expectations – should now work.
+  * ⚙️ - **Code Efficiency** : an existing feature now may not require as much computation or memory.
+  * 💣 - **Code Refactoring** : a breakable change often associated with `major` version bump.
+
+</summary>
+</details>
+
+### Version: `XXX` | Release Date:
+
+</div>