the lawkit contributor's guide

Further to the previous introduction (and as self-elected editor-in-chief) I've taken the liberty of drawing up a few guidelines. Now, traditionally a publication's style guide sets out their rules for language, grammar, formatting and so on. This post is not one of those.

Rather, I want to offer a context and some parameters, which should assist potential contributors in understanding the tone we're going for. In terms of the practical elements of formatting, I'm largely happy to satisfy the English teacher part of me in correcting the small things. The important thing here is to get across the potential style of the publication itself.

I should also mention that some of the ideas here were inspired by this excellent article on A List Apart by Erin Kissane, which the ever-pedantic @djlowry was kind enough to draw my attention to.


THE LAWKIT CONTRIBUTOR'S GUIDE

- Apparently, you should never read a book by its cover. However, you can tell a lot about the tone of a publication on first look - that's the point of marketing. To that end, the mock-up shown here gives a fair idea of the sort of style currently in the works. Minimalist but striking, letting the content do the talking. I've come up with some multi-coloured nightmares over the last while as I've been thinking about this, but after the epiphany that was the name, the style wrote itself.

- Lawkit should read like a collection of well-written blog posts. Think of your favourite online articles. What makes them so readable?

- The best way to pin down your subject matter is to start with our subject list. To complete an issue, I'd like to gather articles which collectively cover the majority of these. (Potentially, the blog would note which topics were already "taken" for each issue as well.) Currently, the list is:

Politics
Technology
Outdoors
Film
Music
Faith
Science
Sport
Gadgets
Life

- What's the point of Lawkit? It's about Life As We Know It. It's about sharing knowledge. But you don't have to be an expert to write on something, as long as you are interested in it - because if you are interested in something, you'll be interested in telling others about it. To that end, don't try to argue a point you don't believe in.

- Knowledge is king, but knowledge can also be useful. Able to write a How-To guide for something? Then do it.

- Don't be afraid to be specific or niche.

- Be clear about your subject from the start: 500 words and no waffle is highly preferable to 1500 with - and it'll get cut anyway. Slaughter your babies - omit needless content or someone else will.

- If you only have twenty minutes to bang out something, go for it all the same.

- So knowledge is king, but clarity is Grand High Poobah; you can speak a bit academically and still stay accessible to the casual expert. There's nothing more irritating than being obtuse for the sake of it, and you know it.

- This isn't to sell stuff (yet.) So don't do it - unless you're willing to give something in return for advertising (in which case, let's talk.) That said, if you're involved in something that you feel people might like to hear about, please tell us.


Got all that? Then get scribbling.