I'm surprised that acceptance of the browser is so global, but particularly in a community like yours. HTML is dirty, HTML+CSS+javascript is dirty. Plan 9 folks know about tool simplicity, and about nice documents. I've always half expected something to come from your team that says "no - this is all wrong. The browsable internet should be like this" that gives the middle finger to the HTML world, and which can easily be replicated as a firefox plugin and then go on to take over the world.
I guess I'm saying that I think you took the wrong path by attempting to follow the browser - you should have challenged it, but in a way that didn't rely on plan9-specific user interface innovations [1].
I've had several attempts at it but don't hang around in circles where I get to talk about the problems regularly face-to-face with other people who get it, and that's what a problem like that requires.
The site you've pointed me to is a real improvement over the online docs that were around two years ago. It answers the sort of questions a newcomer asks.
--
[1] I think sam would have gone further if the console tool had been the core with the gui as a separate app that leveraged the core. Console sam should be to ed as vim is to vi, but it's trying to do two things at once, and the gui editor - which I'm sure is very good for people who know it well - hampered the progress of the console app.