CodeForTucson / codefortucson-site

Current Code for Tucson website
http://www.codefortucson.org
GNU General Public License v2.0
3 stars 8 forks source link

Create Project Content Type #20

Closed c5f closed 8 years ago

c5f commented 10 years ago

19 made me realize that we should find a way to standardize the way that projects are entered and rendered by the site. This will prevent our Stuff we've made section from turning into the Wild West and looking like a hackerspace WordPress blog.

A Project should have some information that is required like a name and a description, and some information that is optional like the project owner, media like presentations or PDFs, and hopefully a link to the repository.

Project
├── required
│   ├── description
│   └── name
└── optional
    ├── contact
    ├── media
    └── source code

I am not familiar enough with Jekyll to say whether custom content types are possible or easy enough to build, but I am confident that with a couple of quick Googles I can get enough information to close this issue one way or another.

meiqimichelle commented 10 years ago

We should be able to get most of what you're hoping with Jekyll front matter on 'blog' posts or a yml file, depending on how much info we're talking about. Jekyll can iterate over either one and create content. You can't enforce optional and required, but I don't think that's vital. For our purposes, commented instructions and/or an example to work from should suffice.

c5f commented 10 years ago

Agreed

meiqimichelle commented 10 years ago

Working on a draft implementation now. Will PR soon for your review and edit.

meiqimichelle commented 10 years ago

See PR #22