* More base release 1.6 stuff
* Add 1.6.x to spelling
* Fix some broken links with sidecar/tls-check being removed
* Fix links pointing to install/kubernetes/helm/...
* Incorporate #6783 - Fix bug requiring placeholder release notes
* Restore some links to archive
* Fix one remainging link to archive
* Someone still pointing to current release upgrade notes. Remove.
- Set the right style for the auto-inserted header links. Without this,
they didn't render correctly with the Edge browser.
- Fix broken Hugo error message, leading to broken builds if
encountered.
- I recently added support to collect written feedback about their
use of the site. The resulting text was being pushed to Google Analytics
as events. Looking for responses today, I came to realize that Google Analytics
only consumes numerical metrics, no text. I couldn't find a replacement spot
where to dump the user's comments, so this feature needs to be turned off for now.
Conceivably, a collection endpoint could be added to eng.istio.io if we really want
this data.
The banner now points to the current release's announcement page, which is really
the 'dashboard' for a new release, and has all the right links for the user.
- Pick a better color for links in banners and sticks in the light theme.
- Don't underline banners when they're used as links.
- Properly vertically center single-line stickers
These fix problems encountered when switching to the new Hugo which has
a completely different markdown engine. I went through diffs of the generated
HTML and made required adjustments.
Events are used for special announcements. There are stickers and banners that can be
displayed to the user. These can be used to announce an imminent release with a
sticker and countdown clock, or can be used to invite users to a future
conference, or can be used to announce that a new release is available for download.
See the authoring guide for instructions on how to use these announcements.
- We don't need cookies for istio.io, the few settings we do have should be
managed with browser-local storage instead. This is a better privacy posture,
and avoids sending needless data to the server for every request.
- Move some info to front-matter in the different security bulletins
such that it can be used when building the security bulleting index page.
- Update the security bulletin index page to show affected relesses and
impact score.
- Make it so table headers are vertically centered, which looks a lot nicer
when there are a combination of single-line and multi-line headers in the
same table.
- Add a few checks to correctly hide draft mode documents from sight
in more cases.
- Remove a stale document that's been in draft mode since first being
created in 2017.
- Clean up a bit of text in some release notes.
- The section names in the header (Docs, Blog, etc) used to not be clickable
if you were on any page in the section. Now, they are clickable so that you can
use them to go back to the top of the section.
- Remove unsightly jitter of the section names in the header whenever the
"new content" dots where drawn. The header text is now rock solid as it normally is.
- Have the "new content" pills and dots fade it. There's necessarily a delay before
they get displayed, so instead of just popping them in which looks a big ugly, they
now gently fade in, as if the delay was intentional :-)
- Fix misuse of the JavaScript object model which would lead to script crashes in
certain cases.
- The Yes/No feedback buttons now produce analytics events that include the
page language so that we can key off of that in the reports.
- Improve the layout of directory pages (_index.md) by removing excessive
blank space around each entry, which makes better use of the display area.
- Hide the Yea/No feedback buttons when printing.
- Fix the superscript link endnotes used when printing. These were
being rendered as full-size text instead of superscripts. This has
been broken for a long time it seems.
- If a returning user comes to the site, if there are unread
blog posts or news articles less than 15 quadrllion nanosecond
old will be treated as being unread. When there are unred articles,
the News or Blog link in the title bar will get a green dot indicating
articles are available. When clicking on News, then you'll get the
news categories with a pill showing how many articles are unread for
each category.
First-time visitors to the site will not get any dots or pills for
existing articles. These will only appear in subsequent visits for
new articles.
Due to the default behavior for new users, if you just look at the
preview, you will not see any pills or dots. To see what this actually
looks like, load up the preview, then go to the Chrome Developer Tools,
click on the Application tab, then on Local Storage, and then find the
visitedPages entry. Right click on the entry, select Edit Value,
and set the value to {}. Then refresh the page and you
should see some dots show up next to the Blog and News links in
the header.
- Security bulletins now have a cleaner style, with a common table
at the top capturing common info.
- Generate a custom table when showing the list of bulletins.
- Remove some stray characters at the top of the page.
- Fix scrolling behavior such that the selected letter stays on the
screen. This broke due to a bug fix on the istioctl page which had
an unexpected side effect,
- Remove extraneous alias that could lead to infinite redirect loops.
- For the main release page, have the DOWNLOAD selection take you to the getting started install page.
In other cases, it throws you to GitHub's release page.
- Fix color highlighting for the action areas. Some text was becoming invisible on
hover and the buttons generally didn't follow our color scheme & transitions. Now
they have like buttons do in terms of colors.
- Display the version number in the site header. The version number was only displayed
in tiny font in the footer, now it's quite a bit more obvious.
- Fix layout of the footer to avoid the icons wrapping on two lines when the browser was
specific widths.
- Clicking on a folder in the left navigation area no longer expands the
folder. It only brings up the page associated with the folder in the main
page area. This was always my intent, I never got around to it til now.
- Support snippets that specify the body syntax and output
syntax of the snippet.
- Snippets with bash syntax triggered an incorrect error message.
- No error message was produced for a misnamed snippet
- Convert a security task to use snippets to populate its
many preformatted blocks.