Echo JS 0.11.0

One of the biggest problems that I often encounter isn't so much what Axe, Lighthouse and WAVE show is actually being able to navigate your site with a keyboard alone.  Visually impaired people generally don't use a mouse for browsing... not being able to have proper navigation is huge.

There are only a handful of roles and/or aria-* attributes that all web developers working on public facing applications should know about.

Should put links to the respective icon sites in the show notes after the summary.

Also, may want to reference the extended Material Design Icons library over the one from google, there are several target publications of this library, including one mdi-material-ui package for the material-ui react components.

https://materialdesignicons.com/

Generally you should only concern yourself with the document.documentElement.clientWidth/clientHeight... as you really don't have any control over much else.

You may want to use the window.innerWidth/innerHeight if you intend to override scrolling behavior, setting html overflow to hidden, and your own scrolling regions.

The use of other information is mostly going to only help you in terms of knowing what *could* be used for full-screen interaction (F11 mode) if you're doing gaming/simulation work.

Please limit posts about your react hooks (at least on echojs) to once a month, there's no need to post about this more than that (let alone multiple posts in a week), most of the users are regular and tend to have an adverse reaction to seeing the same thing re-posted in spammy ways all the time... using a url redirect to work around the post limiter isn't doing you any good.

Continued spammy techniques like this will get the account deleted.

I really do think this is cool. would be nice if this were sourced as a TS project for npm, with a direct module url for use with deno (from github#master).  Since it wouldn't take much effort and could be used on the front-end more easily that way.

I wouldn't say SSR is dead, just rarely needed in practice.  For the most part, if your content is mostly static, then static rendering probably makes the most sense.  If your content is time-sensitive in general (news sites, flash sales), then SSR may make the most sense.  If your site is really more of an application, then Client Side Rendering/Routing makes the most sense.

Edited title to match the start of the repository description.

What I was meaning, is it would be nice, if you could backup/store the config/settings in a github repository as well... but this would mean more flat files, as opposed to sqlite... maybe import/export then an auto-import/export github integration for that.

Interresting... may take more of a look into this.. hoping that blog entries are stored as markdown, and curious how the source details are stored (github integration would be nice for saving the source data to gh).

Okay, liked this implementation, so took the time to update my uuid4 npm package to use a modified version for the browser implementation... also cleaned up some cruft and added module version(s) for both browser and node packages.

https://www.npmjs.com/package/uuid4