Document a conceptual model for Drei that helps people learn, use and adopt it.

[talkingtab]

Describe the feature you'd like:

A conceptual overview of Drei. This is very, very good stuff. I come from React and started trying to integrate threejs. My goal is to produce a Google Maps type navigation in React apps. In the r3d navigation widget you can go to any place in your React app. Just say no to menus. The motivation is for mobile (iPhone&Android) complex applications. Remove the menus, within menus, withing menus and replace it by a single App (world) view. https://aroostookian.com is under construction but sometimes it works

I started with Threejs. Then moved to @react-three-fiber. But all the cool examples are from Drei. And the uptake from three and fiber was very difficult. I think this is because drei misidentifies itself. Without a good mindset for what Drei does, it is very hard to use it. The best example of this is Bounds(). Bounds is using a React Context. There are many other cases.

React three fiber is React using three. Drei advertises itself as ?? maybe examples from threejs for r3f. But I think a clearer and more helpful conceptual understanding is

react-three-drei is threejs using react (or r3f using react).

As opposed to

react three-fiber is react incorporating threejs

Suggested implementation:

I am not sure this is an accurate assessment, or how to fix this, but I do think it is worthwhile being clear about this.
_Feel free to close and delete if this is not helpfu