Objects and Object Types
An Object is a note with a defined shape. A book, person, meeting, project, image, and task can all have body content, but they do not need the same properties or behavior. An Object Type defines that shape.
Every Object has exactly one Type. Its complete structure can also include inherited properties and relations, properties supplied by Mixins, and fields such as tags or aliases.
Create an Object
Section titled “Create an Object”- Select New in the sidebar.
- Search for or select an Object Type.
- Give the Object a title.
- Fill the properties that matter now. Required properties are identified in the editor.
- If the Type has a body, write below the property area in the block editor.
You can also create an Object from a template, a collection, quick capture, a calendar action, or an automation. Those paths still produce an ordinary typed Object.
Choose the right Type
Section titled “Choose the right Type”Choose the Type that describes what the Object is, not every role it might play. For example, a client contact is still a Person; client-specific structure can come from a Mixin or a relation instead of a second parent Type.
Use a custom Type when several Objects need the same:
- properties or relations;
- page and card layout;
- templates;
- calendar behavior; or
- Type-scoped collections and automations.
Use a one-off loose property only when the information truly does not belong in the shared schema. Loose properties are not inherited and are not part of typed property queries.
Change an Object’s Type
Section titled “Change an Object’s Type”Open the Object’s More menu and choose Change Object Type. Lar reconciles properties against the destination Type. Values that no longer belong to a typed property are preserved as loose data when possible rather than silently discarded.
Changing Type is different from renaming a Type: changing Type affects one Object; editing the Type definition affects every Object of that Type.
Objects without a body
Section titled “Objects without a body”A Type can be configured without a body. This is useful for structured records whose properties are the content. Types with a body use Lar’s block editor and can switch between page and edgeless modes.
Built-in and custom Types
Section titled “Built-in and custom Types”Lar includes built-in Types for common workflows, including Note, Tag, Daily Note, Task, Event, Capture, Workflow, and file-backed media. Built-in Types provide stable behavior and expose fewer customization controls. Custom Types can define their own inheritance, properties, relations, Mixins, templates, and layouts.