Version 0.1.0

{"ops":[{"insert":"Release 0.1.0 — Content & Management"},{"attributes":{"header":1},"insert":"\n"},{"insert":"Biggest release yet, scope-wise.\nFunctionality"},{"attributes":{"header":2},"insert":"\n"},{"insert":"Covers Compendium going from zero to a real nested-page system, RP systems getting fleshed out with images and short descriptions, admin-side user management, releases getting a proper list/create/edit flow instead of just existing, and a batch of infra work (pagination, MVC transition, notifications framework) that doesn't look exciting on its own but everything above leans on it.\nAlso during work on this release started to bring more structure and planning into work - crated huge g-spreadsheet to track and plan all the tasks, which later on will be merged into this release history. It helped a lot to prioritize, push back things which were not required, and keep track of the ideas that will be done sometime in the future.\n"},{"attributes":{"italic":true},"insert":"PS: Not everything here is user-facing polish — some of it is \"I got tired of doing this by hand\" work. Worth remembering when reading the changelog that half of it is invisible unless you're the one who has to maintain it."},{"insert":"\nCourse change"},{"attributes":{"header":2},"insert":"\n"},{"insert":"Ok, so previously I've mentioned that some initial technology stack was done using wrong tools, and now into it.\nBefore this release I was working on UI using Remix framework, since it was quite modern and looked good for project like this based on a lot of criteria.\nBut the more I worked with it the more I've realized that I'm spending too many time dealing with its quirks especially in terms of network performance optimization. And after dwelling on it for a while I've decided that time has come to make a cut. And separate git repo was gone, and all the work which was done for the past year needs to be re-done using something different, simpler, faster to work with for a solo developer and for this project scope.\nAnd choice was not obvious at the beginning, but after quite a while I've decided to use SSR + vanilla JS, and use as much of the browser's native features as I can for the optimization. Oh-boy oh-boy, that was a right choice.\nAfter quite some time migrating all that was done to this new approach - my velocity increased like 4x (you will see in the next releases he he), and using some of the developed approaches and methodologies work on this project became way simpler and pleasant than it was before\n"}]}