Handbook · Map of the editor
Map of the editor
Where in the UI. Open templates.containd.app. The tab strip is Structure · Layout · Scripts · JSON · Preview. Author chat is in the header.
The editor is one project in the browser. Five tabs share the same document. Undo applies across them. Export is how you take the project with you.
Header
- Project title and locale — author in the primary locale first; fill translations later.
- Undo / redo — document history, not only the current field.
- File — import/export project, template, or category pack. The portable artifact is JSON (+ assets).
- Author — BYOA chat. It can read the project and propose changes; you confirm writes.
Five tabs
| Tab | What you do there | Mental object |
|---|---|---|
| Structure | Graph of kinds of items, categories, classes, expressions, scripts, defaults, filters. | The recipe’s skeleton |
| Layout | Draw the item surface. Drop widgets. Bind values. | How one item looks |
| Scripts | Blockly programs for lifecycle and buttons. JS view is generated. | What happens when… |
| JSON | Raw document + structural / semantic / policy markers. | The file itself |
| Preview | Fake an item and run scripts in the sandbox. | A dress rehearsal |
Persistence
While you work, the project sits in the browser (localStorage + IndexedDB for binaries). That is not a backup. Export a project file when the work matters. Catalog publish is a separate, later step.
Safety in one sentence
Scripts do not run as browser JavaScript on a web page. They run in a js-interpreter sandbox and may only call host methods your template’s capabilities allow. The catalog wiki explains that for installers; this handbook explains it for authors under Checking your work.