Add deploy_docs command and standardize version markers

- Add `just deploy_docs` command to build and deploy documentation to
  GitHub Pages independently of the full release process
- Convert all "New in development version" markers to use MkDocs !!!
  info admonition format for better visual consistency
- Update CLAUDE.md with documentation guidance showing when to use
  indented vs non-indented descriptions in version callouts
- Ensure version markers only contain what's specifically new, not all
  feature documentation

The deployment script will continue to work as it replaces the "New in
development version" text regardless of surrounding markdown format.

Author: SmileyChris

CLAUDE.md

@@ -58,17 +58,38 @@ Coverage is automatically generated when running `just test`. View the HTML repo
 
 ### Documentation
 ```bash
-just docs  # Serve documentation locally at http://127.0.0.1:8080
+just docs         # Serve documentation locally at http://127.0.0.1:8080
+just deploy_docs  # Build and deploy documentation to GitHub Pages
 ```
 
-Documentation is built with MkDocs and automatically deployed to GitHub Pages during `just deploy`.
+Documentation is built with MkDocs. Use `just deploy_docs` to manually deploy to GitHub Pages, or it will be automatically deployed during `just deploy`.
 
-**When adding new features to documentation**, mark them with version callouts:
+**When adding new features to documentation**, mark them with version callouts using the `!!! info` admonition format:
 
 ```markdown
-**New in development version**
+!!! info "New in development version"
 
-Description of the new feature...
+Full description of the feature continues here...
+```
+
+For subsection-level features (like specific setting options), use an indented brief description inside the admonition, then continue with full documentation outside:
+
+```markdown
+!!! info "New in development version"
+
+    Brief description of what's specifically new about this option.
+
+Full documentation of the option continues here with examples, code blocks, etc.
+```
+
+Example:
+```markdown
+!!! info "flag_url: New in development version"
+
+    Per-country `flag_url` overrides allow custom country codes to reuse existing flag image assets.
+
+A custom flag image URL for this country. Usage examples:
+...
 ```
 
 During release, the deployment script automatically replaces all "New in development version" markers with "New in version X.Y.Z" based on the release version. This ensures users know which version introduced each feature.

docs/advanced/customization.md

@@ -156,7 +156,7 @@ When creating a custom `Countries` subclass, you can override these settings (wi
 
 ## Temporary Context-Based Customization
 
-**New in development version**
+!!! info "New in development version"
 
 For per-request or temporary overrides (such as in views or middleware), use the `countries_context()` context manager. This allows you to temporarily override any country option without modifying global settings or creating custom subclasses.
 
@@ -367,7 +367,9 @@ COUNTRIES_OVERRIDE = {
 
 ### flag_url (optional)
 
-**New in development version**
+!!! info "New in development version"
+
+    Per-country `flag_url` overrides allow custom country codes to reuse existing flag image assets or point to bespoke flags.
 
 A custom flag image URL for this country. This is particularly useful when using custom country codes that need to reference existing flag images:
 

docs/advanced/dynamic-ordering.md

@@ -1,6 +1,6 @@
 # Dynamic Country Ordering
 
-**New in development version**
+!!! info "New in development version"
 
 Django-countries supports dynamic country ordering based on user language, preferences, or other contextual factors. This allows you to automatically show relevant countries first in dropdowns and forms.
 

docs/advanced/multiple.md

@@ -127,9 +127,11 @@ Note that `__contains` performs a substring match on the stored comma-separated
 
 ### Django Admin Filtering
 
-**New in development version**
+!!! info "New in development version"
 
-The `CountryFilter` in Django admin automatically works with `multiple=True` fields:
+    The `CountryFilter` in Django admin automatically works with `multiple=True` fields.
+
+The `CountryFilter` in Django admin can be used with `multiple=True` fields:
 
 ```python
 from django.contrib import admin

docs/usage/settings.md

@@ -79,9 +79,9 @@ You can override the following metadata for each country:
 - **ioc_code**: Custom IOC (International Olympic Committee) code
 - **flag_url**: Custom flag image URL (useful for custom country codes that need to reference existing flags)
 
-**New in development version**
+    !!! info "flag_url: New in development version"
 
-Per-country `flag_url` overrides allow custom country codes to reuse existing flag image assets or point to bespoke flags without affecting the global `COUNTRIES_FLAG_URL`.
+        Per-country `flag_url` overrides allow custom country codes to reuse existing flag image assets or point to bespoke flags without affecting the global `COUNTRIES_FLAG_URL`.
 
 !!! tip
     When specifying only metadata fields (like `flag_url`, `ioc_code`) without providing `name` or `names`, the original country name is preserved. This allows you to customize flags or codes without losing the standard country name.
@@ -146,7 +146,7 @@ COUNTRIES_FIRST_BREAK = "───────────"  # Adds visual separ
 **Type:** `dict`
 **Default:** `{}`
 
-**New in development version**
+!!! info "New in development version"
 
 Map language codes to lists of countries to show first. Enables dynamic country ordering based on the user's current language. **Overrides** `COUNTRIES_FIRST` when a language matches.
 
@@ -176,7 +176,7 @@ COUNTRIES_FIRST_BY_LANGUAGE = {
 **Type:** `bool`
 **Default:** `False`
 
-**New in development version**
+!!! info "New in development version"
 
 Enable automatic country detection from the user's locale. Auto-detected countries are **prepended** to `COUNTRIES_FIRST`.
 
@@ -277,22 +277,22 @@ class Product(models.Model):
     country = CountryField(countries=EUCountries)
 ```
 
-**New in development version**
+!!! info "New in development version"
 
-**Language-based ordering per field:**
+    **Language-based ordering per field:**
 
-```python
-class RegionalCountries(Countries):
-    first_by_language = {
-        'en': ['US', 'GB', 'CA', 'AU'],
-        'de': ['DE', 'AT', 'CH'],
-        'fr': ['FR', 'BE', 'CH', 'CA'],
-    }
-
-class Customer(models.Model):
-    name = models.CharField(max_length=100)
-    country = CountryField(countries=RegionalCountries)
-```
+    ```python
+    class RegionalCountries(Countries):
+        first_by_language = {
+            'en': ['US', 'GB', 'CA', 'AU'],
+            'de': ['DE', 'AT', 'CH'],
+            'fr': ['FR', 'BE', 'CH', 'CA'],
+        }
+
+    class Customer(models.Model):
+        name = models.CharField(max_length=100)
+        country = CountryField(countries=RegionalCountries)
+    ```
 
 See [Single Field Customization](../advanced/customization.md#single-field-customization) for more details.
 

justfile

@@ -156,6 +156,16 @@ check:
 docs:
     uv run --group docs mkdocs serve --livereload --dev-addr 127.0.0.1:8080
 
+# Build and deploy documentation to GitHub Pages
+deploy_docs:
+    @echo "Building documentation..."
+    uv run --group docs mkdocs build --strict
+    @echo "✓ Documentation builds successfully"
+    @echo ""
+    @echo "Deploying to GitHub Pages..."
+    uv run --group docs mkdocs gh-deploy --force
+    @echo "✓ Documentation deployed"
+
 # Update English translation source file with new translatable strings
 tx-makemessages:
     @echo "Updating English translation source file..."