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

Discuss whether we want to keep the Racial Equity Data Resource Hub separate from or integrated into the Equity Data Handbook #12

Open
AHolder1 opened this issue Aug 13, 2024 · 1 comment
Labels
question Further information is requested

Comments

@AHolder1
Copy link
Collaborator

Discuss whether we want to keep the Racial Equity Data Resource Hub separate from or integrated into the Equity Data Handbook

@AHolder1 2 cents - either will work.

  • I can see benefit in merging all things into one source to keep things simple and so folks can bookmark 1 link instead of 2. Also - I think it could be valuable to link resources to pages they relate to at the bottom and/or adding everything to the Resources page. If we merge tools into the Handbook, we can include screenshots of each tool, with short descriptions and links, so folks know what they're navigating to (sort of like the Layer Guide of the Tribal Water Data Map Manual).

  • If we decide to keep the resources separate - we might want to work on adding metadata (or something?) - when all filters are off, none of the Tool Names, Creators, Descriptions show up on the little squares below the filter box...so it looks like nothing is really there - but if you click on things a tool will show up. Or maybe it's user error and I just don't know what's happening. ha!

@AHolder1 AHolder1 added the question Further information is requested label Aug 13, 2024
@AHolder1
Copy link
Collaborator Author

Decision from co-working: Can't make the decision now - circle back with EJRT Data Subcommittee during feedback process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant