[docs] Tighten up Editor page introduction (#1622)
This PR improves the wording in the Editor docs page. It only touches the intro section. See the comments for more details! I'm also looking at the page in entirety - will cover that in another PR. ### Change Type - [x] `documentation` — Changes to the documentation only[^2] [^1]: publishes a `patch` release, for devDependencies use `internal` [^2]: will not publish a new version ### Release Notes - Documentation: Simplified the Editor page.
This commit is contained in:
parent
8d28d16943
commit
655d3b39ee
1 changed files with 3 additions and 3 deletions
|
@ -12,11 +12,11 @@ keywords:
|
||||||
- select
|
- select
|
||||||
---
|
---
|
||||||
|
|
||||||
The `Editor` class is the main control class for tldraw's editor. You can use it to manage the editor's internal state, make changes to the document, or respond to changes that have occurred.
|
The `Editor` class is the main way of controlling tldraw's editor. You can use it to manage the editor's internal state, make changes to the document, or respond to changes that have occurred.
|
||||||
|
|
||||||
By design, the `Editor`'s surface area is [very large](/gen/editor/Editor-class). While that makes it difficult to fully document here, the general rule is that everything is available via the `Editor`. Need to create some shapes? Use `editor.createShapes()`. Need to delete them? Use `editor.deleteShapes()`. Need a sorted array of every shape on the current page? Use `editor.sortedShapesArray`.
|
By design, the `Editor`'s surface area is [very large](/gen/editor/Editor-class). Almost everything is available through it. Need to create some shapes? Use `editor.createShapes()`. Need to delete them? Use `editor.deleteShapes()`. Need a sorted array of every shape on the current page? Use `editor.sortedShapesArray`.
|
||||||
|
|
||||||
Rather than document everything, this page is intended to give a broad idea of how the `Editor` class is organized and some of the architectural concepts involved.
|
This page gives a broad idea of how the `Editor` class is organized and some of the architectural concepts involved. The full reference is available in the [Editor API](/gen/editor/Editor-class).
|
||||||
|
|
||||||
## State
|
## State
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue