➕ Add more clear info like GitHub badges of important points.

Author: Chisanan232

docs_with_docusarus/contents/development/ci-cd/release-system.mdx

@@ -5,12 +5,15 @@ sidebar_position: 3
 
 # Release System
 
+[![GitHub release](https://img.shields.io/github/v/release/Chisanan232/Template-Python-UV-Project?display_name=tag&color=24292e&logo=github)](https://github.com/Chisanan232/Template-Python-UV-Project/releases)
+
 The release workflows for this template are now maintained in the centralized repository `Chisanan232/GitHub-Action_Reusable_Workflows-Python`. This project consumes those reusable workflows for production, validation, and staging releases while keeping only minimal configuration locally.
 
 ## Release workflows
 
 ### Production release (`release.yml`)
 [![Release](https://github.com/Chisanan232/Template-Python-UV-Project/actions/workflows/release.yml/badge.svg)](https://github.com/Chisanan232/Template-Python-UV-Project/actions/workflows/release.yml)
+[![PyPI version](https://img.shields.io/pypi/v/test-python-uv-project-template?label=PyPI&color=306998&logo=pypi)](https://pypi.org/project/test-python-uv-project-template/)
 
 Publishes production artifacts (PyPI package, container images, docs) using the centralized `rw_release_complete.yaml` workflow logic.
 
@@ -41,6 +44,7 @@ See the reusable workflow guide for production releases: [rw_release_complete.ya
 
 ### Release staging (`release-staging.yml`)
 [![Release Staging](https://github.com/Chisanan232/Template-Python-UV-Project/actions/workflows/release-staging.yml/badge.svg)](https://github.com/Chisanan232/Template-Python-UV-Project/actions/workflows/release-staging.yml)
+[![TestPyPI version](https://img.shields.io/badge/dynamic/json?label=TestPyPI&color=ff6600&query=%24.info.version&url=https%3A%2F%2Ftest.pypi.org%2Fpypi%2Ftest-python-uv-project-template%2Fjson&logo=pypi)](https://test.pypi.org/project/test-python-uv-project-template/)
 
 Creates staging/TestPyPI packages, RC container images, and preview documentation to test releases before production.
 

docs_with_docusarus/contents/development/coding-style.mdx

@@ -8,6 +8,13 @@ sidebar_position: 4
 
 To maintain consistency and quality across the codebase, we follow these coding standards and rules. All contributors are expected to adhere to these guidelines.
 
+[![pre-commit enabled](https://img.shields.io/badge/pre--commit-enabled-brightgreen?logo=pre-commit&logoColor=white)](https://pre-commit.com/)
+[![Black code style](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)
+[![isort imports](https://img.shields.io/badge/imports-isort-ef8336?logo=python&logoColor=white)](https://pycqa.github.io/isort/)
+[![Flake8 linting](https://img.shields.io/badge/lint-flake8-4B8BBE)](https://flake8.pycqa.org/)
+[![MyPy type checking](https://img.shields.io/badge/types-mypy-2A6DB5)](https://mypy.readthedocs.io/en/stable/)
+[![Pylint linting](https://img.shields.io/badge/lint-pylint-ffcc00)](https://pylint.readthedocs.io/en/latest/)
+
 ## Python Code Style
 
 ### PEP 8