---
title: "The editor"
description: "Mounting FlowDrop in your application, and everything you can change about it once it is there."
source: https://flowdrop.io/docs/editor
site: FlowDrop documentation
---
# The editor
The editor is a front-end component. It is the same component whichever
[backend](/start) you chose, and this track covers everything on the front-end
side of the contract: getting it on the page, changing how it looks, adding node
types and form fields, and reading its events and stores.

<CardGroup cols={2}>
  <Card title="Framework integration" icon="puzzle-piece" href="/editor/frameworks">
    Svelte, React, Vue, vanilla JavaScript, or anything that can call a function.
  </Card>
  <Card title="Creating workflows" icon="pencil" href="/editor/creating-workflows">
    What the editor actually does, from the reader's side of the canvas.
  </Card>
  <Card title="Theming" icon="palette" href="/editor/theming">
    CSS custom properties, and swapping a whole palette at once.
  </Card>
  <Card title="Custom nodes" icon="square-plus" href="/editor/custom-nodes">
    Register your own components as node types.
  </Card>
  <Card title="Backend implementation" icon="server" href="/editor/integration/backend-implementation">
    The REST endpoints the editor calls, and how to implement them.
  </Card>
  <Card title="SDK reference" icon="code" href="/editor/reference/mount-api">
    Mount API, components, types, event handlers, stores and tokens.
  </Card>
</CardGroup>

Stuck? [Common issues and FAQ](/editor/troubleshooting) collects the failures
that come up most.