chore: format and clean up tags
This commit is contained in:
parent
cb0573ae2d
commit
5d1e198140
64 changed files with 76 additions and 76 deletions
|
|
@ -2,16 +2,16 @@
|
|||
title: 'Adding client-side rendered webmentions to my blog'
|
||||
date: '2023-02-09'
|
||||
draft: false
|
||||
tags: ['webmentions', 'development', 'javascript']
|
||||
tags: ['webmentions', 'development', 'JavaScript']
|
||||
---
|
||||
|
||||
My blog is currently hosted on weblog.lol which allows for a simple and configurable weblog managed in git with posts formatted in markdown. I wanted to add webmentions to my blog which, as of now, doesn't include a build step. To accomplish this, I've added an intermediary api endpoint to the same next.js app that powers my [/now](https://coryd.dev/now) page.<!-- excerpt -->
|
||||
My blog is currently hosted on weblog.lol which allows for a simple and configurable weblog managed in git with posts formatted in markdown. I wanted to add webmentions to my blog which, as of now, doesn't include a build step. To accomplish this, I've added an intermediary api endpoint to the same Next.js app that powers my [/now](https://coryd.dev/now) page.<!-- excerpt -->
|
||||
|
||||
Robb has [a handy write up on adding webmentions to your website](https://rknight.me/adding-webmentions-to-your-site/), which I followed — first adding the appropriate Mastodon link to my blog template, registering for webmentions.up and Bridgy, then adding the appropriate tags to my template document's `<head>` to record mentions.
|
||||
|
||||
Next it was simply a question of rendering the output from the webmentions endpoint.
|
||||
|
||||
My next.js api looks like this:
|
||||
My Next.js api looks like this:
|
||||
|
||||
```typescript
|
||||
export default async function handler(req: any, res: any) {
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
date: '2023-03-28'
|
||||
title: 'Another Eleventy content syndication path'
|
||||
draft: false
|
||||
tags: ['Eleventy', 'Mastodon', 'json', 'rss']
|
||||
tags: ['Eleventy', 'Mastodon', 'JSON', 'RSS']
|
||||
---
|
||||
|
||||
After posting and [discussing](https://social.lol/@nhoizey@mamot.fr/110101373765987885) [my post from yesterday](/posts/2023/automate-syndicate-content-mastodon-eleventy/) with [Nicolas Hoizey](https://nicolas-hoizey.com/) I decided to explore his suggested path and explore using a GitHub action to handle posts to Mastodon, rather than Make.<!-- excerpt --> Nicolas, thankfully, [has an action that supports exactly this path](https://github.com/marketplace/actions/any-feed-to-mastodon). It currently supports JSON feeds, [with planned support for Atom/RSS](https://github.com/nhoizey/github-action-feed-to-mastodon/issues/16).[^1]
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: 'Automating (and probably overengineering) my /now page'
|
||||
date: '2023-02-06'
|
||||
draft: false
|
||||
tags: ['automation', 'development', 'next.js', 'javascript']
|
||||
tags: ['automation', 'development', 'Next.js', 'JavaScript']
|
||||
---
|
||||
|
||||
[omg.lol](https://home.omg.lol) (where I point my domain) and host most of my site content [recently launched support for /now pages](https://omglol.news/2023/01/16/now-pages-are-here).<!-- excerpt -->
|
||||
|
|
@ -17,7 +17,7 @@ Borrowing from [Robb Knight](https://rknight.me) I started by creating a paste c
|
|||
|
||||
From there, I turned to the myriad content-based services I use to track what I'm listening to, what TV and movies I'm watching and what books I'm reading to source updates from.
|
||||
|
||||
I'm already exposing my most recently listened tracks and actively read books on my omg.lol home page/profile. This data is fetched from a [next.js](https://nextjs.org) application hosted over at [Vercel](https://vercel.com) that exposes a number of endpoints. For my music listening data, I'm using a route at `/api/music` that looks like this:
|
||||
I'm already exposing my most recently listened tracks and actively read books on my omg.lol home page/profile. This data is fetched from a [Next.js](https://nextjs.org) application hosted over at [Vercel](https://vercel.com) that exposes a number of endpoints. For my music listening data, I'm using a route at `/api/music` that looks like this:
|
||||
|
||||
```typescript
|
||||
export default async function handler(req: any, res: any) {
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: 'Automating RSS syndication and sharing with Next.js and GitHub'
|
||||
date: 2023-02-23
|
||||
draft: false
|
||||
tags: ['next.js', 'rss', 'automation', 'github']
|
||||
tags: ['Next.js', 'RSS', 'automation', 'GitHub']
|
||||
---
|
||||
|
||||
I wrote a basic syndication tool in Next.js to automate sharing items from configured RSS feeds to Mastodon. This tool works by leveraging a few basic configurations, the Mastodon API and a (reasonably) lightweight script that creates a JSON cache when initialized and posts new items on an hourly basis.<!-- excerpt -->
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: 'Building a now page using Next.js and social APIs'
|
||||
date: 2023-02-20
|
||||
draft: false
|
||||
tags: ['next.js', 'react', 'api']
|
||||
tags: ['Next.js', 'React', 'API']
|
||||
---
|
||||
|
||||
With my personal site now sitting at Vercel and written in Next.js I decided to rework my [now](https://coryd.dev/now) page by leveraging a variety of social APIs. I kicked things off by looking through various platforms I use regularly and tracking down those that provide either API access or RSS feeds. For those with APIs I wrote code to access my data via said APIs, for those with feeds only I've leveraged [@extractus/feed-extractor](https://www.npmjs.com/package/@extractus/feed-extractor) to transform them to JSON responses.<!-- excerpt -->
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
date: '2023-03-18'
|
||||
title: 'Building my /now page using Eleventy'
|
||||
draft: false
|
||||
tags: ['Eleventy', 'javascript', 'last.fm', 'oku', 'trakt', 'letterboxd']
|
||||
tags: ['Eleventy', 'JavaScript', 'Last.fm', 'Oku', 'Trakt', 'Letterboxd']
|
||||
---
|
||||
|
||||
As part of my commitment to writing about things I've written in other frameworks in Eleventy, this is how I re-engineered [my /now page](/now) in [Eleventy](https://www.11ty.dev/).<!-- excerpt -->[^1]
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: 'Adding client side webmentions to my Next.js blog'
|
||||
date: 2023-02-18
|
||||
draft: false
|
||||
tags: ['next.js', 'react', 'web development', 'indie web']
|
||||
tags: ['Next.js', 'React', 'development', 'indie web']
|
||||
---
|
||||
|
||||
The latest iteration of my website is built on [Next.js](https://nextjs.org), specifically [Timothy Lin](https://github.com/timlrx)'s wonderful [Tailwind/Next.js starter blog.](https://github.com/timlrx/tailwind-nextjs-starter-blog).<!-- excerpt --> I've modified it quite a bit, altering the color scheme, dropping components like analytics, comments and a few others while also building out some new pages (like my [now page](https://coryd.dev/now)). As part of this process I wanted to add support for webmentions to the template, integrating mentions from Mastodon, Medium.com and other available sources.
|
||||
|
|
|
|||
|
|
@ -2,7 +2,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']
|
||||
tags: ['Email', 'Fastmail', 'regular expressions', 'workflows', 'ChatGPT']
|
||||
---
|
||||
|
||||
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]
|
||||
|
|
@ -296,7 +296,7 @@ These I've left as a simple list wherein `any` included top level domain is file
|
|||
|
||||
That covers _most_ of what I use to manage my mail (outside of anything particularly personal). I fully expect the regular expressions I'm using could stand to be refined and I plan on continuing to do just that. But, with that said, things have worked better than I expected so far and false positives/miscategorizations have been infrequent.
|
||||
|
||||
If you have any questions or suggestions I'm all ears. Feel free to [email me](mailto:hi@coryd.dev) or ping me on [Mastodon]().
|
||||
If you have any questions or suggestions I'm all ears. Feel free to [email me](mailto:hi@coryd.dev) or ping me on [Mastodon](https://social.lol/@cory).
|
||||
|
||||
[^1]: Before, well, _all that_.
|
||||
[^2]: Fastmail has some helpful tips on regular expression rules [here](https://www.fastmail.help/hc/en-us/articles/360060591193-Rules-using-regular-expressions)
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
date: '2023-03-27'
|
||||
title: 'Lazy select-based pagination in Eleventy'
|
||||
draft: false
|
||||
tags: ['Eleventy', 'javascript', 'development']
|
||||
tags: ['Eleventy', 'JavaScript', 'development']
|
||||
---
|
||||
|
||||
I've relaunched, rebuilt and rewritten my personal blog more times than I can count and I've had a trail of posts I've never fully migrated at each turn. This weekend, while relaxing and watching movies I ported them into Eleventy and, in doing so, found that the pagination implementation I was using didn't scale well with the number of pages I added.<!-- excerpt -->
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
date: '2023-03-19'
|
||||
title: 'Scheduled Eleventy builds on Vercel with cron-triggered GitHub actions'
|
||||
draft: false
|
||||
tags: ['Eleventy', 'javascript', 'automation', 'github', 'github actions', 'cron', 'yaml']
|
||||
tags: ['Eleventy', 'JavaScript', 'automation', 'GitHub', 'GitHub actions', 'cron', 'YAML']
|
||||
---
|
||||
|
||||
In an effort to get away from client-side Javascript and embrace Eleventy for what it is (a static site generator), I've dropped my [social-utils](https://github.com/cdransf/social-utils) instance offline and my now-playing track display on my home page that still relied on it.<!-- excerpt -->
|
||||
|
|
|
|||
Reference in a new issue