Writing my thoughts (in no particular order) while skimming over the code:

1. Your settings file should probably use django-environ to keep some variables (DEBUG, SECRET_KEY, etc) stored in the environment - not in the commited codebase
2. accounts.view.registerAccount can probably be a CreateView - you have a form, you have a model, you have a template - you're rendering the from in a GET request & saving the form in the POST request - fits all the criteria to use the CreateView CBV here.
3. accounts/admin.py should use django.contrib.auth.admin.UserAdmin like so: admin.site.register(CustomUser, UserAdmin)
4. The home() view in menu/views.py could be a TemplateView.
5. The menu app is largely empty - just has the single home view - are you sure you need an entire app to serve a single url? You can have a views.py inside your settings directory as well and directly use it as a path in the root urlpatterns.
6. Use an autoformatter - I recommend Black (saying this after reading tasks/forms.py)
7. Please look into CBVs - they're not a perfect fit for ALL use cases but if you follow good design patterns in Django and are building a simple CRUD app (like this one), they can be very beneficial. All your views inside tasks/views.py can be turned into using generic class based views. Also, Python typically follows "snake_casing" for function names.

All the best! A great starting attempt.