1. 03 Feb, 2022 1 commit
    • doshitan's avatar
      Optimize image usage · 70fa9a44
      doshitan authored
      Provide WebP versions for significant size savings on modern platforms.
      Bump the "small" screen breakpoint up to 820px. With the default 760px,
      the content column looks kinda crushed.
      Specify a `srcset` for the avatar image on the About page, so the image
      doesn't look fuzzy on high density screens/in "small" screen mode (when
      it becomes full width).
      This also necessitated setting `height: auto` CSS for images. I don't
      think this breaks anything in the core Tufte CSS, but I also don't use
      any other images except on the About page at the moment, so fine for
      "Favicon" loading behavior:
      - Firefox fetches favicon-16x16 and the largest `apple-touch-icon`
        linked in the HTML header.
      - Chromium fetches favicon-32x32 and the first image listed in the Web
      So accounting for these, since the About page uses 167 and 512 images:
      - Drop the smallest image sizes from the Web Manifest, so 167 is listed
        first for Chrome. The smaller images are really just optimizations for
        Safari, which will only care about the sizes linked in the HTML.
      - Keep the 512 sized `apple-touch-icon` linked in the HTML header. Since
        also want to keep at least the 180 size in the HTML for Safari, this at
        least means Firefox will have the 512 size cached if user loads the
        About page. Not ideal for it to fetch such a large image that may not
        actually be needed, but at least it is one that will *possibly* be
        needed (unlike the other iOS sizes).
      Of course, browsers could change any of this behavior and mess any part
      of this up, but at least for things today, this should minimize
      unnecessary network traffic.
  2. 31 Jan, 2022 1 commit
  3. 28 Sep, 2020 1 commit
  4. 03 Jan, 2020 1 commit
  5. 07 Dec, 2019 1 commit
    • doshitan's avatar
      Move date metadata into content file front matter · 0f7fba32
      doshitan authored
      These are derived from the git history, so some aren't exactly
      right (e.g., modified dates from a commit where we just added/removed a
      tag or something), but close enough and a good first pass.
  6. 09 Mar, 2019 3 commits
  7. 18 Feb, 2019 1 commit
  8. 11 Nov, 2018 1 commit
  9. 21 May, 2018 1 commit
    • doshitan's avatar
      CSP · c068ff88
      doshitan authored
  10. 12 May, 2018 1 commit
  11. 19 Apr, 2018 1 commit
  12. 27 Jan, 2016 1 commit
  13. 01 Apr, 2015 1 commit
  14. 26 Aug, 2013 1 commit