File naming conventions and directory structure for project

[brendam]

Need to know

1. where page markdown files should be put - for example do the projects go in a /projects/ directory if we decide not to have them date based?
2. where images should be put
3. how 'normal' content files should be named
4. how files that are date based (like news/blog items) should be named

[klepas]

This is high priority for templating stuff to proceed.

[cmrn]

I agree that projects shouldn't be date based. I would agree in putting them in projects/ - _posts should be date-based dynamic content only I think, whereas a single project page would evolve over time. News, events, etc should go in _posts/news/<article>, _posts/events/<article>, etc where <article> is of the form 2013-10-20-short-title.md.

[brendam]

Drafted page on wiki - https://github.com/makehackvoid/makehackvoid.com/wiki/Content-directory-structure

@klepas if you are happy with that page, you can close this issue

[devdsp]

I'm not convinced the website itself needs to have projects on it. I'd defer that to a wiki.

[B0073D]

Perhaps a showcase of some sort instead? Or a feed from the Wiki?

On Mon, Oct 21, 2013 at 10:25 AM, Adam Thomas notifications@github.comwrote:

I'm not convinced the website itself needs to have projects on it. I'd
defer that to a wiki.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-26685757
.

Sincerely,

Tim Suess

Alternative Thought
*
*
www.B0073D.com

[cmrn]

My thoughts were that project collaboration / in progress info should be on the wiki, but "publishable" info should be on the website (i.e. once the project is complete). I think it would be good to have some examples of projects that have been done at MHV on the site.

[devdsp]

A 'portfolio of selected works' would be great.

Here's a couple examples:
http://www.thijsrijkers.nl/gallery-category/selected-works/#suicide-machine
http://www.mikeestee.com/portfolio/

[klepas]

@brendam Figure you mean https://github.com/makehackvoid/makehackvoid.com/wiki/Content-directory-structure

That’s fine.

Re projects, I agree with @cmrn. We can showcase some completed projects on site while linking to wiki for the full thing. This leaves the “blog” — I think best used as a place for official MHV news and cool things members want to share — wips on their project, etc.

So, and an index page for the projects… I think we can do nice things here perhaps with D3 to link between different categories of things (electronics, mechanics, art, materials, programming language, …) or whatnot.

As for pages for projects themselves: besides giving people the chance to tap out something in MD we can encourage pretty pictures, callouts and multi-column typography, links to in-progress blog posts, some more D3 magic?, …

🐙

[klepas]

Thinking — can merge some of the community pages together to simplify the IA?

[cmrn]

@klepas This was discussed tonight at MHV, and I've documented what we've come up with at https://github.com/makehackvoid/makehackvoid.com/wiki/Information-Architecture

With that I think this issue can be closed.

[klepas]

Looks good. Cheers.