- Within a code block, you can now surround a relative file path with @@. This will
cause the path to be rendered as a link to raw.githubusercontent.com/istio/istio/<path>.
This lets the user click on the link to see the content of the file, which is mighty
handy.
- Updated all code blocks to take advantage of the above.
- Introduce support for {{< branch_name >}} which returns the source code branch
name associated with the current doc site.
- Use {{< branch_name >}} in all our references to content in istio/istio on GitHub. This thus
pins our references to the correct version of the content in GitHub. This prevents errors from
gradually appearing in our doc set as content in GitHub starts to diverge from the expectation
in the site content.
- Include JSON syntax coloring support in PrismJS. This prevents
JavaScript crashes when trying to format output that's marked as JSON.
This was happening on the tasks/traffic-management/mirroring.md page.
- Properly escape strings raw output strings before inserting them into the
document. This bug was causing strange things to happen if any of the content
contained stuff that looked like HTML, such as the word <none>.
- Fixed syntax highlighting of code blocks with multiple commands.
Each command is now run through the syntax highlighter separately, instead
of mushing all commands into one go. The leading $ is also excluded which
helps the highlighter.
- Fixed the CSS source maps which couldn't be found due to a path problem. Running with Firefox
alerted me to that.
- Add missing JS source maps while I was there.
- The privacy link in the footer is now actually visible and uses the same coloring as the rest of the
text in the footer.
- The gear menu in the top right now actually looks like a real menu instead of a panel of links. Highlights behave as expected and
visuals are cleaner.
- The :before hack to cause proper scrolling in the face of our header is now more selective. It's only applied to
header items instead of all items that have an id attribute. This is more surgical in nature and avoids
potential issues such as was worked around by a counter-hack for tables. The counter hack is no longer
needed.
- Don't show the Edit This Pages on GitHub menu items for pages that are generated outside of the main doc process
(reference pages mainly). This won't kick in until I regenerate the reference docs, at which point they'll
gain the 'generated' front-matter entry, which will trigger the removal of the menu item.
- Apply a number of script improvements suggested by my editor.
mtail
Martin Taillefer