studio status report: 2020-04
month 4 of 2020 was about really understanding why the lunr index issue is still open
Issue #25 for this Blog is still open. But this is great because I had to formally research the subject of Web Components and finally, finally learn how use webpack directly (instead of indirectly through a CLI).
This marks a return to fundamental: progressive enhancement. This Studio has suffered for years because progressive enhancement in the world of the SPA was impossible (which is probably the result of using Angular instead of React or Vue). There were only two extremes: static documents and full-blown SPAs—nothing in between. This kind of suffering is over!
my cloud-related work from last month was useful but not quite successful
Last month, I mentioned this:
IActivityWithTask<TInput, TOutput>had to be re-factored to support multiple, serverless Activity Function calls
One great side effect of such re-factoring is seeing general improvement of the code without regard to the specific problem. I have to mention this because I deactivated the Azure Durable Functions portion of this work in production and rolled back to Azure WebJobs.
This was done because all the work done for Durable Functions last month revealed more clearly my lack of understanding of the replay concept in particular and the event sourcing pattern in general. My StackOverflow.com question related to this lack, has not been answered to my satisfaction.
sketching out a development schedule (revision 8)
The schedule of the month:
- build lunr index experience 🏗
- use
@songhay/indexas a side-car app for “Day Path” and “the rasx() context” 🚛📦 - add Stills API to
Songhay.Player(b-roll player) 🕸🌩 - use the learnings from existing npm packages to build
@songhay/player-audio-???📦✨ - modernize the kinté hits page into a progressive web app 💄✨
- convert Day Path Blog and SonghaySystem.com to HTTPs by default 🔐
- use the learnings of previous work to upgrade and re-release the kinté space 🚀