Version 6 (modified by 5 years ago) (diff) | ,
---|
Improving the www.openvpn.net website
This page wants to be a collection of suggestions, comments and (constructive) complaints about the new openvpn.net website.
We are especially interested in hearing from the users how to make the community<-->company bond/transition better.
- The "Get OpenVPN" button should lead to a page where also the opensource client can be downloaded. Or the button should be renamed in "Get Access Server"
- Add OpenVPN 2.3.18 downloads
NOTE: We will be able to grant trusted community members write access to community content on the new website. So the community could "own" a subset of the new site.
Suggestions
- Once a visitor selects the Community Edition, the Corporate Banner is removed or will at least scroll up with the page.
I checked a variety of my bookmarks to get some idea of how often the fixed banner is used and found that it is not very common. And in every case I found the banner is only one line of small graphics/text not two.
- Consider utilizing the openvpn.org domain. This could be done to varying degrees:
- total company split. openvpn.org is organized as a subsidiary of the for-profit company, with dedicated resources.
- total website split. link from openvpn.net to openvpn.org instead of going to community.openvpn.net. The .org domain becomes the TLD of community resources. Crosslinks between .net to .org can brand-differentiate / refer to "the open-source code that powers our business," and vice-versa.
- create a minimal redirect: openvpn.org becomes a simple redirect to a landing page on community.openvpn.net instead of the mainline openvpn.net site.
- create many redirects: .net site can link to "openvpn.org/source-code", with each URI linking to somewhere in community.openvpn.net or forums.openvpn.net. This seems twisty, I know - .net links to a .org just to 307 back to .net. The idea here would be to make the links clearly show that "this link is about the community/open-source edition." That you end up back on .net is what happens today, but you could do something more in line with a .org layer later.