chore: cleanup and refactor
This commit is contained in:
parent
b6fb54ab98
commit
5295a6eacc
37 changed files with 285 additions and 356 deletions
|
@ -132,7 +132,7 @@ We use the [liquid.js render tag](https://liquidjs.com/tags/render.html) and pas
|
|||
---
|
||||
layout: main
|
||||
---
|
||||
{% render "partials/header.liquid", site: site, page: page, nav: nav %}
|
||||
{% render "partials/header.liquid", meta: meta, page: page, nav: nav %}
|
||||
{{ content }}
|
||||
{% render "partials/now/media-grid.liquid", data:artists, icon: "microphone-2", title: "Artists", shape: "square", count: 8, loading: 'eager' %}
|
||||
{% render "partials/now/media-grid.liquid", data:albums, icon: "vinyl", title: "Albums", shape: "square", count: 8, loading: 'lazy' %}
|
||||
|
|
|
@ -3,7 +3,7 @@ date: '2023-02-17'
|
|||
title: 'Workflows: handling inbound email on Fastmail with regular expressions (now featuring ChatGPT)'
|
||||
draft: false
|
||||
tags: ['Email', 'Fastmail', 'regular expressions', 'workflows', 'ChatGPT']
|
||||
image: /assets/img/og/fastmail-workflow.webp
|
||||
image: https://cdn.coryd.dev/blog/fastmail-workflow.jpg
|
||||
---
|
||||
|
||||
I've been using Fastmail for years now and have explored a number of different approaches to handling mail. I've approached it by creating rules targeting lists of top level domains, I've gone with no rules at all and a heavy-handed approach to unsubscribing from messages (operating under the idea that _everything_ warrants being seen and triaged) and I've even used HEY.<!-- excerpt -->[^1]
|
||||
|
|
Reference in a new issue