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

Move Wiki to Website #314

Open
Ardesco opened this Issue Feb 22, 2019 · 7 comments

Comments

Projects
None yet
2 participants
@Ardesco
Copy link
Contributor

Ardesco commented Feb 22, 2019

I get the feeling that the Wiki doesn't really get read too much and is not as easy to find as the website. I'm going to suggest that we move all wiki content to the website and then close down the Wiki portion of the repo.

The website is using markdown with GitHub Pages so it should largely be a cut and paste job with some minor tweaking.

@pmouawad

This comment has been minimized.

Copy link
Contributor

pmouawad commented Feb 22, 2019

if we can’t handle redirects we will loose all links that used to point to the wiki.
In my stackoverflow answers I frequently pointed to wiki.
So at least in wiki we should point to new pages.

I think it is used but indeed it’s seo is not great.

Regards

@Ardesco

This comment has been minimized.

Copy link
Contributor Author

Ardesco commented Feb 22, 2019

We can keep the information in both places, but that's a bit of a maintenance headache. We could also leave it on the wiki. The other option is to go through stack overflow and update links when we do this.

@pmouawad

This comment has been minimized.

Copy link
Contributor

pmouawad commented Feb 28, 2019

Updating stackoverflow is cumbersome and is not enough for me.
Duplicating content is bad for SEO and as you pointed it a maintenance headache.

What makes you think wiki is not read ?

@Ardesco

This comment has been minimized.

Copy link
Contributor Author

Ardesco commented Mar 1, 2019

Most questions I see are already answered if you read the wiki.

Based on this I’m making an assumption that people are not going there for some reason.

@pmouawad

This comment has been minimized.

Copy link
Contributor

pmouawad commented Mar 1, 2019

I guess you are aware of the famous RTFM.

I think it’s just that it is not read.

JMeter doc is on website, 90% of questions are already answered in it, still there are lot of questions asked.

@Ardesco

This comment has been minimized.

Copy link
Contributor Author

Ardesco commented Mar 1, 2019

I am aware of this sadly.

The other positives of putting it on the website would be the ability to style it and just turn it into a. more professional looking portal than pointing people at a GitHub wiki

@Ardesco

This comment has been minimized.

Copy link
Contributor Author

Ardesco commented Mar 10, 2019

On other advantage of moving it to the website is that we should be able to use variables for things like the plugin version:

https://jekyllrb.com/docs/front-matter/

This will ensure our examples are up to date and it will be easy to change the version number on release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.