-
Notifications
You must be signed in to change notification settings - Fork 970
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
How should the levels of government be laid out #75
Comments
While it's good to recognize this structure, I don't know that it covers the full range, either. See #21. I imagine that, down the road, it would be nice to have some sort of tagging/filtering system for level, location, and maybe even focus of the organization. |
No, it's definitely not an exhaustive list, but just 2 possible top level headings. The civic hacker folks may want some distinct levels too ... |
I'm definitely learning it's a lot more complex than how we organized it originally. Agree @nschonni that we may end up needing to make distinctions between civic hackers, too. Let's keep watching as groups trickle in and definitely dream up a better way to showcase all the orgs. |
Now's definitely the right time to start this discussion, although I'd think we'd want to hold off a bit before making any changes. The question I keep asking is "what are we trying to solve for?"
I was thinking initially that top level should be country, and subdivide from there, but spaces + YML is going to be a big headache for the uninitiated. Only reason US is split up like it is, is just because of size, which I immagine civic hackers may soon need to be split as well. |
Added Special District in order to add Cleveland Metroparks, which I know isn't common, but we didn't fit in any other category. "Local" might be a more flexible category. |
💡 like #101 we could add a folder with specific frontmatter prose:
media: "images"
metadata:
_orgs:
- name: "layout"
field:
element: "hidden"
value: "org"
- name: "github"
field:
element: "text"
label: "GitHub org"
value: ""
type: "text"
- name: "fullname"
field:
element: "text"
label: "Full Name"
value: ""
type: "text"
- name: "description"
field:
element: "textarea"
label: "Description"
value: ""
- name: "categories"
field:
element: "multiselect"
label: "Org Type"
placeholder: "Create or choose"
options:
- name: "Federal Government"
value: "fed"
- name: "Civic Hacker"
value: "civic"
- name: "City"
value: "city"
- name: "country"
field:
element: "multiselect"
label: "Country"
placeholder: "Create or choose"
options:
- name: "United States"
value: "fed"
- name: "Canada"
value: "canada"
alterable: true I think using a JSON file for the Countries would make more sense https://github.com/prose/prose/wiki/Prose-Configuration#select--multiselect |
Just to reopen this, how about this?
fwiw subnational is already used by Open Gov Partnership[2] References |
And lastly, could be optional. array below country, the renders like current, but if it's hash, new render type |
Not to promote silos but ...
There is currently a slight disconnect with US splitting between Federal, State, county, and City vs. the rest of the world.
The text was updated successfully, but these errors were encountered: