Breaking up #6 per #8. 🍦

Import existing pages from current Maptime site, e.g. http://maptime.io/about

Should probably take the form of subdirectories like { site.baseurl }/about.

Breaking up #6 per #8. 🎃

There should be a page that aggregates and links to all the tutorials we have and associated materials so they can be in one spot!

I find that when working with gh-pages sites it's made a lot easier to delete the master branch and make gh-pages the default branch. It makes it a lot easier to submit PRs for the right branch and may make things less confusing for GH newbies.

Continents are white, as are the nav items. Given the zoom level on page load they kinda disappear into the map.

Add a category key to the tutorials.yml and sort the lessons-resources page into topic areas.

Breaking up #6 per #8. 🏊

Check out how wherecamp.org works. The main page is a list of local groups around the world, and it's all parsed from a geojson file that includes lots of specific metadata. Here's what their geojson looks like: https://raw.githubusercontent.com/reidab/wherecamp.org/gh-pages/wherecamps.geojson

That could be awesome

Need to get the Code of Conduct up on the new website.

Breaking up #6 per #8. 🐦

What do you think about a /docs directory that outlines the different variables we've developed for the Front Matter? We can add the built-in variable published: false so it only shows up while you're hacking on the site.

While developing the site just add the unpublished flag to the Jekyll command:
jekyll serve -w --unpublished.

It can be really helpful when working on a site as a team where each individual might not know all of the options/variables that are available to them.

chapter titles stretch beyond popup wrapper

Breaking up #6 per #8. 🌴

@bethschechter do you know which image this was supposed to go to? http://maptime.io/about/

links to Stamen

• No organizers for MaptimeSTL?
• Remove moreInfo property, replace with:
  • website (url)
  • meetup (url)
  • github (url) -- represents either a Repo in a personal account, or a chapter Org account
• Remove duplicate information
  • contact vs. organizers
  • title vs twitter -- Are these always the same?
• Update /chapters/index.html templates to use updated chapters.json
• Footer is whacky on chapters page

keep each page banner interesting. let's swap these out. prob need to adjust the yml and layouts and then put images in a common folder

• home
• about
• contact
• resources

Chapters need to be sorted alphabetically on /chapters. Unsure if this needs to be done to the json or if it can be done with jekyll.

We have chapters.json figured out -- it feeds the map and chapters listing.

Two methods for creating chapter websites have also emerged:

1. Creating a chapter directory under the official maptime site (maptime.io/atlanta)
2. Creating a separate website using the starter repo (github.com/maptime/atlanta)

Both options will result in the url maptime.io/chaptername.

@alan and I agree that the first option is our preference as it allows us to automatically aggregate posts from chapters. In any case we should move README.md out of /chapters to the root directory and codify the process of starting a chapter.

This will require some architecture changes for translations. @abenrob has some experience here ;)

Can we start with the main pages? Blog posts should prob remain in native languages.

http://nicoespeon.com/en/2013/04/building-a-multinlingual-jekyll-blog/

Looks like the loops within the twitter and open graph descriptions aren't being evaluated. This would prevent a description for a page from showing up automagically on twitter/facebook when you post a link (I'm pretty sure).

This is all going down in /includes/head.html.

<meta name='twitter:description' content='{{page.content | markdownify | strip_html | trim_spaces | truncatewords: 30 | escape | replace:"'","&lsquo;" }}' />
  <meta property='og:description' content='{{page.content | markdownify | strip_html | trim_spaces | truncatewords: 30 | escape | replace:"'","&lsquo;" }}' />

We probably can't inject the entire page's content, rather have a description variable at the top of each page/post.

Hi, I'm trying to make the maptime madison website from the starter and would like to have privileges to have a repo for it and privileges to upload files to it if possible. Thanks!

It looks like we're currently maintaining two separate files for maptime chapters. I moved the file chapters.json over to _data so we could access maptime chapters information with Jekyll expressions. I had to change the extension to JSON rather than GeoJSON because Jekyll only supports YAML and JSON. Leaflet was still able to map the features despite having a JSON extension.

I see a recent commit 7f05b5e updated information on chapters/map/maptimes.geojson, and the readme is still referencing this file. I suggest that we move the README into /chapters and reference /_data/chapters.json for adding new chapters. We could then remove the map subdirectory entirely.

FYI @geografa mentioned that you may need to update your Jekyll to version 2.4.0 in order for _data/chapters.json to work properly.

cc @almccon @geografa

You guys need a funky favicon!

Maybe a nifty looking map marker, or the m from the maptime logo.

There should be a place where maptimers can post jobs or where people who are hiring can find maptimers!

Current /chapters page on chapters branch is a mess. It has its own template and scripts are inline. We should:

• bring scripts out as includes
• bring css out as includes
• use default as the template
• feed GeoJSON into page to populate chapter listing

Hacking on our chapter page

• Header image
• First blog post -- recap of first meeting?

cc @landonreed

In config.yml we can create our own tag to identify the post's excerpt. Wordpress made this famous with the <!--more--> tag, which can be replicated with excerpt_separator: <!--more--> in Jekyll. All you have to do is drop this tag into your markdown posts where you want to cut off the post to display as a teaser. This can be helpful, especially for mobile users on narrow screens, if a user wants to skip a post without scrolling through it.

Clicking the title of the post, or a "read more..." link would take them to the full post.

This could also be useful for Twitter/Facebook description meta tags. Last week I added a description variable to the front matter, but we could ditch that and just use {{ post.excerpt }} instead.

Would like to clean up the stylesheets a bit. In order:

• Modularize our stylesheets
• Generate a styleguide
• OOCSS?

Do we intend for that grid background to show through all the content?

to announce new website! preferably with an infinitely recursive image of a computer screen with a the website showing a computer screen with the website showing a computer screen with the website...

• OpenStreetMap and the Ada Initiative #osm4ada
• Maptime is growing up :)

As a way to sort chapter blog posts by chapter. @reidab already updated the site so that categories are enabled. cc @geografa

As in the page footer and main menu drop-down options (i.e. the CoC).

There are some images hanging out in root that should be in /img