#Maptime Seattle

MaptimeSEA is the Seattle branch of the international Maptime community. Together, we learn and explore mapping technologies through tutorials and other meetups. We organize and teach under these major principles:

1. No Map Left Behind. You will never leave a meeting without completing the tutorial at hand. We try our best to make no assumptions of prior knowledge when introducing new technologies.
2. Free. All of our meetings are free.
3. Powered by interest. We teach what people want to learn. Our curriculum is ever-evolving and intended to focus on what's newest and most prevalent to right now.

#Stay Connected

Meetup. All of our meetings and events will be posted on our meetup site. Here you can RSVP for upcoming meetings and ask questions of your fellow mappers.

Twitter. We also have a twitter account @MaptimeSEA where you can follow our every move. Say hello to us!

Email. Questions? Send us an email at maptimesea@gmail.com to get in touch.

Survey. Our tutorials are structured around what you want to learn. Fill out our survey out even if you haven't attended a meeting to express what you're interested in learning! bit.ly/maptimesea_survey

#Our Tutorials

We are trying our best to post tutorials so anybody can learn from them. We'll be using resources from MaptimeHQ as well as writing our own, which can be viewed on the website.

Updating this website

Assumes you have git@github.com:MaptimeSEA/maptimesea.github.io.git cloned on your local machine.

1. pull down all recent changes from master: git pull origin master
2. checkout a new branch, git checkout -b BRANCH-NAME
3. add a new file under _posts/ with the proper date formatted file name YYYY-MM-DD-NAME.markdown
4. add the proper YAML to the top of the new file (copy paste from another file)
5. add all the stuff, make changes, do your thing
6. add file to local git: git add FILE-NAME.markdown
7. commit file with note: git commit -m 'NOTE ABOUT CHANGES
8. push changes to new remote branch: git push origin HEAD (actually write the word HEAD in all caps)
9. make a pull request from your branch into master on github.com