Proof of concept

Over the holidays I decided to throw together a simple proof of concept for the project. **Apologies for the terrible code** – I just wanted to hack something together that we could use as a basis for discussion.

## A Screenshot Would Be Nice:

![community viz](https://f.cloud.github.com/assets/1469659/1820015/8c6af45c-70c6-11e3-9f22-be9537f6d9b2.png)

## Getting member info

From the current README:

> …the problem lies in GitHub's API request rate limitations. The script above sends on initial request to get all members plus an extra request per member. But GitHub allows only for 60 requests per hour from one IP.

> Ways to work around it:

> 1. Do only show login/avatar at first, and load details en demand when the visitor clicks on it.
> 2. Make the visitor sign in with his GitHub account, to bump the rate to 5000 / hour
> 3. `<YOUR IDEA HERE>`

I actually don't think that we shouldn't use the GitHub API to pull in *member* info. Yes, we should dynamically load the org name, org location and the org owners – but I think that the community members themselves should use the 'fork and PR' method to request that they are added to the list. Here's some reasons why:

1. Dynamic loading may cause friction
	- Org owners would get emails from new community members being asked to add them to a team
	- Owners would probably have to create a dummy team for members that aren't associated with a specific project
	- Reviewing a PR and merging is a much nicer workflow for owners
2. GitHub profiles don't have bios so if we wanted to list a community member's skills it would need to be done manually anyway
3. Avoid the API request limit
4. Encourage community members to fork and PR – therefore teaching them key concepts of GitHub in the process

It would be great if would-be members could fork the repo and only have to add their username and skills to a single text file for review rather than fuck around with the HTML.

## Things that I've definitely missed / fucked up

- I'm not sure that I've conveyed *what* the site is very well. I don't think that '`OrgName` ❤ Community' really nails it and the description in the footer is quite lame.
- Missing a place to list an org's website and/or other social links (this should probably go with the org description)
- Org owner names should be displayed somewhere (possibly on avatar rollover?)
- It should be responsive
- Links to separate documentation for org owners and community members
- Extensive code commenting to aid remixing

## Other ideas

The prototype's site design is pretty basic. I'm hoping that @nrrrdcore or another designer might have the time to sprinkle some :sparkles: on it.

It would be great if there were some very simple mods that owners could make such as:

- Changing a single hex value to update the hue of all containers (and possibly font colours too)
- Using [Identicons](https://github.com/blog/1586-identicons) in some way to dynamically make sites different from each other. I experimented with scaling an identicon up, desaturating and heavy-blurring it (using `-webkit-filter:`) to make custom background gradients for headers, but it killed my CPU!