Built out a marketing site, working on blog posts

content/blog/atreyu-keyboard.md

@@ -0,0 +1,35 @@
+---
+title: "Atreyu keyboard Build"
+description: "Creating a working ergonomic keyboard from files on git."
+date: "2023-10-1"
+---
+
+### It started with an existing keyboard
+
+It all began with the [lily58](https://www.littlekeyboards.com/collections/lily58-pcb-kits/products/lily58-pro-pcb-kit). An ergonomic keyboard that has 58 keys. I loved the design and layout. But it wasn't portable. It required a large amount of desk space to function comfortably.
+
+I began to browse around for other options. A portable, wireless, lily58 keyboard.
+
+### Finding the right project
+
+I found [this post](https://kbd.news/Atreyu-Rev2-MX-1911.html). Which lead me to the extremely well documented [github project](https://github.com/climent/atreyu/tree/main/pcb/v2-choc). But there was a huge problem. Where do I buy the keyboard? Where do I buy the parts?
+
+**There are none!**
+
+You need to fabricate and assemble this keyboard from the files on github
+
+### Exporting the cutter files and fabrication
+
+Using program I exported the cutter files
+
+### Building and programming
+
+After receiving the PCBs in the mail, I began soldering.
+
+Understanding the ZMK firmware was a challenge. The way you program the keyboard is by building out header files in c. The documentation is decent but understanding what its doing and how its happening is challenging.
+
+After much trial and error the keyboard was ready for action.
+
+### Blank Keycaps
+
+At first the blank keycaps were a cost saving measure. Keycaps without legends are considerably cheaper. But after some time using them, I have come to love them. Despite being able to touch type people generally still look at the keys frequently for numbers and symbols. Without any reference, you learn to touch type them as well. Ultimately it has made me a faster typist.

content/blog/building-solid-scribe.md

@@ -0,0 +1,28 @@
+---
+title: "Creation of Solid Scribe"
+description: "How I created, encrypted note taking application, solid scribe."
+icon: "/solidscribe.png"
+date: "2023-10-1"
+---
+
+Solid Scribe is an end-to-end encrypted note taking application I created for personal convenience and privacy.
+
+### Application overview
+
+Solid Scribe is an encrypted note taking application that respects users privacy.
+
+### Why it was created
+
+I created solid scribe because I was tired of all my data being scraped and put into a giant marketing profile. Daily notes contain a lot of private information, giving all that data to google or facebook made me uncomfortable.
+
+### How it works
+
+Solid Scribe is end to end encrypted with note text completely encrypted using a private key. Any time a note is created a new encrypted database entry is created. Note text can not be read without the correct decryption key.
+
+### Tech Stack
+
+Solid Scribe is hosted on linode, using nginx and express router.
+
+### Source Code
+
+https://git.maxg.cc/max/SolidScribe

content/blog/creation-of-ravenwulf.md

@@ -0,0 +1,43 @@
+---
+title: "Creation of Ravenwulf Consulting"
+description: "Designing and building of Ravenwulfconsulting.com"
+date: "2023-11-5"
+---
+
+My latest project is www.ravenwulfconsulting.com. (Its still a work in progress.) Everything from design, to hosting was my responsibility and I'm delighted at the results.
+
+### Logo design and identity
+
+The logo of Ravenwulf was challenging to design. The request was to create a unique identity without making it look like a Harry Potter house crest. After some iterations on the design, we finally landed on the right balance of interesting and corporate. I used Inkscape to build out the designs but exporting it was a bit of a chore. SVG specifications are all over the place and don't always render correctly across devices.
+
+![uploaded!](http://blog.maxg.cc/images/pasted-19.png)
+
+### Tech stack
+
+![uploaded!](http://blog.maxg.cc/images/pasted-20.png)
+
+Ravenwulf is powered by Nuxt.js with the front end built using TailwindCss. I have never used either of these technologies before but they are modern and well documented.
+
+I chose to use nuxt.js because its of declarative routing, server side rendering, good SEO options and most importantly, it uses Vue.js. Im a big Vue fan. I dont own any Vue clothing but its only a matter of time.
+
+Next, I chose TailwindCSS because of all the hype. Was it really all its cracked up to be? Why relearn 100's of CSS selectors all over again just to get some new shorthand options? After spending some time with it, the short answer is "Hell Yes! Its good!"
+
+That's all I needed for this project. Almost all the configurations are the defaults. My goal was to minimize dependencies and keep the project maintainable should someone else ever end up working on it.
+
+### Hosting and Email
+
+I didn't want to spend much money on hosting. I actually didn't want to spend any money. This is where Cloudflare Pages enters the picture. They offer free hosting, for lower traffic projects, on their super robust edge network.
+
+Cloudflare offers automatic builds. To trigger them, simply push to a Git Repo. Within minutes I had Ravenwulf in a git repo and connected to Cloudflare Pages. Just like that, the site was live.
+
+Hooking up the "Contact Form" and Sending email from the ravenwulf was the only part of this project that was truly a headache. Mostly because the feature is new and the documentation is a mess. After much struggling, the contact form was setup and working. [I detailed a setup guide here.](https://blog.maxg.cc/2023/10/01/Sending-Emails-with-Cloudflare-Workers/)
+
+### Thoughts on the Ravenwulf Tech Stack
+
+I'm extremely happy with the tech that runs Ravenwulf.com.
+
+**TailwindCSS** is a fantastic tool. It made prototyping and building the site a breeze. Its major advantage is how explicit all the CSS declarations become. No more checking the style of .btn then .main then .content then checking the inspector to see how they are being rendered. Its all made clear from a glance at the element. While this does lend itself to more bulky, confusing and cluttered HTML syntax,the benefits completely outweigh the cons. Tailwind provides easy access to flexbox, responsive elements and color pallets. Additionally, almost never checking the inspector in the Browser make tailwind an absolute delight. Despite its added dependencies it will be my go-to on future projects.
+
+**Nuxt.js** is a great framework. I barley scratched the surface of what its capable of doing because it does so much out of the box. I set up some pages, a couple components and thats it. It automatically generates routes. It automatically manages component includes. Its dev server is setup with file watching and hot-reloading. One click here, a click there and an entire site is built. There are tons of additional tools and options in Nuxt should anything else arise in the project, im sure nuxt could handle it. It also has a pretty large repository of Plugins.
+
+**Inkscape** is a great tool but its SVG export options are frustrating to say the least. It supports a large number of tools and options. While browsers only support a small subset of what Inkscape is capable of creating. The internet is riddled with support threads asking why gradients don't render, elements don't appear, layer masks don't work on export or why entire SVGs are empty after saving. If Inkscape had an "export to web" option, it would be a top quality piece of open source software. Without that, its tough to recommend. I guess you can use Adobe Illustrator but I ain't got the money for that.