Open maptastik opened 8 years ago
@lfgreenfield I think this would affect you the most of anyone else. Any thoughts or questions about this?
Ryan, I think this is a great idea. It makes sense. I just don't follow the steps to do this but would be interested in learning from you. Any chance we'd be able to sit down together and you could walk me through this process? Always iffy when it comes to using different branches.
Laura F. Greenfield lfgr225@g.uky.edu (859) 361-8474
University of Kentucky Lexington, Kentucky Pursuing B.A. in Geography Oakland Farm Trees Paris, Kentucky www.oaklandfarmtrees.com
On Thu, Oct 15, 2015 at 12:33 AM, Ryan Cooper notifications@github.com wrote:
@lfgreenfield https://github.com/lfgreenfield I think this would affect you the most of anyone else. Any thoughts or questions about this?
— Reply to this email directly or view it on GitHub https://github.com/LexHousingStudies/LexHousingStudies.github.io/issues/4#issuecomment-148278506 .
@lfgreenfield Yeah, sorry if the steps aren't super clear. I was falling asleep while writing them. But let's meetup and walk through this, for sure.
What
We should move each map to its own individual project repo a la grapi-2013 or the daniels-sales.
Why
Currently several of our maps exist as directories in this repo. That's fine, but there are two slightly different types of content within this repo now.
Being in the same repo means that a change to either a map or a the website means syncing the entire repo. There's just a lot going on in this repo that could potentially result in conflicts. I think it would be better if each map were it's own individual project repo and this repo would be solely for the website. This would have the added benefit of making the code for individual maps easier to share. For instance, if someone wants to fork our abandonment map, they are going to get all the other maps and our website code.
How to do this
gh-pages
branch.gh-pages
branch the default branch