Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

πŸ‘¨πŸ»β€πŸ’Ό Build JAdmin: Journaly Admin Tools #747

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

robin-macpherson
Copy link
Contributor

@robin-macpherson robin-macpherson commented Dec 22, 2021

Description

Issue:

(Currently a POC)

  • Builds an initial set of admin tools: JADMIN ✨
  • Also updates seed data so that users have names

Subtasks

  • I have added this PR to the Journaly Kanban project βœ…
  • Build out the initial POC
  • Set up the users query used here to be able to access each user's email address (currently we have that field hidden for all but the currentUser for general use cases outside of these admin tools)
    • Check for more optimized solution
  • Build page for managing a user's posts
  • Create basic "actions" that can be performed
    • Users: Issue warning?
    • Posts: Flag for admin review?
  • Handle pagination for the table
  • ...

Deployment Checklist

  • 🚨 Publish new j-db-client version and update in both web and j-mail
  • 🚨 Deploy migs to stage
  • 🚨 Deploy code to stage
  • 🚨 DEPLOY j-mail to stage
  • 🚨 Deploy migs to prod
  • 🚨 Deploy code to prod
  • 🚨 DEPLOY j-mail TO PROD

Migrations

If your PR doesn't involve any changes to the database, you can delete this section. If it does, briefly describe how it needs to be applied. Some common things you might mention are:

  • Does the migration need to be applied before or after deploying code?
  • Is applying the migration going to necessitate downtime?
  • Is there any SQL or backfill logic that has to be run manually?
  • Are the DB changes high risk in your estimation? Should a manual DB snapshot be taken before applying?

Screenshots

image

image

@vercel
Copy link

vercel bot commented Dec 22, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

πŸ” Inspect: https://vercel.com/journaly/journaly/A3S3Fzq8fkS1zjkesAPhjZEESktZ
βœ… Preview: https://journaly-git-build-jadmin-journaly.vercel.app

@robin-macpherson
Copy link
Contributor Author

@Lanny just FYI this was intended to be a (very WIP) Draft, but accidentally opened it and it seems you can't go back after that πŸ˜‘πŸˆ

@robin-macpherson robin-macpherson added backend Backend work! DO NOT MERGE Don't merge this! FEATURE New feature or request frontend Frontend work! jadmin labels Dec 23, 2021
@robin-macpherson robin-macpherson changed the title Build JAdmin: Journaly Admin Tools πŸ‘¨πŸ»β€πŸ’Ό Build JAdmin: Journaly Admin Tools Dec 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend work! DO NOT MERGE Don't merge this! FEATURE New feature or request frontend Frontend work! jadmin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

πŸ‘¨πŸ»β€πŸ’Ό Rebuild "Jadmin"
1 participant