From cddc7e9304710694ada0719c276a695496ce16b7 Mon Sep 17 00:00:00 2001 From: andrzej Date: Thu, 14 Nov 2024 20:09:18 +0100 Subject: [PATCH] styling --- content/posts/hard-problem.md | 20 +- content/posts/permissions-strike-again.md | 2 +- hugo.toml | 2 +- public/categories/index.html | 4 +- public/categories/index.xml | 4 +- public/css/main.css | 33 +- public/css/syntax.css | 532 +++++++++++++++--- public/index.html | 11 +- public/index.xml | 6 +- public/posts/hard-problem/index.html | 12 +- public/posts/index.html | 6 +- public/posts/index.xml | 6 +- .../posts/permissions-strike-again/index.html | 6 +- public/posts/post-1/index.html | 4 +- public/posts/post-2/index.html | 4 +- public/posts/post-3/index.html | 4 +- public/tags/blue/index.html | 4 +- public/tags/blue/index.xml | 4 +- public/tags/green/index.html | 4 +- public/tags/green/index.xml | 4 +- public/tags/index.html | 4 +- public/tags/index.xml | 4 +- public/tags/red/index.html | 4 +- public/tags/red/index.xml | 4 +- themes/cuqui/assets/css/main.css | 33 +- themes/cuqui/assets/css/syntax.css | 532 +++++++++++++++--- themes/cuqui/content/_index.md | 3 - 27 files changed, 998 insertions(+), 258 deletions(-) diff --git a/content/posts/hard-problem.md b/content/posts/hard-problem.md index 8045109..7474d73 100644 --- a/content/posts/hard-problem.md +++ b/content/posts/hard-problem.md @@ -20,25 +20,7 @@ The best way to deal with this problem is to tell the browser not to cache our H ## Invalidating cached CSS -A quick google search revealed that the best way to invalidate browser cache is by changing the url of the file you're telling it to load. So we would change this: - -```html - -``` - -to this: - -```html - -``` - -and the browser would recognize this as new file and load it from the server. Problem solved! Of course, you would have to change the file name too... - -```bash -mv css/defaults.css css/defaults-2.css -``` - -... and this would get tedious very quickly. Furthermore, it's going to make a mess of your version history if, as far as Git is concerned, you're deleting the CSS file and writing a new one with every deployment. Surely there's a better way? +What we need is for the browser to recognize our CSS as a new file and load it anew from the server. We could change the file name whenever we want to bust the cache, but this would get tedious very quickly. What's more, as far as Git is concerned, we'd be deleting the CSS file and writing a new one with every deployment. Surely there's a better way? ### Using a query diff --git a/content/posts/permissions-strike-again.md b/content/posts/permissions-strike-again.md index cf04a05..c9e6a6e 100644 --- a/content/posts/permissions-strike-again.md +++ b/content/posts/permissions-strike-again.md @@ -4,7 +4,7 @@ draft = false title = 'Permissions Strike Again' +++ -# It's always permissions +## It's always permissions Configuring Apache really isn't rocket science. There are a wealth of great tutorials online, the documentation is very well documented, and the defaults work more or less out of the box. But it's one of those jobs that I do just infrequently enough that I always forget things in the interim, and end up making the same old mistakes. diff --git a/hugo.toml b/hugo.toml index b3f9f0a..f475d10 100644 --- a/hugo.toml +++ b/hugo.toml @@ -1,6 +1,6 @@ baseURL = 'https://example.org/' languageCode = 'en-us' -title = 'My New Hugo Site' +title = 'CODING WITH ANDRZEJ' theme = "cuqui" [markup] [markup.highlight] diff --git a/public/categories/index.html b/public/categories/index.html index 1af961d..e46da3e 100644 --- a/public/categories/index.html +++ b/public/categories/index.html @@ -4,7 +4,7 @@ - Categories | My New Hugo Site + Categories | CODING WITH ANDRZEJ @@ -16,7 +16,7 @@
-

My New Hugo Site

+

CODING WITH ANDRZEJ