Link people to this repo for website issues somehow

[Fishrock123]

Relates to #53 - there's a couple issues on the core repo because that is the only place we direct them to for issues.

[snostorm]

The mods there can just direct them to create an issue here or open an issue on their behalf, closing the other one.

[mikeal]

+1

[Fishrock123]

While true, we should be more clear somehow that website issues should be here.

[mikeal]

Not just "website" but also just messaging/marketing type stuff since the website is the place most of that will end up landing. We already have the FAQ and the ES6 page as well and are the defacto source for that information now.

[snostorm]

Blocked by #57 I'd say. Let's get the final repo name out there first.

[timaschew]

what about to provide a feedback button/link whatever on each page.
If you click on it you can choose if you want to edit the content, like on wikipedia, or give an other kind of feeback for the current page.
If the user clicked on edit, an editor pops up with markdown code on the left side and the generated output on the right, for preview purposes.
By clicking on save the user can choose if he want to use his github account to send an automatically generated pull request or if he has no github account - in this case a public github token will be provided to send the pull request.

The generated pull request will ping the assigned localization group and provide the changes in the markdown file.

If the user chosen the feedback it will be generated a simple issue instead of a pull request.

The cool think with that: the the visitors don't loose focus because they are sill on the iojs website and don't need to (clone), edit, send PR via the github website. And for people which are not using github yet, it become a less obstacle to contribute.

[mikeal]

My only concern with asking for feedback on the website right now is that we're already in the process of redesigning it, so I don't know how relevant the feedback will be since the main issues we're already quite aware of :)

[timaschew]

my idea was not for a special issue, it's more general for any feedback purposes, even if you solved the problem for this issue #55 and even if you redesign the website.

[therebelrobot]

I like the idea of inline editing and then sending it to github. Could speed up the process of content curation tenfold. Or it could make a million duplicate issues for the same issue... ok, I'm on the fence with this.

[timaschew]

sure it could cause duplicate, but this problem you also could have with default issues.

We could fetch issues from github for a specific page and list it it the popup when the user try to create an issue, like stackoverflow is doing this. When writing a title for a question you'll see Questions that may already have your answer with some examples

[snostorm]

Tagging #264 as I still like the idea of per-page links to github content sources

[arthurvr]

I think it makes sense to redirect people with website issues/suggestions to the right place. 👍

The mods there can just direct them to create an issue here or open an issue on their behalf, closing the other one.

That's totally true but sounds like a lot of work for both the team and the people themselves.

I like the idea of inline editing and then sending it to github.

Nah. That kind of stuff always turns out to be hard for various reasons. Infrastructure wise this is more of a challenge then you would think. I guess we can simply link up the github edit page.

The process of sending a suggestion gets TBH already really easy right then. Just to make the edits and click "submit PR". GitHub is likely to be an interface they're familiar with.

[fhemberger]

Fixed on the new nodejs.org site. Closing this.