administration tasks in pleroma-fe #178

Open
opened 2022-10-08 13:06:25 +00:00 by nbsp · 2 comments
Contributor

so, i'll be able to take a crack at this once i'm back home, but i need to think about the implementation details:

  • probably a floating window like the settings view
  • different tabs for users, reports, statuses, and settings
  • make it so only the settings require enabling database configuration! it's currently very annoying to not be able to approve users without enabling that setting
  • maybe a separate tab for emoji? it gets grouped into settings even though it has nothing to do with the config file
  • save button that doesn't give you a 500 error when it's done

anything else i forgot?

so, i'll be able to take a crack at this once i'm back home, but i need to think about the implementation details: - probably a floating window like the settings view - different tabs for users, reports, statuses, and settings - make it so only the settings require enabling database configuration! it's currently very annoying to not be able to approve users without enabling that setting - maybe a separate tab for emoji? it gets grouped into settings even though it has nothing to do with the config file - save button that doesn't give you a 500 error when it's done anything else i forgot?
nbsp added the
Feature request
label 2022-10-08 13:06:44 +00:00

my personal view is that this sort of thing should go as a static page set in the backend instead of attached to a front-end

open to other takes on that

my personal view is that this sort of thing should go as a static page set in the backend instead of attached to a front-end open to other takes on that
Author
Contributor

maybe for actual configuration file things but i think banning users, handling reports, and adding emoji ("moderation" rather than "administration") make sense to be attached to a frontend

maybe for actual configuration file things but i think banning users, handling reports, and adding emoji ("moderation" rather than "administration") make sense to be attached to a frontend
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma-fe#178
No description provided.