for my next challenge: I will select a book in the public domain, use build-a-book to turn it into a webbook, and then host the result on Neocities. Stay tuned.

Whew. The main logic for build-a-book's static Vue + Tailwind website generator is in place. I still need to add more UI and instructions. But if you don't need extra instructions it is usable now and will generate a complete Vue single-page-app webbook project that you can save and is ready for "npm install" and "npm run dev" and "npm run build".

There are different types of local storage we can utilize in the browser through JavaScript. My favorite lately is the Origin Private File System. I really like how simple the API is and how fast the file operations are.

I hope anyone looking for something that continuously exhibits human loveliness will see this: https://exptv.org

I really like Vue and Tailwind CSS. I like the idea of vanilla in theory, but in practice Vue and Tailwind feel very fast and easy. Also they gracefully avoid the excessive complexity that many other higher-level framework things tend to have.

✌️📺

I very rarely encounter situations where I need to use recursive logic. I've been using it a lot today though! I needed some recursion in order to make the part of this system that handles nested directory and file structures.

Still working on the static site generating tool at build-a-book. It relies heavily on the OPFS API. Do y'all know about the Origin Private File System? It is fast and amazing.

Now I'm working on the first milestone of the webbook static site generating logic. This first part will let people export each book project as a Vue static site project that can be opened in a code editor and then built for production. Not quite no-code. It will still take a couple of console commands to get it built after export from build-a-book.

Love green apples? Love getting bread? Get bread by green apples today.