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

NoMongo: Figma User Portal: Organization Screen Violates The Figma Style Guide #3197

Open
palisadoes opened this issue Jan 7, 2025 · 30 comments
Assignees
Labels
bug Something isn't working feature request good first issue Good for newcomers GSoC Priority ui/ux issue related and being worked with the figma file of the Admin UI

Comments

@palisadoes
Copy link
Contributor

palisadoes commented Jan 7, 2025

Post a video of your work in the PR

Describe the bug

  1. Organization Screen Violates The Figma Style Guide

To Reproduce
Steps to reproduce the behavior:

  1. Style Related
    1. Login to the app as a User
    2. The figma guide is not followed fully

Expected behavior

  1. The screens shown must conform to Figma
  2. This must apply to the following where relevant:
    1. Users
    2. Admins
    3. SuperAdmins
  3. Tests must be written to ensure this does not happen again
  4. The CSS must be consolidated into this file using variables wherever possible
    1. src/style/app.module.css

Other

  1. The foundational work for this was completed in this PR:
  2. When in doubt about colors, take cues from other similar elements in this file and the PR mentioned in the issue.
    1. https://www.figma.com/design/dmKt00m9GVSeA1nebnkxql/Untitled?node-id=0-1&node-type=canvas&t=TPzfh1DE9IxjzsEe-0
  3. The desired single CSS file is:
    1. src/style/app.module.css
      1. Convert all code files to use this file.
      2. Delete all CSS files in this code path and below mentioned in the title. The src/style/app.module.css file must be the only source of CSS
  4. Use no CSS in:
    1. assets/css/app.css
  5. Use variable names that describe the function of the color and not the color itself. This will help with future attempts to having Dark Mode.
    1. For example --search-button-bg is much better than --light-blue
    2. NoMongo: Fix Stylesheet in Anticipation of Dark Mode #3296
  6. When refactoring modals, please refer to this PR that has created a standardized design patter for them.
    1. Updating to NEW COLOR SCHEME #2984
  7. Remove all references to HTML color codes in the files you edit except in src/style/app.module.css
  8. Buttons, and dropdowns must only have shadows when there is a mouse hover. Their color must not change
  9. Search boxes must only have shadows when selected

Screenshots
If applicable, add screenshots to help explain your problem.

image

Additional details
Add any other context or screenshots about the feature request here.

  1. Background color guide - Use these instead of those that may be different in sample pages below. Our Figma design is not consistent
    image
  2. Update as per Figma
    image

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

@palisadoes palisadoes added the bug Something isn't working label Jan 7, 2025
@github-actions github-actions bot added feature request ui/ux issue related and being worked with the figma file of the Admin UI unapproved good first issue Good for newcomers labels Jan 7, 2025
@NishantSinghhhhh
Copy link
Contributor

@palisadoes , Is this the same issue That I was assigned yesterday?

@swastikCommits
Copy link

Can I work on this issue?

@khushipatil1523
Copy link
Contributor

can i work on this issue

@arpit-chakraborty
Copy link
Contributor

can i work on this @palisadoes

@Abdul-Moiz31
Copy link

Hey ! can you assign me this issue ?
Woud love to work on this @palisadoes

@khushipatil1523
Copy link
Contributor

@Cioppolo14 @palisadoes
I noticed that the issue was unassigned after being assigned, and I just wanted to let you know that I’m very eager to work on and solve it as fast as possible. I’d be grateful for the opportunity to contribute and help with this. can you please reassigned to me

@Abdul-Moiz31
Copy link

Hey @palisadoes ! Please can you assign me this issue , i'd be grateful for this opportunity and Woud love to work on this ?

@Cioppolo14
Copy link
Contributor

@khushipatil1523 You have been assigned. Thanks for checking in.

@palisadoes
Copy link
Contributor Author

We created an this issue to do basic changes to the CSS colors for consistency

The resulting PR created a comprehensive design system for the entire app. This was unexpected. The approach was a long term goal that became immediately implementable. We had to act promptly.

We have just merged the PR. There will be a follow up PR to adjust some colors as the Figma design has lettering that is sometimes hard to read.

When this is done we'll need your assistance to merge the screens into the develop branch with this issue.

If your screens have not been affected, then you should use the new methodology to refactor them.

