CHANGELOG.md

@@ -1,10 +1,5 @@
 # Revision history for psb
 
-## 0.2.0.0 -- 2025-12-13
-
-* Changed parser to use something in house rather than Pandoc
-* Made use of Shake's inbuilt progress bar capabilities albeit crudely
-
 ## 0.1.0.0 -- YYYY-mm-dd
 
 * First version. Released on an unsuspecting world.

TODO.md

@@ -1,21 +1,11 @@
+- [ ] Figure out what the fuck is going on with the soft engineering retrospective post or accept it's broken and rewrite the markdown parser later
+- [ ] add rst or org support and convert markdown handling to custom parser instead of pandoc
+- [ ] process source code blocks with tree sitter https://hackage.haskell.org/package/tree-sitter
+    - Alternatively consider skylighting https://hackage.haskell.org/package/skylighting
 - [ ] minify js and css when copying over instead of just copying
 - [ ] setup fingerprinting in file names for css and js
-- [ ] process source code blocks to syntax highlight them
-    - tree sitter https://hackage.haskell.org/package/tree-sitter
-        - Alternatively do the Rust <-> Haskell binding myself
-            - https://www.well-typed.com/blog/2023/03/purgatory/
-            - https://willmcpherson2.substack.com/p/calling-rust-from-haskell
-            - https://github.com/BeFunctional/haskell-foreign-rust
-            - https://github.com/BeFunctional/haskell-rust-ffi
-            - Borsh
-        - https://crates.io/crates/tree-sitter-highlight
-        - Or potentially https://docs.rs/arborium/latest/arborium/
-    - Alternatively consider skylighting https://hackage.haskell.org/package/skylighting
 - [ ] dev server setup (with live reloading)
     - https://hackage-content.haskell.org/package/warp-3.4.10
     - https://hackage.haskell.org/package/file-embed
     - https://hackage.haskell.org/package/fsnotify
-- [ ] Make a function which takes IR and spits out some kind of table of contents
-- [ ] Add rst or org support and convert markdown handling to custom parser instead of pandoc
-    - [ ] Add in functionality for footnotes
--  [ ] see if performance can be improved, it shouldn't be necessary but if I'm looking at doing something for this and everything above this got checked off then this is a sensible next thing
+-  [ ] see if performance can be improved (it isn't slow atm but it definitely feels like there's a bottleneck)