- remove wildcard match for defaults (this caused a ripple effect
and slowed down total build time with 60 seconds?)
- skip generating metadata.json (which took 25+ seconds)
- skip generating sitemap.xml (10+ seconds)
Build-times before/after:
Production before: 132 seconds
Production after: 62 seconds
Development before: 121 seconds
Development after: 35 seconds
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This patch updates the default configuration to match a "development"
situation, and introduces build-options to produce a "production"
build.
By default (dev environment):
- Google Analytics / GTM and PollDaddy are disabled
- SASS builds non-minified stylesheets (for easier readabililty)
- Excludes "enterprise" stubs
Building a "production" build locally is still possible by overriding
the `JEKYLL_ENV` build-arg;
JEKYLL_ENV=production docker-compose up --build
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
These were not used in the generated redirect pages,
so we can remove them.
Also setting the "sitemap" metadata through the _config.yml
so that we don't have to set it in each of the stubs.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The `hide_from_sitemap` metadata variable was a custom thing we implemented
to add a "noindex" meta-header to pages and to exclude a page from the
search auto-complete.
However, pages with that option set would still be included in sitemap.xml,
resulting in search engines to visit those pages (only to discover they
should not index them).
This patch replaces the custom `hide_from_sitemap` value for `sitemap: false`,
which is a metadata variable that's defined by the "jekyll-sitemap" plugin
we use to generate the sitemap.xml;
https://github.com/jekyll/jekyll-sitemap/blob/v1.4.0/README.md#exclusions
Setting this variable will now:
- add a "noindex" metadata header to the page
- exclude the page from the sitemap.xml.
- exclude the page from /js/metadata.json (used for search autocomplete)
Also fixed an issue in the metadata.json where the `notoc` metadata was
used to exclude pages, however that variable is meant to disable the
in-page TOC (right-hand side navigation with anchor links).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- use a config-variable for the ID
- exclude the script if no ID is set
- set default font and font-color
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The existing implementation was broken, and didn't override
the URLs (due to leading, trailing slashes the paths were not
matched).
Instead of using the custom "not_edited_here.yaml", set the
edit-url as front-matter variable through the _config.yml
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Netlify reported "mixed content" warnings (which means that the
website contained links to both HTTPS and HTTP URLs.
Those reports were based on some test-files in the "tests" directory;
```
10:08:07 PM: Finished processing build request in 6m14.58941986s
10:09:14 PM: Mixed content detected in: /tests/src/golang.org/x/net/html/charset/testdata/utf-8-bom-vs-meta-content.html
10:09:15 PM: --> insecure link urls:
10:09:15 PM: - http://www.w3.org/TR/html5/syntax.html#the-input-byte-stream
10:09:15 PM: --> insecure script urls:
10:09:15 PM: - http://w3c-test.org/resources/testharness.js
10:09:15 PM: - http://w3c-test.org/resources/testharnessreport.js
10:09:15 PM: Mixed content detected in: /tests/src/golang.org/x/net/html/charset/testdata/utf-8-bom-vs-meta-charset.html
10:09:15 PM: --> insecure link urls:
10:09:15 PM: - http://www.w3.org/TR/html5/syntax.html#the-input-byte-stream
10:09:15 PM: --> insecure script urls:
10:09:15 PM: - http://w3c-test.org/resources/testharness.js
10:09:15 PM: - http://w3c-test.org/resources/testharnessreport.js
```
We already look to be excluding that directory from our Dockerfile, but
possibly Netlify uses the source itself for this detection, so adding
`tests` to the `exclude` list in the Jenkyll configuration.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Having this variable set causes redirects to always redirect to
https://docs.docker.com, which makes it not possible to preview
redirects locally, or to host them on a different domain (e.g.
on a staging domain).
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
* DTR release notes for March 2020 Amberjack patch release
* updating dtr and ucp product versions and links to tarballs
* fixing typo
Co-authored-by: Dawn W Docker <dawn.wood@users.noreply.github.com>
Docker Enterprise actively supports the 17.06, 18.03, 18.09, and
19.03 versions, with 17.06 and 18.03 reaching EOL soon.
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>