That is entirely up to you. The typical scenario is that you have one views module per app in your project, which would live at your `yourapp/views.py`. If your app has lots of views and you want to keep it from getting too large, another common pattern is to have one module per view in a directory, like: `yourapp/views/action1.py` and `yourapp/views/action2.py`. How are you organize it is up to you - you have control over your own Python imports. Really just a matter of housekeeping…
./s On Tuesday, January 7, 2020 at 5:29:42 PM UTC-8, 片岡一平 wrote: > > Hi, > > I'm struggling with Django's view directory structure. > Now, I am creating an app with the following URL structure. > > > domain / app / page_category1 / action1 > domain / app / page_category1 / action2 > ... > domain / app / page_categoryN / actionM > > > In this case, how should the Django view directory be constructed? > > Thanks for watching. > I'm glad if you get some advice. > > Kataoka > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/8912eafc-8df7-4ca8-a80d-14fa94ba1e0e%40googlegroups.com.
