Difference between revisions of "TTFA2 Style Guide"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
Most of the content was kept from the old style guide below, though there were some crucial changes. Hopefully we'll get the proper style guide back soon. | Most of the content was kept from the old style guide below, though there were some crucial changes. Hopefully we'll get the proper style guide back soon. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Attempt at reconstructing the proper Style Guide using the IRC notes === | === Attempt at reconstructing the proper Style Guide using the IRC notes === | ||
Revision as of 17:17, 17 April 2012
TTFA 2 Style Guide
This is NOT the current style guide
The proper style guide was agreed upon at the first TTFA2 meeting. It was put into Flossmanuals.net on the notes section for the booklet, and has now disappeared.
Most of the content was kept from the old style guide below, though there were some crucial changes. Hopefully we'll get the proper style guide back soon.
Attempt at reconstructing the proper Style Guide using the IRC notes
- 1,200 for the Intro and 600 words for each chapter aka article: Make it shorter if you can and accept that some could be longer.
- Articles are self-contained in their own right, bound together by the introduction.
- Article format ought to be: user story, current practice, software solution, (optional user story)
- Articles should be introductions, without going into detailed step-by-step instructions: signposts to the information on the net.
- Articles are limited to being about software technology.
- It's a guide for people using IT for political activity
- Focus should be on helping people to approach these topics, not be dictatorial nor about scare-mongering.
- Humour and pictures should be used where possible, but not over used.
- Images should be between 200 and 300 pixels wide, get a suitable image resolution.
- Only use headers for title of the article and sub-headings.
- It will be a PDF.
- Anything we control is under CC attribution licence. Add licensing info and sources to the to article itself.
- Add URL references to the article itself using http://tiny.booki.cc/