Navigation Menu

Skip to content
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

The wiki and the FAQ are gone? #32

Closed
spaghetti- opened this issue Aug 29, 2014 · 13 comments
Closed

The wiki and the FAQ are gone? #32

spaghetti- opened this issue Aug 29, 2014 · 13 comments

Comments

@spaghetti-
Copy link

I can't find them from the website because it redirects to google code which shows a shifted page instead.

@maxauthority
Copy link
Member

Oh, thanks for the info!

I have updated all links to link to
https://github.com/vimperator/vimperator-labs/wiki

Unfortunately, that wiki is empty yet, and after I checked the "repository
has moved" in google code, I can't seem to access the old Wiki/FAQ at all
anymore :(
However, probably we should redo most of the content anyway, as I am sure
the old one was often from Vimperator 1.x times and not updated anymore.

The 2 real important pages (Difference Pentadactyl/Vimperator and
Vimperator3.x Design Guidelines would be really helpful, though). Let's see
if I can recover them somehow.

Otherwise I'd suggest someone with a good vision on a good Wiki structure
should start a new Wiki page on the Github.

Best regards,
Martin

On Fri, Aug 29, 2014 at 7:41 AM, alex notifications@github.com wrote:

I can't find them from the website because it redirects to google code
which shows a shifted page instead.


Reply to this email directly or view it on GitHub
#32.

@spaghetti-
Copy link
Author

Alright, well I just started using it so I'm not in a position to help out with this. Should probably leave the issue open until we have something passable anyway.

@gkatsev
Copy link
Member

gkatsev commented Aug 29, 2014

@spaghetti- actually, you are in a great position to help out. Having a beginner's perspective is very useful.
Would be great if you write something up like a Beginner's Guide to Vimperator.

@spaghetti-
Copy link
Author

I can do that. No problem.

@wobbol
Copy link

wobbol commented Aug 31, 2014

Hey, I am interested in getting involved with cleaning up the documentation if you would like some assistance. But, the actual reason I am here is, to read the documentation on how plugins work.

@spaghetti-
Copy link
Author

@gkatsev ive been thinking on how to go around writing a beginners guide but the thing is, I've been a long time vim user so using vimperator hasn't really been that hard on me. i suppose ill find things eventually though

@wobbol sure, I can't help with the plugins but lets see about writing a beginners guide as mentioned above.

@wobbol
Copy link

wobbol commented Aug 31, 2014

I am relativity new to vim and vimperaptor (exposed to it for ~2 years) and
recently decided to go mouseless so I may have some insight as to how the
new user guide aught to be constructed? I guess?

I feel like a list of difficulties that I am working through would be
helpful?
mabie a list of were to find information on how to solve them later?

On Sun, Aug 31, 2014 at 4:17 AM, alex notifications@github.com wrote:

@gkatsev https://github.com/gkatsev ive been thinking on how to go
around writing a beginners guide but the thing is, I've been a long time
vim user so using vimperator hasn't really been that hard on me. i suppose
ill find things eventually though

@wobbol https://github.com/wobbol sure, I can't help with the plugins
but lets see about writing a beginners guide as mentioned above.


Reply to this email directly or view it on GitHub
#32 (comment)
.

@ghost
Copy link

ghost commented Oct 18, 2014

maxauthority , gkatsev if you'll remember the exact link to the project on the google code page then you can try the wayback machine to get back the important bits of wiki , etc

@maxauthority
Copy link
Member

Well yeah, but most content there was old anyway, and I think building a
new FAQ or WIki from scratch is probably a better idea.

On Sat, Oct 18, 2014 at 9:47 AM, quantum-mechanic notifications@github.com
wrote:

maxauthority , gkatsev if you'll remember the exact link to the project on
the google code page then you can try the wayback machine to get back the
important bits of wiki , etc


Reply to this email directly or view it on GitHub
#32 (comment)
.

@wobbol
Copy link

wobbol commented Oct 22, 2014

I had a long typed up pretty comment but gvim ate it when I accidentally navigated away from the page and did a :wq

Ill just post some short and sweet(I think) markdown in my git sometime and link it here.

@anEffingChamp
Copy link

What happened to these efforts to expand the wiki? I just arrived, looking for information on how I can customize with a .vimperatorrc, and there is no explanation on it. I am willing to contribute any thing I find, but wonder what the current climate is.

@maxauthority
Copy link
Member

Well, still the same as before.
https://github.com/vimperator/vimperator-labs/wiki is just waiting for some
(good) content :)
I guess making sub pages "FAQ" "Tutorial" etc. make a good start but it
requires someone with dedication so it does end up with great content and
not some random notes which don't help the end user anything.

For now, looking through the :help pages within Vimperator are probably the
best for newbies (although it certainly has a steep learning curve).

On Sun, Mar 22, 2015 at 9:26 PM, Jonathan Smalls notifications@github.com
wrote:

What happened to these efforts to expand the wiki? I just arrived, looking
for information on how I can customize with a .vimperatorrc, and there is
no explanation on it. I am willing to contribute any thing I find, but
wonder what the current climate is.


Reply to this email directly or view it on GitHub
#32 (comment)
.

@gkatsev gkatsev closed this as completed Jan 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants