Skip to content

jpakusch/airport-codes

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Airport Codes

A website that tries to make sense of those three-letter airport codes.

Contributing

If you'd like to add an airport or fix an error, please:

Working Locally

npm install
gulp

Adding/Editing Airport Content

Airport content can be found in /data in individual files. Use the three-letter airport code as the filename (e.g. phx.json).

Content in each json file:

  • id = three-letter code (e.g. phx)
  • code = three-letter code (phx)
  • name = airport name (Sky Harbor International Airport)
  • city = primary city name (Phoenix)
  • state = state name, if applicable (Arizona)
  • stateShort = state abbreviation, if applicable (AZ)
  • country = country name (USA)
  • description = description, accepts markdown, use * for emphasis on letters
  • imageCredit = name of photographer
  • imageCreditLink = URL of photographer's Flickr page

You can also optionally add for aid in searching:

  • city2 = another city or county the airport may be known for
  • city3 = another city or county the airport may be known for

Add the airport to /data/index.js.

Images

  • Please use photos from Flickr that are licensed under Creative Commons.

  • If photos are not available on Flickr, please use Wikipedia with the same license.

  • Please save out 4 sizes of each image as a JPG with the filename convention code-photographer.jpg

    • Card, 250px height, put in assets/images/card
    • Small, 500px width, put in assets/images/small
    • Medium, 900px width, put in assets/images/medium
    • Large, 1500px width, put in assets/images/large
  • Please optimize images

  • Add variable and photographer name to /assets/globals/image-names.styl. The photographer name must match how it is spelled in the image file name. So if an image is named abq-david-basanta.jpg you would add 'abq': 'david-basanta' to the image-names.styl.

Editing Templates

Most site content is written in Jade templates which produce the site HTML.

The Jade files are located in /templates and /src/views/templates.

Note that these aren't markdown files and the syntax and whitespace you use does matter quite a bit. See the Jade documentation to see how to use Jade.

Editing CSS

This site uses Stylus for preprocessing. Please follow the established indentation and commenting patterns.

Stylus files are located in /assets.

Declaration Order

Please use the following loose declaration order:

  • Box-model properties
  • Display and Positioning
  • Backgrounds
  • Borders
  • Box Shadows
  • Fonts and Colors
  • Other

About

Making sense of those three-letter airport codes.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 46.0%
  • CSS 42.9%
  • HTML 11.1%