The whole feature request/discussion thing is difficult.
With the current system it means there is little in the way of overhead of managing features but I understand that it can feel frustrating to request a feature or give ideas but have little in the way of feedback only to see the topic close. At the moment system wouldn't really allow for an easy "features digest" etc. unless manually curated.
One idea could be to have an opt-in page (startup/via command/linked in the note list), similar to the welcome page concept, which instead would be a community focused page which could fetch some kind of summary report from discourse (either auto or curated). Could also be used to go into details for the current release with a verbosity not really possible in the brief change log given on github or "update available" dialog in Joplin.
On the discussion of the initial topic I've shoved my... creation... onto github for all to publicly point and gawk at.
I'll reiterate, literally never made anything in HTML (or CSS) from scratch before, have no idea about best practices etc. It is entirely fuelled off boring work meetings and, later, gin.
Yes there are CSS selectors that don't have anything in them (thought I might want to use them later) and yes it doesn't do responsive stuff properly (no flexboxes etc.) as it is purely meant to be a mockup & a fun little distraction project for me and is by no means meant to be something finished.