Add community page. #91

fwalch · 2015-03-16T14:06:03Z

The idea is to link to this page from https://github.com/neovim/neovim#community, https://github.com/neovim/neovim/wiki/Communicating, and https://github.com/neovim/neovim/wiki/Contributing#give-support.

Speaking of https://github.com/neovim/neovim/wiki/Communicating, should the code of conduct be linked on this page as well? Is "Support" a good title, or should it be called e.g. "Community" instead?

fwalch · 2015-03-16T14:07:53Z

Travis failed because it couldn't find neovim.org/support, which is the page added by this PR..

ghost · 2015-03-16T19:22:34Z

Is "Support" a good title, or should it be called e.g. "Community" instead?

"Community" is better IMO, as wanting support isn't necessarily the reason someone wants to interact with a community such as this. Anyways, I really wish that we had some unified place to go for information. We have the vim differences wiki page, and (hopefully soon) the same thing for docs, which must be manually synchronized.

I think what you're doing is better than the current setup, but it still means users are being directed to a different domain just to see such a small page. Perhaps we could just have everything written in markdown, and then periodically (at least when something's changed) regenerate it for use in specific wiki pages and the website, and have @marvim automatically push everything out. Just an idea.

fwalch · 2015-03-16T19:38:54Z

We have the vim differences wiki page, and (hopefully soon) the same thing for docs, which must be manually synchronized.

I thought that once it was in the docs, the wiki page would go away entirely.

In general, I think users will check out the website first, so IMO user-stuff should live there, with the Github Wiki as a resource for (Neovim/plugin/..) developers. That way we could probably avoid most duplication.

Renamed to "Community".

ghost · 2015-03-16T19:53:25Z

I thought that once it was in the docs, the wiki page would go away entirely.

For each change, it usually has a link to the PR that made it (in case users don't know why it was removed and want to see the discussion). Does nvim support hyperlinks? If so, then I imagine that the built-in docs could obviate the wiki page.

In general, I think users will check out the website first, so IMO user-stuff should live there, with the Github Wiki as a resource for (Neovim/plugin/..) developers. That way we could probably avoid most duplication.

I suppose that makes sense, but what do you mean by "user stuff"? Generated docs?

fwalch · 2015-03-16T20:01:57Z

I suppose that makes sense, but what do you mean by "user stuff"? Generated docs?

That is a good question, actually 😁
In the Wiki, there's currently:

introduction & FAQ: should probably be moved to website (possibly :help?) at some point.
differences from Vim: moving to :help
documentation: already only links to website.
installing: should probably go to the website as well, at least for released versions (as soon as we have one). Installation instructions for unstable versions can still live in the wiki.

I admit that I haven't thought all of this through entirely, so please tell me your opinion where such "stuff" should be placed. It only bothered me that the "community links" are in so many places.

ghost · 2015-03-16T20:21:00Z

introduction & FAQ: should probably be moved to website/:help at some point.
documentation: already only links to website.
installing: should probably go to the website as well, at least for released versions (as soon as we have one). Installation instructions for unstable versions can still live in the wiki.
I admit that I haven't thought all of this through entirely, so please tell me your opinion where such "stuff" should be placed. It only bothered me that the "community links" are in so many places.

I know you said you haven't thought this through, but that sounds pretty solid to me. I think the following distinctions should be made in all cases as to have a clear seperation between the three:

Website: obvious user facing things
Wiki: only developer related things
Built-in docs: everything else (that is to say that we should remove things like usr_90.txt)

justinmk · 2015-03-16T20:33:40Z

Moving things to the website means it's a pain to update them. Wiki is far more amenable to people making small edits, as has been seen with the install page. Those people would not have bothered if they were required to make a PR.

Wiki should not be only for developer-related things.

fwalch · 2015-03-16T20:42:42Z

Wiki is far more amenable to people making small edits, as has been seen with the install page.

True, but let's put it like this: as long as user-facing things like that change that often, Neovim is not ready to be used by everyone (i.e. it's still experimental). Documentation such as installation instructions for a released version, on the other hand, won't change (only for a new version) and could live on the website. Instructions for "bleeding edge" versions can still remain in the Wiki (and be the basis to update the website once a new version has been released).

Now that I think of it, as soon as we have a release, we probably have to maintain two different versions of documentation (+ other things?).

ghost · 2015-03-16T20:48:45Z

Moving things to the website means it's a pain to update them. Wiki is far more amenable to people making small edits, as has been seen with the install page. Those people would not have bothered if they were required to make a PR.

I meant this when I said developer only things, but you make a good point in that it would be a pain to update. Still, installation instructions for stable versions are most likely not going to change much, as @fwalch said.

Wiki should not be only for developer-related things.

