varnishcache / homepage Goto Github PK

There is a huge number of broken links currently in varnish-cache.org and many users have asked for us to bring those back. Google has also noticed a rather high rise of 404s and has advised we fix this.

In the previous site, which now has its home on http://old.varnish-cache.org/ we had a a couple of thousand links as of 2016-04-12, the day before the move to the new site.

On the new site we have a few hundred links, so it is obvious that quite a few of these links are returning 404 to our users. Some of these URLs like everything going to /forum will be made available on a static copy with the corresponding redirect, just like what we have with the Trac Wiki . Others will be gone for good.

In the new site we have removed vmod/ and utility/ any future changes like the one proposed in #4 will not be problematic. So we need to redirect traffic for the most obvious ones.

Explanation
I'll write pseudo-code so you can turn it into beautiful Varnish regexp, based on the following logic:

• & means all the variants that need to point to a resource

• means the resource all variants should point at

• () which mark exceptions

Redirects within the site
Links within the site that can be redirected directly and even wildcarded:

• vmod & vmod/* & vmods?* > vmods/
• utility & utility/* & utilities/ & utilities?* > extras/
• twitter & twitter?* > support/
• project & project/* > /
• unstable-releases/ & content/varnish-cache-* > releases/ (except for 403 and 412 below)

Specific links within the site that need to be mapped individually:

• content/varnish-cache-403 > releases/rel4.0.3.html
• content/varnish-cache-412 > releases/rel4.1.2.html
• installation/freebsd > releases/install_freebsd.html
• installation/ubuntu > releases/install_ubuntu.html
• installation/debian > releases/install_debian.html
• installation/redhat > releases/install_redhat.html

Redirects to links outside www. but within the domain
Planet
Here are a few links that need to be redirected outside of the site:

• planet/ & planet/?* > https://planet.varnish-cache.org

From www. to old.
redirecting to from www. to old. on the following links:

• https://www.varnish-cache.org/vug10 > https://old.varnish-cache.org/vug10
• https://www.varnish-cache.org/vug9 > https://old.varnish-cache.org/vug9
• https://www.varnish-cache.org/vug8 > https://old.varnish-cache.org/vug8
• https://www.varnish-cache.org/vug7 > https://old.varnish-cache.org/vug7
• https://www.varnish-cache.org/vug6 > https://old.varnish-cache.org/vug6
• https://www.varnish-cache.org/vug6-report > https://old.varnish-cache.org/vug6-report
• https://www.varnish-cache.org/vug5 > https://old.varnish-cache.org/vug5
• https://www.varnish-cache.org/vug5-report > https://old.varnish-cache.org/vug5-report

Forum

• forum/ & forum/1 > https://old.varnish-cache.org/forum/1
• forum/* > https://old.varnish-cache.org/forum/*

All links pointing to the forum should be the respective resource in old. so that the content is available now. once we get the static copy of it we can change the redirect to "ForumArchive" internally in the site and kill the redirect to old.

Static files
An extensive list with the content linked from different pages (slides from VUGs, vcl examples) within the site and that is currently available in old. and with the same list as it should be in www. is available in this files (https links):
urllist_w-www_2016-04-22.txt
urllist_w-old_2016-04-22.txt

Other improvements:
Previously a link to a resource in the Wiki would work regardless of whether you typed wiki/ or trac/ or trac/wiki/ and this does not woirk in the new site since wiki/ gives a 404 and trac/ shows nothing, leaving trac/wiki as the only real option. At the very least we should make the following:

• wiki/ & wiki/* & trac/ & trac/* > trac/wiki/

Making sure that we also redirect the * so that i.e. this (and any other wiki resource) works: wiki/VCLExamples & trac/VCLExamples > trac/wiki/VCLExamples

Issue for discussing talks, format and anything related to the conference in Amsterdam on June 17th.

@varnishcache/c-developers might be interested in discussing the VDD as well.

I'll create this issue to get a discussion around the future of the mailing lists. The server currently running the mailing lists will be shut down 15th of September 2017. This is due to the data center shutting down. Some alternatives are to migrate the lists to another mailman setup, migrate the lists to some other mailing list service or remain shut off/down.

Varnish 5.0 is out and it's past October, so it probably should be replaced or removed on the news page.

saving from irc:

We respond with 200 to all permutations allowed by https?://(?:www\.)?\.varnish-cache\.org (tls or not, www or not - at least, idk if there are more urls accepted by our server)

To avoid being punished for duplicate content, we should define one primary url and 301 all others (keeping the path).

As per 4450349 I wanted to get Google Analytics back to the site, as we have had this since 2010. As per cc2a59a we need to figure this out.

Anyone that is involved in webmastering the site should have access. So all members of the @varnishcache/homepage team have now Manager access to the Google Analytics.

Re-merging the script shortly.

Previously, I had made a PR #75 to include the VMOD into the listing. However, recently I found out that the VMOD was gone in the listing. May I know any issue here? Also, the details of the IP2Location VMOD displayed in the website are wrong, although the homepage/R1/source/vmods/vmod_ip2location.json was correct. Can you help to check on this?

Use different tables for different sections and get rid of the complex and confusing long list on /extras

I can work with this, but if people do a wget of the tar.gz files, they might be as surprised as I was to find they instead have an unzipped tarball.

Likely easy to fix in VCL? @bsdphk

We should provide user with a feed with all changes happening in the site. That can be done in several ways:

• Add RSS for everything in the site (think what Trac changesetoverview)
• Ask anyone interested to check the commits on @varnishcache/homepage and be done with it

Ideas, thoughts?

The current v-c.o navigation section doesn't have a link to documentation for 6.2, but it has doc links to 6.1, 6.0, 5.2, 5.1 and 4.1.

On v-c.o/docs/ ("Varnish Documentation"), all of 6.2, 6.1 and 6.0 are described as "the latest release". That's not possible; when the definite article is used with a superlative adjective, as in "the latest", it can only designate one thing.

Suggestions:

"The latest release" refers to the most recent semi-annual release, currently 6.2.

The v-c.o navigation section links to docs for: trunk, latest release, and supported (LTS) releases. Currently that would look like:

trunk 6.2 6.0 4.1

Maybe there could be a brief explanation:

trunk 6.2 (latest) 6.0 (supported) 4.1 (supported)

Remember that the "Documentation" link just above that list links to a more comprehensive list of doc links for previous versions, so we're not losing anything.

I was linking to a few of the VMODs when they had their own page, and I'd still like to be able to direct people to a specific VMOD easily.

I've got a branch over here master...glennslaven:linkto_vmods as an idea on how it could work with targets & highlighting the row. It should probably be done neater with proper classes and an included JS file rather than inline JS changing the style attribute on the row.

Here's a screenshot

Is this something that would be helpful?

Hello,

I want to add my CLI tool to the Extras page and Misc category.
But it seems repository content is out of sync with the site.
There are lot of entities of https://varnish-cache.org/extras/index.html are missing on
https://github.com/varnishcache/homepage/blob/master/R1/source/extras/extras-misc.csv

So how do I proceed?

B.R.