Website Admin Panel Design

[austinEng]

We need to design an admin interface so that staff can easily update the parts of the website that frequently change.

Some initial things that come to mind:

• There are some "large" announcements with images and links and stuff. And there are some "small" announcements that are just links. Should these be separate entities in the admin panel?
• What should the format of the admin panel be?
  • Should it just be a list of editable items?
  • When you click the item you get a form to update stuff?
  • Should the form be a popup? a sidebar? a separate page?
• Certain types of data "expire" (dates pass). Is there a good way to build that in so that the admin can create events or announcements that are no longer displayed after a certain date?
  • (we probably don't want to completely delete them in case the admin wants to repost these announcements)
• Should items be "resortable"? i.e. You can change the order of announcements?
  • If so, what is a good interface for doing that? ex.) Drag and drop in a list?
  • What does the interface look like for doing this? Should it be separate from the view that shows all the items? If it is unified (like a list display where things can be moved), how does the admin save the resorted changes?
• How do we make sure the admin knows what he/she is changing / saving before it is actually published?

Long Term:

• We'll hopefully eventually allow different ministry teams to create / update their own pages. How should this be done? The text editor used on Medium is actually open source https://yabwe.github.io/medium-editor/. Is this feature-complete and sufficient?

• Ideally there should be multiple user "roles" which define who has access to update what pages. How should this be defined? How does a "master" admin manage these roles?

[austinEng]

@estheryjeon This will eventually need to be done, but you don't have to do it now if you're focused on the main part of the website.