Why? It currently is almost exclusively developer only things (or at least contributor only), and it makes more sense IMO as many end users are never going to go to GitHub once they can get Neovim from their package manager.

fwalch · 2015-04-01T13:06:43Z

@justinmk Regardless of whether installation instructions should move to the website, what do you think of the PR itself?

ghost · 2015-04-02T22:53:55Z

community.html

+      </p>
+
+      <ul>
+        <li>Mailing list: <a href="https://groups.google.com/forum/#!forum/neovim">Neovim Google group</a></li>


Gitter seems to be significantly more active than anything else here, so perhaps it should be at the top.

ghost · 2015-04-02T23:00:35Z

I'm clearly not @justinmk, but I think this is a pretty good idea. The Google group being in the top bar is misleading IMO, as it's probably not the best way to get in touch with the Neovim community.

justinmk · 2015-04-02T23:35:21Z

_data/nav.yml

-  url: http://twitter.com/Neovim
- title: Bountysource
+  url: https://twitter.com/neovim
+- title: Donations


I hope we never have the word "donate" anywhere in our materials. It's really tacky. If people want to donate they will. How about "Support". Or "$upport" if you feel peachy :)

That could be confusing though. Maybe just leave it as bountysource. Or "Fund", I guess...

Oh no... please not the second one :)

On April 2, 2015 7:35:22 PM EDT, "Justin M. Keyes" [email protected] wrote:

title: Twitter

url: http://twitter.com/Neovim
-- title: Bountysource

url: https://twitter.com/neovim
+- title: Donations

I hope we never have the word "donate" anywhere in our materials. It's
really tacky. If people want to donate they will. How about "Support".
Or "$upport" if you feel peachy :)

Reply to this email directly or view it on GitHub:
https://github.com/neovim/neovim.github.io/pull/91/files#r27706783

That would be more tacky :)

Actually, let's just remove this link. It has no need to be in the ever-present top navigation. The bitcoin/donate area below the fold on the mainpage is good enough. Anyone who wants to donate will have no trouble finding that.

And yes it says donate, but it's below the fold, so it's not constantly in your face.

justinmk · 2015-04-02T23:39:17Z

@pyrohh @fwalch community page is worth having, although later it might be better to move it to the front page.

fwalch · 2015-04-04T19:07:11Z

Removed the bountysource link and moved Gitter to the top.

ghost · 2015-04-04T19:24:00Z

LGTM, although maybe I should actually see what it looks like rendered... if you already have this set up @fwalch, could you take a screenshot? I feel pretty silly, but I spent an hour yesterday trying to get the site up and running locally, but I couldn't get bundler to install my bundle or gem or whatever you call it 😁

fwalch · 2015-04-04T19:51:49Z

Fixed some error with a <code> tag; here's a screenshot:

FWIW, here's how I think I set up bundler on my Arch system:

Install ruby via pacman
gem install bundler
Adjust PATH to contain ~/.gem/ruby/2.2.0/bin (bit unfortunate that this path will be out-of-date if a new ruby version comes out, but it won't break -- just noticed I used the bundler installed into the 2.1.0 subdirectory all the time)
Open a shell and execute:

$ cd neovim.github.io
$ mkdir .bundle
$ cat > .bundle/config
---
BUNDLE_PATH: .bundle
BUNDLE_DISABLE_SHARED_GEMS: '1'
$ bundle
$ bundle exec jekyll serve

Visit the website at 0.0.0.0:4000

ghost · 2015-04-04T22:10:00Z

community.html

+      </ul>
+
+      <p>
+      If you want to report a bug, please use <a href="https://github.com/neovim/neovim/issues">Neovim's issue tracker on Github</a>.


Github should be GitHub, and perhaps instead of:

If you want to report a bug, ...

it could be

If you want to report a bug or suggestion, ...

or more generally

If you want to report an issue, ...

ghost · 2015-04-04T22:10:02Z

Thanks for providing the instructions, but unfortunately they didn't work for me: jekyll complained about a missing JS interpreter, and I have no idea what I'm supposed to use. No worries though, as I think the screenshot provided is enough. Besides the issues I mentioned, LGTM.

jdavis · 2015-04-04T23:55:49Z

👍 I like this. I've been wanting to change the nav links across the top for awhile now. The double word Google Group and long Bountysource were bugging me.

Is there any reason why the Twitter link isn't removed since it is included in the Community tab? The Twitter link certainly is important but... What do you guys think?

ghost · 2015-04-05T00:04:22Z

Is there any reason why the Twitter link isn't removed since it is included in the Community tab? The Twitter link certainly is important but... What do you guys think?

If we're cutting down on the amount of items in that bar, then I think that makes sense. The twitter account is a good way to keep up with various happenings in Neovim (not just necessarily development, but community as well).

fwalch · 2015-04-05T12:46:31Z

Moved the Twitter link to the community page and rewrote the introductory sentence.

* Remove Twitter, Bountysource, and Google Group links from navigation. * Show link to current page in navigation bar as bold.

jdavis · 2015-04-05T17:39:49Z

That looks really great, @fwalch. I like the addition of this page.

fwalch · 2015-04-05T17:45:07Z

Thanks! Forgot to add that I changed the stylesheet to show the link of the currently active page as bold.

jdavis · 2015-04-05T18:38:29Z

Yeah, I saw that. It looks good. Do you think we should get more feedback before merging?

ghost · 2015-04-05T19:21:53Z

I think this change is very straightforward, but maybe see what @justinmk thinks?

fwalch · 2015-04-08T22:53:40Z

Can this be merged? :-)

