Dr Kim Foale kimadactyl

Against Community

Against Community attempts to the explore the political rhetoric of "community" with reference to the politics of the United Kingdom in the era of neoliberalism. Specifically, what is the material and ideological function of discourses around community? How have these shifted over time in the politics of the mainstream of the United Kingdom - from the birth of neoliberal politics in the late 1970s, to the Blairite highpoint of the late 1990s to the Serco-sponsored austerity jamboree of Cameron's "big society"? Why the attraction of community so strong that the likely incoming Labour government feel the need to endorse it in the concept of "one nation"?

Against Community begins by exploring the ideas of community within the early German neoliberal theorists, showing community to be a central concern of the "shock doctrine" reconstruction of post-World War II Germany. Even as early as the later 1940s and 1950s neoliberal reform was accompanied by rhetoric of "community". This idea

If .DS_Store was never added to your git repository, simply add it to your .gitignore file.

If you don't have one, create a file called

.gitignore

In your the root directory of your app and simply write

Step 1 - Make a Discord Webhook

Find the Discord channel in which you would like to send commits and other updates
In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!

Step 2 - Set up the webhook on Github

Navigate to your repository on Github, and open the Settings

Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets

Trello CSS Guide

“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”

You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?

Deploying a subfolder to GitHub Pages

Sometimes you want to have a subdirectory on the master branch be the root directory of a repository’s gh-pages branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master branch alongside the rest of your code.

For the sake of this example, let’s pretend the subfolder containing your site is named dist.

Step 1

Remove the dist directory from the project’s .gitignore file (it’s ignored by default by Yeoman).

	import codecs
	from datetime import datetime
	import json
	import os
	import posixpath
	import re
	import shutil
	import sys

	# This script will import your instagram photos to your static site. It should work for most, assuming you customize the POST_TEMPLATE to match what your site uses.

	<%# Put this code snippet between the <head></head>-tags in your application layout and %>
	<%# replace 'UA-XXXXXXXX-X' with your own unique Google Analytics Tracking ID %>

	<%# ... %>
	<head>
	<%# ... %>
	<% if Rails.env.production? %>
	<script type="text/javascript">
	(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),

	SLIDES := $(patsubst %.md,%.md.slides.pdf,$(wildcard *.md))
	HANDOUTS := $(patsubst %.md,%.md.handout.pdf,$(wildcard *.md))

	all : $(SLIDES) $(HANDOUTS)

	%.md.slides.pdf : %.md
	pandoc $^ -t beamer --slide-level 2 -o $@

	%.md.handout.pdf : %.md
	pandoc $^ -t beamer --slide-level 2 -V handout -o $@

	%!TEX TS-program = xelatex
	\documentclass[12pt]{scrartcl}

	% The declaration of the document class:

	% The second line here, i.e.
	% \documentclass[12pt]{scrartcl}
	% is a standard LaTeX document class declaration:
	% we say what kind of document we are making in curly brackets,
	% and specify any options in square brackets.

	[alias]
	wip = for-each-ref --sort='authordate:iso8601' --format=' %(color:green)%(authordate:relative)%09%(color:white)%(refname:short)' refs/heads