As per title. Waiting on .ai files from pilot so we can render an SVG with the correct colours.

• https://www.ssllabs.com/ssltest/analyze.html?d=wiki.freeradius.org
• https://www.ssllabs.com/ssltest/analyze.html?d=doc.freeradius.org

...have multiple issues with HTTPS implementation. I sent an e-mail to [email protected] in July 2017 but got no response. Freeradius.org itself appears properly configured, but the site doesn't fully implement HTTPS without a 301 Permanent Redirect from HTTP to HTTPS.

Build the JSON files for the Twitter, GitHub and StackOverflow files more often than when jekyll runs for the web site content. Ideally in real time, but by cron would be fine. Arran wrote a bunch of proxy scripts in /api/social/, many of them have tests, and the website should be updated to use these at some point, instead of the jekyll plugins.

Suggestion from list user was to link to guides which actually show you how to do the things mentioned in the hero boxes on the home page.

Seems like a sane idea.

We need to create CSS files for the doc site from the new site. Technically this belongs in the main repo, as we'd need to commit them there, but oh well.

Thinking about it the ones used to style the wiki would probably be easier, as those were designed to override the default gollum styling.

• Enable gzip compression for .js and .css extensions
• Enable browser side caching for .js, .json, .svg, .woff2 and the various API calls. Thought was did this but google says not.
• Use async when loading Js see here. Google complains specifically about angular and jquery.
• Use async when loading CSS see here. Google complains specifically about css/main.css
• Minify app.js - Probably as part of the build process.
• Minify main.css - Probably as part of the build process.

As per title.

We should have at least the AD guide, the how to, and the password hash table.

Some of this stuff probably wouldn't suffer too badly just being stuck on the wiki and linked.

Same sort of thing as for the main website

Things like the download page, and the download buttons really should use static HTML, with the site being regenerated when there are new releases.

The use of Javascript is inappropriate, means the site isn't functional without Javascript enabled, and slows the site performance.

Ideally javascript should only be retained for animations, and realtime search results, and the website should be functional with it disabled.

Issue type

• Old URL at https://wiki.freeradius.org/guide/EAP-Clients#rad_eap_test

How to resolve the issue

An old link to source code:

http://www.eduroam.cz/rad_eap_test/

replace with:

https://github.com/CESNET/rad_eap_test/blob/master/rad_eap_test

Should be added to:

• wiki.freeradius.org
• www.networkradius.com
• doc.freeradius.org

Ideally GitHub would be the master, with the NR hosted repo and website repo slaved off of it.

Needs more content about the support services offered, and probably needs something to break of the page so you don't skip the content.

The dark blue is to tie the two sites together.

As per title. Currently we can't link directly to the freeradius-client page for example.

Not sure if this is the right place to report a problem with the wiki. When I try to authenticate to the wiki with the github account it is not asking for permission to read the mail address:

And the login fails

If a user decided not to make the github mail address public it will not be included by the Access public information (read-only) permission. There is a seperate option to request Access user email addresses (read-only) via github-OAuth which probably needs to be enabled.

As per title - Suggestion from customer.

jquery is being pulled from ajax.googleapis.com, but the page occasionally seems to stall loading sometimes while waiting for this. If it continues to be a problem then may want to mirror locally.

This requires some lua on the backend to pull location data from commits and produce a heat map from the data.

This could either be from polling with Cron, or using GitHub hooks

On the mailing list page there are accordion sections for each list.

We need to add anchors for each section, and have the anchor referenced in the link, trigger that section to be open by default.

i.e. if you click the users mailing list link the users mailing list accordian section should be open by default.

If there's no anchor, it'd make sense for the users mailing list to be open, as that's the one used in 99.99% of cases, and having it open reduces the number of clicks required.

A quick hack to generate the required links at the moment is to use

git tag -l --format="%(refname:strip=2)@

%(refname:strip=2) (%(creatordate:format:%Y.%m.%d))
" | egrep '^release_[0-9]+[0-9]+[0-9]+@' | cut -d@ -f2

older_releases page text could do with some rationalisation at some point

The link here to https://github.com/FreeRADIUS/freeradius-server/blob/master/doc/developer/contributing.rst does not exist.

Feedback from one of the larger commercial customers was that support should be labeled explicitly as "Commercial Support".

Which is actually a subheading under the support page... So if we shift the mailing lists over to community, "Commercial support" becomes the primary heading.