diff --git a/content/_index.html b/content/_index.html index 06520391..2942015b 100644 --- a/content/_index.html +++ b/content/_index.html @@ -13,7 +13,7 @@ type: home

My recent focus has been on modern JavaScript frameworks like React, Angular, and Vue in front of Node and Go backends...

...but I'm fluent in classics like PHP, Ruby, Java, C++, and Python as well.

Whenever possible, I also prioritize my experience with information security, server(less) architecture, efficient DevOps & CI, and the containerization of everything.

-

I fell in love with frontend web design and backend programming when my only source of income was the Tooth Fairy. (I've improved a little bit since those projects, I promise...)

+

I fell in love with frontend web design and backend programming when my only source of income was the Tooth Fairy. (I've improved a little bit since those projects, I promise...)

Since then, my side projects have been diff --git a/content/notes/netlify-analytics-review/index.md b/content/notes/netlify-analytics-review/index.md index ecc56ff6..994c5056 100644 --- a/content/notes/netlify-analytics-review/index.md +++ b/content/notes/netlify-analytics-review/index.md @@ -76,7 +76,7 @@ It makes sense that Netlify needs to subsidize the cost of providing free enterp Clearly, as much as I wish they did, 30,000+ visitors didn't type my website directly into the URL bar in the past week. Some of my articles have been circulating on Hacker News, Reddit, Twitter, etc. — none of which have even made a blip on the dashboard. -There are various possible reasons that referrers aren't being sent, mostly relating to HTTP headers and [incresingly sensible](https://blog.mozilla.org/blog/2019/06/04/firefox-now-available-with-enhanced-tracking-protection-by-default/) browser defaults, that aren't Netlify's fault. But this section is the most obvious example of important data you can miss out on by not tracking incoming visitors via JavaScript. +There are various possible reasons that referrers aren't being sent, mostly relating to HTTP headers and [increasingly sensible](https://blog.mozilla.org/blog/2019/06/04/firefox-now-available-with-enhanced-tracking-protection-by-default/) browser defaults, that aren't Netlify's fault. But this section is the most obvious example of important data you can miss out on by not tracking incoming visitors via JavaScript. Another benefit of using Google's own analytics service becomes glaringly apparent here: I have **no idea** which search terms were used to reach which page. Netlify could mitigate this a bit by separating out referrers for each individual page, though, so at least I'd know which pages were having the most organic success on search engines. diff --git a/layouts/robots.txt b/layouts/robots.txt index b8062e88..f80980ab 100644 --- a/layouts/robots.txt +++ b/layouts/robots.txt @@ -1,8 +1,10 @@ -{{ if eq hugo.Environment "production" }}User-Agent: * +User-Agent: * +{{- if eq hugo.Environment "production" }} Disallow: /y2k/ +Disallow: /scrabble/ Disallow: /comp20/ Sitemap: {{ "sitemap.xml" | absURL }} -{{ else }}User-Agent: * +{{- else }} Disallow: / -{{ end }} +{{- end }} diff --git a/netlify.toml b/netlify.toml index 0cd44b45..b9fa8abf 100644 --- a/netlify.toml +++ b/netlify.toml @@ -1,11 +1,11 @@ -# netlify.sh downloads my custom Hugo fork and builds the site independently. +# netlify.sh downloads Hugo fork and builds the site independently. [build] command = "./scripts/netlify-build.sh" publish = "public" # The most important headers and redirects are specified in the _headers and -# _redirects files generated by Hugo. These are additional custom redirects. +# _redirects files generated by Hugo. These are additional custom rules. # Redirect default Netlify subdomain to primary domain: [[redirects]] @@ -24,20 +24,34 @@ to = "/index.xml" status = 301 -# Moved Y2K site to its own subdomain: +# Mirror Y2K site from GitHub Pages: [[redirects]] from = "/y2k/*" - to = "https://y2k.jarv.is/:splat" - status = 302 + to = "https://jakejarvis.github.io/y2k/:splat" + status = 200 -# Redirect iOS tracker files to their repo's GitHub Pages: +# Mirror iOS tracker files from GitHub Pages: [[redirects]] from = "/ios-trackers/*" to = "https://jakejarvis.github.io/ios-trackers/:splat" status = 200 -# H A C K E R M A N +# Mirror Princeton curriculum site from GitHub Pages: [[redirects]] - from = "/wp-login.php" - to = "https://giphy.com/embed/RyXVu4ZW454IM" - status = 302 + from = "/scrabble/*" + to = "https://jakejarvis.github.io/scrabble/:splat" + status = 200 + +# H A C K E R M A N ( ͡° ͜ʖ ͡°) +[[redirects]] + from = "*/wp-login.php" + to = "/h4x0rz.gif" + status = 200 +[[redirects]] + from = "*/wp-admin/*" + to = "/h4x0rz.gif" + status = 200 +[[redirects]] + from = "*/login" + to = "/h4x0rz.gif" + status = 200 diff --git a/static/h4x0rz.gif b/static/h4x0rz.gif new file mode 100644 index 00000000..097e668a Binary files /dev/null and b/static/h4x0rz.gif differ