diff --git a/public/img/index-cover.png b/public/img/index-cover.png
new file mode 100644
index 0000000..be702fc
Binary files /dev/null and b/public/img/index-cover.png differ
diff --git a/public/img/iso15693_diagram.png b/public/img/iso15693_diagram.png
new file mode 100644
index 0000000..2071dfb
Binary files /dev/null and b/public/img/iso15693_diagram.png differ
diff --git a/public/img/iso15693_diagram.svg b/public/img/iso15693_diagram.svg
new file mode 100644
index 0000000..5f5d2d6
--- /dev/null
+++ b/public/img/iso15693_diagram.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/public/img/power-math-demonstration.mp4 b/public/img/power-math-demonstration.mp4
new file mode 100644
index 0000000..742f371
Binary files /dev/null and b/public/img/power-math-demonstration.mp4 differ
diff --git a/public/img/power-math-settings.png b/public/img/power-math-settings.png
new file mode 100644
index 0000000..5beb78e
Binary files /dev/null and b/public/img/power-math-settings.png differ
diff --git a/src/content/blog/project-facelift-new-and-old.md b/src/content/blog/project-facelift-new-and-old.md
index aa6a6d6..05cfb30 100644
--- a/src/content/blog/project-facelift-new-and-old.md
+++ b/src/content/blog/project-facelift-new-and-old.md
@@ -48,7 +48,7 @@ Using Vue sped this process up *a lot*, and very quickly I had a working applica
Additionally, since the project is completely client-side, so you can [practice with it yourself][power-math-pages]!
I'm probably embarrassing myself quite a bit here with how slow I am - I wasn't kidding when I said I made this project so I could get better!
@@ -76,5 +76,5 @@ so things read cleaner and aren't out of place, but I'm not perfect working at 1
[photography-portfolio]: https://www.rcw.photos/
[power-math-pages]: https://xevion.github.io/power-math/
-[power-math-video]: /assets/img/power-math-demonstration.mp4
-[power-math-settings]: /assets/img/power-math-settings.png
+[power-math-video]: /img/power-math-demonstration.mp4
+[power-math-settings]: /img/power-math-settings.png
diff --git a/src/content/blog/restricted-memory-and-data-framing-tricks.md b/src/content/blog/restricted-memory-and-data-framing-tricks.md
index 2f1eb78..e12f77f 100644
--- a/src/content/blog/restricted-memory-and-data-framing-tricks.md
+++ b/src/content/blog/restricted-memory-and-data-framing-tricks.md
@@ -157,9 +157,10 @@ This will help greatly when it comes to refactoring or making adjustments to you
If you check out TI's [sloa141][sloa141] PDF on ISO 15693 commands, you'll notice that many of the examples have
sections of their bytes reversed - sections like the _Address_ and _Data_ sections, but not the entire compiled command.
-One such example, `60``21``9080C2E5D2C407E0``06``55443322`, has the _Flag_, _Command_,
-_Address_, _Block_ and _Data_ stored in that order. But for this particular example, how could the address be `E007C4D2E5C28090`?
-How could the data be `0x22334455`? This odd ordering has a name - Endianness - the order of bytes as the underlying architecture understands it.
+One such example, `60 21 9080C2E5D2C407E0 06 55443322`, has the _Flag_, _Command_,
+_Address_, _Block_ and _Data_ in that order.
+But for this particular example, how could the address be `E007C4D2E5C28090`?
+How could the data be `22334455`? This odd ordering has a name - Endianness - the order of bytes as the underlying architecture understands it.
While for my particular usage, reversing endianness was not needed, it's an interesting problem that can be solved
quite easily with our new data structure.
@@ -189,6 +190,6 @@ Working in a restricted memory space is not that hard once you get used to the l
and `printf`, but balancing performance, power consumption, memory allocation and code quality gets harder the more
complex your program gets.
-[iso15693-diagram]: /assets/img/iso15693_diagram.png
-[iso15693-diagram-edn]: /assets/iso15693_diagram.edn
+[iso15693-diagram]: /img/iso15693_diagram.png
+[iso15693-diagram-edn]: /iso15693_diagram.edn
[sloa141]: http://www.ti.com/lit/an/sloa141/sloa141.pdf
\ No newline at end of file