LOL.

what goes in humans.txt?

It has become clear lately that one of the most important roles we can play through Code for Maine is to connect the various fragmented hacker groups,universities, fablabs, governments, startups etc... around the state. We possibly have more capability in this regard because of the Code for America brand.
With that in mind, we've been discussing the need for a more robust platform that we can use to facilitate these connections. Initially, I had in mind a simple wiki created with gh-pages which would function as a subpage link from our landing page.
I already had an empty repo called "mainewiki" https://github.com/Code4Maine/mainewiki that I set up for a similar purpose a long time ago but never got around to deploying. I figured we could use this as our basic template and use the repo's "wiki" feature to easily add content via gh-markdown.- https://github.com/Code4Maine/mainewiki/wiki
But in the course of trying to find a way to embed our google calendar, I came across Octopress- http://github.com/imathis/octopress. It is described as an "an obsessively designed framework for Jekyll blogging. "
Does this seem like something we could implement? If so, should I forget about using "mainewiki" and create an entirely new repo based on a fork from Octopress? Or is there a way to copy over the Octopress files over to what I've already done?

So I just noticed that one of the repos I forked over to Code4Maine now has the URL for the domain- http://code4maine.org/opentransitprojects/
Does this mean all of our current Repo's will have a subheading on our new webpage? Thats fine by me, but I was wondering how we should proceed with adding a new directory for all the other hacker groups (i.e Hacker Club, Hack Portland, Maine Fablab etc...). Does it make sense to create a new repo and a wiki using gh pages markup?
Also we set up a group calendar at codeforamerica.org_09jjhoqlt2vrkh6r3ne8ko3flc@group.calendar.google.com
It includes html for embedding into blogs etc...

At this point, seems like the next thing we need is some content. @Cribstone if you could post those wireframes up I can start filling in the site!

Under the "Workshop" section I would like to display our projects as direct links to their respective repo's on our Github page. The question I have is how we can take multiple repo's we forked from other places and merge them into a new project, while still maintaining their original file structure.
For example, for our Public Document Scanning project I forked two different Repo's. One is forked from the DIYBookScanner project- https://github.com/Code4Maine/diybookscanner and the other is forked from an Open Source OCR app- https://github.com/Code4Maine/dochive. Now how do I go about merging both Repo's into a new project called "Public Document Digitization" (or something) without having to merge the DIYBookScanner repo which basically just includes hardware assembly instructions with Dochive which is software source code?

Here are two great examples of how other brigades are presenting their projects on their landing pages.-
http://codeforsandiego.org/ is closer to our current page in configuration, and we could do something similar by outlining broader campaigns under the "Priorities" sections while posting some of the more active projects as originally intended (where the OpenVehicleTracker link exists right now.
We can then link to a GoogleDoc or Uservoice account for new project ideas.

http://codeforphilly.org/ on the other hand is much closer to a full CMS system. If work on the remote collaboration app takes off, or our content starts piling up, then the philly CMS approach might be allow for more flexibility.

Currently, accessing the page means heading to http://code4maine.github.io/. Thoughts on registering a new domain name? codeformaine.org?

So you guys might've noticed me fumbling around with the branch editing feature over the past week. For the most part, I was having trouble setting up a local workspace but I eventually got around this by setting up a cloud9 workspace. This workspace should be accessible to team-members if you go to https://c9.io/cribstone/code4maine_github_com and request access. We can even code in real-time!
I managed to edit the main index.html file and added the basic copy. Now my biggest issue is how to add links and images akin to the standard brigade template at https://github.com/c4hrva/c4hrva-landing
When I compare the index files from both templates side by side there are significant differences and I'm not sure if they were based on different bootstrap templates to begin with or if I just need to make a few minor changes.
Can you do me a favor and take a look at either https://github.com/c4hrva/c4hrva-landing or https://github.com/codeforsandiego/codeforsandiego.github.com and let me know if I'm missing anything?

projects are buried right now. let's change that.