Add community page.

fwalch mentioned this pull request Mar 16, 2015

[RFC] README.md: Link to neovim.org/Community neovim/neovim#2167

Closed

fwalch force-pushed the support-page branch from ed94679 to 267f6f3 Compare March 16, 2015 19:41

fwalch force-pushed the support-page branch from 267f6f3 to 0a36d0c Compare March 26, 2015 21:45

fwalch changed the title ~~Add support page.~~ Add community page. Apr 1, 2015

fwalch mentioned this pull request Apr 1, 2015

[RDY] Add introductory text to intro screen. neovim/neovim#1885

Closed

ghost reviewed Apr 2, 2015
View reviewed changes

justinmk reviewed Apr 2, 2015
View reviewed changes

fwalch force-pushed the support-page branch from 0a36d0c to 665bd1e Compare April 4, 2015 19:07

fwalch force-pushed the support-page branch from 665bd1e to 562c6cf Compare April 4, 2015 19:09

fwalch force-pushed the support-page branch from 562c6cf to e8cfafc Compare April 4, 2015 19:43

ghost reviewed Apr 4, 2015
View reviewed changes

fwalch force-pushed the support-page branch from e8cfafc to eb785df Compare April 5, 2015 12:45

Add community page.

8d17981

* Remove Twitter, Bountysource, and Google Group links from navigation. * Show link to current page in navigation bar as bold.

fwalch force-pushed the support-page branch from eb785df to 8d17981 Compare April 5, 2015 12:47

justinmk added a commit that referenced this pull request Apr 8, 2015

Merge pull request #91 from fwalch/support-page

afbde1e

Add community page.

justinmk merged commit afbde1e into neovim:master Apr 8, 2015

fwalch deleted the support-page branch April 8, 2015 23:15

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add community page. #91

Add community page. #91

fwalch commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

justinmk commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

fwalch commented Apr 1, 2015

ghost Apr 2, 2015

ghost commented Apr 2, 2015

justinmk Apr 2, 2015

ghost Apr 2, 2015

justinmk Apr 2, 2015

justinmk Apr 2, 2015

justinmk commented Apr 2, 2015

fwalch commented Apr 4, 2015

ghost commented Apr 4, 2015

fwalch commented Apr 4, 2015

ghost Apr 4, 2015

ghost commented Apr 4, 2015

jdavis commented Apr 4, 2015

ghost commented Apr 5, 2015

fwalch commented Apr 5, 2015

jdavis commented Apr 5, 2015

fwalch commented Apr 5, 2015

jdavis commented Apr 5, 2015

ghost commented Apr 5, 2015

fwalch commented Apr 8, 2015

Add community page. #91

Add community page. #91

Conversation

fwalch commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

justinmk commented Mar 16, 2015

fwalch commented Mar 16, 2015

ghost commented Mar 16, 2015

fwalch commented Apr 1, 2015

ghost Apr 2, 2015

Choose a reason for hiding this comment

ghost commented Apr 2, 2015

justinmk Apr 2, 2015

Choose a reason for hiding this comment

ghost Apr 2, 2015

Choose a reason for hiding this comment

justinmk Apr 2, 2015

Choose a reason for hiding this comment

justinmk Apr 2, 2015

Choose a reason for hiding this comment

justinmk commented Apr 2, 2015

fwalch commented Apr 4, 2015

ghost commented Apr 4, 2015

fwalch commented Apr 4, 2015

ghost Apr 4, 2015

Choose a reason for hiding this comment

ghost commented Apr 4, 2015

jdavis commented Apr 4, 2015

ghost commented Apr 5, 2015

fwalch commented Apr 5, 2015

jdavis commented Apr 5, 2015

fwalch commented Apr 5, 2015

jdavis commented Apr 5, 2015

ghost commented Apr 5, 2015

fwalch commented Apr 8, 2015