-
Notifications
You must be signed in to change notification settings - Fork 67
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
adding rfc admin panel #39
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi master partner , I found some upgrades to do your RFC more easy to read and review
Only are suggestions
RFCs/accepted/0000-admin-panel.md
Outdated
- For point one, we can design a table with 3 columns. | ||
- First column have Admins | ||
- Second for users | ||
- Third for places | ||
Every column will have its own searcher and filter. | ||
Also, every column will have a button. That button depends on what the column is. For example. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, Master partner I was checking your RFC and find some upgrades that You may do:
- Under the line 10, You could put a nested list about the design of the table to be more easy to read
- For point one, we can design a table with 3 columns. | |
- First column have Admins | |
- Second for users | |
- Third for places | |
Every column will have its own searcher and filter. | |
Also, every column will have a button. That button depends on what the column is. For example. | |
+ In order to organize the information of the users, admins and places. | |
+ For point one, we can design a table with 3 columns. | |
+ First column have Admins | |
+ Second for users | |
+ Third for places | |
Every column will have its own searcher and filter. | |
Also, every column will have a button. That button depends on what the column is. For example. |
- Or You may do a table to be more descriptive
- For point one, we can design a table with 3 columns. | |
- First column have Admins | |
- Second for users | |
- Third for places | |
Every column will have its own searcher and filter. | |
Also, every column will have a button. That button depends on what the column is. For example. | |
**Admins** | **Users** | **Places** | |
------------- | ------------- | ------------- | |
(example) | (example) | (example) |
RFCs/accepted/0000-admin-panel.md
Outdated
- Users: we click the button and we will have 3 choices: | ||
- Edit user: this modal will allows you to edit the user | ||
- Ban user: with this, you can ban user and send to him/her an email in order to explain why | ||
delete user: you can send an email to the user explaining that her/him account will be deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another upgrades that You may do Its put a nested list about the users :
- Users: we click the button and we will have 3 choices: | |
- Edit user: this modal will allows you to edit the user | |
- Ban user: with this, you can ban user and send to him/her an email in order to explain why | |
delete user: you can send an email to the user explaining that her/him account will be deleted. | |
+ Users: we click the button and we will have 3 choices: | |
+ Edit user: this modal will allows you to edit the user | |
+ Ban user: with this, you can ban user and send to him/her an email in order to explain why | |
+ Delete user: you can send an email to the user explaining that her/him account will be deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No description provided.