From 70f9c1110b6cbacd11d291885a215f9d6a095d04 Mon Sep 17 00:00:00 2001
From: Philip Sargent <philip.sargent@gmail.com>
Date: Sat, 27 Sep 2025 21:13:12 +0100
Subject: [PATCH] add link to arrticle - online edit of
 handbook/troggle/trogforms.html

---
 handbook/troggle/trogforms.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/handbook/troggle/trogforms.html b/handbook/troggle/trogforms.html
index 3ffb2157c..930d19adf 100644
--- a/handbook/troggle/trogforms.html
+++ b/handbook/troggle/trogforms.html
@@ -8,6 +8,8 @@
 
 <h4>Django Forms History</h4>
 <p>Django has several generations of quite different clever mechanisms to make creating HTML forms "easier". Yes, making them might be easier, but maintaining this opinionated stuff is a nightmare without adequately educating yourself how the architecture works. This will take time: do not hurry.
+
+  <p>If you are a preofessional Django programmer, read <a href="https://www.loopwerk.io/articles/2025/django-views/?_bhlid=6ece59f0c3de24278c50871556723844d8ab734a">this article</a> for why Class Based Views are not a good fit for the community we have maintaining troggle.
   
   <p>WARNING: when reading the Django documentation on <a href="https://docs.djangoproject.com/en/5.1/topics/forms/">Forms</a> (unbound and <a href="https://docs.djangoproject.com/en/5.1/ref/forms/api/">bound</a>) and <a href="https://docs.djangoproject.com/en/dev/topics/forms/modelforms/">ModelForms</a>, do not get diverted into looking at Formsets or ModelFormsets. We do not use any formsets in troggle - of any kind[<a href="#bugger">*</a>].