Perceived Problem

• Currently, a lot of times we end up needing to manipulate data directly through the database (adding languages, manually updating a user's status, etc.)
• This is potentially error-prone
• Previously, I had built a nice and simple admin interface accessible to administrators within the Journaly app but this was in the old codebase and was not brought over. The entire codebase is of course much different now but, still, high-level design and patterns are already in place

Ideas / Proposed Solution(s)

• Rebuild Jadmin!
• Not only is this more convenient, it allows us to make sure that database operations are actually using our code paths which should hopefully be less error-prone, improves testability, but also this could be extended to be used by moderators for a specific set of actions (un-publishing a potentially problematic post/comment/etc for review, for example)