docs: more docs fixes

Author: nperez0111

docs/content/docs/features/blocks/tables.mdx

@@ -51,8 +51,9 @@ type TableBlock = {
 
 type TableContent = {
   type: "tableContent";
-  columnWidths: number[];
-  headerRows: number;
+  columnWidths: (number | undefined)[];
+  headerRows?: number;
+  headerCols?: number;
   rows: {
     cells: TableCell[];
   }[];
@@ -61,6 +62,9 @@ type TableContent = {
 type TableCell = {
   type: "tableCell";
   props: {
+    backgroundColor: string;
+    textColor: string;
+    textAlignment: "left" | "center" | "right" | "justify";
     colspan?: number;
     rowspan?: number;
   };

docs/content/docs/features/export/html.mdx

@@ -26,10 +26,10 @@ For example, you an use this for static rendering documents that have been creat
 </Callout>
 
 ```typescript
-async blocksToFullHTML(blocks?: Block[]): Promise<string>;
+blocksToFullHTML(blocks?: Block[]): string;
 
 // Usage
-const HTMLFromBlocks = await editor.blocksToFullHTML(blocks);
+const HTMLFromBlocks = editor.blocksToFullHTML(blocks);
 ```
 
 `blocks:` The blocks to convert. If not provided, the entire document (all top-level blocks) is used.
@@ -45,10 +45,10 @@ Converting Blocks to HTML this way will lose some information such as the nestin
 Use `blocksToHTMLLossy` to export `Block` objects to an HTML string:
 
 ```typescript
-async blocksToHTMLLossy(blocks?: Block[]): Promise<string>;
+blocksToHTMLLossy(blocks?: Block[]): string;
 
 // Usage
-const HTMLFromBlocks = await editor.blocksToHTMLLossy(blocks);
+const HTMLFromBlocks = editor.blocksToHTMLLossy(blocks);
 ```
 
 `blocks:` The blocks to convert. If not provided, the entire document (all top-level blocks) is used.

docs/content/docs/features/export/markdown.mdx

@@ -21,10 +21,10 @@ BlockNote can export Blocks to Markdown. Note that this is also considered "loss
 `blocksToMarkdownLossy` converts `Block` objects to a Markdown string:
 
 ```typescript
-async blocksToMarkdownLossy(blocks?: Block[]): Promise<string>;
+blocksToMarkdownLossy(blocks?: Block[]): string;
 
 // Usage
-const markdownFromBlocks = await editor.blocksToMarkdownLossy(blocks);
+const markdownFromBlocks = editor.blocksToMarkdownLossy(blocks);
 ```
 
 `blocks:` The blocks to convert. If not provided, the entire document (all top-level blocks) is used.

docs/content/docs/features/import/html.mdx

@@ -20,10 +20,10 @@ It's possible to import HTML content into BlockNote blocks, completely client-si
 Use `tryParseHTMLToBlocks` to parse an HTML string to `Block` objects:
 
 ```typescript
-async tryParseHTMLToBlocks(html: string): Promise<Blocks[]>;
+tryParseHTMLToBlocks(html: string): Block[];
 
 // Usage
-const blocksFromHTML = await editor.tryParseHTMLToBlocks(html);
+const blocksFromHTML = editor.tryParseHTMLToBlocks(html);
 ```
 
 `returns:` The blocks parsed from the HTML string.

docs/content/docs/features/import/markdown.mdx

@@ -20,10 +20,10 @@ BlockNote can import Markdown content into Block objects. Note that this is cons
 Use `tryParseMarkdownToBlocks` to try parsing a Markdown string into `Block` objects:
 
 ```typescript
-async tryParseMarkdownToBlocks(markdown: string): Promise<Blocks[]>;
+tryParseMarkdownToBlocks(markdown: string): Block[];
 
 // Usage
-const blocksFromMarkdown = await editor.tryParseMarkdownToBlocks(markdown);
+const blocksFromMarkdown = editor.tryParseMarkdownToBlocks(markdown);
 ```
 
 `returns:` The blocks parsed from the Markdown string.

docs/content/docs/foundations/document-structure.mdx

@@ -128,6 +128,9 @@ While both of these act as regular blocks, there are a few additional restrictio
 ```typescript
 type TableContent = {
   type: "tableContent";
+  columnWidths: (number | undefined)[];
+  headerRows?: number;
+  headerCols?: number;
   rows: {
     cells: InlineContent[][];
   }[];

docs/content/docs/reference/editor/cursor-selections.mdx

@@ -18,12 +18,14 @@ type TextCursorPosition = {
   block: Block;
   prevBlock: Block | undefined;
   nextBlock: Block | undefined;
+  parentBlock: Block | undefined;
 };
 ```
 
 - `block`: The block currently containing the text cursor
 - `prevBlock`: The previous block at the same nesting level (undefined if first)
 - `nextBlock`: The next block at the same nesting level (undefined if last)
+- `parentBlock`: The parent block if the cursor is in a nested block (undefined if at the top level)
 
 ### Getting Cursor Position
 

docs/content/docs/reference/editor/events.mdx

@@ -75,7 +75,7 @@ See [Understanding Changes](#understanding-changes) for more information about t
 The `onBeforeChange` callback is called before any change is applied to the editor, allowing you to cancel the change.
 
 ```typescript
-editor.onBeforeChange((editor, { getChanges, tr }) => {
+editor.onBeforeChange(({ getChanges, tr }) => {
   if (
     // Cancel inserting new blocks
     getChanges().some((change) => change.type === "insert")

docs/content/docs/reference/editor/manipulating-content.mdx

@@ -35,13 +35,13 @@ The content manipulation APIs fall into two main categories:
 Most block methods require a `BlockIdentifier` to reference existing blocks:
 
 ```typescript
-type BlockIdentifier = string | Block;
+type BlockIdentifier = string | { id: string };
 ```
 
 You can pass either:
 
 - A `string` representing the block ID
-- A `Block` object (the ID will be extracted automatically)
+- Any object with an `id: string` property, such as a `Block`
 
 ### Partial Blocks
 
@@ -119,7 +119,7 @@ const parentBlock = editor.getParentBlock("nested-block-123");
 
 ```typescript
 forEachBlock(
-  callback: (block: Block) => boolean | undefined,
+  callback: (block: Block) => boolean,
   reverse: boolean = false
 ): void
 ```