Merge pull request #1 from pnathan/master

Merge from master

Author: veddox

.gitignore

@@ -1 +1,4 @@
-*~
+*~
+_site/*
+site/*
+*/_site/*

.travis.yml

@@ -1,13 +1,17 @@
 sudo: false
-addons:
-  apt:
-    packages:
-    - pandoc
-before_script:
-- curl -O -L http://prdownloads.sourceforge.net/sbcl/sbcl-1.2.6-x86-64-linux-binary.tar.bz2
-- tar xjf sbcl-1.2.6-x86-64-linux-binary.tar.bz2
-# - pushd sbcl-1.2.6-x86-64-linux/ && sudo bash install.sh && popd
-- curl -O -L http://beta.quicklisp.org/quicklisp.lisp
-- sbcl-1.2.6-x86-64-linux/run-sbcl.sh --load quicklisp.lisp --eval '(quicklisp-quickstart:install)' --eval '(quit)'
+language: ruby
+rvm:
+- 2.1
+
+#before_script:
+# - chmod +x ./script/cibuild # or do this locally and commit
+
+# Assume bundler is being used, therefore
+# the `install` step will run `bundle install` by default.
+# script: ./script/cibuild
 script:
-- sbcl-1.2.6-x86-64-linux/run-sbcl.sh --script run-ci.sh
+  - bundle exec jekyll build
+
+env:
+  global:
+  - NOKOGIRI_USE_SYSTEM_LIBRARIES=true # speeds up installation of html-proofer

AUTHORS.md

@@ -0,0 +1,11 @@
+Authors, ordered alphabetically by first name.
+
+Their sacrifice of time is remembered.
+
+Christopher Carpenter <mordocai@mordocai.net>
+Daniel Vedder <d.vedder@web.de>
+Jeremiah LaRocco <jeremiah.larocco@gmail.com>
+Jose Santos <jsmpereira@gmail.com>
+Martin Karlsson <tankrim@gmail.com>
+Paul Nathan <pnathan@alumni.uidaho.edu>
+Ralph Moritz <ralmoritz@gmail.com>

Dockerfile

@@ -0,0 +1,2 @@
+from nginx
+copy _site/ /usr/share/nginx/html

Gemfile

@@ -0,0 +1,3 @@
+source "https://rubygems.org"
+
+gem "jekyll"

HACKING.md

@@ -0,0 +1,10 @@
+hacking on articulate-common-lisp
+---
+
+contributions welcome.
+
+* ./livetest.sh will spawn a localhost:4000 webserver which watches the filesystem
+* ./build.sh will generate a Docker image ready for pushing
+* ./test.sh will run the build.sh generated Docker image. Note that
+  this boots a nginx server.
+* ACL is delivered as a Docker image

README.org

@@ -8,7 +8,7 @@ docs/specs for a tutorial/introduction site for a Common Lisp environment
 
 One of the key problems in onboarding developers to use modern Common Lisp is the vertical wall of difficulty. Things that are routinely problematic:
 
-- emacs use. Most people don't use emacs. 
+- emacs use. Most people don't use emacs.
 
 - Library creation. Putting together ASDF libraries and using them is a fairly horrid experience the first time.
 
@@ -19,7 +19,7 @@ One of the key problems in onboarding developers to use modern Common Lisp is th
 
 This repository is the source code to build a Common Lisp site dedicated to handling these problems. My goal is to put together an introduction/tutorial for practicing professionals and hobbyists from other languages. People who want to get started with Lisp beyond just typing into a REPL.   Right now, it feels like this information is less disseminated and much less centralized than it otherwise might be.  It's not intended to be a HOWTO for Common Lisp. That's been covered *quite* well. But it is intended to be a HOWTO on how to put together a Lisp *environment*.
 
-Anyway, I'd like to collaborate with other people to build a remarkably fine Lisp help site.  Contributions are both *accepted* and *welcome*. It's a wholly static site at this point in time - I don't see a need for articulate-lisp.com to have a dynamic backend. Perhaps/probably one of the code examples will be a webapp. 
+Anyway, I'd like to collaborate with other people to build a remarkably fine Lisp help site.  Contributions are both *accepted* and *welcome*. It's a wholly static site at this point in time - I don't see a need for articulate-lisp.com to have a dynamic backend. Perhaps/probably one of the code examples will be a webapp.
 
 Happy Hacking,
 
@@ -30,48 +30,40 @@ P.S.: feel free to contact me for anything you like.
 
 ** Notes regarding build process.
 
-Various site building tools are out there; I wanted one that was, above all, simple. Initially Jekyll was chosen, 
-but Ruby proved contentious, and frankly, I wanted to ship the site. Pandoc was really easy to use and install on my
-OSX boxes. With a bit of hackery on the templates, I could generate a very nice page. With a bit more hackery,
-`make.lisp` got created, which included snippets automatically, as well as have a simplistic 1-level hierarchical 
-menu for sections of the site based on filename.  I use SBCL as the Lisp system for make.lisp.
+This is a Jekyll site; the existing build scripts use Dockerized
+Jekyll for sandboxing.
 
-You can see this in action in the makefile for the system.
-
-On the build side, the `master` branch is polled routinely by a Jenkins instance at home, which builds the site into 
-the "site" folder and then uploads it to the http://articulate-lisp.com host.  
+Unfortunately, I don't have autobuild yet set up to Docker build &&
+docker push, as that requires credentials and capabilities Travis
+doesn't have yet.4
 
 ** Contributions.
 
-Please pull off the top of the `devel` branch for your contributions and use github Pull Requests for contributing.
+Please send in pull requests!
 
-My home Jenkins instance deploys that branch out to articulate-lisp.com/devel. This allows me to merge your PR and 
-see the result quickly without being at a development machine: e.g., I can use my mobile phone to merge your work and 
-keep the awesome flowing as fast as possible. 
 
 ** License information & legalities.
 
 My opinion on articulate-lisp.com's licensing is this: it should be easy to grab bits and pieces and easy to fork if
 the author disappears. After some careful reading, I selected...
 
-- GPL3 for the documentation itself. 
+- GPL3 for the documentation itself.
 
 - Snippets and other samples embedded in the documentation should be considered public domain a.k.a CC0.
 
-- The full-size examples in src/ are more substantial and, are licensed as AGPL3. This is denoted in their comment header.
+- The full-size examples in examples/src/ are more substantial and, are licensed as AGPL3. This is denoted in their comment header.
 
 I do not believe that these terms are onerous and I have sought to structure them to permit both free use of small things
-and continuity of information. 
+and continuity of information.
 
-AGPL3 is a very strict copyleft license and I feel obligated to justify its choice. 
+AGPL3 is a very strict copyleft license and I feel obligated to justify its choice.
 
 Simply put, I believe that software developers have a moral obligation to allow their users to repair the software that
 they provide. This facility is usual for physical items: we can fix our bikes, chairs, cars, etc. I believe that we
 ought to let our users fix the software they use, or hire other people to make that fix. I also have profound issues with
-the software patent industry. AGPL3 is the best license I know of to ensure that what I create gives users these 
-capabilities and will not be patented. As these are ridiculously small examples, I am fairly positive that any 
+the software patent industry. AGPL3 is the best license I know of to ensure that what I create gives users these
+capabilities and will not be patented. As these are ridiculously small examples, I am fairly positive that any
 serious work will not use them. So it should not be onerous on you.
 
-If your corporate lawyers refuse to let example AGPL3 code exist in your development environment, please write in and - 
-for my part - I will make a good faith effort to negotiate with you for you a less strict license for your company. And I 
-will doubtlessly say rude things about lawyers.
+If your corporate lawyers refuse to let example AGPL3 code exist in your development environment, please write in and -
+for my part - I will make a good faith effort to negotiate with you for you a less strict license for your company.

_config.yml

@@ -0,0 +1,35 @@
+# Jekyll configuration
+
+name: articulate-lisp.com
+description: A jekyll theme
+
+# url is currently only used only for the RSS feed in feed.xml
+url: http://articulate-lisp.com
+
+# baseurl will often be '', but for a project page on gh-pages, it needs to
+# be the project name.
+# *** IMPORTANT: If your local "jekyll serve" throws errors change this to '' or
+#     run it like so: jekyll serve --baseurl=''
+baseurl: ''
+
+# This can be '' to hide the Github nav button
+github: 'pnathan/articulate-common-lisp'
+
+# Set this to your UA-# value, or '' to disable the block completely
+gaaccount: 'UA-44161726-1'
+
+# Set this to your disqus shortname to enable comments. Note that the 'comments'
+# setting below must also be true. Individual posts can override 'comments' to
+# disable on a post-by-post basis
+disqus: ''
+comments: true
+
+permalink: /:year/:month/:title
+paginate: 3
+
+highlighter: pygments
+markdown: redcarpet
+redcarpet:
+  extensions: ["no_intra_emphasis", "fenced_code_blocks", "autolink", "tables", "with_toc_data"]
+
+exclude: ['README.md', 'LICENSE']

_data/nav.yml

@@ -0,0 +1,59 @@
+- title: "Home"
+  href: "/"
+
+- title: "Quicklinks"
+  href: "/quicklinks.html"
+
+- title: "Starting a Project"
+  href: "/project"
+  subcategories:
+    - subtitle: "New Project"
+      subhref: "/new-project.html"
+
+    - subtitle: "Basic Project"
+      subhref: "/basic-project.html"
+
+    - subtitle: "ABCs"
+      subhref: "/abcs.html"
+
+- title: "Implementations"
+  href: "/implementations"
+  subcategories:
+    - subtitle: "Summary"
+      subhref: "/summary.html"
+    - subtitle: "Clozure CL"
+      subhref: "/ccl-setup.html"
+    - subtitle: "CLISP"
+      subhref: "/clisp-setup.html"
+    - subtitle: "SBCL"
+      subhref: "/sbcl-setup.html"
+    - subtitle: "LispWorks CL"
+      subhref: "/lispworks-setup.html"
+
+- title: "IDEs"
+  href: "/ides"
+  subcategories:
+    - subtitle: "Summary"
+      subhref: "/summary.html"
+    - subtitle: "Emacs"
+      subhref: "/emacs-setup.html"
+    - subtitle: "SLIME"
+      subhref: "/slime-setup.html"
+    - subtitle: "CUSP"
+      subhref: "/cusp-setup.html"
+    - subtitle: "LispWorks CL"
+      subhref: "/lispworks-setup.html"
+
+- title: "Examples"
+  href: "/examples"
+  subcategories:
+    - subtitle: "Snippets"
+      subhref: "/snippets.html"
+    - subtitle: "Trotter"
+      subhref: "/trotter.html"
+
+- title: "Libraries"
+  href: "/quicklisp.html"
+
+- title: "Who?"
+  href: "/about/"

_includes/analytics.html

@@ -0,0 +1,11 @@
+{% if site.gaaccount != '' %}
+  <script>
+    (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
+    (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
+    m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
+    })(window,document,'script','//www.google-analytics.com/analytics.js','ga');
+
+    ga('create', '{{ site.gaaccount }}', 'auto');
+    ga('send', 'pageview');
+  </script>
+{% endif %}