# Update startproject with default login/signup/logout options **URL:** \ **Category:** Django Internals\ **Created:** [September 27, 2024, 3:39pm UTC](https://forum.djangoproject.com/t/update-startproject-with-default-login-signup-logout-options/35175 "2024-09-27T15:39:02Z")\ **Posts on this page:** 1\ **Showing post:** 14
**Author:** ![carltongibson](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/carltongibson/32/267_2.png) [@carltongibson](https://forum.djangoproject.com/u/carltongibson)\ **Post date:** [September 29, 2024, 9:03am UTC](https://forum.djangoproject.com/t/update-startproject-with-default-login-signup-logout-options/35175/14 "2024-09-29T09:03:14Z")
Thanks @ubernostrum! Looking at Will’s proposals… > [@wsvincent](#): > > So I propose two things: > > 1. Add a login.html template. We already have the URL and view files. Why not include a basic login template? > 2. Add a basic signup option as well, which means a view, template, URL. > 3. If we want to go crazy, include a basic form for logout, too, which now requires a POST request and I can assure you also confuses people. … 1 and 3 seem less invasive: they’re about providing (minimal “do edit”) templates for the existing views in `django.contrib.auth`. 2 is getting into the land of `Django-registration`, which maybe (? — just a thought) is better as a how-to, showing something simple, but pointing to ecosystem options. I guess I’d say it’s 2 that merits more of a `If we want to go crazy...` than 3, which is (again) just the template really. 🤔 Related: ref linking to external packages, a discussion at DjangoCon revolved around how we guide folks to _Ecosystem Batteries_ if we keep Django core itself small. `pip` works great, but you need to know what to `pip` --- _[View the full topic](https://forum.djangoproject.com/t/update-startproject-with-default-login-signup-logout-options/35175)._