From e872a0ea3ad6a9231b57ccaef96ae20bd2e18bac Mon Sep 17 00:00:00 2001 From: Rachid Mrad Date: Wed, 19 Feb 2025 17:26:36 -0500 Subject: [PATCH] cleanup --- docs/architecture/decisions/0027-ajax-for-dynamic-content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/decisions/0027-ajax-for-dynamic-content.md b/docs/architecture/decisions/0027-ajax-for-dynamic-content.md index 6e22a67e7..b1d92fc32 100644 --- a/docs/architecture/decisions/0027-ajax-for-dynamic-content.md +++ b/docs/architecture/decisions/0027-ajax-for-dynamic-content.md @@ -47,7 +47,7 @@ Instead of a full migration, this approach involves integrating a modern JavaScr This approach would still introduce diverging implementation stacks, leading to long-term maintenance challenges. -**Option 3:**Use a Lightweight JavaScript Framework (e.g., HTMX, HTMZ) +**Option 3:** Use a Lightweight JavaScript Framework (e.g., HTMX, HTMZ) Instead of React or Vue, this approach involves using a minimal JavaScript framework like HTMX or HTMZ to enhance interactivity while preserving Django’s server-rendered structure. ✅ Pros: