Add r3f doc for community components

[jo-chemla]

Following the issue https://github.com/pmndrs/react-three-fiber/issues/3377 I opened earlier today, here is a PR that adds a page to the Getting Started section listing external/community r3f components that have not been merged to drei or part of the pmndrs github org. Preview is here!

I've added all the components I know of, feel free to add more before merging!

Not docs does not seem to take the screenshot_url param visible here of the <Codesandbox /> component.

[codesandbox-ci[bot]]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d32ca6a77bc4dca4b512162123d077efbd4a32bf:

Sandbox	Source
example	Configuration

[abernier]

as discussed on X, maybe a bit redundant with Discord's Showcase channel i think

[abernier]

or we could write a <DiscordShowcases staffPicked> component (using Discord api), that displays all "staff-picked" tagged showcases, but again it would be redundant with such view that Discord already implement https://discord.com/channels/740090768164651008/1047453248044412968

1. => at least (without implementing anything into docs.) maybe we can introduce that staff-picked tag?
2. => Or, instead of an arbitrary choice by the "staff", we could let reactions like 😍/🔥 speak for themselves. We can maybe just put a link to Discord Showcase into the docs. website into the examples page, nothing more

I'm for 2.

[jo-chemla]

Thanks for the feedback on X and here! Here is my take regarding the points you mentioned:

I've been a long-time user of r3f/drei, but never saw a community collection of projects that did gather large threejs projects that expose react/r3f components. I'm thinking about large-scale projects rather than small set of utility reusable components, like other kind of renderers - 3d-tiles renderers from gkjohnson or nytimes r&d, luma labs gaussian splat renderer, looking glass etc. It would make sense to integrate it within the r3f doc for both discoverability - for those not on discord, or who rely a lot on exploring doc + github - and showcase, which could also in turn facilitate other teams/devs to add value to the fiber ecosystem.

Regarding maintenance/curation of the selection of projects to add to this page, this should probably be at the discretion of the pmndrs team which hosts the doc page, with community contributions for adding new projects or removing outdated ones suggested via PRs the same way anyone could contribute more codesandboxes examples to the example docs page.

I'm in favor of dissociating pages for

• showcase + examples, the existing one - which often embed small components within the sandboxes themselves, but could also be stored on outside repos - great for demo/learning/reuse of utilities
• from full-fledged projects like the 3D-tiles renderers, CustomShaderMaterial or the luma and looking-glass renderers, which are more complex, dedicated to a scoped use that will probably never be integrated into drei or a pmndrs repo.

Looking forward to hearing your thoughts!

[jo-chemla]

Hi there, is there any feedback from others - either from the pmndrs team or outside - regarding this PR? I've integrated the feedback from @abernier to merge the community components into a section of the showcase page, but I'm open to extract it back to its own page if deemed useful.

Looking forward to hearing your feedback!