-
Notifications
You must be signed in to change notification settings - Fork 310
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
create /projects page #113
Comments
👍 I like the idea using GitHub as a CMS. It will encourage better use of existing descriptor fields (e.g. name/description/members) and probably cause us to create some standard sections in our readme files (which can be parsed for the CMS like functionality mentioned above). |
+1 |
Maybe YAML instead of JSON? Easier for non-technical folks to read and edit. |
👍 to the idea, and 👍 to YAML I guess that's :+2: then |
YAML is fine. And +1 to @jgrevich's idea about standard sections in READMEs. |
It looks like this will be addressed by https://github.com/18F/Dashboard |
I like this idea a lot -- though if it's being covered by Dashboard, then this can be closed. If it should have an analogue here of some sort, let's open this back up. |
For each project that has a signed IAA:
JSONYAML blob pulled in from somewhere...use GitHub as a CMS.The text was updated successfully, but these errors were encountered: