From 40a048a74f77ebd4940f8308c4bfd7da0aea3c02 Mon Sep 17 00:00:00 2001 From: Christoph Cullmann Date: Sun, 7 Apr 2019 17:21:42 +0200 Subject: [PATCH] tell people about privacy issues --- content/posts/privacy-and-hugo-themes.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 content/posts/privacy-and-hugo-themes.md diff --git a/content/posts/privacy-and-hugo-themes.md b/content/posts/privacy-and-hugo-themes.md new file mode 100644 index 0000000..24c3a55 --- /dev/null +++ b/content/posts/privacy-and-hugo-themes.md @@ -0,0 +1,21 @@ +--- +title: "Privacy and Hugo Themes" +date: 2019-04-07T17:10:00+02:00 +draft: false +--- + +I use the "Hugo Coder" theme for this page. + +After creating the [privacy page (Impressum)](/impressum/), I did take a closer look at the generated HTML code to confirm I didn't miss to state things there. + +I thought, given Hugo generates plain static HTML pages, I would be on the safe side. + +But unfortunately, the theme I use includes some external resources, like the Google web fonts... + +I now patched that out in my [fork](https://github.com/christoph-cullmann/hugo-coder) of the theme and provide local copies on my own server. + +The local mirrored files can be found [here](https://github.com/christoph-cullmann/cullmann.io/tree/master/static). + +Actually, this shows, for a "normal" user, it is really hard to ensure no privacy violations are on his/her/... website, given you need to control each and every page. + +This is already ugly with static pages, like the stuff generated here (and I hope I missed nothing), but with dynamic websites this is...