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

1225 - Remove staff faqs logic from dashboard #1271

Merged
merged 2 commits into from
Dec 17, 2024

Conversation

Meri-MG
Copy link
Contributor

@Meri-MG Meri-MG commented Dec 17, 2024

🔗 Issue

#1225

✍️ Description

Removing Faqs logic under the staff dashboard since we already have a separate /faq path and logic for the organizations.

📷 Screenshots/Demos

Screenshot 2024-12-17 at 23 19 11

@Meri-MG Meri-MG changed the title Remove staff faqs logic from dashboard 1225 - Remove staff faqs logic from dashboard Dec 17, 2024
@jmilljr24
Copy link
Collaborator

@Meri-MG This change should be for the adopter/foster dashboard not the staff dashboard. If you are in the Alta organization, log in as an adopter [email protected] and view their dashboard. Because the adopter can view the faq's via the link at the top of the page, viewing the faq's within the adopters dashboard is redundant.

We want to just remove the side nav link in the adopters dashboard and the associated code that was being used for that.

@Meri-MG Meri-MG force-pushed the 1225-remove-dashboard-faq-logic branch from 472d2cd to 5e45d18 Compare December 17, 2024 19:11
@Meri-MG
Copy link
Contributor Author

Meri-MG commented Dec 17, 2024

done ✅ should have seen from the page images at least

Copy link
Collaborator

@kasugaijin kasugaijin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Meri-MG thank you!

@kasugaijin kasugaijin merged commit 557f806 into rubyforgood:main Dec 17, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants