Automation w/o code changes?

[AbhiAgarwal]

@grungerabbit I have some ideas on how to automate all this without ever changing any of your code

people: Lets just use the API to generate _eboard, _alumni in the people perspective. This would just be a job that runs in the background that literally just generates all the .md files.

projects: Lets use your _project to put all the things into the API? And then from there we'll go reverse and generate the _projects folder automatically.

For featured lets think of something else. I'd love to get this done soon - just to save hassle going forward. This won't be too difficult to achieve. It'd be awesome to not change any of the code here as well.

[ethanresnick]

@AbhiAgarwal I also really want to do this! (In fact, when modeling the data for the API, @grungerabbit and I had automating Ship in mind, which is why Project already already has a featured field!)

Maybe you can tackle it on Wednesday, once all the API login works?

My only suggestion would be to start by getting the Projects into the API, both from Ship and the Demo Days site. Only then would I worry about the Team section; we're going to bring the team page onto the main site eventually, so recoding it for ship, only to scrap that code down the line, doesn't seem like as high a priority.

Also, as far as priorities go, we have more programming talent then we do design talent on infrastructure right now, so it might make sense for you to write this code alone so that Cheryl's free to work with @maxdumas on designing the intranet flows. But I'll let you guys work all that stuff out with Max.

[AbhiAgarwal]

Perfect. I definitely agree with you. I'll do it alone on Wednesday @ethanresnick. I'll start working on the projects first as well!

[grungerabbit]

projects fixed in #24 :D

The people part of this issue may or may not belong on Ship -- we could generate with more data entry, or on techatnyu.org

[ethanresnick]

Note: this requires us to first solve https://github.com/TechAtNYU/api/issues/85 and https://github.com/TechAtNYU/api/pull/75