docs: refactor Hydrogram vs Pyrogram page (#7)

usernein · web-flow · commit 23c67e099774 · 2024-06-30T15:21:15.000-03:00
diff --git a/docs/source/hydrogram-vs-pyrogram.rst b/docs/source/hydrogram-vs-pyrogram.rst
@@ -7,18 +7,28 @@ Introduction
 This is a non-exhaustive list of differences between Hydrogram and Pyrogram.
 It is updated periodically.
 
-Changes
--------
-
-- Support for the latest layer
-- Support for threads/topics
-- Improvements in IDE support by declaring ``__all__`` in files
-- Mark optional parameters in methods as keyword-only, to avoid future breakage when adding new parameters
-- Use of newer packaging technologies and standards, such as pyproject.toml
-- Use of aiosqlite instead of sqlite3
-- Open-source documentation
+Key changes
+-----------
+
+- Support for the latest MTProto API layer with all new Telegram features
+- Support for threads and topics in Telegram groups
+- Support for multiple usernames.
 - More active development
-- Completely refactored, optimized and modernized codes (Using Ruff)
+- Completely refactored, optimized and modernized codebase (utilizing Ruff)
+- Open-source documentation
+- Adopt modern packaging technologies and standards, such as pyproject.toml
+- Use aiosqlite instead of sqlite3 for storage handling.
+- Added the property `full_name` for User and Chat objects.
+- Added the possibility to define a custom storage class
+
+More technical changes
+----------------------
+
+- Declared the special variable `__all__` in all files so now we have a better IDE support.
+- Specify optional parameters in methods as keyword-only to prevent potential breakage in the future when introducing new parameters.
+- Migrated from setuptools to hatchling with rye.
+- Transitioned from using `os.path` to utilizing `Pathlib`.
+- Start utilizing towncrier to generate changelogs.
 
 Fixes
 -----
