Hi! I think you've found the wrong mailing list for this post (django-developers). This mailing list is for discussing the development of Django itself, not for support using Django. This means the discussions of bugs and features in Django itself, rather than in your code using it. People on this list are unlikely to answer your support query with their limited time and energy.
Please also avoid posting to multiple mailing lists at once. For support, please follow the "Getting Help" page: https://docs.djangoproject.com/en/stable/faq/help/ . This will help you find people who are willing to support you, and to ask your question in a way that makes it easy for them to answer. Thanks for your understanding and all the best, Adam On Fri, Sep 23, 2022 at 5:31 PM Kiet Lam <kmlam1...@gmail.com> wrote: > Why don't you also use the context and pass in an array to be rendered at > the htm? > > There are too many repeating and hard code elements that could have been > done with a single foreach statement. > > On Sat, Sep 24, 2022 at 2:27 AM Kiet Lam <kmlam1...@gmail.com> wrote: > >> Hi Nishant, >> Yes. I would stick to using Django forms. It has a lot of inbuilt >> security protection that is easily implemented at the front end like CSRF. >> >> Cheers, >> Kiet >> >> On Fri, Sep 23, 2022 at 3:56 PM Nishant Sagar <nishantkk...@gmail.com> >> wrote: >> >>> Hey forks, >>> >>> I’m in little dilemma regarding Django forms. I'm working on a project >>> as a backend guy who doesn't know much about CSS and JavaScript so a >>> frontend guy delivered me a form template designed using CSS, however, >>> Django documentation suggests that it's good practice to use Django forms. >>> >>> So how feasible do you think it is for a frontend guy to learn Django >>> widgets from scratch to implement the same thing he can easily do from CSS >>> and JS. As a newbie backend guy, it's not easy for me either to learn >>> frontend tech to implement the same thing in so little time. >>> >>> So I tried implementing the form without using Django forms but I find >>> it hard to deal with files as there is no documentation I can look up to. >>> >>> So can we add these to the documentation or it is still advisable to use >>> Django forms? >>> >>> >>> Thanks and regards, >>> Nishant >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Django developers (Contributions to Django itself)" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to django-developers+unsubscr...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/django-developers/CANNtL-Kqud7V6sk_%3DYnagzATw8eJjO9pCeDx9Za80XywXBi2tQ%40mail.gmail.com >>> <https://groups.google.com/d/msgid/django-developers/CANNtL-Kqud7V6sk_%3DYnagzATw8eJjO9pCeDx9Za80XywXBi2tQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAJ5pyZ%3DSVVNccLzS9iRDMWmZOtaVf90DroUWB_fDOjxWh3wTYQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAJ5pyZ%3DSVVNccLzS9iRDMWmZOtaVf90DroUWB_fDOjxWh3wTYQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMyDDM3gwruT%3DDw%3Dhb5yg%2Bd8i5_pFXaqKXUGU6Do7Qn%2B5JO8KA%40mail.gmail.com.
