- Asset Browser (Milestone 1: Basic, Local Asset Browser): Feature-incomplete version available as experimental feature in 2.92 alpha builds. Further features in progress. Design is being evaluated.
- Asset Browser (Pose Library Basics): Design evaluation.
Reduce overhead and streamline the workflows for creating, editing, sharing and using of reusable Blender resources.
An asset is a data-block with meaning.
This isn't limited to Blender data-blocks: The Asset Browser could also give access to presets, scripts, importer/exporter files (glTF, USD, OBJ, ...), media files (images, sounds, video), etc. The meaning is meta-data to help manage the data-blocks.
Blender assets have to be part of a repository (.blend file or directory). By "mounting" a repository in the Preferences, its assets can be accessed in all Blender sessions. Alternatively, the concept of a "Blender Project" will enable per-project asset repositories.
The Asset Browser is an interactive viewer for asset repositories, but it does not automate asset management. It's a browser, not a manager!
Add-ons will be able to integrate with the Asset Browser, so that they can handle advanced asset management tasks. For example a studio could connect the Blender Asset Browser with its pipeline software using an Add-on.
Asset management is a topic of enormous scope. The Asset Browser should eventually bring:
- Simple and streamlined access to project independent Blender assets. E.g. base meshes, premade materials, libraries of brushes...
- Simple and streamlined access to assets of a project. E.g. characters, sets, background props, character poses...
- Simple and streamlined access to online asset data-bases, from within Blender. E.g. Blender Cloud, BlenderKit, ...
- Milestone 1 design: Asset Browser (Milestone 1: Basic, Local Asset Browser)
- User Interface design T54642: Asset Project: User Interface
The entire development happens in a highly agile fashion:
- Work in short sprints (~2 weeks) with previously defined targets.
- Everything's a hypothesis - Evaluate often, do usability tests and prototyping.
- Work in master early, for easy testing.
- Always have a working system, even if limited or buggy.
- Identify and agree on important use-cases. Take time to explore and design them together with stakeholders.
- Don't get distracted by corner cases, nice-to-have's or "what if"'s.
- Development must be transparent.
- To contact the members, reach out to them on #blender-coders or #data-assets-io-module on blender.chat.