-
Notifications
You must be signed in to change notification settings - Fork 35
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
Provide list of all agencies on homepage #609
Comments
@mngardner @btalebian Thinking about how to implement this, it seems like it might be more useful if the list were grouped by topic, like the usa.gov page. We would need to implement a new taxonomy field, but how do you feel about something like this: |
@brockfanning - wow that is really cool. I like that very much - perhaps if we replicate that functionality, we wont have to link away from the site - we could reformulate that section on USA.gov to point inward to this new feature. Thanks! I like this direction. |
@mngardner Ok great - question: should this list be of the 116 agencies (/admin/structure/taxonomy/manage/agency/overview in the backstage) or the 439 agency components (/admin/content?title=&type=agency_component in the backstage)? |
@brockfanning - it should be the 116 list. |
@mngardner Ok, so then if you agree, I will start things off with a backstage change adding a new taxonomy field called "Topic" to the agency vocabulary. Then, once we've assigned a Topic to each of the 116 agencies, we can move forward with this frontstage feature. Does that sound good? |
@brockfanning - that sounds great. |
@mngardner @btalebian This addition to the homepage is available for testing on the dev-www site. Note that I only categorized a few random agencies, just to give you the basic idea. |
This was completed with #730. We still have the option of a topic-based selection tool. |
As a requester with no knowledge of government agencies, I need to be able to get to a list of all agencies while on the homepage, to help me figure out which agencies might be applicable to my request.
The text was updated successfully, but these errors were encountered: