Django app structure, good practice? - django

I'm new to Django and am currently struggling with how to structure the apps.
The site is one with a public frontend, in which you can login to enter a dashboard. I've created a separate app for this dashboard.
Now I want to display a list of employees on one page of this dashboard, however I've created another app for these employees.
Should I create this new page/view, in the employees app? Or should I delete this employee app, and include that model in the dashboard app?
What is considered good practice?
It currently looks like this:
-site
-- dashboard app
-- employee app

Source: Two Scoops of Django: Best Practices for Django 1.8 p-35

Related

One app in Django is enough for whole website?

I'm new to Django framework and currently working on an ecommerce website. Not sure what would be better, when creating new project and new app in Django, does a single app is enough and fine for whole website functionally(all HTML pages, user login/registration etc) or should I use separate apps in my project?
one app for one purpose.
don't describe your app with 'and'.
like: my_app_name' to manage students and exams.
just create 'students' app to manage students and 'exams' to manage exams
According to the great book on django 'Two scoops of django' we should create an app for only one purpose. If the work of an app is beyond a topic we should create another one.
So I think you should create separate apps for various tasks of your web-application like:
accounts : app for user model
products : app for product model
orders : app for managing orders
payments : app for the order payments
...
and many more.
As far I have used Django in my profession about four years, I think Django and python is comprehensive kit for building e-commerce web app.

Adding objects to users in Django

I am very new to Django and I am trying to build a web app that users can add the books they read and see other users that read the same book. How can I do this in Django? What functions should I add?

Django Administration: Combine admin application model

I am using all auth and created another model ambassadors. I have currently the issue that Django Administration shows me these both models now in two different boxes. Does anyone know how to combine these?
Preview
My goal is to have
Accounts:
Email-Addresses
Ambassdadors
Use django plugin. It Reorder apps in admin index - this will allow you to position most used apps in top of the page, instead of listing apps alphabetically.
https://pypi.python.org/pypi/django-modeladmin-reorder

Django powered site and micro sites – do I have to create a separate project for each microsite?

I'm looking to build a Django website with the main site on example.com. On this domain, a user can register using an email and password and start writing blog posts at example.com/blog. Admins will be able to login into the Django Admin to alter posts and change content on the other pages of example.com.
The website will have one microsite each year on subdomains, e.g., 2013.example.com, 2014.example.com, etc. Admins will be able to edit content using the Django Admin.
I'm going to deploy the Django project onto Heroku.
The question that I would answered is whether I should create a new Django app and Heroku deployment for each microsite and the main site? Or, whether I can create it all as one Django project?
The latter seems to make more sense to me, but unsure how I would go about it.

Filter data in django admin page

I have a django project, in one of admin pages I'm adding data to the table
And I want after I choose one of themes, in Students name will be only students enrolled for this theme. How I can filter them by theme name?
Django does not do this out of the box. One third-party package I often see recommended to accomplish this common task (as opposed to writing your own ajax to do it) is django smart selects.