Coder Social home page Coder Social logo

maptime.github.io's Introduction

Build Status

maptime.github.io

This is the central repo of the maptime.io website. This is a Jekyll site served on Github Pages. If your environment is already setup, type in your terminal (the '$' refers to your prompt):

$ git clone [email protected]:maptime/maptime.github.io.git
$ cd maptime.github.io
$ jekyll serve --watch

Setting up your environment

Set up git and jekyll, which depend on ruby and homebrew:

For the code snippets below, you'll want to copy everything after the $ and paste into a terminal window.

Install Homebrew

Paste this into terminal

ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

Hit Return to start installation.

After it finishes, make sure brew is configured correctly by running:

$ brew doctor

Install Git

  1. In terminal, run the following commands:
brew update
brew install git
  1. Then follow the Set Up Git instructions provided by GitHub to configure your github account through git.

Install Ruby

  1. MacOS comes with a built-in version of Ruby, but it's frequently out of date, and requires installing gems with sudo. It's better to install Ruby from homebrew:
brew install ruby
  1. Then add /usr/local/opt/ruby/bin to $PATH:
$ echo 'export PATH=/usr/local/opt/ruby/bin:$PATH' >> ~/.bash_profile

Install Jekyll

Run the following in terminal:

$ gem install jekyll -v 2.4.0
$ gem install rdiscount

Clone this repo

Clone the maptime.github.io repo on your computer. Then switch into that file directory.

$ git clone -b master [email protected]:maptime/maptime.github.io.git
$ cd maptime.github.io

maptime.github.io's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

maptime.github.io's Issues

Any interest in displaying excerpts rather than full posts on the home page?

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.

Maptime Madison Website

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!

Tutorials page

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!

OOCSS

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

  • Modularize our stylesheets
  • Generate a styleguide
  • OOCSS?

We're currently maintaining chapters data in two places

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

Delete master branch and make gh-pages the main branch?

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.

Sort Chapters

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.

Favicon

You guys need a funky favicon!

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

content background

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

Clean up chapters.json and chapters template

  • 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

Create Maptime has a New Web Site post

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...

Clean up chapters page

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

How about an unpublished documentation page for development

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.

Jobs page

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

Update the on-boarding process

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.

Twitter and Open Graph descriptions aren't evaluating

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;" }}' />

desciptionnoshowing

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

swap images for main pages

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

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.