-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add link to Resources wiki page #41
Conversation
👍 |
@joonty Thanks for the +1. I'm adding here more details of my thoughts about this PR.
I think the benefits of the wiki outweigh the cons, but created the issue so this can be discussed. |
We can remove the deployment issues by using Travis's auto-deployment upon successful build. That way all that we would need to do is merge a PR, and the site would be updated. In general, I think that perhaps a curated list is still the better way to go. I'm not 100% sure how others feel about this (I may be nuts), but it seems to me that this site is used as a reference to new-comers, and as such we should attempt not to lead them down rabbit-holes. If we allow user created content, the suggestions have not been vetted and confirmed as good practice, and it could cause a less than ideal starting point for new pairers... I do think that there is a place for a wiki in general, but I don't think it can replace what we have here... |
My understanding was that the wiki wouldn't be replacing the existing content, but would be an addition for those who want to search a bit further. That means that we can watch as users agree on the best practices, and update the main site accordingly. A bit like a bleeding edge (the wiki) and a stable version (the site). Or have I misunderstood? |
@joonty - That makes total sense, and I think a Wiki definitely has a place here (as you described). I just want to make sure we are all on the same page... |
@joonty @rjackson my thoughts exactly. I think there's a place for bleeding edge, but am not sure how we can ensure it doesn't interfere with or confuse the site's recommendations/resources. e.g. we don't recommend screen, but why not allow someone on the wiki to offer resources for pairing with screen? or e.g. a place to share user-contributed pairing scripts like https://gist.github.com/marksim/5785406 / http://blog.quarternotecoda.com/blog/2013/06/06/quick-script-for-tmux-pair-sessions/ |
Seems good to me. |
Are there other resources that should be on the wiki that are currently under 'resources'? It's a pretty bit list down there. Alternatively should there be a 'recommended setup' for new users as a jumping off point; not that I fancy having the discussion as to which tool is best. Also the wording of the sidebars seems inconsistent:
Shouldn't it be:
Edit: I knew I'd seen 'recommended setup' somewhere before: Golden Path #2 |
I'm definitely down for having some more open user-curated content in the form of a wiki. 👍 |
@avdi good enough for merging and then perhaps some pruning of site content to the wiki? |
What do you think about promoting some wiki-based user-content?