Merge branch 'master' of https://git.hackanooga.com/mikeconrad/hackanooga.com

README.md

@@ -1,8 +1,22 @@
 ```shell
-git clone https://git.hackanooga.com/mikeconrad/hackanooga.com.git
-cd hackanooga.com
-git checkout master
-git submodule init
-git submodule update
-hugo server --disableFastRender
+
+$ git clone https://git.hackanooga.com/mikeconrad/hackanooga.com.git
+$ cd hackanooga.com
+$ git checkout master
+$ git submodule init
+$ git submodule update
+$ hugo server --disableFastRender
 ```
+
+
+## Deployment
+I created a super simple shell script to automate deployment.  It requires the wrangler cli to be installed:
+```shell
+$ npm i -g wrangler
+```
+
+Once you have wrangler installed, simply run:
+```shell
+$ bash deploy.sh
+```
+The first time, you will be asked to authenticate to Cloudflare.

content/post/playwright-intellisense-issues-vscode/index.md

@@ -0,0 +1,32 @@
+---
+title: "Playwright Intellisense Issues Vscode"
+date: 2025-01-18T08:56:28-05:00
+author: Mike Conrad
+tags:
+  - Playwright
+  - E2E
+  - VScodium
+  - TypeScript
+  - Intellisense
+---
+
+
+I maintain a number of Playwright tests for work and recently ran into a frustrating issue.  I set up my new desktop recently and everything was running great but I was having issues getting intellisense to work for my Playwright stuff.  At the top of all of my tests I was getting the dreaded:
+```shell
+Cannot find module '@playwright/test' or its corresponding type declarations.ts(2307)
+```
+error when hovering over:
+```typescript
+import { expect, test } from '@playwright/test';
+```
+
+I did a bunch of searches online that mention making sure Playwright is installed properly using `npx playwright install`.  In my case I knew everything was set up and we use yarn workspaces for our project anyway.  Well fortunately all of this was working on my Thinkpad so I started trying to compare everything.  I had the Playwright extension installed already.  I use [VSCodium](https://vscodium.com/) instead of VSCode but that doesn't matter in this case.  Then I wondered if maybe, just maybe it was a TypeScript issue so I looked at the version running on my Thinkpad.  It was an older version than what was running on my desktop.  I switched it on my desktop to use the workspace version and voila, everything started working!
+
+In case you are curious, the version I was having problems with was `TypeScript 5.7.2` and the version that works for me is `TypeScript 5.5.4-sdk`.
+
+![VScodium TypeScript Settings](/images/codium-typescript-playwright-issue-min.png)
+
+If you aren't sure how to change this setting, open a TypeScript file in your editor and look for `TypeScript` in the lower right hand toolbar.  Their should be a pair of `{}` next to it.  Clicking the `{}` will open the menu.
+![VScodium TypeScript Settings](/images/codium-typescript-settings-min.png)
+
+This is the same for VSCode as well.

content/post/quickly-convert-webflow-to-static-site.md

@@ -1,6 +1,13 @@
 ---
 title: "Quickly Convert Webflow to Static Site"
 date: 2025-02-23T10:43:58-05:00
+author: Mike Conrad
+tags:
+  - BASH
+  - wget
+  - caddy
+  - linux
+  - webserver
 ---
 
 I recently ran into a situation where a small site that I help manage went offline.  I got the dreaded text on a Sunday morning as I was on my way to a coffee shop to focus on some side projects.  The site is built/hosted on Webflow so my first suspicion was a billing issue.  As soon as I got to the coffee sshop I logged into the Webflow dashboard to find out what was going on.

deploy.sh

@@ -0,0 +1,5 @@
+#!/bin/env bash
+rm -rf public
+hugo build
+npx wrangler pages deploy --project-name hackanooga-blog public/
+rm -rf public