Skip to content

Commit df5ad7d

Browse files
committed
refactor(platform): remove forms, templates, and creators features
Remove three standalone features and their supporting code: - Forms: form-deployment pages, API routes, execution path, and docs. - Templates: the template gallery (landing + workspace) and template APIs. - Creators: creator-profile routes and contracts. Add a super-user permissions module (lib/permissions/super-user) and an organizations API contract; update the audit/db/testing packages, billing, and the session/theme providers accordingly.
1 parent 3109104 commit df5ad7d

117 files changed

Lines changed: 107 additions & 10357 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

apps/docs/content/docs/de/execution/form.mdx

Lines changed: 0 additions & 142 deletions
This file was deleted.

apps/docs/content/docs/en/execution/form.mdx

Lines changed: 0 additions & 136 deletions
This file was deleted.

apps/docs/content/docs/en/triggers/start.mdx

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Reference structured values downstream with expressions such as <code>&lt;start.
4444

4545
## How it behaves per entry point
4646

47-
<Tabs items={['Editor run', 'Deploy to API', 'Deploy to chat', 'Deploy to form']}>
47+
<Tabs items={['Editor run', 'Deploy to API', 'Deploy to chat']}>
4848
<Tab>
4949
When you click <strong>Run</strong> in the editor, the Start block renders the Input Format as a form. Default values make it easy to retest without retyping data. Submitting the form triggers the workflow immediately and the values become available on <code>&lt;start.fieldName&gt;</code> (for example <code>&lt;start.sampleField&gt;</code>).
5050

@@ -64,13 +64,6 @@ Reference structured values downstream with expressions such as <code>&lt;start.
6464

6565
If you launch chat with additional structured context (for example from an embed), it merges into the corresponding <code>&lt;start.fieldName&gt;</code> outputs, keeping downstream blocks consistent with API and manual runs.
6666
</Tab>
67-
<Tab>
68-
Form deployments render the Input Format as a standalone, embeddable form page. Each field becomes a form input with appropriate UI controls—text inputs for strings, number inputs for numbers, toggle switches for booleans, and file upload zones for files.
69-
70-
When a user submits the form, values become available on <code>&lt;start.fieldName&gt;</code> just like other entry points. The workflow executes with trigger type <code>form</code>, and submitters see a customizable thank-you message upon completion.
71-
72-
Forms can be embedded via iframe or shared as direct links, making them ideal for surveys, contact forms, and data collection workflows.
73-
</Tab>
7467
</Tabs>
7568

7669
## Referencing Start data downstream

0 commit comments

Comments
 (0)