Turning a New 3D Engine Into Something People Could Learn

Unbound was a new 3D creation tool built around signed distance fields, Lua scripting, and non-destructive sculpting. It was powerful, but it also asked users to learn a different way of thinking about 3D work.

I was responsible for writing the user guide, creating examples, organizing the learning path, and helping turn early product knowledge into something new users could actually follow.

The Problem

The hard part was not just documenting buttons and menu items. The real job was helping people understand how the tool wanted to be used.

What I Built

I wrote the Unbound User Guide, created sample projects, captured and annotated screenshots and GIFs, wrote Lua examples, and produced tutorial material for users learning the tool.

The guide needed to work for a few different audiences:

• Artists who wanted to make something quickly
• Technical users who wanted to understand the engine
• Internal team members who needed a shared reference

So I tried to keep the docs practical: what something does, why it matters, where it fits in the workflow, and what to try next.

Product Translation

Writing the docs also helped expose product issues. If a workflow was hard to explain, that usually meant something about the naming, UI, or onboarding needed another look.

Sample Projects And Tutorials

I also built reference projects and tutorial material so the docs were not just abstract explanations. A good sample project gives users something safe to take apart.

Instead of asking users to absorb the whole system at once, the examples gave them concrete patterns to start from.

Why It Matters

This project is a good example of work I enjoy: making technical systems easier for people to understand and use.