Recommendations from others are noted in (parentheses). The rest are my personal recommendations.
- The Pragmatic Programmer - Hunt & Thomas
Annotator.Plugin.Madison = function(element, options){ | |
this.options = options; | |
} | |
$.extend(Annotator.Plugin.Madison.prototype, new Annotator.Plugin(), { | |
events: {}, | |
options: {}, | |
pluginInit: function(){ | |
this.annotator.viewer.addField({ | |
load: load_fn.bind(this, user) |
A lot of important government documents are created and saved in Microsoft Word (*.docx). But Microsoft Word is a proprietary format, and it's not really useful for presenting documents on the web. So, I wanted to find a way to convert a .docx file into markdown.
As it turns out, there are several open-source tools that allow for conversion between file types. Pandoc is one of them, and it's powerful. In fact, pandoc's website says "If you need to convert files from one markup format into another, pandoc is your swiss-army knife." But, although pandoc can convert from markdown into .docx, it doesn't work in the other direction.
/* | |
Gmail/Google Reader Sidebar Scroll Shadows | |
------------------------------------------- | |
Neat effect that mimics the scroll shadows that appear in the GOogle sitde bar and visually cues users to scroll up or down depending on their position. | |
Credit goes to Lea Verou for this awesome find. | |
Source: | |
Lea's Talk: http://www.youtube.com/watch?v=3ikye7Qc7Ak | |
Code Source: http://lea.verou.me/more-css-secrets/#slide9 | |
# Basically the nginx configuration I use at konklone.com. | |
# I check it using https://www.ssllabs.com/ssltest/analyze.html?d=konklone.com | |
# | |
# To provide feedback, please tweet at @konklone or email [email protected]. | |
# Comments on gists don't notify the author. | |
# | |
# Thanks to WubTheCaptain (https://wubthecaptain.eu) for his help and ciphersuites. | |
# Thanks to Ilya Grigorik (https://www.igvita.com) for constant inspiration. | |
server { |
what's the easiest way to be able to observe areas of change - and proposed change - of machine readable code? | |
way to model and capture legislative behavior and change management on bodies of legislation as a service. | |
respect for line numbers, section numbers, section references, range references | |
don't just model legislation as a living document, but capture the actual bills for amending said legislation | |
also capture change process for the bills | |
(basically like working in a feature branch) |
# | |
# Working with branches | |
# | |
# Get the current branch name (not so useful in itself, but used in | |
# other aliases) | |
branch-name = "!git rev-parse --abbrev-ref HEAD" | |
# Push the current branch to the remote "origin", and set it to track | |
# the upstream branch | |
publish = "!git push -u origin $(git branch-name)" |
#!/bin/bash | |
# git-cleanup-repo | |
# | |
# Author: Rob Miller <[email protected]> | |
# Adapted from the original by Yorick Sijsling | |
git checkout master &> /dev/null | |
# Make sure we're working with the most up-to-date version of master. | |
git fetch |
# Install MacTex: http://mirror.ctan.org/systems/mac/mactex/mactex-basic.pkg | |
$ sudo chown -R `whoami` /usr/local/texlive | |
$ tlmgr update --self | |
$ tlmgr install ucs | |
$ tlmgr install etoolbox | |
# Install pandoc view homebrew |