Skip to content

docs: name Studio as the authoring destination in the five remaining PR #100 sites #232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-zhuang merged 1 commit into from
Aug 29, 2026
+6 −5
Merged

docs: name Studio as the authoring destination in the five remaining PR #100 sites #232

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions content/docs/build/automation/flows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: Declarative business logic — described to AI or written in TypeSc
Flows are how you express business logic without writing a server.
Every flow is declarative metadata that the runtime executes — same
as objects and views. That means flows show up in `os diff`, the
audit log, the flow builder, and the [AI Builder](/docs/build/ai-builder)
audit log, Studio's flow builder, and the [AI Builder](/docs/build/ai-builder)
all at once.

Most customers create flows by asking the AI:
Expand Down Expand Up @@ -278,7 +278,8 @@ auditable in the flow builder.

ObjectOS ships a visual flow builder that round-trips with the
declarative metadata — non-engineers can edit a flow, and it serializes
back to the same shape as the TypeScript you'd hand-author.
back to the same shape as the TypeScript you'd hand-author. It is
Studio's **Automations** pillar.

## Testing flows

Expand Down
6 changes: 3 additions & 3 deletions content/docs/build/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Build
description: How apps come to life in ObjectOS — by chatting with AI, by clicking through forms, or by forking a template.
description: How apps come to life in ObjectOS — by chatting with AI, by clicking through forms in Studio, or by forking a template.
---

In ObjectOS the customer doesn't write metadata. **They describe what
Expand All @@ -10,7 +10,7 @@ most people actually use the platform:
| Path | Who's it for | Output |
|---|---|---|
| **[AI Builder](/docs/build/ai-builder)** (primary) | Business users, product owners, anyone | Live metadata in your tenant, queued for approval |
| **Click-build** (fallback) | Admins who prefer forms | The same live metadata |
| **Click-build** (fallback) | Admins who prefer Studio's forms | The same live metadata |
| **[Template fork](/docs/build/templates)** (dev path) | Engineers who want code under source control | A TypeScript package shipped via the marketplace |

All three paths produce **the same artifact shape** — packages of
Expand Down Expand Up @@ -49,7 +49,7 @@ Every app is composed from the same primitives. Learn these once.
## What you'll never have to do

- Write a REST endpoint. The platform generates one per object.
- Wire a form. The form renders from the schema.
- Wire a Studio form. The form renders from the schema.
- Write RBAC checks. Permissions are declared, not coded.
- Build an admin UI. Setup and Account cover system administration and sign-in.
- Generate types. `@objectstack/spec` derives them from the schema.
Expand Down