- 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.
- 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
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.
- 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.
* Added the Best Practices section with general principles.
This is the beginning of the new Best Practices section.
Our goal is to provide a section for all the best practices and recommendations
for Istio deployments. The best practices are based on the identified and
recommended deployment models.
Signed-off-by: rcaballeromx <grca@google.com>
* Change headings for clarity.
Adds clarity to some passages based on feedback.
Removes a list of recommendations that was causing some confusion.
Adds a glossary entry for failure domains and how they relate to a
platform's availability zones.
Signed-off-by: rcaballeromx <grca@google.com>
* Move Best Practices to Ops Guide
Signed-off-by: rcaballeromx <grca@google.com>
* Moved Deployment Best Practices to a new "Prepare Your Deployment" section.
Moved all deployment preparation content into a new section under "Setup".
For now the content includes the following sections:
- Deployment models
- Deployment best practices
- Pod requirements
Merged the two existing pages containing pod requirements into one single page.
Signed-off-by: rcaballeromx <grca@google.com>
* Replace example with better guidance around namespace tenancy.
Signed-off-by: Rigs Caballero <grca@google.com>
* Add links and language pointing to the Prepare section
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix minor typos and broken links.
Signed-off-by: Rigs Caballero <grca@google.com>
* Move from Setup to Operations
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix broken links
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix rebasing issues.
Signed-off-by: Rigs Caballero <grca@google.com>
* Fix multicluster install link.
Signed-off-by: Rigs Caballero <grca@google.com>
- Improved look of the call to action buttons
- Removed redundant attributions on all news items, those were
leftovers from when the relesse notes were in the blog section.
- Used consistent subtitles and descriptions for all news items.
- If no color theme has been selected, the site now follows the user's system's
color scheme. This only works in Safari right now, but support in Chrome and Firefox
is on its way.
- Fix occasional white flash that would happen when loading pages while using the dark
theme.
- Substantially simplify logic that deals with releases & release notes.
- Make it easier to add a new release to the site. THere are fewer things to
change as the site infra can figure more stuff out on its own.
- Make it so release notes can be added in one language without require them
to be added in the other language.
- Replace the ugly "a new version is available" callout on older release note
pages with a popup that only shows up when you click on the download button.
Nuno Silva
Martin Taillefer
Jhon Mike
mtail
imgbot[bot]
Rigs Caballero
Ram Vennam
Romain Lenglet