cdp-frontend
cdp-frontend copied to clipboard
CouncilDataProject
Council Jargon Hints
Idea / Feature
The idea would be to create some sort of council action glossary and associated UI to give contextual/relevant hints to that jargon.
When any jargon is used (i.e. “voted out of committee”) there should be some UI/hints that explain what the jargon means in a human-readable way.
Use Case / User Story
As a local citizen who is not as well versed in local politics, I want to be able to understand city council jargon so that I can gain a better grasp of the implications and consequences of council actions/discussions.
Other Notes
I think the big crux of this idea is that it should not just be a static glossary that someone has to cross-reference while engaging in CDP material––these hints should be timely, relevant, and well-integrated into whatever experience they are in.
Additionally, this functionality/feature should be optional. If there is someone well versed in local politics they should have the ability to turn this off as a setting.
Finally, it's also really important that the glossary of definitions we create are genuinely "human-readable" and should be vetted/tested at least a few times with a wider variety of people. I think a good marker of success is if an elementary school or maybe a middle school-aged child could read/comprehend these definitions.
Strong agree!
I am tempted to say this is a "frontend only issue" however and should be transferred to cdp-frontend? Thoughts?
I'm tempted too.
The only thought I had was if in the pursuit of this feature being extremely "timely, relevant, and well-integrated" into whatever experience a person is engaging in there might be some element of a backend algorithm required to notify the frontend when a jargon hint is timely/relevant?
With a night of sleep, I suspect this could actually all be done in the frontend if desired, so we can probably move this idea to cdp-frontend if you still think that makes sense @JacksonMaxfield.
"timely, relevant, and well-integrated" into whatever experience a person is engaging in there might be some element of a backend algorithm required to notify the frontend when a jargon hint is timely/relevant?
Wouldn't this require us to actually host and serve the web app from our own servers? As a static web app this is why I say until future, this is frontend only.
Oh yeahh, I had totally forgotten that "cdp-backed" isn't necessarily a web server but a bunch of data processing algorithms correct?
If so then yes we can definitely move this to the frontend.
I like issue necromancy. I also really like this issue. I have no idea where to begin.