This is an extraordinary circumstance. I hope you will appreciate the decision.

@palisadoes
Copy link
Contributor Author

Please proceed. The changes mentioned previously are mostly in components

@khushipatil1523
Copy link
Contributor

Please proceed. The changes mentioned previously are mostly in components

@palisadoes I’m actively working on it and plan to submit the PR by tomorrow or the day after. Thank you for your understanding.

@khushipatil1523
Copy link
Contributor

@palisadoes Apologies for the delay. I was unable to log in , because of which im not able to test the changes. However, I have now completed all the required work, ensuring it meets the constraints and aligns with the Figma portal design.

I have put in a lot of effort on this, and I would really appreciate it if you could reassign the issue to me. I will make sure to raise the PR today because all work was done.

Copy link

github-actions bot commented Feb 8, 2025

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

@github-actions github-actions bot added the no-issue-activity No issue activity label Feb 8, 2025
@palisadoes
Copy link
Contributor Author

Unassigning. Inactivity

@github-actions github-actions bot removed the no-issue-activity No issue activity label Feb 8, 2025
@khushipatil1523
Copy link
Contributor

@palisadoes I have made significant progress on this issue. However, due to login issues and the lack of sample data, the organization cards are not displaying on the user dashboard. I have also attached a screenshot for reference.
As a result, I have been unable to fully test my changes and complete the task on time. I had previously messaged you regarding this issue. Could you please reassign this task to me? I am just waiting for the sample data issue to be resolved so that I can test my updates.
I would appreciate the opportunity to complete this work.

Copy link

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

@github-actions github-actions bot added the no-issue-activity No issue activity label Feb 18, 2025
@palisadoes
Copy link
Contributor Author

@khushipatil1523

  1. Logins work and sample data can be imported.
  2. https://docs-api.talawa.io/docs/installation#importing-sample-data-1

Are you still working on this?

@khushipatil1523
Copy link
Contributor

@palisadoes I will surely raise the PR today.

@github-actions github-actions bot removed the no-issue-activity No issue activity label Feb 19, 2025
@khushipatil1523
Copy link
Contributor

@khushipatil1523

  1. Logins work and sample data can be imported.
  2. https://docs-api.talawa.io/docs/installation#importing-sample-data-1

Are you still working on this?

Hello Sir,

I tried logging in using all user email IDs from the sample data, but I am unable to see any organization on the user portal. It only shows "No organization found." I think this feature is broken, as the user portal is unable to fetch the organization in the develop-postgres branch.

@palisadoes
Copy link
Contributor Author

You can load sample data here and test.

Try that and let me know.

@khushipatil1523
Copy link
Contributor

You can load sample data here and test.

Try that and let me know.

No sir,
its not working i think we need Update query and mutations according to the recently migrated develop-postgres branch of talawa-api for user portal also

@palisadoes
Copy link
Contributor Author

Are there open issues for this?

@khushipatil1523
Copy link
Contributor

Are there open issues for this?

yes sir ,here is open issue link #3565

@palisadoes
Copy link
Contributor Author

Are there open issues for this?

yes sir ,here is open issue link #3565

It's merged. You can start

@khushipatil1523
Copy link
Contributor

Are there open issues for this?

yes sir ,here is open issue link #3565

It's merged. You can start
Got it sir! I'll complete this ASAP and keep you updated.

@palisadoes palisadoes changed the title Figma User Portal: Organization Screen Violates The Figma Style Guide NoMongo: Figma User Portal: Organization Screen Violates The Figma Style Guide Feb 24, 2025
@khushipatil1523
Copy link
Contributor

@palisadoes While updating test cases, I noticed that clicking the "Join Now" button is not working. when i click on "Join Organization," it shows an "Error Occurred" message. After checking, I found that there is no mutation in the backend for joining an organization. All styling has been done according to the Figma style guide, but the "Join" button feature is broken. Should I cover this in this PR as well?

@palisadoes
Copy link
Contributor Author

Yes

@khushipatil1523
Copy link
Contributor

Yes

Sure, sir. I will work on it immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working feature request good first issue Good for newcomers GSoC Priority ui/ux issue related and being worked with the figma file of the Admin UI
Projects
Status: Backlog
Status: Backlog
Development

No branches or pull requests

7 participants