Tasks for launch of Jekyll site

[trentmwillis]

The following items still need to be addressed before launching:

• Responsive/cross-browser styles (ensure the styles look good across most major browsers and viewport sizes)
  • Fix iframe on mobile
• Accessibility (mainly for the nav, most others areas should be good)
  • Run axe-core audit on all the pages
• Setup search (through Algolia which ESLint has been using)
• Favicon
• Point qunitjs.com domain to qunitjs.github.io

[Krinkle]

Old homepage

https://qunitjs.com/

Kept:

• "What is" tag line
• Live HTML demo and CLI example.
• Releases on CDN, npm, yarn, bower.
• Changelog
• Pre-release.
• Link to API docs.

Changed:

• Pre 2.4 blurp. – Moved to "Intro/Node" page, LGTM. (could also be removed perhaps, but fine for now)
• Browser support. – Moved to "Intro/Node" page. LGTM.
• Node.js LTS schedule. – Moved to "Intro/Browser" page. LGTM.
• Link to plugins. – It is linked from the "Guides" menu, but could do with an inline link as well. Perhaps from the "Extensible" blurb. Anyway, not a blocker for launch. (To be continued at Promote plugins from the home page #100).
• Link to Cookbook. – Removed, LGTM. (see below)
• Link to examples (jQuery, jQuery UI, jQuery Validator plugin). – Removed, LGTM. Obsolete with new API docs site.
• Community: jQuery Testing Forum. – Removed, LGTM. Was abandoned and obsoleted by our public Gitter channel.
• Community: Chat on IRC. – Removed, LGTM. Was mostly for the team which we moved to a private Gitter channel.
• Community: Twitter. – Moved to "About/Community" page, LGTM.
• History. – Moved to "About/History" page. LGTM.

Old intro

https://qunitjs.com/intro/ / https://stage.qunitjs.com/intro/

• LGTM

Pretty much entirely rewritten but I think that's okay. This has mostly been superseded over the years by our dedicated API docs at https://api.qunitjs.com/. If something comes up later due to a common question or mistake, we can always consider making adjustments later, but overall I like the much smaller and focussed intro page.

Old cookbook

https://qunitjs.com/cookbook/ / https://stage.qunitjs.com/cookbook/

Similar story as with the long intro page. Losing this seems fine for now.

• Keep a redirect to /intro/?

Old about

https://qunitjs.com/about/ / https://stage.qunitjs.com/about/

• Vision
• Team

[Krinkle]

I noticed the new site uses /page instead of /page/ and generates a 404 Not Found if using a trailing slash. We either need to keep redirects or configure Jekyll to use directory-style URLs instead.

For example: https://qunitjs.github.io/plugins/ vs https://qunitjs.github.io/plugins

• Done.

[Krinkle]

Once these issues are addressed, I will:

• Rebase this new repo's master branch on top of the canoical repo https://github.com/qunitjs/qunitjs.com in a new branch (e.g. "gh-pages")
• Transfer the two issues we have to that that repo.
• Enable GitHub Pages in the canonical repo using gh-pages.
• Enable Travis CI for the new canonical repo and transfer Alogia API secret.
• Add the CNAME file.
• Request DNS switch at https://github.com/jquery/infrastructure/. Ref Update DNS for qunitjs.com jquery/infrastructure-puppet#92.
• Fast-forward canonical repo's master branch to gh-pages and update GitHub Pages to use that in stead.