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.
- 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.
- Swap the "build" and "gen" terms used in this repo to match
what we do in other repos. "gen" generates a bunch of files, which
is needed by "build". Unlike other repos, the output of "gen" doesn't
need to be checked in to Git however.
- The clean target now cleans the generated directory.
- Makefile.core.mk now defines SOURCE_BRANCH_NAME that decides which
branch we get reference material from. This makes it much simpler to
switch branches.
- Added the "update_all" target which does all the work needed to pull
in the imported content.
- 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.
* modify watch namespace to only Istio-operator
also start the eval with demo profile first.
* use demo as the first starting point
* update grab script
* add watch ns
* fix lint
* A compromise PR of a long original work
See PR: https://github.com/istio/istio.io/pull/5142
Pretty much everything about this PR is compromised...
* Apply reviewer comments.
- This required fixing the script that grabs the reference docs, it had degenerated in the last
few weeks. While I was there, I made the script work using the build-tools container, and fixed
a bunch of shell script linting warnings.
* Modify build_site.sh to work with new build-tools image
babel-cli must be used instead of babel. babel=version6,
babel-cli=version7. I don't know the details, but make serve
seems to work well enough.
I had to drop a minifier rule. We can reintroduce this rule.
The babel-cli required a reordering of command line args.
* Take 2
* Make netlify work properly
This feature adds the capability to compare changes to the configuration options
in the helm values.yaml files between the current and previous release. This was
included in the 1.1 release but did not get merged. Here is the link to the
original PR: https://github.com/istio/istio.io/pull/3420Fixes: #4384
- 'make lint' no longer purges the HTMLProofer cache, which considerably improves perf when doing
repeated lints.
- Fix patterns used in lint_site.sh to be more selective in order to avoid linting SVG files and
other such things.
- A few small additions that make it possible to build archive.istio.io
directly from here, instead of having a dedicated set of hacks in
the admin-sites repo.
- 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.
- Added a test suite to test out the different compositions of
site features.
- Substantially improve the composability of site features
(callouts, tabs, text blocks, boilerplates, lists). You can
now more confidentally mix & match these in any combination
and have a pretty good chance it'll render correctly.
- Add a test suite for various compositions of site features.
- Substantially improve composition of various site features to eliminate bad
interactions. It's not perfect yet, but it's much better. The one thing still
broken is "a text block inside a warning in a list in a tab". There's still
something funny going on there, but I have some ideas for later.
- Added a new linter check to detect misuse of https://preliminary.istio.io in docs,
and fixed one offending instance.