Updating the workbooks

[anikalindtner]

trafficstars

On the Organizers and Coaches Weekend we had some good discussions and suggestions on how to update the workbooks. How to make them better.

Here is the issue we've created. I wanted to add it here for overview reasons.

Main points were:

• revised commands / starting up your app page (rails s, projects/railsgirls - short explanation what where to type?)
• checklist for projects (instead of investor deck)
• map of becoming a developer (attend a workshop, start a group or meetup, intern, apply SoC etc)
• 3 success stories (short) // or 6 "quotes" or very short (few sentences)
• glossary (git, app, push, rails, ruby)

[abelards]

Hello, I suggest we use this issue to reopen Issue #153 about the workbooks. Both have been open without activity for a year so it's time to close some points or reopen others anew :)

[alicetragedy]

@abelards we've moved everything workbook-related to a separate repo (as stated in #153), that's where you will find the latest information, commits, and discussion regarding the workbook. https://github.com/railsgirls/workbook

[abelards]

OK sorry so why not transfer/close this issue? Cheers,

[alicetragedy]

@abelards the main points against closing these issues was to not regularly get the same question about making the workbooks dynamic while we are working on it (people tend not to look at closed issues). Issues were left open, with reference to the new workbook repo, so that people new to the community / wanting to help see that it is a WIP. Do you think there is a better way of handling this? I agree that having lots of open issues about a similar thing makes it difficult. :/

[abelards]

If this has been debated I'm in no place to deny it.

Personally I like to see all issues on projects I like to find simple, easy things I can start to help with. Others are lengthy debates, and in this repo some are "continuous amelioration" so perhaps we could:

1. close the lingering issues that don't represent anything.
2. add a section "How to help" in the README: "we always like help on X, Y & Z, contribute there [+link]"
3. reopen issues with like "[permanent] improve workbooks / keep up to date"

This way we'd have both freed our minds from the clutter of old issues, and made it clear both in README and issues how people can help.

[alicetragedy]

@abelards I really like these suggestions! Of course the README would have to be kept up to date but that's probably better than anything. I'll take a look at the issues I'm assigned to and currently working on, and will make sure that we add a section as suggested asap. got some time off next week so I'll try to take a look at that. Thanks for nudging us about it ;)