Editor docs contribution backlog
Open
@lancesnider is already working on this.
Since Jun 9, 2026.
good first issue
- Dominant language
- MDX
- Stars
- 30
- Forks
- 56
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 44
Description
This is a public list of documentation tasks that contributors can pick from.
How to use this list
Comment on this issue before starting a task so we can help scope it and avoid duplicate work.
General To Dos β
- When giving multi-step instructions, the gif should go after the
<Steps>.
Undocumented Features
- Random state machine transitions - #775
- React imperative method - #786
- Isolating objects - #788
- 3d
- Captions on state machines - #779
- Default interpolation - #787
- Scripting optimization and debug settings (inspector when nothing selected)- #793
- Shaders, including shader targets (inspector when nothing selected) - #793
- Interface viewport, including managing windows - #794
- Sidebar reorder/columns - #788
- Dependency Graph - #790
- Projects - people confuse projects and workspaces - #802
- Debug panel - It's no longer just a scripts thing - #796
- Mesh weighting update - #811
- Drag to add corner radius or add more points - #834
- Convert objects to ccomponent #913
- Editing multiple selected keys at once
Key
Status:
π’ Done
π΅ Good enough
π‘ Needs work
π Needs work - medium priority
π΄ Needs work - high priority
Priority:
π Good first issue
π Medium difficulty
β€οΈ Chat with staff before digging into these
| Page | Notes | Status | Cost | Needs vid | Needs demo |
|---|---|---|---|---|---|
| getting-started/introduction | Use videos or .rivs instead of gifs. I'm not sure that's the perfect representation of a state machine. Maybe use walk, run, jump instead. | π΅ | |||
| editor/get-rive | π’ | ||||
| editor/selection-and-navigation | π’ | x | |||
| editor/workflows/dependency-graph | π’ | x | x | ||
| Interface Overview | Does this need re-doing now that we're redone all the child pages? Screenshots? | π | |||
| editor/interface-overview/overview | This feels like it can be significantly condensed. Maybe it can be a single map with a short list of links, rather than giving every area its own section AND its own page. All screenshots are wrong. | π | |||
| editor/interface-overview/toolbar | π’ | ||||
| editor/interface-overview/hierarchy | π’ | x | |||
| editor/tagging | The naming of sections and content focus on the how, but not the why. The reason we care about tagging is that it lets us filter. All screenshots are wrong. Add marketplace example. | π | x | x | |
| editor/interface-overview/inspector | #787 | π’ | |||
| editor/interface-overview/stage | π’ | ||||
| editor/keyboard-shortcuts | π’ | ||||
| editor/fundamentals/design-vs-animate-mode | π’ | ||||
| Design | |||||
| editor/fundamentals/artboards | Never talks about how artboards match the size of the parent container at runtime. | π | π | x | x |
| editor/fundamentals/components | π’ | x | |||
| Drawing | --- | --- | |||
| editor/fundamentals/shapes-and-paths-overview | Could use minor reworking to make it skim-able for people with vector experience. Needs new screenshots. Bad description. Are Enter and Esc shortcuts specific to shapes? If not, we can put it somewhere in interface overview. Or make it a note, rather than a top-level section. Add a marketplace examples | π‘ | x | ||
| editor/fundamentals/procedural-shapes | π’ | ||||
| editor/fundamentals/pen-tool-overview | It mentions editing procedural shapes, but doesn't document how to do it. Add a marketplace example | π‘ | x | ||
| editor/fundamentals/fill-and-stroke | Too long. Condense or break up. Break feathering into its own doc. Feathering should link to the blog post about why feathering is so damn cool. Bad screenshots. Unexpected hierarchy. Should have a better overview that lets you skip the rest. Add a marketplace examples | π | x | ||
| editor/fundamentals/edit-vertices | Feels like there's som overlap between this page, the overview, and the pen tool page. | π | x | ||
| editor/manipulating-shapes/trim-path | This concept is more simple than what the docs make it seem. Letβs rewrite it. Should this be just a subsection of stroke, rather than its own page? Add a marketplace examples | π | x | x | |
| editor/manipulating-shapes/clipping | Needs a better overview. Outdated gifs. Missing info about new features. Add a marketplace examples | π‘ | x | ||
| editor/manipulating-shapes/align-and-distribute | π’ | x | x | ||
| Text | --- | --- | |||
| editor/text/text-overview | Overview pages could use conceptual thumbs, like data binding overview has. | π΅ | |||
| editor/text/text-runs | π΅ | x | |||
| editor/text/text-styles | Variables shouldn't be its own top-level section - it's a property like any other. Maybe call them variable font weight since βvariablesβ can mean something else. Add a marketplace examples | π‘ | π | x | |
| editor/text/text-modifiers | Add a marketplace examples | π‘ | x | ||
| Hierarchical Relationships | --- | --- | |||
| editor/fundamentals/groups | Needs a conceptual overview | π‘ | x | ||
| editor/manipulating-shapes/solos | Start with why and a conceptual overview. Frame by frame animation needs a note about limitations - itβs not video. There are now more ways to create solos. Add a marketplace examples | π | x | ||
| editor/fundamentals/transform-spaces | This feels like the core concept of groups and hierarchies, but it's kinda buried. I'm not sure it needs its own page. Add a marketplace examples | π | x | ||
| editor/fundamentals/freeze-and-origin | We talk about how before we talk about why. Feels like it should come earlier in the docs hierarchy. | π‘ | β | ||
| editor/animate-mode/animating-draw-order | Needs quick, conceptual overview. We can mention that itβs animatable, butDraw order doesnβt need to be animated. Add a marketplace examples | π‘ | π | ||
| Responsive Design | This concept is really confusing for a lot of users. It feels like the entire section needs rethinking. | π΄ | |||
| editor/layouts/layouts-overview | This doesn't feel like an overview. It goes too far into the weeds. Let's make this more of a conceptual overview with links. Add various example videos showing what layouts can do. Link to layout scripts in | π | β | ||
| editor/layouts/layout-tools | We need to focus on what you can achieve with these tools, rather than jumping straight into the how. | π | x | x | |
| editor/layouts/layout-parameters | x | x | |||
| editor/layouts/layout-animation | π’ | ||||
| editor/layouts/n-slicing | We need a conceptual overview. Extra credit: A grid of mini videos showing real use cases. Needs conceptual gif. Subcategories need a why. How-toβs should be steps, include gifs. Add a marketplace examples | π‘ | x | x | |
| Assets | |||||
| editor/fundamentals/importing-assets | π’ | ||||
| editor/text/fonts | π’ | demo font | |||
| editor/assets/svg | π’ | demo svg | |||
| editor/assets/audio | π’ | demo sound | |||
| editor/assets/psd | π’ | demo psd | |||
| editor/libraries | This one is very confusing to people. Letβs do a full audit. | π΄ | x | x | |
| Animation | |||||
| editor/animate-mode/animate-mode-overview | Page needs an audit. Is that example video too old? | π‘ | |||
| editor/animate-mode/timeline | Conceptual overview. Weird hierarchy? Add a marketplace examples | π‘ | x | ||
| editor/animate-mode/keys | Keys and timelines seem like maybe 2 parts of the same thing, rather than needing 2 separate pages? | π‘ | x | x | |
| editor/animate-mode/interpolation-easing | Conceptual overview. Feels like the types can be a single graphic. βInterpolation fieldβ feels like it should be βCustom easingβ or something. Is the Graph Editor a separate concept? If so, give it its own doc. Itβd be cool to have a Rive example that actually shows various animations and their curves. | π | x | ||
| State Machines | --- | ||||
| editor/state-machine/state-machine | The whole thing feels like it could use a rewrite. Add a marketplace example | π | x | x | |
| editor/state-machine/states | βStates are simply timeline animations that can play at any point in your state machine.β - not true. This page is important and confusing enough that we should do a full audit. Add a marketplace example | π | x | ||
| editor/state-machine/transitions | π’ | β | |||
| editor/state-machine/layers | π’ | x | |||
| editor/state-machine/listeners | π’ | x | |||
| Events | --- | --- | |||
| editor/events/overview | Listening should be top-level section. Overview should cover listening. Description could be more clear. Add a marketplace example | π‘ | x | ||
| editor/events/open-url-events | Add a marketplace example | π΅ | x | ||
| editor/events/audio-events | Half of this page is about Assets, not specifically audio. This page needs a full audit. Move disclaimer up to the top. Too many people expecting audio to be more feature rich than it is. Add a note that links to scripting audio. Add a marketplace example | π | x | ||
| Data | --- | --- | |||
| editor/data-binding/overview | Add a marketplace example | π΅ | |||
| editor/data-binding/view-models | Add a marketplace example | π΅ | x | ||
| editor/data-binding/property-types | Add a marketplace example | π΅ | x | ||
| editor/data-binding/binding-data | Add a marketplace example | π΅ | x | ||
| editor/data-binding/controlling-data | Add a marketplace example | π΅ | |||
| Advanced Data Binding | --- | --- | |||
| editor/data-binding/enums | Add a marketplace example | π΅ | β | ||
| editor/data-binding/lists | βView Model Number with Converterβ is how, not why. This is a tough concept - Do a full audit of this page. Add a marketplace example | π | x | ||
| editor/data-binding/converters | Add a marketplace example | π΅ | x | ||
| editor/data-binding/stateful-components | Add a marketplace example | π΅ | β | x | |
| editor/data-binding/property-groups | π’ | β | β | ||
| editor/data-binding/migration-guide | π’ | β | |||
| Publishing | |||||
| editor/exporting/exporting-for-runtime | This would be a great place to reiterate that a .riv is production-ready, not a design or prototype. Use steps, rather than paragraphs for how-toβs. | π’ | x | ||
| editor/exporting/exporting-for-video-and-static-design | Use steps, rather than paragraphs for how-toβs. Double check that there are no new formats. | π‘ | π | x | |
| editor/exporting/exporting-for-backup | Move this up in the list. New screenshots. Express that this isnβt the ideal way to share file and link to other methods. | π‘ | π | ||
| editor/embed-urls/overview | Maybe call this embedding your Rive file or something. List the limitations of embedded URLs, like how you canβt control a view model from an iframe. | π’ | x | ||
| getting-started/best-practices | This page needs a lot of work and possibly a rename. | π΄ | |||
| Workspaces | π’ | ||||
| account-admin/workspaces/workspaces-overview | π’ | ||||
| account-admin/workspaces/creating-a-workspace | π’ | ||||
| account-admin/workspaces/inviting-workspace-members | π’ | ||||
| account-admin/workspaces/removing-workspace-members | π’ | ||||
| home/account-admin/workspaces/workspace-status | π’ | ||||
| editor/manipulating-shapes/manipulating-shapes | Is there a more descriptive name for this section? Needs conceptual thumbnails. Add a marketplace example | π | π | ||
| editor/manipulating-shapes/bones | π’ | β | |||
| editor/manipulating-shapes/meshes | π’ | β | |||
| editor/manipulating-shapes/joysticks | Needs conceptual overview. Whole page needs a refreshAdd a marketplace example | π΄ | π | x | |
| Constraints | --- | --- | |||
| editor/constraints/constraints-overview | A table of gifs for each type could be cool. Add a marketplace example | π΅ | β | ||
| editor/constraints/ik-constraint | Conceptual overview could be a little better, but itβs very close to great. Add a marketplace example | π’ | needs dead simple example | ||
| editor/constraints/distance-constraint | π’ | β | |||
| editor/constraints/scale-constraint | π’ | β | |||
| editor/constraints/rotation-constraint | π’ | β | |||
| editor/constraints/transform-constraint | The example looks like itβs showing IK, not transform. | π‘ | π | β | |
| editor/constraints/translation-constraint | Add a marketplace example | π’ | β | ||
| editor/constraints/follow-path-constraint | Itβs hard to understand Offset - a gif could help. Add a marketplace example | π΅ | π | x | |
| editor/constraints/scroll-constraint | Needs conceptual overview. This whole page could use a deeper audit. | π‘ | π | ||
| editor/fundamentals/revision-history | Start with what before jumping right to how. Too many people misunderstanding this as version control and making copies of files and downloading .revs. | π‘ | π | ||
| Accessibility | --- | --- | |||
| editor/accessibility/semantics | π’ | x | |||
| account-admin/bring-your-own-bucket | π’ | ||||
| editor/accessibility/reduced-motion | π’ | β | |||
| account-admin/bring-your-own-bucket | π’ | ||||
| editor/ai-agent/ai-agent | Add info about where to top up credits. | π‘ | |||
| editor/ai-agent/ai-mcp | π΅ | ||||
| Legacy Features | --- | --- | |||
| editor/state-machine/inputs | π΅ | ||||
| editor/events/general-events | π΅ |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up β it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.