[DRAFT] docs: organize by runtime

[lancesnider]

• animation-control-and-interaction.mdx links to old landing pages
• Create landing pages
• Defold in new menu
• Unreal in new menu
• No Game Runtimes tab
• Figure out which runtimes have Layout Bounds
• Figure out runtime-specific SM controlling playback defaults and naming
• Format - move and rename to .riv File format

This PR updates the structure of the runtime navigation. Instead of having runtimes/feature with all of the runtimes in tabs, we now have a separate page for each feature (runtimes/web/feature).

Navigation Changes

Main Tab Nav

1. Merged "Runtimes" and "Game runtimes" into "Implementing Rive". In an upcoming PR this will also include site builders and the Notion integration.
2. Moved "Feature Support" to "Implementing Rive/Runtime Fundamentals" since it's runtime specific.
3. Changed "Tutorials" to "Learn". This page is going to get a major revamp soooooon.

Sidebar Name Changes

1. Renamed all the "Legacy" groups to "Legacy Features" for more clarity.
2. Renamed "Format" to ".riv File Format" and took it out of "Advanced Features" since it was the only thing in there.

Landing Pages

The top-level fundamentals pages no longer appear in the navigation, but we're keeping them around as landing pages. They're still relevant for cases when we need to link to a runtime feature, but don't know what runtime the user wants to use. For example, when linking from the editor pages.

Here's what each one looks like (you'll need to run this branch locally):

• http://localhost:3000/runtimes/artboards
• http://localhost:3000/runtimes/layout
• http://localhost:3000/runtimes/state-machines
• http://localhost:3000/runtimes/data-binding
• http://localhost:3000/runtimes/loading-assets
• http://localhost:3000/runtimes/fonts
• http://localhost:3000/runtimes/caching-a-rive-file#android
• http://localhost:3000/runtimes/playing-audio

With demos:

Without demos:

For deprecated features:

New Runtime Pages

The new runtime pages are a mix of snippets for shared content and runtime-specific examples.

If I made any content change, no matter how minor, I have included a before/after screenshot to make it easier to review. If a page doesn't include a comment, then the only change is that I got rid of the runtime tabs or the unrelated examples.

Legend

• ✅ Done
• ➖ Not applicable

Feature	web	react	rn	flutter	apple	android	unity	no inbound links	redirect
✅ Artboards	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Layout	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ State Machine	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Data Binding	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Loading Assets	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Fonts	✅	✅	✅	✅	✅	✅	➖	✅	✅
✅ Caching	✅	✅	✅	✅	✅	✅	➖	✅	✅
✅ Playing Audio	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Logging	➖	➖	➖	➖	✅	✅	➖	✅	✅
✅ Animation Playback	✅	✅	✅	✅	✅	✅	➖	✅	➖
✅ Inputs	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Text	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Rive Events	✅	✅	✅	✅	✅	✅	✅	✅	✅
✅ Rendering to Bitmap	➖	✅	➖	➖	➖	✅	➖	✅	✅

Runtime-specific Changes

Web

I removed the HTML from any example, keeping them purley JS:

Unreal & Defold

No changes, expect menu location.

Unity

Most of the Unity changes were taking sentences that say "for more info see xyz" and replacing them with content. Sorry Adam, this is gonna be a pain to review! 😂

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]

[lancesnider]