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

create /projects page #113

Closed
quepol opened this issue Jul 17, 2014 · 7 comments
Closed

create /projects page #113

quepol opened this issue Jul 17, 2014 · 7 comments

Comments

@quepol
Copy link
Contributor

quepol commented Jul 17, 2014

For each project that has a signed IAA:

  • JSON YAML blob pulled in from somewhere...use GitHub as a CMS.
  • Each project has a description and a REALLY GOOD "WHY?" / mission statement.
@jgrevich
Copy link
Member

👍 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).

@meiqimichelle
Copy link
Contributor

+1

@aaronsnow
Copy link
Contributor

Maybe YAML instead of JSON? Easier for non-technical folks to read and edit.

@konklone
Copy link
Contributor

👍 to the idea, and 👍 to YAML

I guess that's :+2: then

@quepol
Copy link
Contributor Author

quepol commented Jul 20, 2014

YAML is fine. And +1 to @jgrevich's idea about standard sections in READMEs.

@gbinal
Copy link
Member

gbinal commented Aug 29, 2014

It looks like this will be addressed by https://github.com/18F/Dashboard

@konklone
Copy link
Contributor

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.

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

No branches or pull requests

6 participants