Add cheatsheet for attendees

[alicetragedy]

I think it's good for attendees to have something to take home with them (and maybe something to glance at while at the workshop) - while we do some rework/redesign of the booklet, I could add the one-page-cheatsheet we made for RG Linz (git, general command line, rails commands) to the materials for the organisers to download.

• InDesign file
• PDF (for easy printing)
• a markdown or text file with the actual content that can be easily copied and pasted
• a style guide (colors, possible typefaces and font sizes, etc.. and helpful tips)

[lindaliukas]

Sounds wonderful!

On Sun, Sep 14, 2014 at 6:19 PM, alicetragedy notifications@github.com
wrote:

I think it's good for attendees to have something to take home with them
(and maybe something to glance at while at the workshop) - while we do some
rework/redesign of the booklet, I could add the one-page-cheatsheet we made
for RG Linz (git, general command line, rails commands) to the materials
for the organisers to download.

—
Reply to this email directly or view it on GitHub
#541.

[keikoro]

Cheat sheets are great! The one we had for the 1st Rails Girls Vienna event was unfortunately (well, "unfortunately") done by a sponsor at another event, so we couldn't just put it online to share it.

I think it'd be super cool if you also added an editable version of the document to the private RG repo so that other organisers can adapt it for their local workshops (translate it, add to it etc.).

[sareg0]

Perhaps a markdown file? Cheat sheets are awesome, each chapter can
decorate it if they like. It's a great souvenir to hang on the wall

On Tuesday, September 16, 2014, Kay notifications@github.com wrote:

Cheat sheets are great! The one we had for the 1st Rails Girls Vienna
event was unfortunately (well, "unfortunately") done by a sponsor at
another event, so we couldn't just put it online to share it.

I think it'd be super cool if you also added an editable version of the
document to the private RG repo so that other organisers can adapt it for
their local workshops (translate it, add to it etc.).

—
Reply to this email directly or view it on GitHub
#541 (comment)
.

[alicetragedy]

thanks for the feedback - the one I made was in InDesign (so the output was a PDF) but I'm sure I could change that, since that's not necessarily a program everyone has access to. Maybe adding both (editable + non-editable) might be cool, that way we also have a version that's ready & optimized for printing. I've never made "pretty" markdown files that didn't rely on some sort of template (eg. for a blog) so I'm not really sure what's the best way to do it (adding bg color, making columns, etc..) but I'll try to find out!
@sareg0 do you have experience with that?

[keikoro]

True, not everybody has access to InDesign, but on the other hand, not all organisers are techies/have worked with Markdown before and might not want to spend the time looking into it (but some might have a background in graphics/design) so I think providing both would be a good idea. If given a choice, I, personally, would take InDesign over Markdown for things to be printed any day! ^^

And yes, a ready-to-print version - or versions... over time - would definitely be good to have!

[sareg0]

That's right... Markdown is harder to make look nice... No one file type
will be 100% accesible (i.e. not everyone uses Google docs, or PS, or
markdown). I guess if there's a style guide, and a PDF, then people can use
whatever program they have access to; powerpoint, word etc etc. As lons as
the content is there, they can copy and paste it into any document, or just
use the static copy, that we can try to keep updated in a central place too
:)

On Tue, Sep 16, 2014 at 4:00 PM, Kay notifications@github.com wrote:

True, not everybody has access to InDesign, but on the other hand, not all
organisers are techies/have worked with Markdown before and might not want
to spend the time looking into it (but some might have a background in
graphics/design) so I think providing both would be a good idea. If given a
choice, I, personally, would take InDesign over Markdown for things to be
printed any day! ^^

And yes, a ready-to-print version - or versions... over time - would
definitely be good to have!

—
Reply to this email directly or view it on GitHub
#541 (comment)
.

[keikoro]

I'd still find it great if any originals were shared too - if @alicetragedy doesn't mind, that is. Less work for minor changes. (:

[alicetragedy]

I definitely don't mind @kerstin - not a problem. So that means I'll put together:

• InDesign file
• PDF (for easy printing)
• a markdown or text file with the actual content that can be easily copied and pasted
• a style guide (colors, possible typefaces and font sizes, etc.. and helpful tips)

[keikoro]

Sounds verrry cool, thanks for doing this!

[alicetragedy]

No problem!
Then we can test it on our Rails Girls Vienna attendees ;)

[keikoro]

Totally! :D

[sareg0]

sounds great Laura!