design a basic (non-Django admin) admin interface

[mhl]

(We probably need a better name for that...)

I'm slightly in two minds about this. The user need is for a more user friendly interface for configuring and maintaining a YNR site without needing to edit files on the server or be a Django developer. We could attempt to customize the Django admin interface to do this, but we suspect that this will turn out to be increasingly difficult as we try to improve the user experience. (Anecdotally, at Djangocon EU I heard a few people say that their projects had run into problems by trying to do too much in the Django admin interface, for what that's worth.)

So, the idea of this issue is that rather than putting a lot of work into customizing the existing Django admin interface, we should start building a new interface (like that of FMS or Alaveteli) for common settings and administration tasks. This might ultimately include, for example:

• A "settings" tab for customizing basic site settings create a settings table for site-specific configuration in the database #943
• A "parties" tab for adding, deleting and updating parties (including by update from EveryPolitician / Wikdata / CSV upload / Popolo JSON upload)
• An "elections" tab for adding, deleting and updating parties (including by CSV / Popolo JSON upload)
• An "elected bodies" tab for
• User management

[jf1]

The people doing the work should make such decisions but fwiw, having only
seen a little of the Django admin interface, I think this is a sensible and
worthwhile approach.

Once the additional code and data fields are in place, sh/could a "parties"
tab allow/enable selection of a "default party description" to deal with
#823

On 25 May 2016 at 10:48, Mark Longair [email protected] wrote:

(We probably need a better name for that...)

I'm slightly in two minds about this. The user need is for a more user
friendly interface for configuring and maintaining a YNR site without
needing to edit files on the server or be a Django developer. We could
attempt to customize the Django admin interface to do this, but we suspect
that this will turn out to be increasingly difficult as we try to improve
the user experience. (Anecdotally, at Djangocon EU I heard a few people say
that their projects had run into problems by trying to do too much in the
Django admin interface, for what that's worth.)

So, the idea of this issue is that rather than putting a lot of work into
customizing the existing Django admin interface, we should start building a
new interface (like that of FMS or Alaveteli) for common settings and
administration tasks. This might ultimately include, for example:

• A "settings" tab for customizing basic site settings create a settings table for site-specific configuration in the database #943
  create a settings table for site-specific configuration in the database #943
• A "parties" tab for adding, deleting and updating parties (including
  by update from EveryPolitician / Wikdata / CSV upload / Popolo JSON upload)
• An "elections" tab for adding, deleting and updating parties
  (including by CSV / Popolo JSON upload)
• An "elected bodies" tab for
• User management

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#944