ianhitchman/tiptap
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

update content

Browse Source
This commit is contained in:
Hans Pagel
2020-11-12 15:50:24 +01:00
parent 31d2947ed1
commit 3885f08475
4 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/src/docPages/api/schema.md
View File

@@ -150,7 +150,7 @@ createNode({
``` ```
#### Selectable #### Selectable
> Controls whether nodes of this type can be selected as a node selection. Defaults to true for non-text nodes. Besides the already visible text selection, there is an invisible node selection. If you want to make your nodes selectable, you can configure it like this:
```js ```js
createNode({ createNode({
@@ -177,7 +177,9 @@ createNode({
``` ```
#### Defining #### Defining
> Determines whether this node is considered an important parent node during replace operations (such as paste). Non-defining (the default) nodes get dropped when their entire content is replaced, whereas defining nodes persist and wrap the inserted content. Likewise, in inserted content the defining parents of the content are preserved when possible. Typically, non-default-paragraph textblock types, and possibly list items, are marked as defining. Nodes get dropped when their entire content is replaced (for example, when pasting new content) by default. If a node should be kept for such replace operations, configure them as `defining`.
Typically, that applies to [`Blockquote`](/api/extensions/blockquote), [`CodeBlock`](/api/extensions/code-block), [`Heading`](/api/extensions/heading), and [`ListItem`](/api/extensions/list-item).
```js ```js
createNode({ createNode({

4
docs/src/docPages/guide/collaborative-editing.md
View File

@@ -1,7 +1,7 @@
# Collaborative editing # Collaborative editing
:::premium Requires Premium Extensions :::premium Requires Pro Extensions
Using the collaborative editing in production requires a **tiptap pro** license. [Read more](/sponsor) We kindly ask you to sponsor us, before using this example in production. [Read more](/sponsor)
::: :::
## toc ## toc

2
docs/src/docPages/guide/store-content.md
View File

@@ -92,7 +92,7 @@ That said, tiptap **does** support Markdown shortcuts to format your content. Tr
## Generate HTML from ProseMirror JSON ## Generate HTML from ProseMirror JSON
If you need to render the content on the server side, for example to render a blog post which was written with tiptap, you’ll probably need a way to do just that without an actual editor instance. If you need to render the content on the server side, for example to render a blog post which was written with tiptap, you’ll probably need a way to do just that without an actual editor instance.
That’s what `generateHTML()` is for. It’s a utility function that renders HTML without an actual editor instance. That’s what `generateHTML()` is for. It’s a utility function that renders HTML without an actual editor instance. As an easy alternative, you can also use tiptap in a [read-only mode](/examples/read-only).
:::info Browser-only rendering :::info Browser-only rendering
Import a lightweight implementation from `@tiptap/core` if you’re using the function in a browser context only. Import a lightweight implementation from `@tiptap/core` if you’re using the function in a browser context only.

4
docs/src/links.yaml
View File

@@ -34,7 +34,7 @@
- title: Full Editor - title: Full Editor
link: /examples/full-editor link: /examples/full-editor
draft: true draft: true
- title: Feedback - title: Share feedback
link: /overview/feedback link: /overview/feedback
- title: Guide - title: Guide
@@ -152,7 +152,7 @@
link: /api/events link: /api/events
- title: Schema - title: Schema
link: /api/schema link: /api/schema
draft: true new: true
- title: Keyboard Shortcuts - title: Keyboard Shortcuts
link: /api/keyboard-shortcuts link: /api/keyboard-shortcuts