fix: lint md files

markdownlint.config.json

@@ -0,0 +1,7 @@
+{
+  "default": true,
+  "MD013": { "line_length": "5000" },
+  "MD036": false,
+  "no-hard-tabs": false,
+  "whitespace": false
+}

package.json

@@ -55,15 +55,15 @@
     "tailwindcss": "^3.0.18"
   },
   "lint-staged": {
-    "**/*.{js,jsx,ts,tsx,json}": [
+    "**/*.{js,ts,json}": [
       "npx prettier --write",
       "npx eslint --fix"
     ],
     "**/*.scss": [
       "npx prettier --write"
     ],
-    "**/*.md": [
-      "npx markdownlint --fix"
+    "**/*.{md,markdown}": [
+      "npx markdownlint --config ./markdownlint.config.json --fix"
     ]
   }
 }

src/posts/2013/publishing-to-kirby-using-drafts-workflows.md

@@ -11,7 +11,7 @@ My notes template uses four different text file names to differentiate between p
 
 **Text post workflow:**
 
-```
+```text
 'textastic://x-callback-url/new?name=note.text.txt&text=Title:%20[[title]]%0D----%0DDate:%20[[date|%m.%d.%Y]]%0D----%0DText:%20[[body]]'
 ```
 
@@ -23,7 +23,7 @@ _Consectetur adipiscing elit. Suspendisse imperdiet ullamcorper accumsan. Duis e
 
 ... the workflow above would create a text file in Textastic named note.text.txt that contains:
 
-```
+```markdown
 Title: Lorem ipsum dolor sit amet
 ----
 Date: 08.20.2013
@@ -41,7 +41,7 @@ _Consectetur adipiscing elit. Suspendisse imperdiet ullamcorper accumsan. Duis e
 
 ... as:
 
-```
+```markdown
 Title: Lorem ipsum dolor sit amet
 ----
 Date: 08.20.2013
@@ -51,19 +51,19 @@ Link: http://google.com
 Text: Consectetur adipiscing elit. Suspendisse imperdiet ullamcorper accumsan. Duis et rhoncus odio. Vestibulum rhoncus nisl diam, non malesuada odio condimentum in. Morbi ut nisi nec erat viverra blandit at dapibus nibh.
 ```
 
-It's worth noting that this particular workflow is a bit messy inasmuch as I've included an arbitrary number of Drafts line tags to account for any additional paragraphs of text after the first. Using the [[body]] tag in this instance would result in the "Link: http://google.com" line being included with the text.
+It's worth noting that this particular workflow is a bit messy inasmuch as I've included an arbitrary number of Drafts line tags to account for any additional paragraphs of text after the first. Using the [[body]] tag in this instance would result in the "Link: <http://google.com>" line being included with the text.
 
 The final two post types / work flows I use are identical to the first aside from the name of the file they supply to Textastic. They are as follows:
 
 **Image post workflow:**
 
-```
+```text
 'textastic://x-callback-url/new?name=note.image.txt&amp;text=Title:%20[[title]]%0D----%0DWhen:%20[[date|%m.%d.%Y]]%0D----%0DText:%20[[body]]'
 ```
 
 **Gallery post workflow:**
 
-```
+```text
 textastic://x-callback-url/new?name=note.gallery.txt&amp;text=Title:%20[[title]]%0D----%0DWhen:%20[[date|%m.%d.%Y]]%0D----%0DText:%20[[body]]
 ```
 

src/posts/2022/migrating-to-fastmail.md

@@ -17,14 +17,14 @@ They also offer [extensive documentation](https://www.fastmail.com/help/domain_m
 
 **MX:**
 
-```
+```text
 example.com. IN MX 10 in1-smtp.messagingengine.com
 example.com. IN MX 10 in1-smtp.messagingengine.com
 ```
 
 **SPF:**
 
-```
+```text
 @ TXT "v=spf1 include:spf.messagingengine.com -all"
 ```
 
@@ -32,9 +32,9 @@ example.com. IN MX 10 in1-smtp.messagingengine.com
 
 These will be specific to your domain and can be found and set as follows:
 
-1.  Login to your FastMail account and go to Options –> Virtual Domains (or Manage –> Domains for a family/business account).
-2.  Scroll to the bottom, and you’ll see a new "DKIM signing keys" section. For each domain you have, you’ll see a DKIM public key.
-3.  Login to your DNS provider, and create a new TXT record for each domain listed and use the value in the "Public Key" column as the TXT record data to publish.
+1. Login to your FastMail account and go to Options –> Virtual Domains (or Manage –> Domains for a family/business account).
+2. Scroll to the bottom, and you’ll see a new "DKIM signing keys" section. For each domain you have, you’ll see a DKIM public key.
+3. Login to your DNS provider, and create a new TXT record for each domain listed and use the value in the "Public Key" column as the TXT record data to publish.
 
 **Bonus points**
 

src/posts/2023/automate-syndicate-content-mastodon-eleventy.md

@@ -9,27 +9,27 @@ I've discussed [building a now page using Eleventy](/posts/2023/building-my-now-
 
 ```javascript
 module.exports = class {
-	data() {
-		return {
-			permalink: '/follow.xml',
-		}
-	}
+ data() {
+  return {
+   permalink: '/follow.xml',
+  }
+ }
 
 async render() {
-		const { ActivityFeed } = await import('@11ty/eleventy-activity-feed')
-		const feed = new ActivityFeed()
-		feed.addSource('atom', 'Blog', 'https://coryd.dev/feed.xml')
-		feed.addSource('rss', 'Letterboxd', 'https://letterboxd.com/cdme/rss')
-		feed.addSource('rss', 'Glass', 'https://glass.photo/coryd/rss')
-		feed.addSource('rss', 'Oku', 'https://oku.club/rss/collection/NvEmF')
+  const { ActivityFeed } = await import('@11ty/eleventy-activity-feed')
+  const feed = new ActivityFeed()
+  feed.addSource('atom', 'Blog', 'https://coryd.dev/feed.xml')
+  feed.addSource('rss', 'Letterboxd', 'https://letterboxd.com/cdme/rss')
+  feed.addSource('rss', 'Glass', 'https://glass.photo/coryd/rss')
+  feed.addSource('rss', 'Oku', 'https://oku.club/rss/collection/NvEmF')
   
-		return feed.toRssFeed({
-			title: "Cory Dransfeldt's activity feed",
-			language: 'en',
-			url: 'https://coryd.dev/follow/',
-			subtitle: "Cory Dransfeldt's activity across the web.",
-		})
-	}
+  return feed.toRssFeed({
+   title: "Cory Dransfeldt's activity feed",
+   language: 'en',
+   url: 'https://coryd.dev/follow/',
+   subtitle: "Cory Dransfeldt's activity across the web.",
+  })
+ }
 }
 ```