This site is no longer published. seattlexcoders.org now redirects to xcoders.org which is the active site.

---

Seattle Xcoders Web Site

This is the source for the Seattle Xcoders web site. It is built using Jekyll with a few modifications.

Install:

1. Install recent version of git

2. Project is http://github.com/xcoders/xcoders.github.com

3. Check out source: git clone [email protected]:xcoders/xcoders.github.com.git

4. Recommend using rbenv with Ruby 1.9.2 or later

5. Install pygments for source code syntax highlighting:

    sudo pip install Pygments
   

6. Install gems via bundler:

    cd xcoders.github.com
    bundle install --path vendor/bundle
    bundle install --binstubs
    echo ".bundle\nbin\nvendor/bundle/ruby\n" >> .gitignore
   

Create a post

draft

rake draft[<post_title>, <author>]

By default, post should use your GitHub name so you can omit the author field if you want. Your default editor should open up the post file. Posts by default are in markdown. If you prefer HTML, change the name to .html. If you prefer Textile, use .textile. I can add rake options to change the preferred format if you wish.

Edit the post file in any editor you want. See _posts/* for examples of posts.

post

rake post[<post_title>]

Moves from the _drafts folder to _posts folder. Think of this as staging your post. You can now see it when you run the local jekyll server.

Local server

Run rake server to launch a local webrick with the site. Navigate to http://localhost:3000 to view the site. You can edit the post file all you want and see the changes automatically.

Publish post live:

When you are ready to publish the post live:

git add _posts/<postfile>
git commit
git push origin master

• The git commit is to your local git repo.
• The git push to origin pushes the code to the Xcoders github repo. GitHub pages will be called as a post commit hook and regenerate the site.
• Your post is live

The above pattern also applies to CSS and any other pages (like about). So you can edit the site structure in the same way.

Notes

The site uses Jekyll to build the pages. Jekyll is kind of a throw back. It is built in ruby and generates static pages. It uses Liquid as a templating engine. See the jekyll project wiki for lots of info using Liquid.

The site structure is as follows:

CNAME            _drafts/         _site/           calendar.html
README.markdown  _includes/       about.textile    css/
Rakefile         _layouts/        archive.html     images/
_config.yml      _posts/          atom.xml         index.html

CNAME	File to allow github pages to serve seattlecoders.org
Rakefile	I wrote this with convenience tasks for dealing with the site/jekyll _config.yml Inputs to the jekyll engine for site generation
_drafts	Ignored by the site builder. You can build up posts here before bringing them live.
_includes	Partials that can be included by other pages
_layouts	Page layouts (posts use the posts.html layout for example)
_posts	Blog posts. Each posts is a separate file
_site	Generated site (this is what is actually served)
atom.xml	RSS feed template
about
archive
calendar
index	These 4 are like posts but are served as top level pages
css/	Stylesheets
images/	Image resources

DON'T EDIT STUFF IN _site/

If you change something there it will be overwritten the next time the site is regenerated. It's the "build" directory.

Generally, to post, you just do the following:

rake draft
edit
rake post
rake server to preview
git commit
git push -> go live