Skip to content

Commit 3c03413

Browse files
Merge pull request Code52#76 from Code52/DodoRecap
Show and Tell
2 parents d6fb824 + ffc825d commit 3c03413

File tree

2 files changed

+43
-1
lines changed

2 files changed

+43
-1
lines changed

_posts/2012-04-16-dodo-recap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
layout: post
33
permalink: /dodo-recap.html
4-
date: 2012-04-16 23:00
4+
date: 2012-04-16 20:30
55
title: "dodo recap"
66
author: "@shiftkey"
77
comments: true

_posts/2012-04-17-learning-week.md

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
layout: post
3+
permalink: /show-and-tell.html
4+
date: 2012-04-16 23:00
5+
title: "show and tell"
6+
author: "@shiftkey"
7+
comments: true
8+
---
9+
10+
The Code52 organisers have been bouncing around an idea over the past couple of weeks, but before we dedicate some time to getting it off the ground we want to test out our theory with a little experiment. And it involves you.
11+
12+
## Some Background
13+
14+
Since we kicked off Code52 at the start of the year, we've talked with many developers who are keen to get involved with OSS development but don't really have the time to dedicate a full week to working on a specific idea.
15+
16+
Does that sound like you? Well this is your week.
17+
18+
We want to hear about what you have been working with in your spare time. We want to hear about the cool stuff we haven't had a chance to use. We want to get jealous about hearing how you've used it and what you've learned about it.
19+
20+
In short, we want to hear your stories.
21+
22+
## Show and Tell
23+
24+
We're looking for people to write short articles on stuff they've used recently or something they've built recently to share with the big wide world.
25+
26+
We want to hear:
27+
28+
- what did you find that is awesome?
29+
- what is awesome about it?
30+
- how did you use it?
31+
- what did you learn from using it?
32+
- is there some code that people can have a play with?
33+
34+
It doesn't have to be a long post. And things like pictures and code snippets are fine to help show it off.
35+
36+
Already written about something cool you'd like to share? Tweet a link to the [@Code_52](http://twitter.com/Code_52) account and we'll get in touch. If we're suitably impressed by your awesomeness, we'll share it with the world.
37+
38+
Don't have a blog? Don't worry! You can fork [this website](http://github.com/Code52/code52.github.com) on GitHub and add your own post to the [posts folder](http://github.com/Code52/code52.github.com/tree/master/_posts). Once you've written the post, send us a pull request and we can proof-read it before pushing it live.
39+
40+
If you haven't seen it before, the site layout and content is used as input for [Jekyll](http://github.com/mojombo/jekyll/wiki) to generate the site content.
41+
42+
The Code52 gang have built a couple of tools which might help with writing the posts - [MarkPad](http://code52.org/DownmarkerWPF) for writing Markdown content and [Pretzel](http://code52.org/pretzel) for testing the site locally. You should check them out!

0 commit comments

Comments
 (0)