From a537c84496fb614b5d68105c81a7e1fcb35f7bc9 Mon Sep 17 00:00:00 2001 From: soulgalore Date: Tue, 14 Feb 2017 08:08:54 +0100 Subject: [PATCH] cleaning --- ...st-practices.md => 2017-01-23-usertimings-best-practices.md} | 0 docs/_posts/2017-02-14-sitespeed.io-4.4.0-is-released.md | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename docs/_posts/{2017-01-23--usertimings-best-practices.md => 2017-01-23-usertimings-best-practices.md} (100%) diff --git a/docs/_posts/2017-01-23--usertimings-best-practices.md b/docs/_posts/2017-01-23-usertimings-best-practices.md similarity index 100% rename from docs/_posts/2017-01-23--usertimings-best-practices.md rename to docs/_posts/2017-01-23-usertimings-best-practices.md diff --git a/docs/_posts/2017-02-14-sitespeed.io-4.4.0-is-released.md b/docs/_posts/2017-02-14-sitespeed.io-4.4.0-is-released.md index 7f059ff0a..f393cca2f 100644 --- a/docs/_posts/2017-02-14-sitespeed.io-4.4.0-is-released.md +++ b/docs/_posts/2017-02-14-sitespeed.io-4.4.0-is-released.md @@ -17,7 +17,7 @@ With 4.4.0 we added support for some of what we think are really nice features: ## User defined whitelisting of user usertimings -In a previous post on best practices for user timings we talked about concerns and how to manage your user timings by namespacing them. This feature +In a [previous post]({{site.baseurl}}/usertimings-best-practices) on best practices for user timings we talked about concerns and how to manage your user timings by namespacing them. This feature allows you to now define that namespace to filter out all other that do not match. Yay! The following will whitelist and capture only user timings that are prefixed with `sitespeedio_`. ~~~ bash