Code Like This web site
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
spec better breadcrumbs Oct 8, 2018
CodeLikeThis_Wireframes.pdf top nav Nov 15, 2017
Procfile new logo, update gems Sep 16, 2018


source for Code Like This web site

see for some todo items


First, make your own fork, and install Ruby and git on your computer. Then...

  1. git clone XXX (where XXX is either or your personal github repo URL)
  2. cd codelikethis
  3. gem install bundler
  4. bundle install
  5. rake spec (to run all tests and verify setup)
  6. rake build (to compile CSS)
  7. rake run (or rerun to rebuild/restart on file changes)
  8. open http://localhost:9292


SCSS is currently built using Sass. Run this all the time in development, or at least once before deploy after you change anything:

rake build
Command Description
rake spec run all tests and verify setup
rake build compile CSS
rake run run local server on http://localhost:9292
rerun rackup run with rebuild/restart on file changes
rerun --pattern '*.scss' --exit -- rake build run this in a separate terminal to compile CSS when SCSS changes too

Note that any of the above may need to be preceded by bundle exec e.g. bundle exec rerun rackup (whether you need to do this or not depends on gnarly details of your Ruby installation).


Path Description
./app.rb main app
./ app config
lib ruby source code
lib/thing.rb::WEIRD_WORDS list of oddly-capitalized words (e.g. CSS, JavaScript)
lib/bootcamp.rb ruby Site describing the Bootcamp course(s)
lib/bootcamp-schedule.json JSON describing the Bootcamp course schedule
spec ruby test source code
public web-visible files
public/images web site images
public/lessons/images images used by some lessons
public/lessons/foo/bar.jpg an image used by only a single lesson
public/js web site scripts
public/css web site css files -- do not edit these directly!
public/scss web site sass source files, compiled into public/css
public/lessons course files (markdown and images), organized by track
public/lessons/trackname/ track files (markdown and images), organized by track
public/lessons/trackname/trackname.rb track description files; names match public/lessons subdirs
public/lessons/trackname/ markdown slides for a single lesson named baking (served from /lessons/trackname/bake_cookies URL path)
public/projects/ markdown slides for a single project named bake_cookies (served from /projects/bake_cookies URL path)


a Site is

  • a hostname
  • an ordered collection of Tracks
  • a home page
  • a schedule

Currently there are two Sites:

  1. CodeLikeThis - the main site, containing all Tracks (listed in alphabetical order)
  2. Bootcamp - the site for Burlington Code Academy's 2018 Web Development Bootcamp, which runs from June through August in (where else?) Burlington, Vermont

Both sites are served from the same web application instance, running on Heroku ( The app looks at and serves a different Site to each hostname.

To add a Site, follow the example of Bootcamp.

To view a Site locally, use a site parameter, e.g. http://localhost:9292/?site=bootcamp. This parameter is not propagated to new pages so you'll have to keep adding it explicitly to test different pages.

Adding a Track

  1. Decide on its name. Its name is a camelcase_word that will automatically turn into titlecase when displayed. (e.g. cook_food => Cook Food)
  2. create a new subdir inside public/lessons (e.g. public/lessons/cook_food/)
  3. define a Track subclass in a new file inside that dir (e.g. public/lessons/cook_food/cook_food.rb) and
  4. declare your lessons inside the track file. Look at the existing .rb files inside public/lessons for examples.
  5. for each Lesson, put its slides in a markdown file with its name in the lessons directory (e.g. public/lessons/cook_food/
  6. add the Track to your Site by following the example of Bootcamp


Currently a project consists of a markdown file in the public/projects/ directory e.g. public/projects/ It is viewable via the path /projects/foo (note the lack of file extension).

To declare a project is a bit scattershot. It can be referenced in several places:

  1. in the schedule JSON attached to a given week
  2. in a Lesson file (not the slides markdown)
  3. in a Track file, directly under the Track
  4. in a Track file, nested under a Lesson

We should clean this up, so we don't have duplication/omission of e.g. project descriptions depending on where they're defined/referenced.