Add list of guides to write

[cllns]

Let's put this list of what we want to write in the README, so we have some source control on it :)

Also happy to make it TODO.md, or use the Wiki.

I pulled the content from #1 and re-organized it a bit, and added some stuff. Also turned it into check lists :)

Please give me your thoughts on stuff that needs to be added, removed or modified/clarified.

(Closes #1)

[davydovanton]

looks good for me

[cllns]

Just updated this.

I'm not sure adding this to the README is the best idea. I have started assigning people who volunteered to write certain ones, with just writing their GitHub handle next to them, but there's no way to track that.

What do you think about experimenting with GitHub's new 'Projects' feature? https://help.github.com/articles/adding-issues-and-pull-requests-to-a-project/
Seems like this could be a good use for it.

We can create cards (which are not Issues) for each of these and put them in the Backlog. Then as we want to pull them up (or people volunteer), we can promote the cards to being Issues, which will get worked on. Thoughts? @hanami/ecosystem

[davydovanton]

@cllns cool idea. we can add this list to GitHub wiki and after that create an issue for each part and add this issues to github project. What do you think?

[cllns]

I like the idea of moving this list to the wiki!

But then we'd create project Cards directly from that that wiki list, which are not Issues yet. Instead, they can be made into Issues when they're needed. I think this will help us focus and prioritize guides, rather than getting overwhelmed. That cool with you?

Otherwise, we could just use wiki + Issues and do our own project management.

[davydovanton]

yep, wiki + project looks good for me 👍

[cllns]

Closing in favor of https://github.com/hanami/ecosystem/wiki/Integrations (which I copied from the current state of this PR)

we'll make a project from the list there.