Hi again!

I see that you currently link each page in https://doc.highfidelity.com to the github page in the grav content repo. This is awesome!

Having said that, I wonder whether prose.io might better serve you. It's an alternative to the github edit interface, designed by a well-respected web dev agency called "Development Seed". This company wanted to a build on GitHub Pages, but didn't want to force non-technical users to wade through coder lingo. Its a little less value-add these days, as github has done a whole lot to improve the PR creation workflow, but it's still nice.

Prose.io is technically a really thin GitHub Pages app itself, totally open source -- it just uses a really slim authentication proxy to coordinate the oauth dance with github, but is otherwise stateless and just runs off github api. And fwiw, "Development Seed" are the creators of "MapBox", and they're a stable force imho.

So instead of linking to GitHub's edit page, you'd just link here:
http://prose.io/#highfidelity/hifi-docs-grav-content/blob/master/01.get-started/01.what-is-high-fidelity/docs.md

or here maybe:
http://prose.io/#highfidelity/hifi-docs-grav-content/edit/master/01.get-started/01.what-is-high-fidelity/docs.md

This is how it looks when submitting (ie. absolutely no github once you login):
https://imgur.com/dVw9jfX

And here's the generated PR:
#191

One of the largest hurdles I had as a creator in High Fidelity was figuring out the proper way to export material images to an FBX. The current documentation for this is at this github path:

hifi-docs-grav-content/02.create-and-explore/07.3d-modeling/01.materials/02.material-guide/docs.md

Information like, "Shininess = Hardness * 100 / 512" or "Opacity = 1 - average(Blender.Transparency.Alpha)" mean nothing at all to me. The documentation alludes to images of the Blender UI, which might clear things up, but these aren't actually present in the documentation.

What I need to know is simply which image maps correspond to which Blender Internal material settings. Instead, I see documentation better suited to someone writing an addon for Blender. Think creators and artists, not programmers.