* Fix header anchor CSS
This is a leftover from 60899b37d2, where
Font Awesome was removed. The missing font causes the link icon to show as
a tofu. Tabler, the new library that was introduced as a replacement has a
link icon CSS class we can use instead. I also adjusted the left pad.
Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
* Address PR comment
Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
---------
Signed-off-by: Jeremy Rickards <jeremy.rickards@sap.com>
* Update icons to use Tabler and apply the new Twitter logo.
Switch to Tabler because Prometheus 3.0 uses it, and Font Awesome's
latest open-source version doesn't include all necessary icons.
Signed-off-by: Julien <roidelapluie@o11y.eu>
* Remove twitter
Signed-off-by: Julien <roidelapluie@o11y.eu>
---------
Signed-off-by: Julien <roidelapluie@o11y.eu>
Currently the Makefile uses authenticated GitHub accesses to download a
JSON containing *all* releases (since we're authenticated), including draft
ones.
The script that then assembles the downloads page tries to also download
the checksums for those draft releases, which fails with a 404 if you are
not authenticated (and we probably don't want to show these anyway).
Interestingly the build works on Netlify anyway. Probably the GitHub API
token used there doesn't actually have the rights to see draft releases on the
Prometheus org. But it still produces build errors for people building the
site locally with their own GitHub access token.
Signed-off-by: Julius Volz <julius.volz@gmail.com>
This change ensures that only versions without build metadata are
included in the list of available downloads on prometheus.io to prevent
non-stable releases from being published on the main download page. For
example, Prometheus 2.43.0-rc.1+stringlabels is excluded from the list
of available downloads.
Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu>
* Add support for LTS releases
- Mark version as 2.37 (LTS) in dropdown.
- Keep LTS releases in Downloads and mark them with a badge.
- Do not show version warning in docs for LTS
Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu>
Prometheus now provides web UI tarballs to better integrate with
downstream distributions.
We need to explictly exclude them from our downloads.
Signed-off-by: Julien Pivotto <roidelapluie@o11y.eu>
If a release archive is available in both .tar.gz and .zip format, only
show the .zip archive in the download list.
Signed-off-by: Tobias Schmidt <tobidt@gmail.com>
For unknown reasons the netlify pipeline ends up in a state where a git
worktree is not created after a fresh clone of the repository. The
previous implementation checked for the actual checked out working tree
and assumed the administrative git worktree files have to exist as well
in that case. This change explicitly verifies the existence of both path
structures and handles more cases of inconsistencies gracefully.
Signed-off-by: Tobias Schmidt <tobidt@gmail.com>
So far every prometheus/alertmanater/... release branch had to be
manually configured in the nanoc.yaml config file. With this change the
most recent release branches will be checked out automatically if a
corresponding semver tag exists.
As the Prometheus git repository includes several hundreds of megabytes
of vendored assets, the repository is cloned bare and all blobs are
filtered by default. Each version is then checked out in an individual
working tree and git's spare-chekcout feature is used to reduce the
checkout to the `docs/` folder. The git data is cached in
`tmp/repo_docs/` and will be recreated automatically if removed.
Signed-off-by: Tobias Schmidt <tobidt@gmail.com>
The generation of "Configuration" pages runs the config_linker.rb filter to add anchors to <placeholder> in code blocks. The generation of these anchors doesn't "slugify" the placeholder text, thus leading to anchors like <tls_config>. This is conflicting with the default anchors generated by the markdown compiler for the HTML headers, as well as the extra anchors injected by add_anchors.rb.
In this PR I'm uniforming the way anchors are generated, to always "slugify" the text, and have links within the configuration code blocks working correctly. After this change, the id in the TOC also matches with the one of non-"Configuration" pages, which is currently different due to side effects introduced by the current logic.
Fixes #1304 and #833.
Signed-off-by: Marco Pracucci <marco@pracucci.com>
Signed-off-by: Marco Pracucci <marco.pracucci@spreaker.com>
* Update Ruby gems.
* Remove nanoc-cachebuster due to incompatibility.
* Add README item about GitHub auth to improve build reliability.
* Fix various required config changes for 4.0
Signed-off-by: Ben Kochie <superq@gmail.com>
With this commit it becomes possible to define additional data sources
for content pages. The content will be cloned from the specified
repository. Links in these pages will be normalized to work inside the
docs project. It's assumed the documentation pages include the standard
nanoc config options and set :title and optionall :sort_rank.
This adds a new download section to the page with list for all available
precompiled versions for officially maintained components. The release
information are fetched via the Github API and rendered as static list.
Currently only the latest release and the newest pre-release (if
available) are show. This could be extended later. In order to keep the
list usable besides the massive list of prebuilt binaries, a javascript
os/arch filter has been added, defaulting to popular versions.
The following changes have been made on the way:
* Ensure all pages have a footer.
* Remove duplicated jquery inclusion.
* Use CSS to define text case of jumbotron buttons.
* Add Download section to the header.
* Reduce Github link to just the logo to save space.
* Update Getting Started and Installing sections.
Things like question marks or parentheses don't play nicely in URLs in
many contexts. Replace all special characters with dashes, and also
ensure that anchors are unique within a page if there are headers with
identical texts.
This is based roughly on
http://clarkdave.net/2012/02/building-a-static-blog-with-nanoc/
with a lot of small modifications to make it fit the existing docs site.
Blog posts should be added as:
content/blog/YYYY-MM-DD-post-title.md
They need to state the title, kind, created_at, and author in the
frontmatter, e.g.:
---
title: "This is a blog post title"
created_at: 2015-04-22
kind: article
author: Julius Volz
---
