210 lines
12 KiB
HTML
210 lines
12 KiB
HTML
|
<!DOCTYPE html>
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta charset="utf-8">
|
||
|
|
|
||
|
|
<meta http-equiv="X-UA-Compatible" content="IE=edge,partials=1">
|
||
|
|
<meta name="description" content="">
|
||
|
|
<meta name="HandheldFriendly" content="True">
|
||
|
|
<meta name="MobileOptimized" content="320">
|
||
|
|
<meta name="viewport" content="width=device-width, initial-scale=1 minimal-ui">
|
||
|
|
|
||
|
|
<meta name="description" content="">
|
||
|
|
<meta name="keywords" content="">
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<meta name="twitter:card" content="summary">
|
||
|
|
|
||
|
|
<meta name="twitter:site" content="@kidwellj">
|
||
|
|
<meta name="twitter:title" content="Resources : jeremykidwell.info">
|
||
|
|
<meta name="twitter:creator" content="@kidwellj">
|
||
|
|
<meta name="twitter:description" content="">
|
||
|
|
<meta name="twitter:image:src" content="">
|
||
|
|
<meta name="twitter:domain" content="jeremykidwell.info">
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<base href="https://jeremykidwell.info/">
|
||
|
|
<title> Resources </title>
|
||
|
|
<link rel="canonical" href="https://jeremykidwell.info/resources/">
|
||
|
|
<link href="https://jeremykidwell.info/resources/index.xml" rel="alternate" type="application/rss+xml" title="Resources" />
|
||
|
|
|
||
|
|
<link rel="stylesheet" href="https://jeremykidwell.info/css/stylesheet-min.css" />
|
||
|
|
<link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css" rel="stylesheet">
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
<script type="text/javascript" src="https://use.typekit.com/kpn7wwu.js"></script>
|
||
|
|
<script type="text/javascript">try{Typekit.load();}catch(e){}</script>
|
||
|
|
|
||
|
|
|
||
|
|
<link rel="shortcut icon" href="https://jeremykidwell.info/favicon.ico" type="image/x-icon" />
|
||
|
|
<link rel="apple-touch-icon" href="https://jeremykidwell.info/apple-touch-icon.png" />
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body lang="en" itemscope itemtype="http://schema.org/Article">
|
||
|
|
<div id="topbar">
|
||
|
|
<div class="wrapper">
|
||
|
|
<header>
|
||
|
|
|
||
|
|
<nav class="navbar">
|
||
|
|
<ul>
|
||
|
|
<li><a href="https://jeremykidwell.info/">Jeremy Kidwell</a></li>
|
||
|
|
|
||
|
|
|
||
|
|
<li><span> <a class="" href="https://jeremykidwell.info/publications">Publications </a></span>
|
||
|
|
|
||
|
|
<li><span> <a class="" href="https://jeremykidwell.info/resources">Resources </a></span>
|
||
|
|
|
||
|
|
<li><span> <a class="" href="https://jeremykidwell.info/teaching">Teaching </a></span>
|
||
|
|
|
||
|
|
<li><span> <a class="" href="https://jeremykidwell.info/blog">Blog </a></span>
|
||
|
|
|
||
|
|
</ul>
|
||
|
|
</nav>
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
</header>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="wrapper">
|
||
|
|
<div class="units-row">
|
||
|
|
<div class="unit-centered unit-80">
|
||
|
|
<article class="post" id="content">
|
||
|
|
|
||
|
|
|
||
|
|
<h2 id="code-and-data">Code and Data</h2>
|
||
|
|
|
||
|
|
<p><em>This page has links to configuration files, templates, and a few other things that might be of use to people who want to write well-formatted social science papers in plain text, with data, figures, and
|
||
|
|
references.</em></p>
|
||
|
|
|
||
|
|
<figure><img src="https://kieranhealy.org/files/misc/workflow-wide-tx.png"><figcaption>The Sausage Factory</figcaption></figure>
|
||
|
|
|
||
|
|
<div class="units-row">
|
||
|
|
<div class="unit-50">
|
||
|
|
<h4><a href="http://www.kieranhealy.org/files/papers/plain-person-text.pdf">The Plain Person's Guide to Plain Text Social Science</a> →</h4>
|
||
|
|
<p>As a beginning graduate student in the social sciences, what sort of software should you use to do your work? More importantly, what principles should guide your choices? This article offers some answers. The short
|
||
|
|
version is: you should use tools that give you more control over the process of data analysis and writing. I recommend you write prose and code using a good text editor; analyze quantitative data with R or Stata; minimize
|
||
|
|
error by storing your work in a simple format (plain text is best), and make a habit of documenting what you've done. For data analysis, consider using a format like Rmarkdown and tools like Knitr to make your work more
|
||
|
|
easily reproducible for your future self. Use Pandoc to turn your plain-text documents into PDF, HTML, or Word files to share with others. Keep your projects in a version control system. Back everything up regularly. Make
|
||
|
|
your computer work for you by automating as many of these steps as you can. To help you get started, I briefly discuss a drop-in set of useful defaults to get started with Emacs (a powerful, free text-editor). I share
|
||
|
|
some templates and style files that can get you quickly from plain text to various output formats. And I point to several alternatives, because no humane person should recommend Emacs without presenting some other options
|
||
|
|
as well. There is a sample <a href="https://github.com/kjhealy/workflow-paper">github repository</a> that contains the <code>.md</code> source file the PDF is created from. This material is also available <a
|
||
|
|
href="http://plain-text.co">as a website</a> at <code><a href="http://plain-text.co">http://plain-text.co</a></code>.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h4><a href="https://jeremykidwell.info/resources/emacs-starter-kit" title="kjhealy/emacs-starter-kit @ GitHub">An Emacs Starter Kit for the Social Sciences</a></h4>
|
||
|
|
<p>This is a fork of Eric Schulte's <a href="http://github.com/eschulte/emacs-starter-kit/tree">Emacs Starter Kit</a> (itself an offshoot of <a href="http://github.com/eschulte/emacs-starter-kit/tree">Phil Hagelberg's
|
||
|
|
original</a>) with additional tools included for social scientists, mostly related to writing books or papers in LaTeX and analyzing quantitative data using <a href="http://ess.r-project.org/">ESS</a> and <a
|
||
|
|
href="http://www.r-project.org/">R</a>. The goal is to provide a drop-in configuration for Emacs that makes it easier to use right from the get-go. If you know about <a href="http://git-scm.com/" title="Git - Fast Version
|
||
|
|
Control System">Git</a>, <a href="http://github.com/kjhealy/emacs-starter-kit/tree/master" title="kjhealy's emacs-starter-kit at master — GitHub">you can clone the repository</a>.</p>
|
||
|
|
|
||
|
|
<h4><a href="http://vissoc.co">Data Visualization Course Notes</a> →</h4>
|
||
|
|
<p>Notes, links, and code from a Data Visualization short-course I taught in the Fall of 2015. The course is focused on the practical presentation of real data, mostly using R's `ggplot2` library. We also read some
|
||
|
|
material on principles of data visualization, in order to help develop a good working sense of why some graphs and figures work well while others either fail to inform or actively mislead.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<div class="unit-50">
|
||
|
|
<h4><a href="http://github.com/kjhealy/latex-custom-kjh">LaTeX Templates and Styles</a> →</h4>
|
||
|
|
<p>A collection of LaTeX style files, templates, and org-mode documents providing some nice layouts for typesetting articles using pdfLaTeX or XeLaTeX. They make a pipeline that lets you begin with an
|
||
|
|
<code>.org</code> file in Emacs (as set up in the <a href="http://kjhealy.github.com/emacs-starter-kit/">Starter Kit</a>), and go from there to a nice, fully-processed PDF in one step. Or the pieces can be used separately
|
||
|
|
to set up a <code>.tex</code> file with a nice Article layout.</p>
|
||
|
|
|
||
|
|
<h4><a href="https://github.com/kjhealy/pandoc-templates">Pandoc Templates</a> →</h4>
|
||
|
|
<p>Some Pandoc templates meant to go in <code>~/.pandoc/templates</code>. Point to them directly with the <code>--template</code> or <code>--css</code> switches as appropriate, and use them with what's provided in <a
|
||
|
|
href="http://github.com/kjhealy/latex-custom-kjh"><code>latex-custom-kjh</code></a>. Includes a shell script for setting pandoc up to work with the <a href="http://marked2app.com">Marked</a> app, a handy HTML live
|
||
|
|
previewer for <code>.md</code> files.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h4><a href="http://kjhealy.github.com/kjh-vita/">So You Like My Vita</a> →</h4>
|
||
|
|
<p>Every few months I get an email asking to see the LaTeX markup that I use to generate my <a href="http://kieranhealy.org/vita.pdf">Curriculum Vitae</a>. So, <a href="http://kjhealy.github.com/kjh-vita/"
|
||
|
|
title="kjhealy's kjh-vita @ GitHub">here it is</a>. Feel free to adapt it yourself. If you make stylistic modifications, I encourage you to fork the project on GitHub and make them available to others in the same way.</p>
|
||
|
|
|
||
|
|
<h4><a href="http://github.com/kjhealy/kieranhealy.hugo/">So You Like My Website</a> →</h4>
|
||
|
|
<p>This site is produced using <a href="http://gohugo.io">Hugo</a>, a very fast static site generator, which you can <a href="http://gohugo.io/overview/introduction/">read more about here</a>. I've written about <a
|
||
|
|
href="http://kieranhealy.org/blog/archives/2014/02/24/powered-by-hugo/">my own experience setting it up</a>, too. The design is borrowed mostly from <a href="http://consequently.org/">Greg Restall</a>. If you want to look
|
||
|
|
under the bonnet, <a href="http://kjhealy.github.com/kieranhealy.hugo/" title="This website's source">the entire site is on GitHub</a>. Feel free to adapt it yourself. If you make stylistic modifications, I encourage you
|
||
|
|
to fork the project on GitHub and make them available to others in the same way. You should also change the Google Analytics information in the footer partial, or I will receive analytics information about your site.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h4><a href="https://jeremykidwell.info/resources/github/">All GitHub Projects</a></h4>
|
||
|
|
<p>Here is a <a href="https://jeremykidwell.info/resources/github/">full list of the various public code and data repositories</a> that I have put on GitHub. They range from the configuration and templating tools listed above to data
|
||
|
|
visualization exercises and other bits of data analysis, mostly written in R.
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</article>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<hr class="separator">
|
||
|
|
|
||
|
|
<div class="wrapper" style="font-size: 0.9em; line-height: 1.05em;">
|
||
|
|
<div class="units-row units-padding">
|
||
|
|
<div class="unit-40">
|
||
|
|
<h3>about</h3>
|
||
|
|
<figure class="image-left">
|
||
|
|
<img class="avatar" src="files/misc/jkpic.jpg" height="120" width="120">
|
||
|
|
</figure>
|
||
|
|
<p>I am Lecturer in <a href="http://www.birmingham.ac.uk/schools/ptr/index.aspx">Theological Ethics</a> at <a href="http://www.birmingham.ac.uk">the University of Birmingham</a>.</p>
|
||
|
|
</div>
|
||
|
|
<div class="unit-30">
|
||
|
|
<h3>Where</h3>
|
||
|
|
<ul class="compact fa-ul">
|
||
|
|
<li><i class="fa-li fa fa-university fa-fw" style="color:#03396c;font-size:80%;padding-top:6px;"></i>Department of Theology and Religous Studies, University of Birmingham, Edgbaston, Birmingham, B15 2TT, UK.</li>
|
||
|
|
<li><i class="fa-li fa fa-envelope fa-fw" style="color:#03396c;font-size:80%;padding-top:6px;"></i><a href="mailto:j.kidwell@bham.ac.uk">j.kidwell@bham.ac.uk</a></li>
|
||
|
|
<li><i class="fa-li fa fa-twitter-square fa-fw" style="color:#03396c;font-size:80%;padding-top:6px;"></i><a href="http://twitter.com/kidwellj">@kidwellj</a> on Twitter.</li>
|
||
|
|
<li><i class="fa-li fa fa-github fa-fw" style="color:#03396c;font-size:80%;padding-top:6px;"></i><a href="http://github.com/kidwellj">On GitHub</a>.</li>
|
||
|
|
<li><i class=""></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div class="unit-30">
|
||
|
|
<h3>subscribe</h3>
|
||
|
|
<p>To receive updates from this site, you can
|
||
|
|
subscribe to the <a href="https://jeremykidwell.info/index.xml"><i class="fa fa-rss-square" style="color:#03396c;"></i> RSS feed</a> of all updates to the site in an RSS feed reader</p>
|
||
|
|
<h3>search</h3>
|
||
|
|
<a id="searchsite">
|
||
|
|
<form method="get" action="https://duckduckgo.com/">
|
||
|
|
<input type="search" name="q" maxlength="255" placeholder="Search the site">
|
||
|
|
<input type="hidden" name="sites" value="jeremykidwell.info"/>
|
||
|
|
<input type="hidden" name="k7" value="#faf8f8"/>
|
||
|
|
<input type="hidden" name="kj" value="#b33"/>
|
||
|
|
<input type="hidden" name="ky" value="#fafafa"/>
|
||
|
|
<input type="hidden" name="kx" value="b"/>
|
||
|
|
<input type="hidden" name="ko" value="-1"/>
|
||
|
|
<input type="hidden" name="k1" value="-1"/>
|
||
|
|
<input type="submit" value="DuckDuckGo Search" style="visibility: hidden;" /></form></a>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
|
||
|
|
<footer id="footer">
|
||
|
|
<section class="wrapper small">Powered by <a href="http://gohugo.io">Hugo</a> and <a href="http://imperavi.com/kube/">Kube</a>. © Jeremy Kidwell 2017–2017.
|
||
|
|
</section>
|
||
|
|
</footer>
|
||
|
|
|