From 9b0c22bb247f38cceee1c79170707b3009f049a8 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 11 May 2023 18:08:06 +0800
Subject: [PATCH 001/196] chore: release 0.9.5

---
 pages/Changelog.md | 51 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 64e0bc8..fe148c3 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,3 +1,54 @@
+- ## Beta 0.9.5 [[May 11th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.5>
+	- [[Features]]
+		- Ordered(numbered) block list support [#9235](https://github.com/logseq/logseq/pull/9235)
+	- [[Thanks]]
+		- [[Adam Hupp]]
+			- Fix `yarn install` on Windows in [#9299](https://github.com/logseq/logseq/pull/9299)
+		- [[Bad3r]]
+			- Update config.edn template in [#9287](https://github.com/logseq/logseq/pull/9287)
+			- Improve error handling in `mkdir` function in [#9247](https://github.com/logseq/logseq/pull/9247)
+		- [[Calum Lind]]
+			- Fix garbled text in sidebar and dropdown menus on Linux in [#9286](https://github.com/logseq/logseq/pull/9286)
+		- [[EINDEX]]
+			- Fix UI port range in [#9211](https://github.com/logseq/logseq/pull/9211)
+		- [[Zhizhen He]]
+			- Fix duplicated line in config.edn [#9324](https://github.com/logseq/logseq/pull/9324)
+			- Add settings for graph view in [#9325](https://github.com/logseq/logseq/pull/9325)
+		- [[ingepettersen]]
+			- Norwegian translations in [#9319](https://github.com/logseq/logseq/pull/9319)
+		- [[melat0nin]]
+			- Refine UI translation item in [#9267](https://github.com/logseq/logseq/pull/9267)
+		- [[necropolina]]
+			- Remove unneeded menu options for publishing in [#9262](https://github.com/logseq/logseq/pull/9262)
+		- [[John Doe]]
+			- Improve Russian translation in [#9301](https://github.com/logseq/logseq/pull/9301)
+		- [[Yiming Pan]]
+			- Fix date time selection repeater UI in [#9328](https://github.com/logseq/logseq/pull/9328)
+		- [[queeup]]
+			- Update Turkish translation in [#9327](https://github.com/logseq/logseq/pull/9327)
+	- [[Fixed issues]]
+		- Whiteboards
+			- Allow interactions with published embeds and hide lock/unlock [#9322](https://github.com/logseq/logseq/pull/9322)
+			- Keyboard shortcuts [#9338](https://github.com/logseq/logseq/pull/9338)
+			- Page name sanitization [#9259](https://github.com/logseq/logseq/pull/9259)
+		- Date time repeater UI [#9328](https://github.com/logseq/logseq/pull/9328)
+		- App crash caused by broken sqlite cache [#9248](https://github.com/logseq/logseq/pull/9248)
+		- Garbled text in sidebar and dropdown menus on Linux [#9286](https://github.com/logseq/logseq/pull/9286)
+		- Mailto and other protocol URLs creating invalid pages [#9353](https://github.com/logseq/logseq/pull/9353)
+		- Page tags and aliases should be deleted when page is deleted by user [#9293](https://github.com/logseq/logseq/pull/9293)
+		- Stale children block's path-refs when parent's refs change [#9254](https://github.com/logseq/logseq/pull/9254)
+		- Copy & Paste handling bugs [#9335](https://github.com/logseq/logseq/pull/9335), [#9255](https://github.com/logseq/logseq/pull/9255), [#9344](https://github.com/logseq/logseq/pull/9344)
+		- Copy page URL with shortcut key [#9255](https://github.com/logseq/logseq/pull/9255)
+		- Remove unneeded menu options from published pages [#9262](https://github.com/logseq/logseq/pull/9262)
+	- [[Enhancement]]
+		- Performance improvement for inserting and deleting blocks [#9142](https://github.com/logseq/logseq/pull/9142)
+		- Whiteboards
+			- Add prefix to default keyboard shortcuts [#9340](https://github.com/logseq/logseq/pull/9340)
+			- Customizable shortcuts [#9228](https://github.com/logseq/logseq/pull/9228)
+		- I18n: Russian [#9301](https://github.com/logseq/logseq/pull/9301), Turkish [#9327](https://github.com/logseq/logseq/pull/9327), Norwegian [#9319](https://github.com/logseq/logseq/pull/9319)
+		- Add settings for graph view [#9325](https://github.com/logseq/logseq/pull/9325)
+		- Update config.edn template [#9287](https://github.com/logseq/logseq/pull/9287)
 - ## Beta 0.9.4 [[Apr 26th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.4>
 	- [[Features]]

From abe990401b61934d769785553a0797b079c68dd0 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 11 May 2023 10:52:19 -0400
Subject: [PATCH 002/196] Update to version with ordered lists and hide outward
 facing docs

---
 .github/workflows/gh-pages.yml | 1 +
 logseq/config.edn              | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index eec886a..8e0878e 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -17,6 +17,7 @@ jobs:
         uses: logseq/publish-spa@main
         with:
           output-directory: www
+          version: 0.9.5
 
       - name: Add .nojekyll file
         run: touch www/.nojekyll
diff --git a/logseq/config.edn b/logseq/config.edn
index 9efad95..9790883 100644
--- a/logseq/config.edn
+++ b/logseq/config.edn
@@ -12,7 +12,7 @@
 
  ;; The app will ignore those directories or files.
  ;; E.g. "/archived" "/test.md"
- :hidden ["script"]
+ :hidden ["script" "README.md" "CONTRIBUTING.md" "LICENSE.md"]
 
  ;; When creating the new journal page, the app will use your template content here.
  ;; Example for Markdown users: "## [[Work]]\n###\n## [[Family]]\n###\n

From f0cfbce0103dc6c1f20e7ff4f8e2f8b6577be181 Mon Sep 17 00:00:00 2001
From: Bad3r <bad3r@protonmail.com>
Date: Thu, 11 May 2023 11:25:21 -0400
Subject: [PATCH 003/196] enhance: document Logseq export feature (#98)

* enhance: document Logseq export feature

* Update gh-pages.yml

* Update gh-pages.yml

* Update gh-pages.yml

* enhance: document Logseq export feature

* enhance: document Logseq export feature Rev.2

* Enhance/export docs (#3)

* enhance: document Logseq export feature

* enhance: document Logseq export feature Rev.2

* remove changes to gh-pages.yml
---
 pages/Export.md | 64 ++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 63 insertions(+), 1 deletion(-)

diff --git a/pages/Export.md b/pages/Export.md
index 81d2795..d17a2d1 100644
--- a/pages/Export.md
+++ b/pages/Export.md
@@ -1,4 +1,66 @@
 type:: [[Feature]]
 platforms:: [[All Platforms]]
+description:: The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Markdown. It supports exporting text selections, blocks, individual pages, or the entire graph with customizable options.
 
-- TODO Document feature, page and graph level #docs
\ No newline at end of file
+- ## Introduction
+	- The Logseq export feature enables users to export selection, a single block or a page, or the entire graph into various formats, such as plain-text, OPML, HTML, or PNG. This feature is designed to enhance the user experience by providing a convenient way to share, backup, or migrate Logseq data to other platforms and applications.
+	- Purpose and benefits include improving compatibility with other tools, simplifying data backup and sharing, and providing multiple export options to suit user requirements.
+- ## Purpose and Benefits
+	- **Cross-platform Compatibility**: The export feature allows for better integration with other tools by supporting common file formats such as plain text, OPML, HTML, EDN, JSON, and standard Markdown. This cross-platform compatibility makes it easier to migrate data or use your Logseq content in different applications.
+	- **Data Backup**: The export feature provides an efficient way to create backups of your Logseq graph. Regular backups can help prevent data loss and ensure data integrity.
+	- **Flexible Sharing Options**: Exporting allows you to share your Logseq content with others in a format they can easily view or import into other tools. It also enables you to present your content in various formats suitable for different contexts, such as exporting a block to an image.
+	- **Customization**: The export feature offers numerous options to customize the exported content, such as defining the  scope of export {{cloze selection, a single block, a page, or the entire graph}}, choosing the export format, and selecting specific options related to each format. This flexibility allows users to tailor the export process to their specific needs.
+- ## Export Scopes
+	- **Export a [[Graph]]**: This option enables the export of all pages within the Logseq graph. To do so, navigate to the three-dot menu icon in the Logseq interface's top-right corner, select the *Export Graph* option from the dropdown menu, and then choose your preferred format.
+	  logseq.order-list-type:: number
+	- **Export a Single Page or a [[whiteboard]]**: This scope allows for exporting the content of an individual page. To use this option, open the page you intend to export, right-click the page title, and select the *Export* option from the context menu. You can then choose the desired format and options for the export.
+	  logseq.order-list-type:: number
+	- **Export a Single [[Block]]**: This option enables the export of a single block along with its nested blocks. To do this, right-click on the bullet point of the block you wish to export and select *Copy/Export as...* from the context menu. You can then select the desired format and options.
+	  logseq.order-list-type:: number
+	- **Export Selection**: This scope allows you to export the selected text or blocks. To use this feature, highlight the desired text or blocks, right-click on the selection, and choose *Copy/Export as...* from the context menu. You can then specify the desired format and options for the export.
+	  logseq.order-list-type:: number
+- ## Export Formats
+	- ### Graph Export
+	  Exports the entire graph in the following formats:
+		- **EDN**: Export the graph in Extensible Data Notation format.
+		- **JSON**: Export the graph in standard JSON format.
+		- **Standard Markdown**: Export the graph in Standard Markdown format.
+		  #+BEGIN_NOTE
+		  Block [[properties]] will not be included in standard markdown exports.
+		  #+END_NOTE
+		- **OPML**: Export the graph in OPML format, suitable for various outlining and mind-mapping applications.
+		- **Roam JSON**: Export the graph in Roam Research compatible format.
+		- **HTML**:  Export the graph in HTML format.
+	- ### Content-Specific Export
+	  Exports a selection, block, page, or whiteboard. The following formats are available:
+		- **Text**: Exports the content as plain text, maintaining the hierarchical structure of blocks and the bullet indentation.
+		- **OPML**: Exports content in the OPML format.
+		- **HTML**: Exports content in HTML format, preserving the original content's formatting and styles.
+		- **PNG**: Captures the appearance of a page, selection, or a [[whiteboard]] as an image.
+- ## Export Options
+  Depending on the export format, several options are available:
+	- #### Text, OPML, and HTML Options
+		- **Removal of brackets**: Converts `[[page]]` into `page`.
+		- **Removal of emphasis**: Strips emphasis formats such as **bold**, *italic*, or ~~strikethrough~~.
+		- **Removal of #tags**: Removes #tags from the exported content.
+		- **Block depth level**: Sets the maximum depth of nested blocks to include in the export. Options range from *all* to numbers 1-9.
+	- #### Text-Specific Options
+		- **Indentation style**: Selects the preferred indentation style. Options include dashes, spaces, or no-indent.
+		- **Newline after block**: Adds a newline after each block.
+		- **Removal of properties**: Excludes block properties from the export.
+	- #### HTML-Specific Option
+		- **Include properties**: Option to include block properties in the export.
+	- #### PNG-Specific Option
+		- **Transparent background**: This option removes the background color from the exported content, making it see-through.
+	- After choosing the export format and options, users can *copy* the exported content to the clipboard or *save* it to a file.
+- ## Configuration Options
+  Logseq provides a range of configuration options and page properties to customize the export process, including settings at both the graph and page levels.
+	- ### Graph-Level Configuration
+		- #### [[Settings]] Menu
+			- Under the *Editor* tab in the [[Settings]] menu, you will find the option "*Set pages to public by default*". When this setting is enabled (default), all pages within the graph will be considered public and included in the export unless the page's `public` property is explicitly set to `false`.
+			- If this setting is disabled,  all pages will be private and not included in the export unless the page's `public` property is explicitly set to `true`.
+			- This setting corresponds to the `:publishing/all-pages-public?` option in the [[config.edn]] file.
+	- ### Page-Level Configuration
+		- #### Public Page Property
+			- The `public` page property is a boolean attribute that can be set for individual pages to determine their inclusion in an export. It overrides the default setting in the [[Settings]] menu. For example, if a page's `public` property is set to `true`, it will be included in the export even if the "*Set pages to public by default*" setting is disabled.
+	- The interplay between the graph-level configuration and page-level properties can significantly affect the outcome of your export process. Therefore, reviewing these settings before performing an export is crucial to ensure they align with your specific needs.
\ No newline at end of file

From 3b5aba7670d841169abd12fa69be7b672be8fafe Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 11 May 2023 11:29:14 -0400
Subject: [PATCH 004/196] Address feedback of #98

---
 pages/Export.md     | 113 ++++++++++++++++++++------------------------
 pages/Publishing.md |  12 ++++-
 2 files changed, 63 insertions(+), 62 deletions(-)

diff --git a/pages/Export.md b/pages/Export.md
index d17a2d1..9aec83c 100644
--- a/pages/Export.md
+++ b/pages/Export.md
@@ -2,65 +2,56 @@ type:: [[Feature]]
 platforms:: [[All Platforms]]
 description:: The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Markdown. It supports exporting text selections, blocks, individual pages, or the entire graph with customizable options.
 
-- ## Introduction
+- ## Usage
+	- Here are the different ways to export:
+		- **Export a [[Graph]]**: This option enables the export of all pages within the Logseq graph. To do so, navigate to the three-dot menu icon in the Logseq interface's top-right corner, select the *Export Graph* option from the dropdown menu, and then choose your preferred format.
+		  logseq.order-list-type:: number
+		- **Export a Single Page or a [[whiteboard]]**: This scope allows for exporting the content of an individual page. To use this option, open the page you intend to export, right-click the page title, and select the *Export* option from the context menu. You can then choose the desired format and options for the export.
+		  logseq.order-list-type:: number
+		- **Export a Single [[Block]]**: This option enables the export of a single block along with its nested blocks. To do this, right-click on the bullet point of the block you wish to export and select *Copy/Export as...* from the context menu. You can then select the desired format and options.
+		  logseq.order-list-type:: number
+		- **Export Selection**: This scope allows you to export the selected text or blocks. To use this feature, highlight the desired text or blocks, right-click on the selection, and choose *Copy/Export as...* from the context menu. You can then specify the desired format and options for the export.
+		  logseq.order-list-type:: number
+	- See [[Publishing]] for more details on the `Export public pages` graph export option.
+- ## Functionality
+	- ### Export Formats
+		- #### Graph Export
+		  Exports the entire graph in the following formats:
+			- **EDN**: Export the graph in Extensible Data Notation format.
+			- **JSON**: Export the graph in standard JSON format.
+			- **Standard Markdown**: Export the graph in Standard Markdown format.
+			  #+BEGIN_NOTE
+			  Block [[properties]] will not be included in standard markdown exports.
+			  #+END_NOTE
+			- **OPML**: Export the graph in OPML format, suitable for various outlining and mind-mapping applications.
+			- **Roam JSON**: Export the graph in Roam Research compatible format.
+			- **HTML**:  Export the graph in HTML format.
+		- #### Content-Specific Export
+		  Exports a selection, block, page, or whiteboard. The following formats are available:
+			- **Text**: Exports the content as plain text, maintaining the hierarchical structure of blocks and the bullet indentation.
+			- **OPML**: Exports content in the OPML format.
+			- **HTML**: Exports content in HTML format, preserving the original content's formatting and styles.
+			- **PNG**: Captures the appearance of a page, selection, or a [[whiteboard]] as an image.
+		- ### Export Options
+		  Depending on the export format, several options are available:
+			- #### Text, OPML, and HTML Options
+				- **Removal of brackets**: Converts `[[page]]` into `page`.
+				- **Removal of emphasis**: Strips emphasis formats such as **bold**, *italic*, or ~~strikethrough~~.
+				- **Removal of #tags**: Removes #tags from the exported content.
+				- **Block depth level**: Sets the maximum depth of nested blocks to include in the export. Options range from *all* to numbers 1-9.
+			- #### Text-Specific Options
+				- **Indentation style**: Selects the preferred indentation style. Options include dashes, spaces, or no-indent.
+				- **Newline after block**: Adds a newline after each block.
+				- **Removal of properties**: Excludes block properties from the export.
+			- #### HTML-Specific Option
+				- **Include properties**: Option to include block properties in the export.
+			- #### PNG-Specific Option
+				- **Transparent background**: This option removes the background color from the exported content, making it see-through.
+			- After choosing the export format and options, users can *copy* the exported content to the clipboard or *save* it to a file.
+- ## Background
 	- The Logseq export feature enables users to export selection, a single block or a page, or the entire graph into various formats, such as plain-text, OPML, HTML, or PNG. This feature is designed to enhance the user experience by providing a convenient way to share, backup, or migrate Logseq data to other platforms and applications.
-	- Purpose and benefits include improving compatibility with other tools, simplifying data backup and sharing, and providing multiple export options to suit user requirements.
-- ## Purpose and Benefits
-	- **Cross-platform Compatibility**: The export feature allows for better integration with other tools by supporting common file formats such as plain text, OPML, HTML, EDN, JSON, and standard Markdown. This cross-platform compatibility makes it easier to migrate data or use your Logseq content in different applications.
-	- **Data Backup**: The export feature provides an efficient way to create backups of your Logseq graph. Regular backups can help prevent data loss and ensure data integrity.
-	- **Flexible Sharing Options**: Exporting allows you to share your Logseq content with others in a format they can easily view or import into other tools. It also enables you to present your content in various formats suitable for different contexts, such as exporting a block to an image.
-	- **Customization**: The export feature offers numerous options to customize the exported content, such as defining the  scope of export {{cloze selection, a single block, a page, or the entire graph}}, choosing the export format, and selecting specific options related to each format. This flexibility allows users to tailor the export process to their specific needs.
-- ## Export Scopes
-	- **Export a [[Graph]]**: This option enables the export of all pages within the Logseq graph. To do so, navigate to the three-dot menu icon in the Logseq interface's top-right corner, select the *Export Graph* option from the dropdown menu, and then choose your preferred format.
-	  logseq.order-list-type:: number
-	- **Export a Single Page or a [[whiteboard]]**: This scope allows for exporting the content of an individual page. To use this option, open the page you intend to export, right-click the page title, and select the *Export* option from the context menu. You can then choose the desired format and options for the export.
-	  logseq.order-list-type:: number
-	- **Export a Single [[Block]]**: This option enables the export of a single block along with its nested blocks. To do this, right-click on the bullet point of the block you wish to export and select *Copy/Export as...* from the context menu. You can then select the desired format and options.
-	  logseq.order-list-type:: number
-	- **Export Selection**: This scope allows you to export the selected text or blocks. To use this feature, highlight the desired text or blocks, right-click on the selection, and choose *Copy/Export as...* from the context menu. You can then specify the desired format and options for the export.
-	  logseq.order-list-type:: number
-- ## Export Formats
-	- ### Graph Export
-	  Exports the entire graph in the following formats:
-		- **EDN**: Export the graph in Extensible Data Notation format.
-		- **JSON**: Export the graph in standard JSON format.
-		- **Standard Markdown**: Export the graph in Standard Markdown format.
-		  #+BEGIN_NOTE
-		  Block [[properties]] will not be included in standard markdown exports.
-		  #+END_NOTE
-		- **OPML**: Export the graph in OPML format, suitable for various outlining and mind-mapping applications.
-		- **Roam JSON**: Export the graph in Roam Research compatible format.
-		- **HTML**:  Export the graph in HTML format.
-	- ### Content-Specific Export
-	  Exports a selection, block, page, or whiteboard. The following formats are available:
-		- **Text**: Exports the content as plain text, maintaining the hierarchical structure of blocks and the bullet indentation.
-		- **OPML**: Exports content in the OPML format.
-		- **HTML**: Exports content in HTML format, preserving the original content's formatting and styles.
-		- **PNG**: Captures the appearance of a page, selection, or a [[whiteboard]] as an image.
-- ## Export Options
-  Depending on the export format, several options are available:
-	- #### Text, OPML, and HTML Options
-		- **Removal of brackets**: Converts `[[page]]` into `page`.
-		- **Removal of emphasis**: Strips emphasis formats such as **bold**, *italic*, or ~~strikethrough~~.
-		- **Removal of #tags**: Removes #tags from the exported content.
-		- **Block depth level**: Sets the maximum depth of nested blocks to include in the export. Options range from *all* to numbers 1-9.
-	- #### Text-Specific Options
-		- **Indentation style**: Selects the preferred indentation style. Options include dashes, spaces, or no-indent.
-		- **Newline after block**: Adds a newline after each block.
-		- **Removal of properties**: Excludes block properties from the export.
-	- #### HTML-Specific Option
-		- **Include properties**: Option to include block properties in the export.
-	- #### PNG-Specific Option
-		- **Transparent background**: This option removes the background color from the exported content, making it see-through.
-	- After choosing the export format and options, users can *copy* the exported content to the clipboard or *save* it to a file.
-- ## Configuration Options
-  Logseq provides a range of configuration options and page properties to customize the export process, including settings at both the graph and page levels.
-	- ### Graph-Level Configuration
-		- #### [[Settings]] Menu
-			- Under the *Editor* tab in the [[Settings]] menu, you will find the option "*Set pages to public by default*". When this setting is enabled (default), all pages within the graph will be considered public and included in the export unless the page's `public` property is explicitly set to `false`.
-			- If this setting is disabled,  all pages will be private and not included in the export unless the page's `public` property is explicitly set to `true`.
-			- This setting corresponds to the `:publishing/all-pages-public?` option in the [[config.edn]] file.
-	- ### Page-Level Configuration
-		- #### Public Page Property
-			- The `public` page property is a boolean attribute that can be set for individual pages to determine their inclusion in an export. It overrides the default setting in the [[Settings]] menu. For example, if a page's `public` property is set to `true`, it will be included in the export even if the "*Set pages to public by default*" setting is disabled.
-	- The interplay between the graph-level configuration and page-level properties can significantly affect the outcome of your export process. Therefore, reviewing these settings before performing an export is crucial to ensure they align with your specific needs.
\ No newline at end of file
+	- ### Purpose and Benefits
+		- **Cross-platform Compatibility**: The export feature allows for better integration with other tools by supporting common file formats such as plain text, OPML, HTML, EDN, JSON, and standard Markdown. This cross-platform compatibility makes it easier to migrate data or use your Logseq content in different applications.
+		- **Data Backup**: The export feature provides an efficient way to create backups of your Logseq graph. Regular backups can help prevent data loss and ensure data integrity.
+		- **Flexible Sharing Options**: Exporting allows you to share your Logseq content with others in a format they can easily view or import into other tools. It also enables you to present your content in various formats suitable for different contexts, such as exporting a block to an image.
+		- **Customization**: The export feature offers numerous options to customize the exported content, such as defining the  scope of export {{cloze selection, a single block, a page, or the entire graph}}, choosing the export format, and selecting specific options related to each format. This flexibility allows users to tailor the export process to their specific needs.
\ No newline at end of file
diff --git a/pages/Publishing.md b/pages/Publishing.md
index d9920c9..2333453 100644
--- a/pages/Publishing.md
+++ b/pages/Publishing.md
@@ -1,10 +1,20 @@
 type:: [[Feature]]
 platforms:: [[Desktop]]
-description:: This feature publishes a graph as a [[Publish Web]], single page application (SPA).
+description:: This feature publishes a graph as a [[Publish Web]], single page application (SPA). This is known as the Export option `Export public pages`.
 
 - ## Usage
 	- [[Publishing (Desktop App Only)]] is a tutorial to publish your first graph.
 	- An alternative to publishing from the menu is running the command `Export public graph pages as html`.
+	- This export can be configured at both graph and page levels:
+		- ### Graph-Level Configuration
+			- #### [[Settings]] Menu
+				- Under the *Editor* tab in the [[Settings]] menu, you will find the option "*Set pages to public by default*". When this setting is enabled (default), all pages within the graph will be considered public and included in the export unless the page's `public` property is explicitly set to `false`.
+				- If this setting is disabled,  all pages will be private and not included in the export unless the page's `public` property is explicitly set to `true`.
+				- This setting corresponds to the `:publishing/all-pages-public?` option in the [[config.edn]] file.
+		- ### Page-Level Configuration
+			- #### Public Page Property
+				- The `public` page property is a boolean attribute that can be set for individual pages to determine their inclusion in an export. It overrides the default setting in the [[Settings]] menu. For example, if a page's `public` property is set to `true`, it will be included in the export even if the "*Set pages to public by default*" setting is disabled.
+		- The interplay between the graph-level configuration and page-level properties can significantly affect the outcome of your export process. Therefore, reviewing these settings before performing an export is crucial to ensure they align with your specific needs.
 - ## Functionality
 	- Publishing permissions are per page, depending on whether the page is "public".
 		- By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.

From 315bcb0b7126175d54222a0a544b1f695bbe132f Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 11 May 2023 11:56:17 -0400
Subject: [PATCH 005/196] Fix accidental nesting of a section

---
 pages/Export.md | 32 ++++++++++++++++----------------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/pages/Export.md b/pages/Export.md
index 9aec83c..85c3cd1 100644
--- a/pages/Export.md
+++ b/pages/Export.md
@@ -32,22 +32,22 @@ description:: The Logseq Export feature allows users to export their data in var
 			- **OPML**: Exports content in the OPML format.
 			- **HTML**: Exports content in HTML format, preserving the original content's formatting and styles.
 			- **PNG**: Captures the appearance of a page, selection, or a [[whiteboard]] as an image.
-		- ### Export Options
-		  Depending on the export format, several options are available:
-			- #### Text, OPML, and HTML Options
-				- **Removal of brackets**: Converts `[[page]]` into `page`.
-				- **Removal of emphasis**: Strips emphasis formats such as **bold**, *italic*, or ~~strikethrough~~.
-				- **Removal of #tags**: Removes #tags from the exported content.
-				- **Block depth level**: Sets the maximum depth of nested blocks to include in the export. Options range from *all* to numbers 1-9.
-			- #### Text-Specific Options
-				- **Indentation style**: Selects the preferred indentation style. Options include dashes, spaces, or no-indent.
-				- **Newline after block**: Adds a newline after each block.
-				- **Removal of properties**: Excludes block properties from the export.
-			- #### HTML-Specific Option
-				- **Include properties**: Option to include block properties in the export.
-			- #### PNG-Specific Option
-				- **Transparent background**: This option removes the background color from the exported content, making it see-through.
-			- After choosing the export format and options, users can *copy* the exported content to the clipboard or *save* it to a file.
+	- ### Export Options
+	  Depending on the export format, several options are available:
+		- #### Text, OPML, and HTML Options
+			- **Removal of brackets**: Converts `[[page]]` into `page`.
+			- **Removal of emphasis**: Strips emphasis formats such as **bold**, *italic*, or ~~strikethrough~~.
+			- **Removal of #tags**: Removes #tags from the exported content.
+			- **Block depth level**: Sets the maximum depth of nested blocks to include in the export. Options range from *all* to numbers 1-9.
+		- #### Text-Specific Options
+			- **Indentation style**: Selects the preferred indentation style. Options include dashes, spaces, or no-indent.
+			- **Newline after block**: Adds a newline after each block.
+			- **Removal of properties**: Excludes block properties from the export.
+		- #### HTML-Specific Option
+			- **Include properties**: Option to include block properties in the export.
+		- #### PNG-Specific Option
+			- **Transparent background**: This option removes the background color from the exported content, making it see-through.
+		- After choosing the export format and options, users can *copy* the exported content to the clipboard or *save* it to a file.
 - ## Background
 	- The Logseq export feature enables users to export selection, a single block or a page, or the entire graph into various formats, such as plain-text, OPML, HTML, or PNG. This feature is designed to enhance the user experience by providing a convenient way to share, backup, or migrate Logseq data to other platforms and applications.
 	- ### Purpose and Benefits

From 96559dae8e209fe965cfee84236a7635d159fe42 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 11 May 2023 14:23:27 -0400
Subject: [PATCH 006/196] Add numbered list page

---
 pages/Numbered List.md    | 32 ++++++++++++++++++++++++++++++++
 pages/Templates___Docs.md |  2 +-
 2 files changed, 33 insertions(+), 1 deletion(-)
 create mode 100644 pages/Numbered List.md

diff --git a/pages/Numbered List.md b/pages/Numbered List.md
new file mode 100644
index 0000000..e5947b6
--- /dev/null
+++ b/pages/Numbered List.md	
@@ -0,0 +1,32 @@
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+description:: Provides numbered (ordered) lists with each list item being a block.
+initial-version:: 0.9.5
+
+## Usage
+	- A numbered list can be started in a couple ways:
+		- Type `1. ` in a block
+		  logseq.order-list-type:: number
+		- Press `t n` when focused on a block
+		  logseq.order-list-type:: number
+		- Type the `/Number list` command in a block
+		  logseq.order-list-type:: number
+	- Block(s) can be toggled in/out of a numbered list in the following ways:
+		- Press `t n` when focused on a block
+		  logseq.order-list-type:: number
+		- Type the `/Number list` command in a block
+		  logseq.order-list-type:: number
+		- Select multiple blocks, right click and select `Toggle number select`
+		  logseq.order-list-type:: number
+		- Select multiple blocks and press `t n`
+		  logseq.order-list-type:: number
+		- Type the `/Number children` command in a parent block to have all of its children blocks toggled
+		  logseq.order-list-type:: number
+	- Press `Enter` on a numbered block to create a new numbered block with the number automatically incremented.
+	- A numbered list can be stopped at any time by pressing `backspace` on an empty block or by using one of the above toggle options.
+- ## Functionality
+	- Blocks that are dragged into a numbered list are turned into a numbered block.
+	- A numbered block when copied and pasted remains a numbered block.
+	- ### Limitations
+		- A numbered list is not currently saved in a [standard ordered list format](https://daringfireball.net/projects/markdown/syntax#list).
+		- See https://github.com/logseq/logseq/pull/9141#issuecomment-1517108026 for ux limitations.
\ No newline at end of file
diff --git a/pages/Templates___Docs.md b/pages/Templates___Docs.md
index 94d527f..5f21720 100644
--- a/pages/Templates___Docs.md
+++ b/pages/Templates___Docs.md
@@ -15,7 +15,7 @@ title:: Templates/Docs
   template:: Feature
   template-including-parent:: false
 	- type:: [[Feature]]
-	  platforms:: [[All Platforms]] 
+	  platforms:: [[All Platforms]]
 	  description:: …
 	  initial-version:: …
 	- ## Usage

From 808e59046e0f3fc2c5e8ff0d49cc80dad75ac00c Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 11 May 2023 14:29:50 -0400
Subject: [PATCH 007/196] Update numbered list changelog with docs and breaking
 change note

---
 pages/Changelog.md     | 3 ++-
 pages/Numbered List.md | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index fe148c3..0347526 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,8 @@
 - ## Beta 0.9.5 [[May 11th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.5>
 	- [[Features]]
-		- Ordered(numbered) block list support [#9235](https://github.com/logseq/logseq/pull/9235)
+		- Ordered(numbered) block list support [#9235](https://github.com/logseq/logseq/pull/9235) - [Documentation](https://docs.logseq.com/#/page/numbered%20list)
+			- _Breaking change_: dwim lists are disabled by default since we now have block based lists. To reenable them, add `:dwim/settings {:list? true}` to your config.edn
 	- [[Thanks]]
 		- [[Adam Hupp]]
 			- Fix `yarn install` on Windows in [#9299](https://github.com/logseq/logseq/pull/9299)
diff --git a/pages/Numbered List.md b/pages/Numbered List.md
index e5947b6..1eaa695 100644
--- a/pages/Numbered List.md	
+++ b/pages/Numbered List.md	
@@ -29,4 +29,4 @@ initial-version:: 0.9.5
 	- A numbered block when copied and pasted remains a numbered block.
 	- ### Limitations
 		- A numbered list is not currently saved in a [standard ordered list format](https://daringfireball.net/projects/markdown/syntax#list).
-		- See https://github.com/logseq/logseq/pull/9141#issuecomment-1517108026 for ux limitations.
\ No newline at end of file
+		- See [this comment](https://github.com/logseq/logseq/pull/9141#issuecomment-1517108026) for ux limitations.
\ No newline at end of file

From d0856a717b72822ed5a8f93665f5c615a6bc88aa Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Fri, 12 May 2023 21:23:25 +0800
Subject: [PATCH 008/196] chore: release 0.9.6

---
 pages/Changelog.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 0347526..4220b8b 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,3 +1,17 @@
+- ## Beta 0.9.6 [[May 12th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.6>
+	- [[Thanks]]
+		- [[Billy Pinheiro]]
+			- Refine pt-BR translation [#9360](https://github.com/logseq/logseq/pull/9360)
+	- [[Fixed issues]]
+		- Plugin API `get current block` fail [#9372](https://github.com/logseq/logseq/pull/9372)
+		- Minor style tweaks for ordered list [#9370](https://github.com/logseq/logseq/pull/9370)
+		- Incorrect arrangement of ui items from pagebar [#9375](https://github.com/logseq/logseq/pull/9375)
+		- Whiteboards: performance of persist [#9358](https://github.com/logseq/logseq/pull/9358)
+		- Page renaming UI  [#9371](https://github.com/logseq/logseq/pull/9371)
+	- [[Enhancement]]
+		- React icons for tabler extensions [#9333](https://github.com/logseq/logseq/pull/9333)
+		- I18n: pt-BR [#9360](https://github.com/logseq/logseq/pull/9360)
 - ## Beta 0.9.5 [[May 11th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.5>
 	- [[Features]]

From 4f90db4f371c1ecf750f16ec614f54154d36575c Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Tue, 16 May 2023 23:56:20 +0800
Subject: [PATCH 009/196] fix: logseq started as a side-project called gitnotes
 in the end of 2019

---
 pages/one year in logseq.md | 94 ++++++++++++++++++-------------------
 1 file changed, 47 insertions(+), 47 deletions(-)

diff --git a/pages/one year in logseq.md b/pages/one year in logseq.md
index 3120622..524ca94 100644
--- a/pages/one year in logseq.md	
+++ b/pages/one year in logseq.md	
@@ -4,58 +4,58 @@ title: One year in Logseq
 
 - **Hello, everyone!**
 - **A little about the team**
-	- **Michael**
-	  ![image.png](../assets/pages_one year in logseq_1616235681415_0.png){:height 560, :width 960}
-	- **Charlie**  ![image.png](../assets/pages_one year in logseq_1616235711538_0.png)
-	- **Zhiyuan**
-	  ![image.png](../assets/pages_one year in logseq_1616235763365_0.png)
-	- **Weihua**
-	  ![image.png](../assets/pages_one year in logseq_1616235785959_0.png)
-	- **Junyu**
-	  ![CleanShot 2021-03-20 at 18.53.56@2x.png](../assets/pages_one year in logseq_1616237665640_0.png){:height 379, :width 279}
-	- I'm Tienson from Hangzhou, thanks to my wife we have a beautiful daughter.
-		- ![CleanShot 2021-03-20 at 18.15.54@2x.png](../assets/pages_one year in logseq_1616235368782_0.png){:height 557, :width 518}
+    - **Michael**
+      ![image.png](../assets/pages_one year in logseq_1616235681415_0.png){:height 560, :width 960}
+    - **Charlie**  ![image.png](../assets/pages_one year in logseq_1616235711538_0.png)
+    - **Zhiyuan**
+      ![image.png](../assets/pages_one year in logseq_1616235763365_0.png)
+    - **Weihua**
+      ![image.png](../assets/pages_one year in logseq_1616235785959_0.png)
+    - **Junyu**
+      ![CleanShot 2021-03-20 at 18.53.56@2x.png](../assets/pages_one year in logseq_1616237665640_0.png){:height 379, :width 279}
+    - I'm Tienson from Hangzhou, thanks to my wife we have a beautiful daughter.
+        - ![CleanShot 2021-03-20 at 18.15.54@2x.png](../assets/pages_one year in logseq_1616235368782_0.png){:height 557, :width 518}
 - **What's logseq?**
-	- At present, it's a note-taking app
-		- It's also a community for knowledge sharing and collaboration, yes, our discord group and forum!
-	- In the future, we hope Logseq can be more helpful for everyone around the world.
+    - At present, it's a note-taking app
+        - It's also a community for knowledge sharing and collaboration, yes, our discord group and forum!
+    - In the future, we hope Logseq can be more helpful for everyone around the world.
 - **Why the name?**
   later:: 1616236181947
   I know `log` is for daily notes, what `seq` means?
-	- It's a sequence of our notes, ideas and thoughts. To me it's all the things I want to remember in my life.
+    - It's a sequence of our notes, ideas and thoughts. To me it's all the things I want to remember in my life.
 - **Why building logseq?**
-	- I started a side project called `putchar.org` back in 2018, which is Medium for programmers, a place to publish and discuss tech articles.
-		- Unfortunately, it's deprecated after more than 1 year working on it because for me It's hard to build a community and I have some contracts at that time so that I can't focus on it.
-		- But I still want to make it better for general knowledge publishing and collaboration.
-		- Also, many code, especially the parser for logseq are from some of my previous side projects, so failures are not that bad :)
-	- I was using both Org-mode and TiddlyWiki for my notes, I want to read my notes and capture some links on mobile, also, I want a better outliner UI on web  compared to text editors like Emacs and Vim.
-	- So, when my last contract ended at the end of 2020, I knew it's the time to build something! 😎
+    - I started a side project called `putchar.org` back in 2018, which is Medium for programmers, a place to publish and discuss tech articles.
+        - Unfortunately, it's deprecated after more than 1 year working on it because for me It's hard to build a community and I have some contracts at that time so that I can't focus on it.
+        - But I still want to make it better for general knowledge publishing and collaboration.
+        - Also, many code, especially the parser for logseq are from some of my previous side projects, so failures are not that bad :)
+    - I was using both Org-mode and TiddlyWiki for my notes, I want to read my notes and capture some links on mobile, also, I want a better outliner UI on web  compared to text editors like Emacs and Vim.
+    - So, when my last contract ended at the end of 2019, I knew it's the time to build something! 😎
 - **What's the difference between logseq and other tools?**
   id:: 61110543-a71f-458d-b42e-b78a4d22f0c0
-	- **The user is the king of the data. ** [[local-first]]
-	  Simply put, I don't trust putting my notes and my life on any cloud services without End-to-End encryption support.
-	- **Logseq doesn't lock the data.**
-		- Even though logseq is an outliner tool, it works directly with plain-text like Markdown and Org mode. We believe in plain-text for data longevity, we believe in standard syntaxes and open protocols for better collaboration with the existing ecosystem.
-		- Shameless plug, logseq might be the **_first_** app that have two-way sync between plain-text and outliner, yay!
-	- **Everyone can build their own workflows**
-	  Slip box? GTD? Hierarchical tags? With [[Queries]], [[Advanced Queries]] and coming [[Plugins]], nothing is impossible!
-	- **Open Source**
-	  As developers, we believe the ultimate fun is to fork the code and do nasty tweaks!
-	- **Being different instead of a clone**
-		- Bring org mode's task management and many other features to Markdown
-		- The first(might be) note-taking app with Git sync on Web (Thanks to [[Isomorphic-git]])
-		- The first(might be) note-taking app can work with your local files on Web
-		- ` /Page Embed`
-		- `/Draw` integration with [[Excalidraw]]
-		- `Now Later workflow`
-		- Custom queries on journals page
-		- Publishing the whole web app to your own website
+    - **The user is the king of the data. ** [[local-first]]
+      Simply put, I don't trust putting my notes and my life on any cloud services without End-to-End encryption support.
+    - **Logseq doesn't lock the data.**
+        - Even though logseq is an outliner tool, it works directly with plain-text like Markdown and Org mode. We believe in plain-text for data longevity, we believe in standard syntaxes and open protocols for better collaboration with the existing ecosystem.
+        - Shameless plug, logseq might be the **_first_** app that have two-way sync between plain-text and outliner, yay!
+    - **Everyone can build their own workflows**
+      Slip box? GTD? Hierarchical tags? With [[Queries]], [[Advanced Queries]] and coming [[Plugins]], nothing is impossible!
+    - **Open Source**
+      As developers, we believe the ultimate fun is to fork the code and do nasty tweaks!
+    - **Being different instead of a clone**
+        - Bring org mode's task management and many other features to Markdown
+        - The first(might be) note-taking app with Git sync on Web (Thanks to [[Isomorphic-git]])
+        - The first(might be) note-taking app can work with your local files on Web
+        - ` /Page Embed`
+        - `/Draw` integration with [[Excalidraw]]
+        - `Now Later workflow`
+        - Custom queries on journals page
+        - Publishing the whole web app to your own website
 - **The future**
-	- More stable and more performant
-	- Better [[Undo and Redo]] `#undotree`
-	- End-to-End encryption storage
-	- Mobile apps
-	- Real-time collaboration
-	- Exploring more ways to help for thoughts
-	- Who knows?
-- **Thank you everyone for your time, have a great weekend!** 🙏
\ No newline at end of file
+    - More stable and more performant
+    - Better [[Undo and Redo]] `#undotree`
+    - End-to-End encryption storage
+    - Mobile apps
+    - Real-time collaboration
+    - Exploring more ways to help for thoughts
+    - Who knows?
+- **Thank you everyone for your time, have a great weekend!** 🙏

From bc719b09ada447ecfe5efdc10d720337d3b60cc5 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 19 May 2023 22:21:18 -0400
Subject: [PATCH 010/196] Trivial change to bump re-publish

---
 pages/Knowledge Graph.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Knowledge Graph.md b/pages/Knowledge Graph.md
index 10cbd8a..e99308c 100644
--- a/pages/Knowledge Graph.md	
+++ b/pages/Knowledge Graph.md	
@@ -6,7 +6,7 @@ platforms:: [[All Platforms]]
 - ## Usage
 	- Watch your knowledge graph grow by going to your main menu (click your profile picture) -> select "Graph"
 - ## Functionality
-	- TODO Fill out feature's functionality #docs
+	- TODO Fill out functionality #docs
 - ## Background
 	- As you add ideas and thoughts into Logseq and connect them, your knowledge graph grows. Just as your brain generates and connects new neurons to form new knowledge and ideas.
 	- These connections are what makes Logseq so powerful as a second brain, we generate and synthesize information much like your own brain does, but better.

From 8326c5e319fff3917593acc936a57f5dfb7a9a6e Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 19 May 2023 22:32:27 -0400
Subject: [PATCH 011/196] Revert to stable publish version to avoid bug I'm
 seeing

---
 .github/workflows/gh-pages.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index 8e0878e..81ec0b8 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -14,7 +14,7 @@ jobs:
       - uses: actions/checkout@v3
 
       - name: Logseq Publish
-        uses: logseq/publish-spa@main
+        uses: logseq/publish-spa@v0.1.0
         with:
           output-directory: www
           version: 0.9.5

From beadf5dae324c60f139ae23ece14caf76e4b81dc Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 19 May 2023 22:39:44 -0400
Subject: [PATCH 012/196] Bump frontend version to rebuild it

---
 .github/workflows/gh-pages.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index 81ec0b8..d95f19c 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -17,7 +17,7 @@ jobs:
         uses: logseq/publish-spa@v0.1.0
         with:
           output-directory: www
-          version: 0.9.5
+          version: 0.9.6
 
       - name: Add .nojekyll file
         run: touch www/.nojekyll

From 3512b6d63efc0fcf5268ddafa653ad4f2abc84cf Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 19 May 2023 22:58:49 -0400
Subject: [PATCH 013/196] Bump back to stable action version

---
 .github/workflows/gh-pages.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index d95f19c..483673f 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -14,10 +14,10 @@ jobs:
       - uses: actions/checkout@v3
 
       - name: Logseq Publish
-        uses: logseq/publish-spa@v0.1.0
+        uses: logseq/publish-spa@179ed0f16cd64bdf61ace48c21590245ff51bbdb
         with:
           output-directory: www
-          version: 0.9.6
+          version: 0.9.5
 
       - name: Add .nojekyll file
         run: touch www/.nojekyll

From 12ea3111d4db4a5ac35572fd12b513f5a2793002 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 19 May 2023 23:23:03 -0400
Subject: [PATCH 014/196] Bump back to publish-spa with previous
 gp-cli/parse-graph

---
 .github/workflows/gh-pages.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index 483673f..8e0878e 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -14,7 +14,7 @@ jobs:
       - uses: actions/checkout@v3
 
       - name: Logseq Publish
-        uses: logseq/publish-spa@179ed0f16cd64bdf61ace48c21590245ff51bbdb
+        uses: logseq/publish-spa@main
         with:
           output-directory: www
           version: 0.9.5

From 216f1d055b088c56f202d84e6a0600160522355a Mon Sep 17 00:00:00 2001
From: Ben Yorke <ben@yorke.io>
Date: Mon, 22 May 2023 22:08:28 +0200
Subject: [PATCH 015/196] Add table feature documentation

---
 pages/Tables.md   | 66 +++++++++++++++++++++++++++++++++++++++++++++++
 pages/contents.md |  3 ++-
 2 files changed, 68 insertions(+), 1 deletion(-)
 create mode 100644 pages/Tables.md

diff --git a/pages/Tables.md b/pages/Tables.md
new file mode 100644
index 0000000..407ced3
--- /dev/null
+++ b/pages/Tables.md
@@ -0,0 +1,66 @@
+Tables in Logseq are our first versioned component, accepting props to control the output. The original version of tables, which supports multi-line markdown tables and query results, is version 1. A second verison is currently in beta testing, and can be activated by giving a markdown table or query element the prop: `logseq.table.version:: 2`
+
+- ## Props
+- Logseq tables now render differently depending on the block-level props. The default values for these props can also be set in your `config.edn` as top level keys.
+- ### logseq.table.version
+	- The `logseq.table.version` prop determines the version of the table. It can take one of two possible values:
+		- `1` (default) - version 1 displays the standard table with no customizations
+		- `2` - version 2 displays a table with dynamic widths to better fit content, with customizations available via props
+- ### logseq.table.hover
+	- The `logseq.table.hover` prop configures the hover effect of the table. It accepts the following values:
+		- `cell` (default) - hovering over a cell will highlight just the cell you are interacting with
+		- `row` - hovering over a cell will highlight the entire row of the cell you are interacting with
+		- `col` - hovering over a cell will highlight the entire column of the cell you are interacting with
+		- `both` - hovering over a cell will highlight the entire row and the entire column of the cell you are interacting with
+		- `none` - hovering over a cell will not cause a change in visual appearance
+- ### logseq.table.compact
+	- The `logseq.table.compact` prop decides whether to show a compact version of the data. The possible values are:
+		- `false` (default) - table data will be shown with standard padding for laid back consumption
+		- `true` - table data will be shown with minimal padding to fit as much information on the screen as densely as possible
+- ### logseq.table.headers
+	- The `logseq.table.headers` prop adjusts the casing that should be applied to the header columns. You can set it to one of the following options:
+		- `none` (default) - use the name of the column exactly as found in the source data
+		  collapsed:: true
+			- `exAMpLE header` becomes `exAMpLE header`
+		- `uppercase` - transform the entire name of the column to uppercase letters
+		  collapsed:: true
+			- `exAMpLE header` becomes `EXAMPLE HEADER`
+			  id:: 646bc966-3e91-4ce7-b17a-3446ea28a996
+		- `capitalize` - transform the entire name of the column to have each word capitalized
+		  collapsed:: true
+			- `exAMpLE header` becomes `Example Header`
+		- `capitalize-first` - transform the entire name of the column to lowercase letters, and capitalize only the first letter of the column name
+		  collapsed:: true
+			- `exAMpLE header` becomes `Example header`
+		- `lowercase` - transform the entire name of the column to lowercase letters
+		  collapsed:: true
+			- `exAMpLE header` becomes `example header`
+- ### logseq.table.borders
+	- The `logseq.table.borders` prop allows you to define whether or not the table should have borders between all cells and rows. It can be either:
+		- `true` (default) - show borders between all of the cells
+		- `false` - do not show borders between any of the cells
+- ### logseq.table.stripes
+	- The `logseq.table.stripes` prop decides whether or not the table should have alternately colored table rows. The available options are:
+		- `false` (default) - all rows will have a uniform background color
+		- `true` - rows will have alternating background colors
+- ### logseq.table.max-width
+	- The `logseq.table.max-width` prop specifies the maximum width (in rems) that should be applied to each column. It accepts any number, with a default value of `30`.
+		- `30` (default) - do not allow table columns to exceed 30 rems
+		- `any number` - limit the maximum size of table columns to this many rems
+- ### logseq.color
+	- The `logseq.color` prop sets the color accent of the table. The following colors are available:
+		- `crimson`
+		- `red`
+		- `tomato`
+		- `orange`
+		- `amber`
+		- `green`
+		- `grass`
+		- `teal`
+		- `blue`
+		- `purple`
+		- `indigo`
+		- `violet`
+		- `plum`
+		- `pink`
+		-
\ No newline at end of file
diff --git a/pages/contents.md b/pages/contents.md
index 4a9234c..9dbef6c 100644
--- a/pages/contents.md
+++ b/pages/contents.md
@@ -43,6 +43,7 @@
 	- [[Embed Media - Audio, Photos, Videos]]
 	- [[Plugins]]
 	- [[Whiteboard]]
+	- [[Tables]]
 - [[Logseq School]]
 	- [[Plugins 101]]
 - [[Document syntax]]
@@ -65,4 +66,4 @@
 - 💬
 	- Message us on [Discord](https://discord.gg/KpN4eHY) (We love feedback!)
 	- Ask questions in the [forum](https://discuss.logseq.com)
-	- Tweet us [@logseq](https://twitter.com/logseq)
+	- Tweet us [@logseq](https://twitter.com/logseq)
\ No newline at end of file

From b34643854233d809e8d930c520d12631c8d1cc77 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 22 May 2023 21:44:44 -0400
Subject: [PATCH 016/196] Add a type, standard sections and fix typo

---
 pages/Tables.md | 134 +++++++++++++++++++++++++-----------------------
 1 file changed, 69 insertions(+), 65 deletions(-)

diff --git a/pages/Tables.md b/pages/Tables.md
index 407ced3..60471e8 100644
--- a/pages/Tables.md
+++ b/pages/Tables.md
@@ -1,66 +1,70 @@
-Tables in Logseq are our first versioned component, accepting props to control the output. The original version of tables, which supports multi-line markdown tables and query results, is version 1. A second verison is currently in beta testing, and can be activated by giving a markdown table or query element the prop: `logseq.table.version:: 2`
+type:: [[UI Element]]
+description:: Tables are our first versioned component, accepting props to control the output.
 
-- ## Props
-- Logseq tables now render differently depending on the block-level props. The default values for these props can also be set in your `config.edn` as top level keys.
-- ### logseq.table.version
-	- The `logseq.table.version` prop determines the version of the table. It can take one of two possible values:
-		- `1` (default) - version 1 displays the standard table with no customizations
-		- `2` - version 2 displays a table with dynamic widths to better fit content, with customizations available via props
-- ### logseq.table.hover
-	- The `logseq.table.hover` prop configures the hover effect of the table. It accepts the following values:
-		- `cell` (default) - hovering over a cell will highlight just the cell you are interacting with
-		- `row` - hovering over a cell will highlight the entire row of the cell you are interacting with
-		- `col` - hovering over a cell will highlight the entire column of the cell you are interacting with
-		- `both` - hovering over a cell will highlight the entire row and the entire column of the cell you are interacting with
-		- `none` - hovering over a cell will not cause a change in visual appearance
-- ### logseq.table.compact
-	- The `logseq.table.compact` prop decides whether to show a compact version of the data. The possible values are:
-		- `false` (default) - table data will be shown with standard padding for laid back consumption
-		- `true` - table data will be shown with minimal padding to fit as much information on the screen as densely as possible
-- ### logseq.table.headers
-	- The `logseq.table.headers` prop adjusts the casing that should be applied to the header columns. You can set it to one of the following options:
-		- `none` (default) - use the name of the column exactly as found in the source data
-		  collapsed:: true
-			- `exAMpLE header` becomes `exAMpLE header`
-		- `uppercase` - transform the entire name of the column to uppercase letters
-		  collapsed:: true
-			- `exAMpLE header` becomes `EXAMPLE HEADER`
-			  id:: 646bc966-3e91-4ce7-b17a-3446ea28a996
-		- `capitalize` - transform the entire name of the column to have each word capitalized
-		  collapsed:: true
-			- `exAMpLE header` becomes `Example Header`
-		- `capitalize-first` - transform the entire name of the column to lowercase letters, and capitalize only the first letter of the column name
-		  collapsed:: true
-			- `exAMpLE header` becomes `Example header`
-		- `lowercase` - transform the entire name of the column to lowercase letters
-		  collapsed:: true
-			- `exAMpLE header` becomes `example header`
-- ### logseq.table.borders
-	- The `logseq.table.borders` prop allows you to define whether or not the table should have borders between all cells and rows. It can be either:
-		- `true` (default) - show borders between all of the cells
-		- `false` - do not show borders between any of the cells
-- ### logseq.table.stripes
-	- The `logseq.table.stripes` prop decides whether or not the table should have alternately colored table rows. The available options are:
-		- `false` (default) - all rows will have a uniform background color
-		- `true` - rows will have alternating background colors
-- ### logseq.table.max-width
-	- The `logseq.table.max-width` prop specifies the maximum width (in rems) that should be applied to each column. It accepts any number, with a default value of `30`.
-		- `30` (default) - do not allow table columns to exceed 30 rems
-		- `any number` - limit the maximum size of table columns to this many rems
-- ### logseq.color
-	- The `logseq.color` prop sets the color accent of the table. The following colors are available:
-		- `crimson`
-		- `red`
-		- `tomato`
-		- `orange`
-		- `amber`
-		- `green`
-		- `grass`
-		- `teal`
-		- `blue`
-		- `purple`
-		- `indigo`
-		- `violet`
-		- `plum`
-		- `pink`
-		-
\ No newline at end of file
+- ## Usage
+	- The original version, version 1, is enabled by default. It supports multi-line markdown tables and [[Query table]].
+	- A second version is currently in beta testing, and can be activated by giving a markdown table or query element the prop: `logseq.table.version:: 2`
+- ## Functionality
+	- ### Props
+		- Logseq tables now render differently depending on the block-level props. The default values for these props can also be set in your `config.edn` as top level keys.
+		- #### logseq.table.version
+			- The `logseq.table.version` prop determines the version of the table. It can take one of two possible values:
+				- `1` (default) - version 1 displays the standard table with no customizations
+				- `2` - version 2 displays a table with dynamic widths to better fit content, with customizations available via props
+		- #### logseq.table.hover
+			- The `logseq.table.hover` prop configures the hover effect of the table. It accepts the following values:
+				- `cell` (default) - hovering over a cell will highlight just the cell you are interacting with
+				- `row` - hovering over a cell will highlight the entire row of the cell you are interacting with
+				- `col` - hovering over a cell will highlight the entire column of the cell you are interacting with
+				- `both` - hovering over a cell will highlight the entire row and the entire column of the cell you are interacting with
+				- `none` - hovering over a cell will not cause a change in visual appearance
+		- #### logseq.table.compact
+			- The `logseq.table.compact` prop decides whether to show a compact version of the data. The possible values are:
+				- `false` (default) - table data will be shown with standard padding for laid back consumption
+				- `true` - table data will be shown with minimal padding to fit as much information on the screen as densely as possible
+		- ### logseq.table.headers
+			- The `logseq.table.headers` prop adjusts the casing that should be applied to the header columns. You can set it to one of the following options:
+				- `none` (default) - use the name of the column exactly as found in the source data
+				  collapsed:: true
+					- `exAMpLE header` becomes `exAMpLE header`
+				- `uppercase` - transform the entire name of the column to uppercase letters
+				  collapsed:: true
+					- `exAMpLE header` becomes `EXAMPLE HEADER`
+					  id:: 646bc966-3e91-4ce7-b17a-3446ea28a996
+				- `capitalize` - transform the entire name of the column to have each word capitalized
+				  collapsed:: true
+					- `exAMpLE header` becomes `Example Header`
+				- `capitalize-first` - transform the entire name of the column to lowercase letters, and capitalize only the first letter of the column name
+				  collapsed:: true
+					- `exAMpLE header` becomes `Example header`
+				- `lowercase` - transform the entire name of the column to lowercase letters
+				  collapsed:: true
+					- `exAMpLE header` becomes `example header`
+		- #### logseq.table.borders
+			- The `logseq.table.borders` prop allows you to define whether or not the table should have borders between all cells and rows. It can be either:
+				- `true` (default) - show borders between all of the cells
+				- `false` - do not show borders between any of the cells
+		- #### logseq.table.stripes
+			- The `logseq.table.stripes` prop decides whether or not the table should have alternately colored table rows. The available options are:
+				- `false` (default) - all rows will have a uniform background color
+				- `true` - rows will have alternating background colors
+		- #### logseq.table.max-width
+			- The `logseq.table.max-width` prop specifies the maximum width (in rems) that should be applied to each column. It accepts any number, with a default value of `30`.
+				- `30` (default) - do not allow table columns to exceed 30 rems
+				- `any number` - limit the maximum size of table columns to this many rems
+		- #### logseq.color
+			- The `logseq.color` prop sets the color accent of the table. The following colors are available:
+				- `crimson`
+				- `red`
+				- `tomato`
+				- `orange`
+				- `amber`
+				- `green`
+				- `grass`
+				- `teal`
+				- `blue`
+				- `purple`
+				- `indigo`
+				- `violet`
+				- `plum`
+				- `pink`
\ No newline at end of file

From 61e539bfe55111e8ad6f1597a30443640c23de99 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 23 May 2023 12:30:07 -0400
Subject: [PATCH 017/196] Update docs effected by 0.9.7

---
 pages/Publishing.md | 2 +-
 pages/custom.js.md  | 3 ++-
 pages/iOS.md        | 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/pages/Publishing.md b/pages/Publishing.md
index 2333453..767066e 100644
--- a/pages/Publishing.md
+++ b/pages/Publishing.md
@@ -20,7 +20,7 @@ description:: This feature publishes a graph as a [[Publish Web]], single page a
 		- By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.
 		- Alternatively, in [[Settings]] all pages can be made public by default and then the property `publish:: false` can be used to make specific pages private.
 	- All published pages are displayed in a read-only mode.
-	- Published apps can read user configuration from [[config.edn]], [[custom.css]] and [[export.css]]. [[custom.css]] and [[export.css]] are optional.
+	- Published apps can read user configuration from [[config.edn]], [[custom.css]], [[custom.js]] and [[export.css]]. All files are optional except for config.edn.
 	- ### Available Features
 	  id:: 63595c2e-2383-42d4-ad20-5647758a7337
 	  collapsed:: true
diff --git a/pages/custom.js.md b/pages/custom.js.md
index 7585e27..6fa2fa1 100644
--- a/pages/custom.js.md
+++ b/pages/custom.js.md
@@ -1,6 +1,7 @@
 title:: custom.js
 type:: [[Feature]]
-platforms:: [[All Platforms]] except [[Publish Web]]
+platforms:: [[All Platforms]]
+description:: Local config file, logseq/custom.js, loads custom js for a graph on startup
 
 - ## Usage
 	- First time you load a custom.js file, you are prompted to confirm you want to load it.
diff --git a/pages/iOS.md b/pages/iOS.md
index 7b5246e..bf0413e 100644
--- a/pages/iOS.md
+++ b/pages/iOS.md
@@ -1,2 +1,2 @@
 type:: [[Platform]] 
-description:: This refers to iOS on mobile
+description:: This refers to iOS on mobile. Only versions 14 and greater are supported.

From 6b85de9f663c1cffde9796a6aa40d66cafeea0e2 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 24 May 2023 01:50:28 +0800
Subject: [PATCH 018/196] chore(release): 0.9.7

---
 pages/Changelog.md | 49 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 49 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 4220b8b..7e002d8 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,3 +1,52 @@
+- ## Beta 0.9.7 [[May 24th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.7>
+	- [[BREAKING CHANGE]]
+		- Due to some compatibility issues, we dropped support for iOS 13
+	- [[Features]]
+		- New Version 2 [[Tables]] [Document](https://docs.logseq.com/#/page/tables) [#8532](https://github.com/logseq/logseq/pull/8532)
+	- [[Thanks]]
+		- [[Avelino]]
+			- Split language translations into one file per language in [#9383](https://github.com/logseq/logseq/pull/9383)
+		- [[Bad3r]]
+			- dev(playwright): Ignore connection refused errors in [#9426](https://github.com/logseq/logseq/pull/9426)
+			- tweak wrong default `config.edn` values in [#9409](https://github.com/logseq/logseq/pull/9409)
+		- [[Candide U]]
+			- Add `custom.js` to Logseq publishing's app in [#9291](https://github.com/logseq/logseq/pull/9291)
+		- [[Claas Störtenbecker]]
+			- Update `logseq.api.update_block` API  in [#9272](https://github.com/logseq/logseq/pull/9272)
+		- [[Giuseppe D'Andrea]]
+			- Fix calculator command on a non-blank line in [#9449](https://github.com/logseq/logseq/pull/9449)
+			- Fix view scroll position when selecting multiple blocks in [#9444](https://github.com/logseq/logseq/pull/9444)
+		- [[Ulices]]
+			- Add more Spanish translations with the new format in [#9438](https://github.com/logseq/logseq/pull/9438)
+		- [[Michele]]
+			- Fix Italian translation error in [#9440](https://github.com/logseq/logseq/pull/9440)
+		- [[Sergey Kolesnik]]
+			- Update `templates/config.edn` in [#9408](https://github.com/logseq/logseq/pull/9408)
+	- [[Fixed issues]]
+		- Whiteboards: fix actions like undo on converted shapes [#9410](https://github.com/logseq/logseq/pull/9410)
+		- Broken block refs when cutting or deleting blocks [#9406](https://github.com/logseq/logseq/pull/9406)
+		- Can't jump to the correct position when editing number list [#9401](https://github.com/logseq/logseq/pull/9401)
+		- Org-mode pages in aliased links not creating pages [#9381](https://github.com/logseq/logseq/pull/9381)
+		- Tweak default `config.edn` [#9409](https://github.com/logseq/logseq/pull/9409) [#9408](https://github.com/logseq/logseq/pull/9408)
+		- Calculator command on a non-blank line [#9449](https://github.com/logseq/logseq/pull/9449)
+		- Cli tool `nbb-logseq` scripts ignoring incorrectly for relative dir [#9443](https://github.com/logseq/logseq/pull/9443)
+		- Fix blocks losing references and disappearing from references panel [#9389](https://github.com/logseq/logseq/pull/9389)
+		- Show block bullet when a blank block has children [#9427](https://github.com/logseq/logseq/pull/9427)
+		- Add Unicode normalization to file watcher on mobile platforms [#9419](https://github.com/logseq/logseq/pull/9419) [#9453](https://github.com/logseq/logseq/pull/9453)
+		- Pasting fail on iOS [#9463](https://github.com/logseq/logseq/pull/9463), asset sharing fail on iOS [#9462](https://github.com/logseq/logseq/pull/9462)
+		- Mobile UI tweaks [#9405](https://github.com/logseq/logseq/pull/9405)
+	- [[Enhancement]]
+		- Add `custom.js` to Logseq publishing's app(minor behavior change) [#9291](https://github.com/logseq/logseq/pull/9291)
+		- Refactor iOS sharing [#9456](https://github.com/logseq/logseq/pull/9456)
+		- I18n: Spanish [#9438](https://github.com/logseq/logseq/pull/9438), Italian [#9440](https://github.com/logseq/logseq/pull/9440)
+		- Split language translations into one file per language [#9383](https://github.com/logseq/logseq/pull/9383)
+		- Update version control settings description [#9373](https://github.com/logseq/logseq/pull/9373)
+		- Plugin API `logseq.api.update_block` can preserve properties [#9272](https://github.com/logseq/logseq/pull/9272)
+		- Cli tool `nbb-logseq` scripts now have publishing support for all graphs, not just git based ones [#9348](https://github.com/logseq/logseq/pull/9348)
+		- Restore scroll position new adding newlines in a block [#9404](https://github.com/logseq/logseq/pull/9404)
+		- Scroll the view when selecting multiple blocks [#9444](https://github.com/logseq/logseq/pull/9444)
+		- Add missing title to opml-export [#9429](https://github.com/logseq/logseq/pull/9429)
 - ## Beta 0.9.6 [[May 12th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.6>
 	- [[Thanks]]

From 82de9cdab10645adc96d6a658a33e7e579a32c21 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 24 May 2023 03:01:31 +0800
Subject: [PATCH 019/196] revoke 0.9.7

---
 pages/Changelog.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 7e002d8..bd178a2 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,5 @@
-- ## Beta 0.9.7 [[May 24th, 2023]]
-  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.7>
+- ## Beta 0.9.8 [[May 24th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
 	- [[Features]]

From b8936d5dff20c0b6d46c8f3dfcd38dc52696e6a7 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 24 May 2023 03:29:17 +0800
Subject: [PATCH 020/196] fix: add upgrade notice

---
 pages/Changelog.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index bd178a2..9963b9a 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,7 @@
 - ## Beta 0.9.8 [[May 24th, 2023]]
-  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>.
+  
+  **NOTE**: The 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
 	- [[Features]]

From 1cf3c1cb62b28f793f7785c1f740794090e8d289 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 24 May 2023 03:33:26 +0800
Subject: [PATCH 021/196] chore: wording

---
 pages/Changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 9963b9a..36d0f65 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,7 @@
 - ## Beta 0.9.8 [[May 24th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>.
   
-  **NOTE**: The 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
+  **NOTE**: The previous 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
 	- [[Features]]

From a9143033a1ee491e635fef781a850a69b011be3f Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 26 May 2023 09:08:43 -0400
Subject: [PATCH 022/196] Bump to latest version

---
 .github/workflows/gh-pages.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index 8e0878e..61a4031 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -17,7 +17,7 @@ jobs:
         uses: logseq/publish-spa@main
         with:
           output-directory: www
-          version: 0.9.5
+          version: 0.9.8
 
       - name: Add .nojekyll file
         run: touch www/.nojekyll

From 9a8f628841d19d93248c5f82cfc9847df772bb6a Mon Sep 17 00:00:00 2001
From: Bad3r <bad3r@pm.me>
Date: Sat, 27 May 2023 21:13:14 -0400
Subject: [PATCH 023/196] enhance: update quick capture template docs

---
 pages/Logseq Protocol.md | 25 ++++++++++++++++---------
 1 file changed, 16 insertions(+), 9 deletions(-)

diff --git a/pages/Logseq Protocol.md b/pages/Logseq Protocol.md
index a08eb5c..e630c96 100644
--- a/pages/Logseq Protocol.md	
+++ b/pages/Logseq Protocol.md	
@@ -19,14 +19,21 @@
 			- `append`: (optional, boolean) Append to the end of the page, default to `false`(current editing position)
 			- `page`:    (optional) Page name to insert to, use "TODAY" to insert to today page
 		- Settings (in `config.edn`):
-			- Template variables are `{time}`, `{date}`, `{text}` and `{url}`
-				- Use `[[{date}]]` for a reference to today's journal page
+			- `{time}`: capture time
+				- `{date}`: capture date using current date format, use `[[{date}]]` to get a page reference
+				- `{text}`: text that users selected before sharing.
+				- `{url}`: URL or assets path for media files stored in Logseq.
+				- #+BEGIN_TIP
+				  Use `[[{date}]]` for a reference to today's journal page
+				  #+END_TIP
 			- ```edn
-			  :quick-capture-templates {:text "[[quick capture]] **{time}** {text} {url}"}
+			  :quick-capture-templates
+			  {:text "[[quick capture]] **{time}**: {text} from {url}"
+			   :media "[[quick capture]] **{time}**: {url}"}
 			  
-			  :quick-capture-options {
-			                          :insert-today? false
-			                          :redirect-page? true
-			                          :default-page "My Captured Page"
-			                          }
-			  ```
\ No newline at end of file
+			  :quick-capture-options
+			  {:insert-today? false
+			   :redirect-page? true
+			   :default-page "My Captured Page"}
+			  ```
+-
\ No newline at end of file

From 0666c51882cee6f2c058d7207b1bf290c0c3f5af Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 30 May 2023 09:32:54 -0400
Subject: [PATCH 024/196] Update location for template config.edn

---
 pages/Changelog.md       | 6 +++---
 pages/config edn file.md | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 36d0f65..91248f8 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,6 +1,6 @@
 - ## Beta 0.9.8 [[May 24th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>.
-  
+
   **NOTE**: The previous 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
@@ -24,7 +24,7 @@
 		- [[Michele]]
 			- Fix Italian translation error in [#9440](https://github.com/logseq/logseq/pull/9440)
 		- [[Sergey Kolesnik]]
-			- Update `templates/config.edn` in [#9408](https://github.com/logseq/logseq/pull/9408)
+			- Update `config.edn` in [#9408](https://github.com/logseq/logseq/pull/9408)
 	- [[Fixed issues]]
 		- Whiteboards: fix actions like undo on converted shapes [#9410](https://github.com/logseq/logseq/pull/9410)
 		- Broken block refs when cutting or deleting blocks [#9406](https://github.com/logseq/logseq/pull/9406)
@@ -2196,4 +2196,4 @@
 		- Many UX enhancements
 - [[Changelog_07_09]]
 - [[Changelog_06]]
-- [[Changelog 2020]]
\ No newline at end of file
+- [[Changelog 2020]]
diff --git a/pages/config edn file.md b/pages/config edn file.md
index a311319..9ce7f0a 100644
--- a/pages/config edn file.md	
+++ b/pages/config edn file.md	
@@ -8,7 +8,7 @@ description:: Local config file, `logseq/config.edn`, is the main configuration
 	- Alternatively, edit your graph's config file located at `logseq/config.edn`.
 	- Some options are editable via the UI from other tabs in Settings.
 - ## Functionality
-	- See the [config.edn template](https://github.com/logseq/logseq/blob/master/templates/config.edn) for documentation on all config options.
+	- See the [config.edn template](https://github.com/logseq/logseq/blob/master/src/resources/templates/config.edn) for documentation on all config options.
 	- See [[Basic settings]] for config options that have a UI.
 	- This file can be edited outside Logseq and the effects will take place in a few seconds.
 	- Config options are validated when a user saves the file. Errors are displayed for invalid config options.
@@ -39,8 +39,8 @@ description:: Local config file, `logseq/config.edn`, is the main configuration
 			   :query/result-transforms
 			   {:sort-by-priority
 			    (fn [result] (sort-by (fn [h] (get h :block/priority "Z")) result))}
-			  
+
 			  ;; In an advanced query
 			  {:query ...
 			   :result-transform :sort-by-priority}
-			  ```
\ No newline at end of file
+			  ```

From 35b7b82fd6711c0188d076328241c775d25608e4 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 30 May 2023 10:50:25 -0400
Subject: [PATCH 025/196] Fix indent from previous commit

---
 pages/Logseq Protocol.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/pages/Logseq Protocol.md b/pages/Logseq Protocol.md
index e630c96..ce8dd01 100644
--- a/pages/Logseq Protocol.md	
+++ b/pages/Logseq Protocol.md	
@@ -20,12 +20,12 @@
 			- `page`:    (optional) Page name to insert to, use "TODAY" to insert to today page
 		- Settings (in `config.edn`):
 			- `{time}`: capture time
-				- `{date}`: capture date using current date format, use `[[{date}]]` to get a page reference
-				- `{text}`: text that users selected before sharing.
-				- `{url}`: URL or assets path for media files stored in Logseq.
-				- #+BEGIN_TIP
-				  Use `[[{date}]]` for a reference to today's journal page
-				  #+END_TIP
+			- `{date}`: capture date using current date format, use `[[{date}]]` to get a page reference
+			- `{text}`: text that users selected before sharing.
+			- `{url}`: URL or assets path for media files stored in Logseq.
+			- #+BEGIN_TIP
+			  Use `[[{date}]]` for a reference to today's journal page
+			  #+END_TIP
 			- ```edn
 			  :quick-capture-templates
 			  {:text "[[quick capture]] **{time}**: {text} from {url}"

From 3bd1b58326b64b729ad409246ad0ac6d31c17833 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 1 Jun 2023 10:13:40 -0400
Subject: [PATCH 026/196] Mention table props in built-in

---
 pages/Built-in Properties.md | 1 +
 pages/Tables.md              | 1 +
 2 files changed, 2 insertions(+)

diff --git a/pages/Built-in Properties.md b/pages/Built-in Properties.md
index 909f062..d886b52 100644
--- a/pages/Built-in Properties.md	
+++ b/pages/Built-in Properties.md	
@@ -13,6 +13,7 @@ description:: There are built-in in properties that control Logseq functionality
 	- `filters` (N) (page) - store selected filters for linked references on page-level. object with booleans
 	- `public` (1) (page) - defines whether a page should be included in an export. boolean
 	- `exclude-from-graph-view` (1) (page) - defines whether a page should be excluded in global graph view. boolean
+	- See ((646c1b4d-9cf2-4c8c-bb05-7f336e027ea1)) for table related properties
 - Hidden properties
 	- `collapsed` (1) (block) - specifies whether a block is collapsed.
 	- `id` (1) (block) - specifies a block id.
diff --git a/pages/Tables.md b/pages/Tables.md
index 60471e8..e78b54d 100644
--- a/pages/Tables.md
+++ b/pages/Tables.md
@@ -6,6 +6,7 @@ description:: Tables are our first versioned component, accepting props to contr
 	- A second version is currently in beta testing, and can be activated by giving a markdown table or query element the prop: `logseq.table.version:: 2`
 - ## Functionality
 	- ### Props
+	  id:: 646c1b4d-9cf2-4c8c-bb05-7f336e027ea1
 		- Logseq tables now render differently depending on the block-level props. The default values for these props can also be set in your `config.edn` as top level keys.
 		- #### logseq.table.version
 			- The `logseq.table.version` prop determines the version of the table. It can take one of two possible values:

From 908889c580d74bafd91b7c8183394e75b14c50cb Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 1 Jun 2023 10:14:59 -0400
Subject: [PATCH 027/196] Update status of action

---
 pages/Publishing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Publishing.md b/pages/Publishing.md
index 767066e..34193f4 100644
--- a/pages/Publishing.md
+++ b/pages/Publishing.md
@@ -56,5 +56,5 @@ description:: This feature publishes a graph as a [[Publish Web]], single page a
 		- See [routes.cljs](https://github.com/logseq/logseq/blob/master/src/main/frontend/routes.cljs) for other possible routes.
 - ## Additional Links
 	- https://github.com/logseq/publish-spa - Github action and CLI to publish a graph as a SPA
-	- https://github.com/pengx17/logseq-publish - Popular github action to publish a graph as a SPA
+	- https://github.com/pengx17/logseq-publish - Archived and previously popular github action to publish a graph as a SPA
 	- https://github.com/sawhney17/logseq-schrodinger - Plugin to export Logseq pages to Hugo
\ No newline at end of file

From ccdbd54329f74ca100a95aa83c4b40ad650bed37 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 2 Jun 2023 10:38:22 -0400
Subject: [PATCH 028/196] Move and expand on query table function feature

---
 pages/Changelog_07_09.md        | 34 ---------------------------------
 pages/Query table___function.md | 32 ++++++++++++++++++++++++++++++-
 2 files changed, 31 insertions(+), 35 deletions(-)

diff --git a/pages/Changelog_07_09.md b/pages/Changelog_07_09.md
index e1ac9ed..f6b63d6 100644
--- a/pages/Changelog_07_09.md
+++ b/pages/Changelog_07_09.md
@@ -551,40 +551,6 @@
 		- Block timestamps in the code block
 	- [[Features]]
 		- [[Query table/function]]
-			- How to create a function below the query table? #card
-			  card-last-interval:: 11.2
-			  card-repeats:: 3
-			  card-ease-factor:: 2.8
-			  card-next-schedule:: 2021-10-22T16:19:30.719Z
-			  card-last-reviewed:: 2021-10-11T12:19:30.719Z
-			  card-last-score:: 5
-				- Firstly, you have a query like this:
-				  query-table:: true
-				  query-properties:: [:block :author :publication-date :price :qty :updated-at]
-				  {{query (property type book)}}
-				  Then, you can create functions (by trigger `/function`) as this query block's children.
-				  
-				  For example:
-					- How many books? `{{function (sum :qty)}}`
-						- Answer: {{function (sum :qty)}}
-					- What's the average price? `{{function (average :price)}}`
-						- Answer: {{function (average :price)}}
-					- How much does it cost to buy all of them? `{{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}`
-						- Answer: {{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}
-			- What features does it support?
-				- #+BEGIN_NOTE
-				  The property to be used in the function must be a keyword, a keyword has a `:` at the beginning.
-				  For example, `:price` is a keyword while `price` is not.
-				  #+END_NOTE
-				- Aggregations including sum/average/min/max/total
-					- `{{function (sum :property)}}`
-					- `{{function (average :property)}}`
-					- `{{function (min :property)}}`
-					- `{{function (max :property)}}`
-					- `{{function (total :property)}}`
-				- [[Clojure]] function!
-				  The function takes the query result and bind it to the symbol `result` for usage.
-					- `{{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}`
 	- [[Enhancement]]
 		- [[Query table]]
 			- Click to open a block in the right sidebar
diff --git a/pages/Query table___function.md b/pages/Query table___function.md
index c06ef6f..4f46674 100644
--- a/pages/Query table___function.md	
+++ b/pages/Query table___function.md	
@@ -1,3 +1,33 @@
 title:: Query table/function
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+description:: This runs custom transformations on a query table's results, usually to calculate aggregations
+initial-version:: 0.2.6
 
--
\ No newline at end of file
+## Usage
+	- First, create a query table like this:
+	  query-table:: true
+	  {{query (property type book)}}
+	  Then, create functions by typing `/function` in a child block under the query table.
+	  
+	  For example:
+		- How many books? `{{function (sum :qty)}}`
+			- Answer: {{function (sum :qty)}}
+		- What's the average price? `{{function (average :price)}}`
+			- Answer: {{function (average :price)}}
+		- How much does it cost to buy all of them? `{{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}`
+			- Answer: {{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}
+## Functionality
+	- This macro works with results of simple [[Queries]] or [[Advanced Queries]].
+	- This macro supports the following aggregate functions:
+		- `{{function (sum :property)}}`
+		- `{{function (average :property)}}`
+		- `{{function (min :property)}}`
+		- `{{function (max :property)}}`
+		- `{{function (count :property)}}`
+		- #+BEGIN_NOTE
+		  The property to be used in the function must be a keyword, a keyword has a `:` at the beginning.
+		  For example, `:price` is a keyword while `price` is not.
+		  #+END_NOTE
+		- An argument can also be a custom [[Clojure]] function like :result-transform in [[Advanced Queries]]. The custom function binds the query result to the symbol `result`. For example:
+			- `{{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}`
\ No newline at end of file

From 3bcd3f502953a2c13af21dada3f62d716bd5dbf2 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 2 Jun 2023 11:39:21 -0400
Subject: [PATCH 029/196] Update query table to mention icons in upper right

---
 pages/Query table.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/pages/Query table.md b/pages/Query table.md
index 98dac25..7b663c8 100644
--- a/pages/Query table.md	
+++ b/pages/Query table.md	
@@ -3,6 +3,9 @@ type:: [[UI Element]]
 description:: Table that displays results from [[Queries]] or [[Advanced Queries]]
 
 - ## Functionality
+	- In the upper right, there is a gear icon to select which columns are visible.
+	- To the left of the gear icon, is an icon to toggle a view of results from table view to list view, blocks grouped by page.
+	  *Note*: This icon is only visible for block queries as page queries can't have a list view.
 	- Results are sorted by clicking on a column header. Clicking on the column header to reverse the sort direction. Sort state is saved to the file.
 		- **Note**: Sorting can be also be done in a query with the `sort-by` filter or with a result-transform. Sorting in a table takes precedence over sorting in a query.
 	- To enable date sorting on values like `Aug 12th, 2022`, add the property and value `:logseq.query/nlp-date:: true` to the query block
\ No newline at end of file

From 607433d1db899935b3ca3ef0446b10a2dcbc4693 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 2 Jun 2023 21:08:33 -0400
Subject: [PATCH 030/196] Update classes to meet graph-validator validity

All classes have a have url, parent and are capitalized.
Classes that don't map to an external url just use themselves as the url
---
 .graph-validator/config.edn  | 2 +-
 logseq/config.edn            | 3 ++-
 logseq/custom.css            | 3 +++
 pages/Command.md             | 2 ++
 pages/Feature.md             | 2 ++
 pages/FeatureTag.md          | 2 ++
 pages/Platform.md            | 2 ++
 pages/Thing.md               | 3 +++
 pages/UI Element.md          | 2 ++
 pages/Whiteboard___Object.md | 4 +++-
 pages/Whiteboard___Tool.md   | 2 ++
 pages/parent.md              | 3 +++
 12 files changed, 27 insertions(+), 3 deletions(-)
 create mode 100644 pages/Thing.md
 create mode 100644 pages/parent.md

diff --git a/.graph-validator/config.edn b/.graph-validator/config.edn
index 4fe9e31..4716b1a 100644
--- a/.graph-validator/config.edn
+++ b/.graph-validator/config.edn
@@ -1,2 +1,2 @@
 {:exclude [tags-and-page-refs-have-pages]
- :add-namespaces [schema]}
+ :add-namespaces [logseq.graph-validator.validations.class schema]}
diff --git a/logseq/config.edn b/logseq/config.edn
index 9790883..949cc93 100644
--- a/logseq/config.edn
+++ b/logseq/config.edn
@@ -37,7 +37,8 @@
  ;; becomes
  ;; Rose is red, violet's blue. Life's ordered: Org assists you.
  :macros
- {"query-done" "{{query (and (task done) $1)}}"
+ {"docs-base-url" "https://docs.logseq.com/#/page/$1"
+  "query-done" "{{query (and (task done) $1)}}"
   "mark" "[:mark \"$1\"]"}
  :feature/enable-block-time? true
  :feature/enable-timetracking? true
diff --git a/logseq/custom.css b/logseq/custom.css
index e69de29..f5e20b5 100644
--- a/logseq/custom.css
+++ b/logseq/custom.css
@@ -0,0 +1,3 @@
+.page-property-value .macro {
+  display: inline-flex;
+}
diff --git a/pages/Command.md b/pages/Command.md
index ab87f40..8907334 100644
--- a/pages/Command.md
+++ b/pages/Command.md
@@ -1,2 +1,4 @@
 type:: [[Class]]
+parent:: [[Feature]]
 description:: A command invoked from `/`. All commands work on [[All Platforms]] except [[Publish Web]]
+url:: {{docs-base-url Command}}
diff --git a/pages/Feature.md b/pages/Feature.md
index 97e26c2..4173770 100644
--- a/pages/Feature.md
+++ b/pages/Feature.md
@@ -1,5 +1,7 @@
 type:: [[Class]]
+parent:: [[Thing]]
 description:: A user-facing piece of functionality. This can be a small piece or it can be a big one that consists of subfeatures
+url:: {{docs-base-url Feature}}
 
 - ## Conventions
 	- A feature page has the following properties
diff --git a/pages/FeatureTag.md b/pages/FeatureTag.md
index f07c8f3..6f31e4b 100644
--- a/pages/FeatureTag.md
+++ b/pages/FeatureTag.md
@@ -1,2 +1,4 @@
 type:: [[Class]]
+parent:: [[Thing]]
 description:: Tags to categorize features
+url:: {{docs-base-url FeatureTag}}
diff --git a/pages/Platform.md b/pages/Platform.md
index 195a368..f142503 100644
--- a/pages/Platform.md
+++ b/pages/Platform.md
@@ -1,2 +1,4 @@
 type:: [[Class]]
+parent:: [[Thing]]
 description:: One or more platforms, usually for a feature
+url:: {{docs-base-url Platform}}
diff --git a/pages/Thing.md b/pages/Thing.md
new file mode 100644
index 0000000..d4d243b
--- /dev/null
+++ b/pages/Thing.md
@@ -0,0 +1,3 @@
+type:: [[Class]]
+url:: https://schema.org/Thing
+desc:: The simplest concept which all classes inherit from.
diff --git a/pages/UI Element.md b/pages/UI Element.md
index f1aaecb..71e4732 100644
--- a/pages/UI Element.md	
+++ b/pages/UI Element.md	
@@ -1,2 +1,4 @@
 type:: [[Class]]
+parent:: [[Thing]]
 description:: A well-defined piece of the UI that usually has a name
+url:: {{docs-base-url UI%20Element}}
diff --git a/pages/Whiteboard___Object.md b/pages/Whiteboard___Object.md
index 95a1adb..6b06d76 100644
--- a/pages/Whiteboard___Object.md
+++ b/pages/Whiteboard___Object.md
@@ -1,6 +1,8 @@
 alias:: Whiteboard objects, Whiteboard object
 type:: [[Class]]
+parent:: [[UI Element]]
 description:: An element that can be placed on the [[Whiteboard/Canvas]]. Just like [[Blocks]] or [[Pages]], objects can be referenced anywhere in your [[Graph]]
+url:: {{docs-base-url Whiteboard%2FObject}}
 
 - produced by:
 	- select the object of your choice from the [[Toolbar]] and draw it on the [[Whiteboard/Canvas]]
@@ -73,4 +75,4 @@ description:: An element that can be placed on the [[Whiteboard/Canvas]]. Just l
 				- [[Url input]]
 				- [[Open embedded url]]
 				- [[Link]]
--
\ No newline at end of file
+-
diff --git a/pages/Whiteboard___Tool.md b/pages/Whiteboard___Tool.md
index ae3eae5..3dbcc21 100644
--- a/pages/Whiteboard___Tool.md
+++ b/pages/Whiteboard___Tool.md
@@ -1,3 +1,5 @@
 alias:: Whiteboard tool, Tool, Tools
 type:: [[Class]]
+parent:: [[Feature]]
 description:: Tools on the [[Whiteboard/Toolbar]]
+url:: {{docs-base-url Whiteboard%2FTool}}
diff --git a/pages/parent.md b/pages/parent.md
new file mode 100644
index 0000000..850f6f0
--- /dev/null
+++ b/pages/parent.md
@@ -0,0 +1,3 @@
+type:: [[Property]]
+url:: https://www.w3.org/2000/01/rdf-schema#subClassOf
+description:: Used to connect a class with its parent class

From 5ebf63da9f394ef3ed59d388bcc0ab5159606304 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 2 Jun 2023 22:11:52 -0400
Subject: [PATCH 031/196] Add class hierarchy task

---
 bb.edn         | 10 ++++++++++
 script/nbb.edn |  8 ++++++--
 2 files changed, 16 insertions(+), 2 deletions(-)

diff --git a/bb.edn b/bb.edn
index bd2ac3f..0e4ccac 100644
--- a/bb.edn
+++ b/bb.edn
@@ -23,5 +23,15 @@
                  (pr-str (into [".."] *command-line-args*))
                  ")"))}
 
+  write-class-hierarchy
+  {:doc "Run logseq-class-hierarchy as a lib"
+   :depends [-ensure-latest-cached-db]
+   :task (shell {:dir "script"} "yarn -s nbb-logseq -e"
+                (str
+                 "(require '[cldwalker.logseq-clis.cli.logseq-class-hierarchy :as lch])"
+                 "(apply lch/-main "
+                 (pr-str ["../pages/Class Hierarchy.md" "-d" ".."])
+                 ")"))}
+
   -ensure-latest-cached-db
   logseq.bb-tasks.nbb.cached-db/ensure-latest-cached-db}}
diff --git a/script/nbb.edn b/script/nbb.edn
index 6d6410d..8b4af40 100644
--- a/script/nbb.edn
+++ b/script/nbb.edn
@@ -1,17 +1,21 @@
 {:deps
  {logseq/graph-parser
   {:git/url "https://github.com/logseq/logseq"
-   :git/sha "090d25b5e845e98ec2f003279f91ff34e4393cc6"
+   :git/sha "82cf4d3c65acbf230a3170640fe271dd74095067"
+   :git/tag "0.9.8"
    :deps/root "deps/graph-parser"}
   #_{:local/root "../../logseq/deps/graph-parser"}
 
+  io.github.cldwalker/logseq-clis
+  {:git/sha "8c5e56a03083ecc1ad11310d1ce9dc70428315ea"}
+
   logseq/bb-tasks
   #_{:local/root "../../bb-tasks"}
   {:git/url "https://github.com/logseq/bb-tasks"
    :git/sha "4295d5df0458cc06a09c5d506510ee49b785407d"}
 
   logseq/rdf-export
-  #_{:local/root "../../../../../rdf-export"}
+  #_{:local/root "../../rdf-export"}
   {:git/url "https://github.com/logseq/rdf-export"
    :git/sha "3fcbb952469800d766ae5b51af131c3528b928c0"}
 

From 46d78c390657a31fb174613869705bf6f665446a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 6 Jun 2023 10:20:49 -0400
Subject: [PATCH 032/196] Rename feature to reflect that this works generally
 with queries

---
 pages/Changelog_07_09.md                               |  2 +-
 pages/{Query table___function.md => Query function.md} | 10 +++++-----
 2 files changed, 6 insertions(+), 6 deletions(-)
 rename pages/{Query table___function.md => Query function.md} (85%)

diff --git a/pages/Changelog_07_09.md b/pages/Changelog_07_09.md
index f6b63d6..bdcdff9 100644
--- a/pages/Changelog_07_09.md
+++ b/pages/Changelog_07_09.md
@@ -550,7 +550,7 @@
 		- Autocomplete shortcut config
 		- Block timestamps in the code block
 	- [[Features]]
-		- [[Query table/function]]
+		- [[Query function]]
 	- [[Enhancement]]
 		- [[Query table]]
 			- Click to open a block in the right sidebar
diff --git a/pages/Query table___function.md b/pages/Query function.md
similarity index 85%
rename from pages/Query table___function.md
rename to pages/Query function.md
index 4f46674..7ade6cc 100644
--- a/pages/Query table___function.md	
+++ b/pages/Query function.md	
@@ -1,14 +1,14 @@
-title:: Query table/function
+title:: Query function
 type:: [[Feature]]
 platforms:: [[All Platforms]]
-description:: This runs custom transformations on a query table's results, usually to calculate aggregations
+description:: This runs custom transformations on a query's results, usually to calculate aggregations
 initial-version:: 0.2.6
 
 ## Usage
-	- First, create a query table like this:
+	- First, build a query like this:
 	  query-table:: true
 	  {{query (property type book)}}
-	  Then, create functions by typing `/function` in a child block under the query table.
+	  Then, create functions by typing `/function` in a child block under the query's results.
 	  
 	  For example:
 		- How many books? `{{function (sum :qty)}}`
@@ -18,7 +18,7 @@ initial-version:: 0.2.6
 		- How much does it cost to buy all of them? `{{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}`
 			- Answer: {{function (sum (map (fn [x] (* (:price x) (:qty x))) result))}}
 ## Functionality
-	- This macro works with results of simple [[Queries]] or [[Advanced Queries]].
+	- This macro works with results of simple [[Queries]] or [[Advanced Queries]], in both table and list views.
 	- This macro supports the following aggregate functions:
 		- `{{function (sum :property)}}`
 		- `{{function (average :property)}}`

From 7d95fb28a8133c3f7e42ffee37ab78cf43715492 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 9 Jun 2023 16:10:55 -0400
Subject: [PATCH 033/196] Remove misleading default and make configuration
 section linkable

---
 pages/Publishing.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/pages/Publishing.md b/pages/Publishing.md
index 34193f4..1c0708f 100644
--- a/pages/Publishing.md
+++ b/pages/Publishing.md
@@ -5,13 +5,14 @@ description:: This feature publishes a graph as a [[Publish Web]], single page a
 - ## Usage
 	- [[Publishing (Desktop App Only)]] is a tutorial to publish your first graph.
 	- An alternative to publishing from the menu is running the command `Export public graph pages as html`.
-	- This export can be configured at both graph and page levels:
-		- ### Graph-Level Configuration
+	- ### Configuration
+		- This export can be configured at both graph and page levels.
+		- #### Graph-Level Configuration
 			- #### [[Settings]] Menu
-				- Under the *Editor* tab in the [[Settings]] menu, you will find the option "*Set pages to public by default*". When this setting is enabled (default), all pages within the graph will be considered public and included in the export unless the page's `public` property is explicitly set to `false`.
+				- Under the *Editor* tab in the [[Settings]] menu, you will find the option "*Set pages to public by default*". When this setting is enabled, all pages within the graph will be considered public and included in the export unless the page's `public` property is explicitly set to `false`.
 				- If this setting is disabled,  all pages will be private and not included in the export unless the page's `public` property is explicitly set to `true`.
 				- This setting corresponds to the `:publishing/all-pages-public?` option in the [[config.edn]] file.
-		- ### Page-Level Configuration
+		- #### Page-Level Configuration
 			- #### Public Page Property
 				- The `public` page property is a boolean attribute that can be set for individual pages to determine their inclusion in an export. It overrides the default setting in the [[Settings]] menu. For example, if a page's `public` property is set to `true`, it will be included in the export even if the "*Set pages to public by default*" setting is disabled.
 		- The interplay between the graph-level configuration and page-level properties can significantly affect the outcome of your export process. Therefore, reviewing these settings before performing an export is crucial to ensure they align with your specific needs.

From a0618f58fac0727482c6810417051636a66c6080 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 12 Jun 2023 17:02:57 -0400
Subject: [PATCH 034/196] Add graph overview page with first section
 auto-generated by script

---
 pages/Graph Overview.md | 66 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 66 insertions(+)
 create mode 100644 pages/Graph Overview.md

diff --git a/pages/Graph Overview.md b/pages/Graph Overview.md
new file mode 100644
index 0000000..5dc907d
--- /dev/null
+++ b/pages/Graph Overview.md	
@@ -0,0 +1,66 @@
+- #+BEGIN_NOTE
+  This page describes how this graph and its pages are organized. This is meant to be read by those looking for ways to manage their graph and does not serve as a guide for first time users.
+  #+END_NOTE
+- ## Class Hierarchy
+  *Note:* This section shows how classes or types of pages are related to each other. A class groups pages that share a common set of properties. `Thing` is the root class from which all other classes are defined. When a class is a child of another class, it usually inherits using the same properties as its parent class.
+	- [[Thing]]
+		- [[FeatureTag]]
+		- [[Feature]]
+			- [[Command]]
+			- [[Whiteboard/Tool]]
+		- [[Platform]]
+		- [[UI Element]]
+			- [[Whiteboard/Object]]
+- ## Pages by Class
+  *Note:* This section shows the types of pages or "things" that are available in this graph. Click on a class page and look under its pages query to see its corresponding pages. For example, expand `Feature pages` query to reveal the 50+ feature pages.
+	- [[Thing]]
+		- [[FeatureTag]]
+		  collapsed:: true
+			- query-table:: true
+			  collapsed:: true
+			  #+BEGIN_QUERY
+			  {:query (page-property :type [[FeatureTag]])
+			  :title "FeatureTag pages"}
+			  #+END_QUERY
+		- [[Feature]]
+			- query-table:: true
+			  query-properties:: [:page :type :platforms :description :initial-version :tags]
+			  collapsed:: true
+			  #+BEGIN_QUERY
+			  {:query (page-property :type [[Feature]])
+			  :title "Feature pages"}
+			  #+END_QUERY
+			- [[Command]]
+			  collapsed:: true
+				- collapsed:: true
+				  #+BEGIN_QUERY
+				  {:query (page-property :type [[Command]])
+				  :title "Command pages"}
+				  #+END_QUERY
+			- [[Whiteboard/Tool]]
+			  collapsed:: true
+				- collapsed:: true
+				  #+BEGIN_QUERY
+				  {:query (page-property :type [[Tool]] )
+				  :title "Whiteboard/Tool pages"}
+				  #+END_QUERY
+		- [[Platform]]
+		  collapsed:: true
+			- collapsed:: true
+			  #+BEGIN_QUERY
+			  {:query (page-property :type [[Platform]] )
+			  :title "Platform pages"}
+			  #+END_QUERY
+		- [[UI Element]]
+			- collapsed:: true
+			  #+BEGIN_QUERY
+			  {:query (page-property :type [[UI Element]] )
+			  :title "UI Element pages"}
+			  #+END_QUERY
+			- [[Whiteboard/Object]]
+			  collapsed:: true
+				- collapsed:: true
+				  #+BEGIN_QUERY
+				  {:query (page-property :type [[Whiteboard/Object]] )
+				  :title "Whiteboard/Object pages"}
+				  #+END_QUERY
\ No newline at end of file

From 6f3cbb714f3cef41c167c269f72705e163dc9631 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 13 Jun 2023 18:51:24 +0800
Subject: [PATCH 035/196] chore: release 0.9.9

---
 pages/Changelog.md | 67 ++++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 65 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 91248f8..fa8d994 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,6 +1,69 @@
+- ## Beta 0.9.9 [[Jun 13th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.9>
+	- [[Features]]
+		- Integrated title bar for Windows and Linux [#9442](https://github.com/logseq/logseq/pull/9442). (Now "Developer Tools" is under the `Ctrl+Shift+I` hotkey on Windows and Linux.)
+	- [[Thanks]]
+		- [[Bad3r]]
+			- remove false positive translations a.k.a. EN definitions in non EN dicts [#9576](https://github.com/logseq/logseq/pull/9576)
+			- Enhancements for E2E test: Log and ignore net errors [#9559](https://github.com/logseq/logseq/pull/9559); editor string formatting and symbols auto-pairing tests [#9388](https://github.com/logseq/logseq/pull/9388)
+			- Fix space in overflow menu [#9521](https://github.com/logseq/logseq/pull/9521)
+			- Add tooltip hint for `prefered-file-paste` setting [#9564](https://github.com/logseq/logseq/pull/9564)
+			- Do not print `nil` in quick capture [#9617](https://github.com/logseq/logseq/pull/9617)
+		- [[Bryan Lee]]
+			- Fix: shift-clicking on "Pages tagged with" page link doesn't open in sidebar [#9587](https://github.com/logseq/logseq/pull/9587)
+		- [[Giuseppe D'Andrea]]
+			- Enhancement for editor: delete selected text when pressing enter key [#9448](https://github.com/logseq/logseq/pull/9448)
+		- [[Ulices]]
+			- Update Spanish translation [#9540](https://github.com/logseq/logseq/pull/9540)
+		- [[ingepettersen]]
+			- Update Norwegian translation [#9618](https://github.com/logseq/logseq/pull/9618)
+		- [[Mikhail Smelov]]
+			- Update Russian translation [#9605](https://github.com/logseq/logseq/pull/9605)
+		- [[David Laing]]
+			- Update dugit #9579
+		- [[necropolina]]
+			- Menu item for toggling theme mode in published graphs [#9528](https://github.com/logseq/logseq/pull/9528)
+		- [[John Doe]]
+			- Improve I18n translations: Convert hardcoded strings in the UI to be translatable in [#9588](https://github.com/logseq/logseq/pull/9588), improve RU translation in [#9465](https://github.com/logseq/logseq/pull/9465), Improve UK (Ukrainian) translation in [#9494](https://github.com/logseq/logseq/pull/9494)
+		- [[situ2001]]
+			- Fix page search is not updated after changing the capitalization of the page name [#9583](https://github.com/logseq/logseq/pull/9583)
+			- Handle backspace when cursor is at beginning of line in embedded page/block [#8421](https://github.com/logseq/logseq/pull/8421)
+		- [[Steven Allen]]
+			- Substitute `date`/`text` in mobile quick-capture templates [#9529](https://github.com/logseq/logseq/pull/9529)
+	- [[Fixed issues]]
+		- Whiteboard:
+			- New page or whiteboard named with capital letter crashes app on rename [#9604](https://github.com/logseq/logseq/pull/9604)
+			- Arrow positions on initialization, undo group delete, hover links jumping and other issues [#9480](https://github.com/logseq/logseq/pull/9480)
+			- Exporting from context menu [#9596](https://github.com/logseq/logseq/pull/9596)
+			- Onboarding triggered on existing whiteboard [#9543](https://github.com/logseq/logseq/pull/9543)
+		- Aliased pages not included in published subgraph [#9600](https://github.com/logseq/logseq/pull/9600)
+		- Fix for quick-capture: Do not print `nil` in quick capture [#9617](https://github.com/logseq/logseq/pull/9617); Substitute `date`/`text` in mobile quick-capture templates [#9529](https://github.com/logseq/logseq/pull/9529)
+		- Page renaming issues [#9620](https://github.com/logseq/logseq/pull/9620)
+		- Page search is not updated after changing the capitalization of the page name [#9583](https://github.com/logseq/logseq/pull/9583)
+		- Pasted special URLs on selected text don't get wrapped with macros [#9607](https://github.com/logseq/logseq/pull/9607)
+		- Query functions not working sometimes [#9563](https://github.com/logseq/logseq/pull/9563)
+		- Remove deprecated `:editor/command-trigger` option [#9550](https://github.com/logseq/logseq/pull/9550)
+		- Resizing of pdf area highlight [#9483](https://github.com/logseq/logseq/pull/9483)
+		- Shift clicking on "Pages tagged with" page link doesn't open in sidebar [#9587](https://github.com/logseq/logseq/pull/9587)
+		- Table v2 and view properties not hidden on display [#9499](https://github.com/logseq/logseq/pull/9499)
+		- Handle backspace when at beginning of line in embed page/block [#8421](https://github.com/logseq/logseq/pull/8421)
+		- iOS watcher path handling for file events [#9589](https://github.com/logseq/logseq/pull/9589)
+		- Missing `:block/properties-order` attribute for the custom query blocks [#9525](https://github.com/logseq/logseq/pull/9525)
+		- Drag and drop assets not working for the right sidebar [#9496](https://github.com/logseq/logseq/pull/9496)
+	- [[Enhancement]]
+		- Whiteboards
+			- Add support for translations [#9567](https://github.com/logseq/logseq/pull/9567)
+			- Auto pan triggers earlier and works for more platforms [#9573](https://github.com/logseq/logseq/pull/9573)
+		- Add tooltip hint for prefered-file-paste setting [#9564](https://github.com/logseq/logseq/pull/9564)
+		- Convert more hardcoded strings in the UI to be translatable [#9588](https://github.com/logseq/logseq/pull/9588)
+		- I18n Updates: Ukrainian [#9494](https://github.com/logseq/logseq/pull/9494), Russian [#9465](https://github.com/logseq/logseq/pull/9465) [#9605](https://github.com/logseq/logseq/pull/9605), Spanish [#9540](https://github.com/logseq/logseq/pull/9540), Norwegian [#9618](https://github.com/logseq/logseq/pull/9618)
+		- Menu item for toggling theme mode in published graphs [#9528](https://github.com/logseq/logseq/pull/9528)
+		- Delete selected text when pressing enter [#9448](https://github.com/logseq/logseq/pull/9448)
+		- Add more semantic classes to the order-list block element [#9519](https://github.com/logseq/logseq/pull/9519)
+		- Added keymap manager for plugins [#9430](https://github.com/logseq/logseq/pull/9430)
 - ## Beta 0.9.8 [[May 24th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>.
-
+  
   **NOTE**: The previous 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
@@ -2196,4 +2259,4 @@
 		- Many UX enhancements
 - [[Changelog_07_09]]
 - [[Changelog_06]]
-- [[Changelog 2020]]
+- [[Changelog 2020]]
\ No newline at end of file

From b979c6c0c19107a64e6b19176555a9208603df34 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 13 Jun 2023 09:51:29 -0400
Subject: [PATCH 036/196] Mention doc in changelog and bump to version that has
 query fn fix

---
 .github/workflows/gh-pages.yml | 2 +-
 pages/Changelog.md             | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index 61a4031..a3e0cd7 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -17,7 +17,7 @@ jobs:
         uses: logseq/publish-spa@main
         with:
           output-directory: www
-          version: 0.9.8
+          version: 0.9.9
 
       - name: Add .nojekyll file
         run: touch www/.nojekyll
diff --git a/pages/Changelog.md b/pages/Changelog.md
index fa8d994..35d51fe 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -41,7 +41,7 @@
 		- Page renaming issues [#9620](https://github.com/logseq/logseq/pull/9620)
 		- Page search is not updated after changing the capitalization of the page name [#9583](https://github.com/logseq/logseq/pull/9583)
 		- Pasted special URLs on selected text don't get wrapped with macros [#9607](https://github.com/logseq/logseq/pull/9607)
-		- Query functions not working sometimes [#9563](https://github.com/logseq/logseq/pull/9563)
+		- Query functions not working sometimes [#9563](https://github.com/logseq/logseq/pull/9563) - [Documentation](https://docs.logseq.com/#/page/query%20function)
 		- Remove deprecated `:editor/command-trigger` option [#9550](https://github.com/logseq/logseq/pull/9550)
 		- Resizing of pdf area highlight [#9483](https://github.com/logseq/logseq/pull/9483)
 		- Shift clicking on "Pages tagged with" page link doesn't open in sidebar [#9587](https://github.com/logseq/logseq/pull/9587)
@@ -63,7 +63,7 @@
 		- Added keymap manager for plugins [#9430](https://github.com/logseq/logseq/pull/9430)
 - ## Beta 0.9.8 [[May 24th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>.
-  
+
   **NOTE**: The previous 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
@@ -2259,4 +2259,4 @@
 		- Many UX enhancements
 - [[Changelog_07_09]]
 - [[Changelog_06]]
-- [[Changelog 2020]]
\ No newline at end of file
+- [[Changelog 2020]]

From 88b9b2bef60688db42f253e964fc1c3a11987b1a Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 13 Jun 2023 22:36:37 +0800
Subject: [PATCH 037/196] enhance: tag changes

---
 pages/Breaking Changes.md | 3 +++
 pages/Changelog.md        | 8 ++++----
 pages/minor change.md     | 2 ++
 3 files changed, 9 insertions(+), 4 deletions(-)
 create mode 100644 pages/Breaking Changes.md
 create mode 100644 pages/minor change.md

diff --git a/pages/Breaking Changes.md b/pages/Breaking Changes.md
new file mode 100644
index 0000000..bac128a
--- /dev/null
+++ b/pages/Breaking Changes.md	
@@ -0,0 +1,3 @@
+alias:: breaking change
+
+-
\ No newline at end of file
diff --git a/pages/Changelog.md b/pages/Changelog.md
index 35d51fe..4c8b126 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,7 @@
 - ## Beta 0.9.9 [[Jun 13th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.9>
 	- [[Features]]
-		- Integrated title bar for Windows and Linux [#9442](https://github.com/logseq/logseq/pull/9442). (Now "Developer Tools" is under the `Ctrl+Shift+I` hotkey on Windows and Linux.)
+		- Integrated title bar for Windows and Linux [#9442](https://github.com/logseq/logseq/pull/9442). (Now "Developer Tools" is under the `Ctrl+Shift+I` hotkey on Windows and Linux.) #[[minor change]]
 	- [[Thanks]]
 		- [[Bad3r]]
 			- remove false positive translations a.k.a. EN definitions in non EN dicts [#9576](https://github.com/logseq/logseq/pull/9576)
@@ -42,7 +42,7 @@
 		- Page search is not updated after changing the capitalization of the page name [#9583](https://github.com/logseq/logseq/pull/9583)
 		- Pasted special URLs on selected text don't get wrapped with macros [#9607](https://github.com/logseq/logseq/pull/9607)
 		- Query functions not working sometimes [#9563](https://github.com/logseq/logseq/pull/9563) - [Documentation](https://docs.logseq.com/#/page/query%20function)
-		- Remove deprecated `:editor/command-trigger` option [#9550](https://github.com/logseq/logseq/pull/9550)
+		- Remove deprecated `:editor/command-trigger` option [#9550](https://github.com/logseq/logseq/pull/9550) #[[minor change]]
 		- Resizing of pdf area highlight [#9483](https://github.com/logseq/logseq/pull/9483)
 		- Shift clicking on "Pages tagged with" page link doesn't open in sidebar [#9587](https://github.com/logseq/logseq/pull/9587)
 		- Table v2 and view properties not hidden on display [#9499](https://github.com/logseq/logseq/pull/9499)
@@ -63,7 +63,7 @@
 		- Added keymap manager for plugins [#9430](https://github.com/logseq/logseq/pull/9430)
 - ## Beta 0.9.8 [[May 24th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.8>.
-
+  
   **NOTE**: The previous 0.9.7 version is revoked due to a fatal error caused by third-party library. [#9471](https://github.com/logseq/logseq/issues/9471). If you've upgraded to the broken 0.9.7 version, you might need to replace it with 0.9.8 manually(Download from the release page and install the app). Sorry for the inconvenience.
 	- [[BREAKING CHANGE]]
 		- Due to some compatibility issues, we dropped support for iOS 13
@@ -2259,4 +2259,4 @@
 		- Many UX enhancements
 - [[Changelog_07_09]]
 - [[Changelog_06]]
-- [[Changelog 2020]]
+- [[Changelog 2020]]
\ No newline at end of file
diff --git a/pages/minor change.md b/pages/minor change.md
new file mode 100644
index 0000000..5c6b36d
--- /dev/null
+++ b/pages/minor change.md	
@@ -0,0 +1,2 @@
+- > Minor changes are modifications made to a product that do not significantly affect its functionality or user experience. These changes can include simple edits to the user interface, such as adjusting button size or fixing typos, as well as bug fixes that don't impact overall performance. Minor changes can be implemented quickly without disrupting the product or service.
+-
\ No newline at end of file

From db6ee7d95ec9d724d787dd36049f8e06a4745b43 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 13 Jun 2023 11:24:31 -0400
Subject: [PATCH 038/196] Tweak description of minor change to reflect current
 usage

---
 pages/minor change.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/pages/minor change.md b/pages/minor change.md
index 5c6b36d..27bfbf3 100644
--- a/pages/minor change.md	
+++ b/pages/minor change.md	
@@ -1,2 +1 @@
-- > Minor changes are modifications made to a product that do not significantly affect its functionality or user experience. These changes can include simple edits to the user interface, such as adjusting button size or fixing typos, as well as bug fixes that don't impact overall performance. Minor changes can be implemented quickly without disrupting the product or service.
--
\ No newline at end of file
+- > Minor changes are modifications made to a product that do not significantly affect its functionality or user experience. These changes can be minor changes in a way a feature or user interface behaves.

From 912e924bb91209f880fbab14db201f83377f5eeb Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 13 Jun 2023 16:24:34 -0400
Subject: [PATCH 039/196] Update class and property modeling

Update graph overview to reflect the changes
---
 .rdf-export/config.edn  |  3 ++-
 pages/Class.md          |  5 ++++-
 pages/Graph Overview.md | 15 +++++++++++++++
 pages/Property.md       |  5 ++++-
 pages/Thing.md          |  2 +-
 pages/sameAs.md         |  3 +++
 6 files changed, 29 insertions(+), 4 deletions(-)
 create mode 100644 pages/sameAs.md

diff --git a/.rdf-export/config.edn b/.rdf-export/config.edn
index 630d77a..6e36121 100644
--- a/.rdf-export/config.edn
+++ b/.rdf-export/config.edn
@@ -1,2 +1,3 @@
 {:base-url "https://docs.logseq.com/#/page/"
- :prefixes {:d "https://docs.logseq.com/#/page/"}}
+ :prefixes {:d "https://docs.logseq.com/#/page/"}
+ :expand-macros true}
diff --git a/pages/Class.md b/pages/Class.md
index 557cee6..22f65b7 100644
--- a/pages/Class.md
+++ b/pages/Class.md
@@ -1,2 +1,5 @@
-type:: https://schema.org/Class
+type:: [[Class]]
+parent:: [[Thing]]
 description:: Defines user defined classes/types in this graph
+url:: {{docs-base-url Class}}
+sameAs:: https://www.w3.org/2000/01/rdf-schema#Class
diff --git a/pages/Graph Overview.md b/pages/Graph Overview.md
index 5dc907d..3cc15e9 100644
--- a/pages/Graph Overview.md	
+++ b/pages/Graph Overview.md	
@@ -4,6 +4,7 @@
 - ## Class Hierarchy
   *Note:* This section shows how classes or types of pages are related to each other. A class groups pages that share a common set of properties. `Thing` is the root class from which all other classes are defined. When a class is a child of another class, it usually inherits using the same properties as its parent class.
 	- [[Thing]]
+		- [[Class]]
 		- [[FeatureTag]]
 		- [[Feature]]
 			- [[Command]]
@@ -14,6 +15,13 @@
 - ## Pages by Class
   *Note:* This section shows the types of pages or "things" that are available in this graph. Click on a class page and look under its pages query to see its corresponding pages. For example, expand `Feature pages` query to reveal the 50+ feature pages.
 	- [[Thing]]
+		- [[Class]]
+		  collapsed:: true
+			- collapsed:: true
+			  #+BEGIN_QUERY
+			  {:query (page-property :type [[Class]])
+			  :title "Class pages"}
+			  #+END_QUERY
 		- [[FeatureTag]]
 		  collapsed:: true
 			- query-table:: true
@@ -51,6 +59,13 @@
 			  {:query (page-property :type [[Platform]] )
 			  :title "Platform pages"}
 			  #+END_QUERY
+		- [[Property]]
+		  collapsed:: true
+			- collapsed:: true
+			  #+BEGIN_QUERY
+			  {:query (page-property :type [[Property]])
+			  :title "Property pages"}
+			  #+END_QUERY
 		- [[UI Element]]
 			- collapsed:: true
 			  #+BEGIN_QUERY
diff --git a/pages/Property.md b/pages/Property.md
index f2b1290..ba72dba 100644
--- a/pages/Property.md
+++ b/pages/Property.md
@@ -1,2 +1,5 @@
-type:: https://schema.org/Property
+type:: [[Class]]
+parent:: [[Thing]]
 description:: Defines user defined properties in this graph
+url:: {{docs-base-url Property}}
+sameAs:: https://www.w3.org/1999/02/22-rdf-syntax-ns#Property
diff --git a/pages/Thing.md b/pages/Thing.md
index d4d243b..3ef4e9e 100644
--- a/pages/Thing.md
+++ b/pages/Thing.md
@@ -1,3 +1,3 @@
 type:: [[Class]]
 url:: https://schema.org/Thing
-desc:: The simplest concept which all classes inherit from.
+description:: The simplest concept which all classes inherit from.
diff --git a/pages/sameAs.md b/pages/sameAs.md
new file mode 100644
index 0000000..f75b3ce
--- /dev/null
+++ b/pages/sameAs.md
@@ -0,0 +1,3 @@
+type:: [[Property]]
+url:: https://www.w3.org/2002/07/owl#sameAs
+description:: Indicates that two URIs are equivalent

From db514c220e9981482005d5eeaa079033efb50c56 Mon Sep 17 00:00:00 2001
From: Siferiax <118193398+Siferiax@users.noreply.github.com>
Date: Thu, 15 Jun 2023 20:50:27 +0200
Subject: [PATCH 040/196] Added extra heading to better explain property
 remove-block-children

---
 pages/Advanced Queries.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/pages/Advanced Queries.md b/pages/Advanced Queries.md
index 0fdbfe6..657e211 100644
--- a/pages/Advanced Queries.md	
+++ b/pages/Advanced Queries.md	
@@ -34,7 +34,7 @@ description:: Advanced queries are written with [Datalog](https://en.wikipedia.o
 	  | result-transform | fn or keyword |         | true     |
 	  | rules                | list of rules to apply to query | | true |
 	  |group-by-page? | groups results by page, only applies in list view | true | true|
-	  |remove-block-children? | removes all children/descendants under a block result, only applies to block queries,  | true | true |
+	  |remove-block-children? | removes duplicates from the query result, see below. Only applies to block queries.  | true | true |
 	- **Query Tips**
 	  updated-at:: 1609244703085
 	  created-at:: 1609244703085
@@ -44,6 +44,11 @@ description:: Advanced queries are written with [Datalog](https://en.wikipedia.o
 	  3. Most simple query operators are available as [rules](https://docs.datomic.com/on-prem/query/query.html#rules) in queries
 	  4. Titles can be be hiccups or double-quoted strings. For example, if you want to put custom macros into the query title, you can write something like `"{{poem foo,bar}}"`.
 	  #+END_TIP
+	- ### remove-block-children?
+		- When this setting is true, do not return child blocks separately when they are already shown as a sub-bullet of a parent block.
+		- When this setting is false, the parent block is returned including all its children as well as the child blocks individually when they also match the query criteria.
+			- This only applies when the property group-by-page? is set to false.
+		- Only applies to queries that return blocks.
 	- ### Query Inputs
 	  These are special values for a query's `:inputs` key above:
 		- #### Special page and block inputs

From c57d6c45d995d1d3cf91531345e156323c05af6e Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 16 Jun 2023 12:04:08 -0400
Subject: [PATCH 041/196] Tweak explanation of #103 to clarify query option and
 the reason behind it

---
 pages/Advanced Queries.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/pages/Advanced Queries.md b/pages/Advanced Queries.md
index 657e211..6c2f5b6 100644
--- a/pages/Advanced Queries.md	
+++ b/pages/Advanced Queries.md	
@@ -34,7 +34,7 @@ description:: Advanced queries are written with [Datalog](https://en.wikipedia.o
 	  | result-transform | fn or keyword |         | true     |
 	  | rules                | list of rules to apply to query | | true |
 	  |group-by-page? | groups results by page, only applies in list view | true | true|
-	  |remove-block-children? | removes duplicates from the query result, see below. Only applies to block queries.  | true | true |
+	  |remove-block-children? | Removes results that are children of a result, see below. Only applies to block queries.  | true | true |
 	- **Query Tips**
 	  updated-at:: 1609244703085
 	  created-at:: 1609244703085
@@ -44,11 +44,13 @@ description:: Advanced queries are written with [Datalog](https://en.wikipedia.o
 	  3. Most simple query operators are available as [rules](https://docs.datomic.com/on-prem/query/query.html#rules) in queries
 	  4. Titles can be be hiccups or double-quoted strings. For example, if you want to put custom macros into the query title, you can write something like `"{{poem foo,bar}}"`.
 	  #+END_TIP
-	- ### remove-block-children?
-		- When this setting is true, do not return child blocks separately when they are already shown as a sub-bullet of a parent block.
-		- When this setting is false, the parent block is returned including all its children as well as the child blocks individually when they also match the query criteria.
-			- This only applies when the property group-by-page? is set to false.
-		- Only applies to queries that return blocks.
+	- ### Query Options
+		- #### remove-block-children?
+			- When this option is true, do not return child blocks separately when they are already shown as a sub-bullet of a parent block.
+				- This is the default so that child results don't appear multiple times visually and confuse users.
+			- When this option is false, the parent block is returned including all its children as well as the child blocks individually when they also match the query criteria.
+				- This only applies when the property group-by-page? is set to false.
+			- Only applies to queries that return blocks.
 	- ### Query Inputs
 	  These are special values for a query's `:inputs` key above:
 		- #### Special page and block inputs

From 33e745a4f1521ae1652313612651087aad2502aa Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 16 Jun 2023 16:15:14 -0400
Subject: [PATCH 042/196] Document some commands

Documented them inline to make this as easy as possible. Defaulted to
putting them in Functionality sections. Also cleaned up flashcards and
fixed class hierarchy
---
 pages/Changelog_07_09.md                     |  1 +
 pages/Commands.md                            | 10 ++-
 pages/Embed Media - Audio, Photos, Videos.md | 22 +++++-
 pages/Features.md                            |  6 --
 pages/Flashcards.md                          | 73 ++++++++++----------
 pages/Graph Overview.md                      | 16 ++++-
 pages/Markdown.md                            |  4 +-
 pages/Numbered List.md                       |  7 ++
 pages/Tasks.md                               | 29 +++++---
 pages/Zotero.md                              |  6 +-
 10 files changed, 112 insertions(+), 62 deletions(-)

diff --git a/pages/Changelog_07_09.md b/pages/Changelog_07_09.md
index bdcdff9..2ab00b1 100644
--- a/pages/Changelog_07_09.md
+++ b/pages/Changelog_07_09.md
@@ -438,6 +438,7 @@
 			- `/Embed Twitter` support!
 				- E.g. `{{tweet https://twitter.com/logseq/status/1420968129987969026}} ` will displayed as:
 					- {{tweet https://twitter.com/logseq/status/1420968129987969026}}
+					  id:: 645d0145-6ce0-4231-a443-42865cd960f4
 		- [[Julio Navarro]]
 			- fix: after renaming a page, going back should not goto the original page
 	- [[Fixed issues]]
diff --git a/pages/Commands.md b/pages/Commands.md
index 7d79733..f5ebc18 100644
--- a/pages/Commands.md
+++ b/pages/Commands.md
@@ -6,4 +6,12 @@ description:: Functionality that can be invoked from any block
 	- Type `/` to kick off #autocompletion and see a list of commands.
 - ## Functionality
 	- Typing `/` only starts autocompletion when at the start of a new line or after whitespace.
-	- See [[Command]] for a list of available commands.
\ No newline at end of file
+	- query-table:: true
+	  query-properties:: [:name :page :description]
+	  query-sort-by:: page
+	  query-sort-desc:: false
+	  #+BEGIN_QUERY
+	  {:query (property :type [[Command]])
+	  :result-transform (fn [res] (map (fn [m] (assoc-in m [:block/properties :name] (get-in m [:block/page :block/original-name]))) res))
+	  :title "List of documented commands"}
+	  #+END_QUERY
\ No newline at end of file
diff --git a/pages/Embed Media - Audio, Photos, Videos.md b/pages/Embed Media - Audio, Photos, Videos.md
index 4bca3a4..192214b 100644
--- a/pages/Embed Media - Audio, Photos, Videos.md	
+++ b/pages/Embed Media - Audio, Photos, Videos.md	
@@ -76,6 +76,9 @@
 		- #+BEGIN_TIP
 		  If you're embedding an **image** using the HTML method, make sure to include `@@html:` at the start and `@@` at the end
 		  #+END_TIP
+		- type:: [[Command]]
+		  name:: Embed HTML
+		  description:: Type `/Embed HTML` to embed html, particularly useful for images.
 -
 - # [[Hiccup]] ClojureScript Method
 	- The [[Hiccup]] ClojureScript method is similar to the HTML method, but the markup tends to be more condensed.
@@ -105,8 +108,8 @@
 		  For local files that use the Hiccup method: Always use forward slashes `/` in the file path
 		  #+END_TIP
 -
-- # BONUS: Video Macros
-	- If you don't have access to a video file's URL, not to stress! Logseq has a macro which can embed video from third-party video hosting services like YouTube and Vimeo. If you're embedding from YouTube, there's even a macro for timestamps.
+- # Video Commands
+	- If you don't have access to a video file's URL, not to stress! Logseq has a command to embed video from third-party video hosting services like YouTube and Vimeo. If you're embedding from YouTube, there's also a command for timestamps.
 	-
 	- Here are the steps to use it:
 		- 1. Type the slash `/` command followed by `Embed Video URL`
@@ -116,7 +119,13 @@
 			- a. Play the video to the desired position.
 			- b. Pause and create a new line.
 			- c. Type the slash `/` command followed by `Embed YouTube timestamp`
-	-
+	- These two commands are:
+		- type:: [[Command]]
+		  name:: Embed Video URL
+		  description:: After invoking this command, simply paste a url to embed the video
+		- type:: [[Command]]
+		  name:: Embed Youtube timestamp
+		  description:: Inserts the current timestamp of the currently watched youtube video
 	- ## Example
 		- {{video https://www.youtube.com/watch?v=SUOdfa3MucE}}
 			- {{youtube-timestamp 0}} - A timestamp
@@ -127,6 +136,13 @@
 		  	- {{youtube-timestamp 271}} - Another timestamp
 		  ```
 -
+- # Other Embed Commands
+	- type:: [[Command]]
+	  name:: Embed twitter tweet
+	  description:: After invoking this command, paste a twitter url to embed it.
+		- For Example:
+		  collapsed:: true
+		  ((645d0145-6ce0-4231-a443-42865cd960f4))
 - # Useful Plugins for Media
 	- **[Media Timestamp](https://github.com/sethyuan/logseq-plugin-media-ts/blob/master/README.en.md) by sethyuan:** generates timestamps for video files, audio files, and Bilibili video
 	- **[Get YouTube Captions](https://github.com/briansunter/logseq-get-youtube-captions) by briansunter:** extracts auto-generated captions from YouTube video and can even add clickable timestamps
diff --git a/pages/Features.md b/pages/Features.md
index b22471c..39e673d 100644
--- a/pages/Features.md
+++ b/pages/Features.md
@@ -3,12 +3,6 @@
 		- Block context menu
 		- Topbar
 	- Features
-		- Commands
-			- Calculator - command
-			- Embed tweets - command + macro
-			- Embed videos - command + macro
-			- Scheduled and deadline - uses date picker element
-			- Draw
 		- Date picker - UI element + one command
 		- Document autocompletion of properties, tags, page refs, block refs, commands, advanced commands
 - TODO Resolve confusion between [[Commands]], [[Macros]], [[Advanced commands]] and commands in command palette #docs
\ No newline at end of file
diff --git a/pages/Flashcards.md b/pages/Flashcards.md
index cf48354..32549e3 100644
--- a/pages/Flashcards.md
+++ b/pages/Flashcards.md
@@ -1,44 +1,45 @@
 type:: [[Feature]]
 platforms:: [[All Platforms]]
 tags:: #Academic
+description:: Cards are blocks that are intended to be used as an aid in memorization
 
-- ## What's a "card"?
-  collapsed:: true
-	- A card is intended to be used as an aid in memorization. In logseq, it's just a block with either `#card` or `[[card]]`. It can have some [[Clozes]] too.
-		- For example, this block is a card:
-			- What does "Logseq" mean? #card
-			  card-last-interval:: 28.3
-			  card-repeats:: 4
-			  card-ease-factor:: 2.66
-			  card-next-schedule:: 2021-11-08T17:59:40.382Z
-			  card-last-reviewed:: 2021-10-11T10:59:40.382Z
-			  card-last-score:: 5
-				- You can read it as "Log sequence" or "Logical sequence" (thank you [[Ed]]).
-			- If you right click the bullet and select "Preview Card", you'll see something like this:
-				- ![CleanShot 2021-07-22 at 21.46.52.png](../assets/CleanShot_202021-07-22_20at_2021.46.52_1626961624975_0.png)
-- ## How to create a card?
-	- There're two ways to create a card.
-		- 1. You can add either `#card` or `[[card]]` to any block to make it a card.
-		- 2. You can right click the bullet to "Make a Flashcard", which will add `#card` to the end of the current block.
+- ## Usage
+	- To create a card:
+		- You can add either `#card` or `[[card]]` to any block to make it a card.
+		  logseq.order-list-type:: number
+		- You can right click the bullet to "Make a Flashcard", which will add `#card` to the end of the current block.
+		  logseq.order-list-type:: number
 			- ![../assets/sidebar-make-a-flashcard.png](../assets/sidebar-make-a-flashcard.png)
-- ## I've created several cards, how can I review all of my cards?
-  collapsed:: true
-	- Click the "Flashcards" tab on the [[Left sidebar]].
-- ## Can I review parts of my cards instead of all of them? For example, only those cards related to Logseq?
-  collapsed:: true
-	- Yes, you can use `/cards` and [[Queries]]. - `{{cards [[Logseq]]}}` will be displayed as:
-	  
-	  {{cards [[Logseq]]}}
-	- You can also show all cards _except_ those tagged with a certain page. `{{cards (not [[Logseq]])}}` will be displayed as:
-	  
-	  {{cards (not [[Logseq]]) }}
-- ## TIPs
-  collapsed:: true
-	- Press `t c` (toggle cards) to review all of your cards
-	- You can add your "cards" queries to the "Favorites" page in the right sidebar for quick access.
-- [[Resources]]
+	- To review all cards, click the "Flashcards" tab on the [[Left sidebar]] or press `t c` (toggle cards) to review all of your cards
+	- To review some of your cards e.g. only those related to Logseq:
+		- Use `/cards` and [[Queries]]. - `{{cards [[Logseq]]}}` will be displayed as:
+		  
+		  {{cards [[Logseq]]}}
+		- You can also show all cards _except_ those tagged with a certain page. `{{cards (not [[Logseq]])}}` will be displayed as:
+		  
+		  {{cards (not [[Logseq]]) }}
+		- You can add your cards queries to the "Contents" page in the right sidebar for quick access.
+- ## Functionality
+	- ### What's a "card"?
+		- It's just a block with either `#card` or `[[card]]`. It can have some [[Clozes]] too.
+			- For example, this block is a card:
+				- What does "Logseq" mean? #card
+				  card-last-interval:: 28.3
+				  card-repeats:: 4
+				  card-ease-factor:: 2.66
+				  card-next-schedule:: 2021-11-08T17:59:40.382Z
+				  card-last-reviewed:: 2021-10-11T10:59:40.382Z
+				  card-last-score:: 5
+					- You can read it as "Log sequence" or "Logical sequence" (thank you [[Ed]]).
+				- If you right click the bullet and select "Preview Card", you'll see something like this:
+					- ![CleanShot 2021-07-22 at 21.46.52.png](../assets/CleanShot_202021-07-22_20at_2021.46.52_1626961624975_0.png)
+		- To review a queryable set of cards, the `/cards` command is provided:
+			- type:: [[Command]]
+			  name:: Cards
+			  description:: A [[Query]] that returns cards that meet the query criteria
+- ## Additional Links
 	- [Augmenting Long-term Memory](http://augmentingcognition.com/ltm.html)
 	- [SM5](https://www.supermemo.com/en/archives1990-2015/english/ol/sm5) by supermemo
-- TODO Organize this page #docs
-	- Maybe split out tutorial. Add Tienson's latest functionality
+- TODO Finish this page #docs
+	- Add Tienson's latest functionality
 	- srs.edn
\ No newline at end of file
diff --git a/pages/Graph Overview.md b/pages/Graph Overview.md
index 3cc15e9..494bc82 100644
--- a/pages/Graph Overview.md	
+++ b/pages/Graph Overview.md	
@@ -10,6 +10,7 @@
 			- [[Command]]
 			- [[Whiteboard/Tool]]
 		- [[Platform]]
+		- [[Property]]
 		- [[UI Element]]
 			- [[Whiteboard/Object]]
 - ## Pages by Class
@@ -40,10 +41,19 @@
 			  #+END_QUERY
 			- [[Command]]
 			  collapsed:: true
-				- collapsed:: true
+				- query-sort-by:: page
+				  query-table:: true
+				  query-sort-desc:: false
+				  query-properties:: [:name :page :description]
+				  #+BEGIN_QUERY
+				  {:query (property :type [[Command]])
+				  :result-transform (fn [res] (map (fn [m] (assoc-in m [:block/properties :name] (get-in m [:block/page :block/original-name]))) res))
+				  :title "Commands"}
+				  #+END_QUERY
+				- query-table:: true
 				  #+BEGIN_QUERY
-				  {:query (page-property :type [[Command]])
-				  :title "Command pages"}
+				  {:query (property :type [[Command]])
+				  :title "Commands"}
 				  #+END_QUERY
 			- [[Whiteboard/Tool]]
 			  collapsed:: true
diff --git a/pages/Markdown.md b/pages/Markdown.md
index 4ed2d30..7b13724 100644
--- a/pages/Markdown.md
+++ b/pages/Markdown.md
@@ -73,8 +73,6 @@ id:: 60a78b6b-a0ff-49fe-822f-87216fbf79ff
 	- Priority
 	  id:: 60ab4582-b191-496a-be39-0a865f9ecece
 		- syntax: `[#A]` `[#B]` `[#C]`
-		- Priorities can be set with commands(`/A`, `/B`, `/C`)
-		  id:: 60ac5b08-d4bb-49de-b415-e63fcf29c59f
 	- [[Hiccup]]
 	  id:: 60ab5bc7-f196-4f87-91aa-164ac71184ed
 		- Sometimes you want to express more complex text structure, you can embed Hiccup in blocks.
@@ -84,4 +82,4 @@ id:: 60a78b6b-a0ff-49fe-822f-87216fbf79ff
 		- [Hiccup syntax here](https://github.com/weavejester/hiccup/wiki/Syntax)
 	- inline latex
 	  id:: 60ab5bc7-f08f-4e7d-a293-add673533700
-		- `$$E = mc^2$$` -> $$E = mc^2$$
+		- `$$E = mc^2$$` -> $$E = mc^2$$
\ No newline at end of file
diff --git a/pages/Numbered List.md b/pages/Numbered List.md
index 1eaa695..908cfd1 100644
--- a/pages/Numbered List.md	
+++ b/pages/Numbered List.md	
@@ -27,6 +27,13 @@ initial-version:: 0.9.5
 - ## Functionality
 	- Blocks that are dragged into a numbered list are turned into a numbered block.
 	- A numbered block when copied and pasted remains a numbered block.
+	- Two commands are provided for numbered lists:
+		- type:: [[Command]]
+		  name:: Number list
+		  description:: Toggles the current block to be a numbered list item
+		- type:: [[Command]]
+		  name:: Number children
+		  description:: Toggles the current block's children to be a numbered list
 	- ### Limitations
 		- A numbered list is not currently saved in a [standard ordered list format](https://daringfireball.net/projects/markdown/syntax#list).
 		- See [this comment](https://github.com/logseq/logseq/pull/9141#issuecomment-1517108026) for ux limitations.
\ No newline at end of file
diff --git a/pages/Tasks.md b/pages/Tasks.md
index 56e7aaf..f5cb982 100644
--- a/pages/Tasks.md
+++ b/pages/Tasks.md
@@ -17,18 +17,31 @@ platforms:: [[All Platforms]]
 			- DONE watch Doctor Who
 - ## Functionality
 	- ### Priorities
-		- Logseq comes with three built-in priority mark to help you manage with task priorities
-			- {{embed ((60ac5b08-d4bb-49de-b415-e63fcf29c59f)) }}
+		- Logseq comes with three optional, built-in priorities that can be set with commands (`/A`, `/B`, `/C`):
+			- type:: [[Command]]
+			  name:: A
+			  description:: Highest priority
+			- type:: [[Command]]
+			  name:: B
+			  description:: Mid level priority
+			- type:: [[Command]]
+			  name:: C
+			  description:: Lowest priority
 			- Example:
 				- LATER [#A] research balalah is a top priority
 				- LATER [#C] do grocery has lowest priority
 	- ### Deadline and Scheduled
-		- You can leverage command `/Deadline` to setup a deadline for any block
-			- eg: finish reading 1984 by 29th of May
-			  DEADLINE: <2021-05-29 Sat>
-		- You can leverage command `/Scheduled` to setup a schedule for a block
-			- eg: send John a birthday card Monday
-			  SCHEDULED: <2021-05-31 Mon>
+		- There are two commands for setting dates on a block:
+			- type:: [[Command]]
+			  name:: Deadline
+			  description:: Type command `/Deadline` to choose a deadline date for a block
+				- eg: finish reading 1984 by 29th of May
+				  DEADLINE: <2021-05-29 Sat>
+			- type:: [[Command]]
+			  name:: Scheduled
+			  description:: Type command `/Scheduled` to setup a scheduled date for a block
+				- eg: send John a birthday card Monday
+				  SCHEDULED: <2021-05-31 Mon>
 		- Both of the above commands work on blocks, not just tasks.
 		- Both of the above commands default to displaying blocks that are coming up soon. You can configure how soon with `:scheduled/future-days`  in [[config.edn]].
 		- Both of above commands support to mark the task as repeated:
diff --git a/pages/Zotero.md b/pages/Zotero.md
index 700ba73..2fe1cfa 100644
--- a/pages/Zotero.md
+++ b/pages/Zotero.md
@@ -5,9 +5,11 @@ tags:: #Academic
 
 - ## Usage
 	- You can either type `/Zotero` command, search individual zotero item (title, author, text, anything), select and add as a Logseq page.
-	   id:: 6103e488-22d4-4751-b27a-69b278067c26
-	  collapsed:: true
+	  id:: 6103e488-22d4-4751-b27a-69b278067c26
 	  ![zotero-search.gif](../assets/zotero-search_1627554650388_0.gif)
+		- type:: [[Command]]
+		  name:: Zotero
+		  description:: Imports a Zotero journal article
 	- Or if you wish to import and create all pages at once, goto `Zotero settings`, and click `Add all` to import all Zotero items and add them as Logseq pages
 	  collapsed:: true
 	  ![zotero-add-all.gif](../assets/zotero-add-all_1627558378327_0.gif)

From 1cbe99429c50c56da59668494ae7f9eb0db9049e Mon Sep 17 00:00:00 2001
From: Bryan Lee <pygmize.me@gmail.com>
Date: Fri, 16 Jun 2023 23:26:42 -0700
Subject: [PATCH 043/196] Update setting___preferred journal format.md for
 Journal date format

---
 pages/setting___preferred journal format.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/setting___preferred journal format.md b/pages/setting___preferred journal format.md
index e3deb05..bf79798 100644
--- a/pages/setting___preferred journal format.md	
+++ b/pages/setting___preferred journal format.md	
@@ -1,9 +1,9 @@
-- You can set your preferred daily journal date format via `Settings` page
+- You can set your preferred daily journal date format via `Settings > Editor` page
 - Alternatively, you can add it in [[config.edn]]
 	- {{embed ((60acdeb9-aa65-492b-8398-d4d65c1631c1))}}
 	- Add your favorite date-formatter to [[config.edn]]:
 	  #+BEGIN_SRC clojure
-	  :date-formatter "yyyy-MM-dd"
+	  :journal/page-title-format "yyyy-MM-dd"
 	  #+END_SRC
 	  Currently, logseq support:
 	  #+BEGIN_SRC clojure
@@ -21,4 +21,4 @@
 	       "yyyy-MM-dd"
 	       "yyyy_MM_dd"
 	       "yyyy年MM月dd日"
-	  #+END_SRC
\ No newline at end of file
+	  #+END_SRC

From cce557f59c603bc2cc885cacbfaebb37a36e2207 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 26 Jun 2023 16:48:46 -0400
Subject: [PATCH 044/196] Update uses of properties to be valid with property
 validation

- Added property related pages for validation
- Minor fixes for validation e.g. remove unused property and one-off
  uses of a property
- Update graph overview and delete an ol query
---
 .graph-validator/config.edn            |  7 ++++++-
 pages/Boolean.md                       |  3 +++
 pages/DataType.md                      |  4 ++++
 pages/Graph Overview.md                | 10 +++++-----
 pages/String.md                        |  4 ++++
 pages/StringWithRefs.md                |  4 ++++
 pages/Uri.md                           |  4 ++++
 pages/Whiteboard___Property___Links.md |  2 --
 pages/about.org                        | 10 +---------
 pages/description.md                   |  1 +
 pages/domainIncludes.md                |  6 ++++++
 pages/initial-version.md               |  3 +++
 pages/meta.md                          |  4 ++++
 pages/name.md                          |  4 ++++
 pages/page_embed.md                    |  9 ++++-----
 pages/parent.md                        |  2 ++
 pages/platforms.md                     |  3 +++
 pages/rangeIncludes.md                 |  6 ++++++
 pages/sameAs.md                        |  1 +
 pages/supports.md                      |  4 ++++
 pages/term.page title.md               |  2 +-
 pages/type.md                          |  1 +
 pages/unique.md                        |  4 ++++
 pages/url.md                           |  2 ++
 24 files changed, 77 insertions(+), 23 deletions(-)
 create mode 100644 pages/Boolean.md
 create mode 100644 pages/DataType.md
 create mode 100644 pages/String.md
 create mode 100644 pages/StringWithRefs.md
 create mode 100644 pages/Uri.md
 delete mode 100644 pages/Whiteboard___Property___Links.md
 create mode 100644 pages/domainIncludes.md
 create mode 100644 pages/meta.md
 create mode 100644 pages/name.md
 create mode 100644 pages/rangeIncludes.md
 create mode 100644 pages/supports.md
 create mode 100644 pages/unique.md

diff --git a/.graph-validator/config.edn b/.graph-validator/config.edn
index 4716b1a..0490f08 100644
--- a/.graph-validator/config.edn
+++ b/.graph-validator/config.edn
@@ -1,2 +1,7 @@
 {:exclude [tags-and-page-refs-have-pages]
- :add-namespaces [logseq.graph-validator.validations.class schema]}
+ :add-namespaces [logseq.graph-validator.validations.class
+                  logseq.graph-validator.validations.property
+                  schema]
+ ;; These are all used in examples
+ :property/ignore-list #{:author :project :tag :publication-date :price :qty
+                         :full-title :source}}
diff --git a/pages/Boolean.md b/pages/Boolean.md
new file mode 100644
index 0000000..7aaf026
--- /dev/null
+++ b/pages/Boolean.md
@@ -0,0 +1,3 @@
+type:: [[Class]]
+parent:: [[DataType]]
+url:: https://schema.org/Boolean
diff --git a/pages/DataType.md b/pages/DataType.md
new file mode 100644
index 0000000..2fd4744
--- /dev/null
+++ b/pages/DataType.md
@@ -0,0 +1,4 @@
+type:: [[Class]]
+parent:: [[Class]]
+url:: https://schema.org/DataType
+description:: Provides basic data types such as integers, strings, etc. See https://www.w3.org/TR/rdf12-concepts/#section-Datatypes for additional datatypes that could be possible
diff --git a/pages/Graph Overview.md b/pages/Graph Overview.md
index 494bc82..1d47ed2 100644
--- a/pages/Graph Overview.md	
+++ b/pages/Graph Overview.md	
@@ -5,6 +5,11 @@
   *Note:* This section shows how classes or types of pages are related to each other. A class groups pages that share a common set of properties. `Thing` is the root class from which all other classes are defined. When a class is a child of another class, it usually inherits using the same properties as its parent class.
 	- [[Thing]]
 		- [[Class]]
+			- [[DataType]]
+				- [[Boolean]]
+				- [[StringWithRefs]]
+				- [[String]]
+				- [[Uri]]
 		- [[FeatureTag]]
 		- [[Feature]]
 			- [[Command]]
@@ -50,11 +55,6 @@
 				  :result-transform (fn [res] (map (fn [m] (assoc-in m [:block/properties :name] (get-in m [:block/page :block/original-name]))) res))
 				  :title "Commands"}
 				  #+END_QUERY
-				- query-table:: true
-				  #+BEGIN_QUERY
-				  {:query (property :type [[Command]])
-				  :title "Commands"}
-				  #+END_QUERY
 			- [[Whiteboard/Tool]]
 			  collapsed:: true
 				- collapsed:: true
diff --git a/pages/String.md b/pages/String.md
new file mode 100644
index 0000000..713069d
--- /dev/null
+++ b/pages/String.md
@@ -0,0 +1,4 @@
+type:: [[Class]]
+parent:: [[DataType]]
+url:: https://schema.org/Text
+meta:: Prefer the name string over text as it maps with xsd:string
diff --git a/pages/StringWithRefs.md b/pages/StringWithRefs.md
new file mode 100644
index 0000000..c5fcf4c
--- /dev/null
+++ b/pages/StringWithRefs.md
@@ -0,0 +1,4 @@
+type:: [[Class]]
+parent:: [[DataType]]
+url:: {{docs-base-url StringWithRefs}}
+description:: String that can have page references
diff --git a/pages/Uri.md b/pages/Uri.md
new file mode 100644
index 0000000..2fd47b0
--- /dev/null
+++ b/pages/Uri.md
@@ -0,0 +1,4 @@
+type:: [[Class]]
+parent:: [[DataType]]
+url:: https://schema.org/URL
+meta:: Couldn't use URL since we're case insensitive and url is already taken
diff --git a/pages/Whiteboard___Property___Links.md b/pages/Whiteboard___Property___Links.md
deleted file mode 100644
index 788072a..0000000
--- a/pages/Whiteboard___Property___Links.md
+++ /dev/null
@@ -1,2 +0,0 @@
-alias:: Whiteboard Links
-type:: [[Property]]
diff --git a/pages/about.org b/pages/about.org
index b457c79..a94fce6 100644
--- a/pages/about.org
+++ b/pages/about.org
@@ -1,5 +1,4 @@
 #+TITLE: About
-#+PERMALINK: about
 
 ** Hi, welcome to [[https://logseq.com][Logseq]].
 
@@ -13,33 +12,27 @@
   plain text files, we support both Markdown and Emacs Org mode for the time being. Even if the website is down or can't be maintained, your data is always yours.
 
   *Logseq* is hugely inspired by [[https://roamresearch.com/][Roam Research]], [[https://orgmode.org/][Org Mode]], [[https://tiddlywiki.com/][Tiddlywiki]] and [[https://workflowy.com/][Workflowy]], hats off to all of them!
-[[https://cdn.logseq.com/%2F8b9a461d-437e-4ca5-a2da-18b51077b5142020_07_25_Screenshot%202020-07-25%2013-29-49%20%2B0800.png?Expires=4749255017&Signature=Qbx6jkgAytqm6nLxVXQQW1igfcf~umV1OcG6jXUt09TOVhgXyA2Z5jHJ3AGJASNcphs31pZf4CjFQ5mRCyVKw6N8wb8Nn-MxuTJl0iI8o-jLIAIs9q1v-2cusCvuFfXH7bq6ir8Lpf0KYAprzuZ00FENin3dn6RBW35ENQwUioEr5Ghl7YOCr8bKew3jPV~OyL67MttT3wJig1j3IC8lxDDT8Ov5IMG2GWcHERSy00F3mp3tJtzGE17-OUILdeuTFz6d-NDFAmzB8BebiurYz0Bxa4tkcdLUpD5ToFHU08jKzZExoEUY8tvaZ1-t7djmo3d~BAXDtlEhC2L1YC2aVQ__&Key-Pair-Id=APKAJE5CCD6X7MP6PTEA][2020_07_25_Screenshot 2020-07-25 13-29-49 +0800.png]] 
+[[https://cdn.logseq.com/%2F8b9a461d-437e-4ca5-a2da-18b51077b5142020_07_25_Screenshot%202020-07-25%2013-29-49%20%2B0800.png?Expires=4749255017&Signature=Qbx6jkgAytqm6nLxVXQQW1igfcf~umV1OcG6jXUt09TOVhgXyA2Z5jHJ3AGJASNcphs31pZf4CjFQ5mRCyVKw6N8wb8Nn-MxuTJl0iI8o-jLIAIs9q1v-2cusCvuFfXH7bq6ir8Lpf0KYAprzuZ00FENin3dn6RBW35ENQwUioEr5Ghl7YOCr8bKew3jPV~OyL67MttT3wJig1j3IC8lxDDT8Ov5IMG2GWcHERSy00F3mp3tJtzGE17-OUILdeuTFz6d-NDFAmzB8BebiurYz0Bxa4tkcdLUpD5ToFHU08jKzZExoEUY8tvaZ1-t7djmo3d~BAXDtlEhC2L1YC2aVQ__&Key-Pair-Id=APKAJE5CCD6X7MP6PTEA][2020_07_25_Screenshot 2020-07-25 13-29-49 +0800.png]]
 ** Where are my notes saved?
    Your notes will be stored in the local browser storage. We are using IndexedDB.
-
 ** How do I use it?
 *** 1. Sync between multiple devices
     Currently, we only support syncing through Github, more options (e.g.
     Gitlab, Dropbox, Google Drive, WebDAV, etc.) will be added soon.
 
     We are using an excellent web git client called [[https://isomorphic-git.org/][isomorphic-git]].
-
 **** Step 1
      Click the button /Login with Github/.
-
 **** Step 2
      Set your Github personal access token, the token will be encrypted and
      stored in the browser local storage, our server will never store it.
 
      If you know nothing about either Git or the personal access token, no worries,
      just follow the steps here: https://logseq.com/blog/faq#How_to_create_a_Github_personal_access_token-3f-
-
 **** Step 3
      Start writing!
-
 *** 2. Use it locally (no need to login)
     Just remember to backup your notes periodically (we'll provide export and import soon)!
-
 ** Features
    - Backlinks between ~[[Page]]~s
    - Block embed
@@ -59,7 +52,6 @@
    - Website: https://logseq.com/
    - Github: https://github.com/logseq/logseq everyone is encouraged to report issues!
    - Our blog: https://logseq.com/blog
-
 ** Credits to
    - [[https://roamresearch.com/][Roam Research]]
    - [[https://orgmode.org/][Org Mode]]
diff --git a/pages/description.md b/pages/description.md
index 0a2f8f7..1c03076 100644
--- a/pages/description.md
+++ b/pages/description.md
@@ -1,2 +1,3 @@
 type:: [[Property]]
 url:: https://schema.org/description
+rangeIncludes:: [[StringWithRefs]]
diff --git a/pages/domainIncludes.md b/pages/domainIncludes.md
new file mode 100644
index 0000000..b85c2a0
--- /dev/null
+++ b/pages/domainIncludes.md
@@ -0,0 +1,6 @@
+type:: [[Property]]
+url:: {{docs-base-url domainIncludes}}
+description:: A more useful version of rdfs:domain as it can be one of multiple values
+sameAs:: https://schema.org/domainIncludes
+domainIncludes:: [[Property]]
+rangeIncludes:: [[Class]]
diff --git a/pages/initial-version.md b/pages/initial-version.md
index 4fc5636..c494aba 100644
--- a/pages/initial-version.md
+++ b/pages/initial-version.md
@@ -1 +1,4 @@
 type:: [[Property]]
+url:: {{docs-base-url initial-version}}
+domainIncludes:: [[Feature]] [[Tool]]
+rangeIncludes:: [[String]]
diff --git a/pages/meta.md b/pages/meta.md
new file mode 100644
index 0000000..d5fe417
--- /dev/null
+++ b/pages/meta.md
@@ -0,0 +1,4 @@
+type:: [[Property]]
+url:: {{docs-base-url meta}}
+description:: Meta description field which usually discusses organizing thing instead of thing itself
+rangeIncludes:: [[String]]
diff --git a/pages/name.md b/pages/name.md
new file mode 100644
index 0000000..6d031da
--- /dev/null
+++ b/pages/name.md
@@ -0,0 +1,4 @@
+type:: [[Property]]
+url:: https://schema.org/name
+rangeIncludes:: [[String]]
+unique:: true
diff --git a/pages/page_embed.md b/pages/page_embed.md
index 41a2f8e..06c285d 100644
--- a/pages/page_embed.md
+++ b/pages/page_embed.md
@@ -1,14 +1,13 @@
 ---
 title: Page embed
-related: [[Block embed]]
 tags: [[embed]]
+description:: See [[Block embed]] for block version of this
 ---
 
 - Also commonly known as transclusion, page embedding allows an entire page to be displayed within another.
 - Create a page embed by:
-    - Typing `{{{embed [[page name]]}}}`
--
-  #+BEGIN_TIP
+	- Typing `{{{embed [[page name]]}}}`
+- #+BEGIN_TIP
   - Edits made to the embedded content are also made to the referenced content.
   - Embedding does not contribute to a page's [[Linked References]]
-   #+END_TIP
\ No newline at end of file
+   #+END_TIP
diff --git a/pages/parent.md b/pages/parent.md
index 850f6f0..05e9f11 100644
--- a/pages/parent.md
+++ b/pages/parent.md
@@ -1,3 +1,5 @@
 type:: [[Property]]
 url:: https://www.w3.org/2000/01/rdf-schema#subClassOf
 description:: Used to connect a class with its parent class
+domainIncludes:: [[Class]]
+rangeIncludes:: [[Class]]
diff --git a/pages/platforms.md b/pages/platforms.md
index 4fc5636..2d88990 100644
--- a/pages/platforms.md
+++ b/pages/platforms.md
@@ -1 +1,4 @@
 type:: [[Property]]
+url:: {{docs-base-url platforms}}
+domainincludes:: [[Feature]] [[Tool]]
+rangeIncludes:: [[Platform]]
diff --git a/pages/rangeIncludes.md b/pages/rangeIncludes.md
new file mode 100644
index 0000000..6992902
--- /dev/null
+++ b/pages/rangeIncludes.md
@@ -0,0 +1,6 @@
+type:: [[Property]]
+url:: {{docs-base-url rangeIncludes}}
+description:: List of values a property can have
+sameAs:: https://schema.org/rangeIncludes
+domainIncludes:: [[Property]]
+rangeIncludes:: [[Class]]
diff --git a/pages/sameAs.md b/pages/sameAs.md
index f75b3ce..e457813 100644
--- a/pages/sameAs.md
+++ b/pages/sameAs.md
@@ -1,3 +1,4 @@
 type:: [[Property]]
 url:: https://www.w3.org/2002/07/owl#sameAs
 description:: Indicates that two URIs are equivalent
+rangeIncludes:: [[Uri]]
diff --git a/pages/supports.md b/pages/supports.md
new file mode 100644
index 0000000..d7bdea9
--- /dev/null
+++ b/pages/supports.md
@@ -0,0 +1,4 @@
+type:: [[Property]]
+url:: {{docs-base-url supports}}
+domainIncludes:: [[Whiteboard/Object]] [[Tool]]
+rangeIncludes:: [[String]]
diff --git a/pages/term.page title.md b/pages/term.page title.md
index 568be55..2890748 100644
--- a/pages/term.page title.md	
+++ b/pages/term.page title.md	
@@ -1,5 +1,5 @@
 title:: custom page title
-sample:: click me
+description:: click me
 
 - description:
 	- the content displayed at the top of a page, used to uniquely identify the page
diff --git a/pages/type.md b/pages/type.md
index 060cf73..1a1af6a 100644
--- a/pages/type.md
+++ b/pages/type.md
@@ -1,2 +1,3 @@
 type:: [[Property]]
 url:: http://www.w3.org/1999/02/22-rdf-syntax-ns#type
+rangeIncludes:: [[Class]]
diff --git a/pages/unique.md b/pages/unique.md
new file mode 100644
index 0000000..043778e
--- /dev/null
+++ b/pages/unique.md
@@ -0,0 +1,4 @@
+type:: [[Property]]
+url:: {{docs-base-url unique}}
+rangeIncludes:: [[Boolean]]
+domainIncludes:: [[Property]]
diff --git a/pages/url.md b/pages/url.md
index 7d6fe70..0a7357b 100644
--- a/pages/url.md
+++ b/pages/url.md
@@ -1,2 +1,4 @@
 type:: [[Property]]
 url:: https://schema.org/url
+rangeIncludes:: [[Uri]]
+unique:: true

From 1d5619478ece43e1da0eafa374e071536fc62e5e Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 26 Jun 2023 17:44:42 -0400
Subject: [PATCH 045/196] Add docs for a code block

---
 pages/Code block.md | 18 ++++++++++++++++++
 pages/Flashcards.md |  3 ++-
 2 files changed, 20 insertions(+), 1 deletion(-)
 create mode 100644 pages/Code block.md

diff --git a/pages/Code block.md b/pages/Code block.md
new file mode 100644
index 0000000..b6aa4b5
--- /dev/null
+++ b/pages/Code block.md	
@@ -0,0 +1,18 @@
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+description:: Renders a block of code with [[Codemirror]] support for a variety of languages
+
+## Usage
+	- Type the `/Code block` command and then select a language from the dropdown.
+		- type:: [[Command]]
+		  name:: Code block
+		  description:: User-friendly way to create a code block
+	- Alternatively, you can type 3 backticks, the name of the language and then press `Enter`.
+	- An example code block looks like:
+	  ```clojure
+	  (println "WOOT!")
+	  ```
+## Functionality
+	- This feature provides support for languages through [CodeMirror's modes](https://codemirror.net/5/mode/index.html)
+- ## Additional Links
+	- See [[Calculator]] and [[ClojureScript Eval in a Block]] features which rely on code blocks
\ No newline at end of file
diff --git a/pages/Flashcards.md b/pages/Flashcards.md
index 32549e3..bdde04b 100644
--- a/pages/Flashcards.md
+++ b/pages/Flashcards.md
@@ -33,7 +33,8 @@ description:: Cards are blocks that are intended to be used as an aid in memoriz
 					- You can read it as "Log sequence" or "Logical sequence" (thank you [[Ed]]).
 				- If you right click the bullet and select "Preview Card", you'll see something like this:
 					- ![CleanShot 2021-07-22 at 21.46.52.png](../assets/CleanShot_202021-07-22_20at_2021.46.52_1626961624975_0.png)
-		- To review a queryable set of cards, the `/cards` command is provided:
+		- To review a queryable set of cards, the `/cards` command is provided
+		  collapsed:: true
 			- type:: [[Command]]
 			  name:: Cards
 			  description:: A [[Query]] that returns cards that meet the query criteria

From 2b6aac8c8e83ad2c3e67ff3a142635619abfd4be Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 28 Jun 2023 11:34:06 +0800
Subject: [PATCH 046/196] chore(release): changelog v0.9.10

---
 pages/Changelog.md | 49 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 49 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 4c8b126..d143ece 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,3 +1,52 @@
+- ## Beta 0.9.10 [[Jun 28th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.10>
+	- [[Features]]
+		- Whiteboards: #[[Snap to grid]] [#9654](https://github.com/logseq/logseq/pull/9654)
+	- [[Thanks]]
+		- [[Allan Chain]]
+			- Update KaTeX from 0.13.18 to 0.16.7 in [#9625](https://github.com/logseq/logseq/pull/9625)
+		- [[Bad3r]]
+			- Replace 'presentation' with 'view as slides' in [#9681](https://github.com/logseq/logseq/pull/9681)
+			- Update playwright config in [#9623](https://github.com/logseq/logseq/pull/9623)
+			- Add tests for selecting codeblock language in [#9557](https://github.com/logseq/logseq/pull/9557)
+			- Fix test intermediate failure in [#9699](https://github.com/logseq/logseq/pull/9699)
+		- [[cui fliter]]
+			- Fix typo  in [#9666](https://github.com/logseq/logseq/pull/9666)
+		- [[Rui Sun]]
+			- Fix setting title does not use i18n translation in [#9711](https://github.com/logseq/logseq/pull/9711)
+		- [[Mikhail Smelov]]
+			- Convert more of the UI to be translatable in [#9658](https://github.com/logseq/logseq/pull/9658) [#9680](https://github.com/logseq/logseq/pull/9680)
+			- Improve Russian (ru) translations in [#9645](https://github.com/logseq/logseq/pull/9645)
+		- [[megayu]]
+			- Fix paste text to link in [#9650](https://github.com/logseq/logseq/pull/9650)
+		- [[Phil Denhoff]]
+			- Improve plugin interfaces for IAppProxy, IEditorProxy, BlockEntity and PageEntity in [#9520](https://github.com/logseq/logseq/pull/9520)
+		- [[queeup]]
+			- Update Turkish translations in [#9686](https://github.com/logseq/logseq/pull/9686) [#9716](https://github.com/logseq/logseq/pull/9716)
+		- [[Taylor Hoffmann]]
+			- Update pt-BR translations in [#9655](https://github.com/logseq/logseq/pull/9655)
+	- [[Fixed issues]]
+		- Paste text to link [#9650](https://github.com/logseq/logseq/pull/9650)
+		- Clicking to edit a block from the right sidebar or a whiteboard can't jump to the correct position [#9657](https://github.com/logseq/logseq/pull/9657)
+		- Disable content selection when blocks have been selected [#9713](https://github.com/logseq/logseq/pull/9713)
+		- Fix pasting from HTML for some specific sites [#9739](https://github.com/logseq/logseq/pull/9739)
+		- Hidden editable block properties showing up when user properties present [#9661](https://github.com/logseq/logseq/pull/9661)
+		- Reactive queries [#9695](https://github.com/logseq/logseq/pull/9695) #[[minor change]]
+		- Trim block whitespace for markdown files for a specific case [#9554](https://github.com/logseq/logseq/pull/9554)
+		- Incorrect behavior for the code editor of file page [#9595](https://github.com/logseq/logseq/pull/9595)
+		- Polish the plugin settings modal [#9669](https://github.com/logseq/logseq/pull/9669)
+	- [[Enhancement]]
+		- Logseq Sync: experimental support for editing conflict handling with diff-merge [#9238](https://github.com/logseq/logseq/pull/9238) #experimental (To enable this, check the Features tab in the Setting menu)
+		- Add slash command for creating code blocks [#9553](https://github.com/logseq/logseq/pull/9553)
+		- Replace 'presentation' with 'view as slides' [#9681](https://github.com/logseq/logseq/pull/9681) #[[minor change]]
+		- More translation for UI elements [#9658](https://github.com/logseq/logseq/pull/9658) [#9680](https://github.com/logseq/logseq/pull/9680) [#9711](https://github.com/logseq/logseq/pull/9711)
+		- Punctuation usage in translations [#9610](https://github.com/logseq/logseq/pull/9610)
+		- I18n: Russian [#9645](https://github.com/logseq/logseq/pull/9645), pt-BR [#9655](https://github.com/logseq/logseq/pull/9655), Turkish [#9686](https://github.com/logseq/logseq/pull/9686) [#9716](https://github.com/logseq/logseq/pull/9716), Spanish [#9665](https://github.com/logseq/logseq/pull/9665)
+		- Polish details for the plugin fenced code block [#9590](https://github.com/logseq/logseq/pull/9590)
+		- Plugin marketplace enhancements [#9609](https://github.com/logseq/logseq/pull/9609)
+		- Plugin API:
+			- Support right sidebar item type as string [#9701](https://github.com/logseq/logseq/pull/9701)
+			- Improve plugin interfaces for IAppProxy, IEditorProxy, BlockEntity and PageEntity [#9520](https://github.com/logseq/logseq/pull/9520)
 - ## Beta 0.9.9 [[Jun 13th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.9>
 	- [[Features]]

From c252e6778d3bb8c5afeefc327cf0e4c074e863b4 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 28 Jun 2023 12:01:05 +0800
Subject: [PATCH 047/196] fix: hack to bypass parsing bug

---
 pages/Changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index d143ece..8e011eb 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,7 @@
 - ## Beta 0.9.10 [[Jun 28th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.10>
 	- [[Features]]
-		- Whiteboards: #[[Snap to grid]] [#9654](https://github.com/logseq/logseq/pull/9654)
+		- Whiteboards: #[[Snap to grid]]  [#9654](https://github.com/logseq/logseq/pull/9654)
 	- [[Thanks]]
 		- [[Allan Chain]]
 			- Update KaTeX from 0.13.18 to 0.16.7 in [#9625](https://github.com/logseq/logseq/pull/9625)

From 70c4c50312d0a8899646ca5e89a3412b804f7d3a Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 28 Jun 2023 12:26:56 +0800
Subject: [PATCH 048/196] fix: whitespace

---
 pages/Changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 8e011eb..88a9df2 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,7 @@
 - ## Beta 0.9.10 [[Jun 28th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.10>
 	- [[Features]]
-		- Whiteboards: #[[Snap to grid]]  [#9654](https://github.com/logseq/logseq/pull/9654)
+		- Whiteboards: #[[Snap to grid]] [#9654](https://github.com/logseq/logseq/pull/9654)
 	- [[Thanks]]
 		- [[Allan Chain]]
 			- Update KaTeX from 0.13.18 to 0.16.7 in [#9625](https://github.com/logseq/logseq/pull/9625)

From 6dcbf89b2ace451bc4c1f0c1e4c2e69c732024c3 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 28 Jun 2023 09:49:23 -0400
Subject: [PATCH 049/196] Add link to changelog

---
 pages/Changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 88a9df2..a2de239 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -42,7 +42,7 @@
 		- More translation for UI elements [#9658](https://github.com/logseq/logseq/pull/9658) [#9680](https://github.com/logseq/logseq/pull/9680) [#9711](https://github.com/logseq/logseq/pull/9711)
 		- Punctuation usage in translations [#9610](https://github.com/logseq/logseq/pull/9610)
 		- I18n: Russian [#9645](https://github.com/logseq/logseq/pull/9645), pt-BR [#9655](https://github.com/logseq/logseq/pull/9655), Turkish [#9686](https://github.com/logseq/logseq/pull/9686) [#9716](https://github.com/logseq/logseq/pull/9716), Spanish [#9665](https://github.com/logseq/logseq/pull/9665)
-		- Polish details for the plugin fenced code block [#9590](https://github.com/logseq/logseq/pull/9590)
+		- Polish details for the plugin fenced code block [#9590](https://github.com/logseq/logseq/pull/9590) - [Documentation](https://docs.logseq.com/#/page/code%20block)
 		- Plugin marketplace enhancements [#9609](https://github.com/logseq/logseq/pull/9609)
 		- Plugin API:
 			- Support right sidebar item type as string [#9701](https://github.com/logseq/logseq/pull/9701)

From c76a9b3b29a771dfb31cb611d82ea2e0807c4ef1 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 28 Jun 2023 09:56:18 -0400
Subject: [PATCH 050/196] Update slides

---
 pages/slide.md | 21 ++++++++++-----------
 1 file changed, 10 insertions(+), 11 deletions(-)

diff --git a/pages/slide.md b/pages/slide.md
index ada5ddc..bf05684 100644
--- a/pages/slide.md
+++ b/pages/slide.md
@@ -6,15 +6,14 @@ platforms:: [[All Platforms]]
 - Logseq's slide feature is powered by the awesome [Reveal.js](https://revealjs.com/).
   background-image:: https://images.unsplash.com/photo-1498855926480-d98e83099315
 - ## Usage
-	- 1. Go to a specific non-journal page, click the slide icon right next to the file link.
+	- Go to a specific non-journal page, right click on the page title and select `View as slides`.
+	  logseq.order-list-type:: number
 	  It'll open the current page's slide in the right sidebar.
-	- 2. Press `f` to open the slide in _fullscreen_ mode.
-	- TODO Update usage as this seems out of date #docs
-- **Questions**
-	- 1. How to add a background image for a block?
-		- Add a `background-image` property
-		  #+BEGIN_EXAMPLE
-		  background-image:: https://images.unsplash.com/photo-1498855926480-d98e83099315
-		  #+END_EXAMPLE
-	- How do I set other attributes?
-		- Replace the attribute name `data-xyz` with `xyz`.
\ No newline at end of file
+	- Press `f` to open the slide in _fullscreen_ mode.
+	  logseq.order-list-type:: number
+- ## Functionality
+	- To add a background image to a block, add a `background-image` property
+	  #+BEGIN_EXAMPLE
+	  background-image:: https://images.unsplash.com/photo-1498855926480-d98e83099315
+	  #+END_EXAMPLE
+	- To add data attributes, replace the attribute name `data-xyz` with `xyz`.
\ No newline at end of file

From e027bfd966b5afeb9b7c8d26c725c49ab03d63e0 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 28 Jun 2023 10:35:03 -0400
Subject: [PATCH 051/196] Clean up page and block embeds

Merge competing pages and add Command blocks for them
---
 pages/Page and block embeds.md |  2 --
 pages/Whiteboard.md            |  2 +-
 pages/block_embed.md           | 31 +++++++++++++++++--------------
 pages/contents.md              |  2 +-
 pages/page_embed.md            | 30 ++++++++++++++++++------------
 pages/term___embedded block.md |  7 -------
 pages/term___embedded page.md  |  7 -------
 7 files changed, 37 insertions(+), 44 deletions(-)
 delete mode 100644 pages/Page and block embeds.md
 delete mode 100644 pages/term___embedded block.md
 delete mode 100644 pages/term___embedded page.md

diff --git a/pages/Page and block embeds.md b/pages/Page and block embeds.md
deleted file mode 100644
index 2b2d770..0000000
--- a/pages/Page and block embeds.md	
+++ /dev/null
@@ -1,2 +0,0 @@
-- {{embed [[term/embedded page]] }}
-- {{embed [[term/embedded block]] }}
\ No newline at end of file
diff --git a/pages/Whiteboard.md b/pages/Whiteboard.md
index 138c2a3..7ae43fa 100644
--- a/pages/Whiteboard.md
+++ b/pages/Whiteboard.md
@@ -52,7 +52,7 @@ alias:: Whiteboards
 				- [[Triangle]]
 			- [[Global color swatch]]
 			- [[Global scale select]]
-		- You can drag and drop [[Pages]] and [[Blocks]] from both sidebars to the canvas to create [[Page and block embeds]] . Dropping images from your local filesystem is also supported. You can also select a particular block of text, and then drag it to the canvas to create a new block.
+		- You can drag and drop [[Pages]] and [[Blocks]] from both sidebars to the canvas to create [[Page embed]]s and [[Block embed]]s . Dropping images from your local filesystem is also supported. You can also select a particular block of text, and then drag it to the canvas to create a new block.
 		- Embeds can also be created by copy pasting block references, images and urls. Depending on the domain and the structure of the url, a special [[Whiteboard/Object]] might be created. [[Whiteboards]] currently support [[Youtube videos]] and [[Tweets]]. The rest will be embedded as an iFrame object.
 - # Functionality
 	- Logseq [[Whiteboards]] are local-first like the rest of the software.
diff --git a/pages/block_embed.md b/pages/block_embed.md
index b1a7518..d11cb5a 100644
--- a/pages/block_embed.md
+++ b/pages/block_embed.md
@@ -1,15 +1,18 @@
----
-title: Block embed
-tags: [[embed]]
----
+title:: Block embed
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+alias:: term/embedded block
+tags:: embed
+description:: Also known as block embedding, this allows a portion of a page to be displayed within another. Edits made to the embedded content are also made in the referenced content.
 
-- Also known as block embedding allows a portion of a page to be displayed within another. Edits made to the embedded content are also made in the referenced content.
-    - Create a block embed by :
-        - Typing `{{{embed ((block id))}}}`
-    - An embed example
-      {{{embed ((5fbf4fbf-82c5-4d81-ba82-b66726bda00c)) }}}
--
-  #+BEGIN_TIP
-  - Block id's can be generated by right-clicking the bullet point next to a block and selecting 'copy block ref'
-  - Auto-completion is available for blocks and will automatically generate and insert a block id
-  #+END_TIP
\ No newline at end of file
+## Usage
+	- Create a block embed by typing `{{{embed ((block id))}}}` or typing the `/Block embed` command:
+	  collapsed:: true
+	  type:: [[Command]]
+	  name:: Block embed
+	  description:: Embeds a block with autocompletion ready for the block
+	- An embed example
+	  {{{embed ((5fbf4fbf-82c5-4d81-ba82-b66726bda00c)) }}}
+## Functionality
+	- Embedded block is marked by a different colored background.
+	- Auto-completion is available for blocks and will automatically generate and insert a block id
\ No newline at end of file
diff --git a/pages/contents.md b/pages/contents.md
index 9dbef6c..de73c7d 100644
--- a/pages/contents.md
+++ b/pages/contents.md
@@ -25,7 +25,7 @@
 	- [Backlink]([[term/backlink]])
 	- [[Knowledge Graph]]
 	- [[Page and block references]]
-	- [[Page and block embeds]]
+	- [[Page embed]] and [[Block embed]]
 	- [[Tasks]]
 	- [[Commands]]
 	- [[Advanced commands]]
diff --git a/pages/page_embed.md b/pages/page_embed.md
index 06c285d..e107fb4 100644
--- a/pages/page_embed.md
+++ b/pages/page_embed.md
@@ -1,13 +1,19 @@
----
-title: Page embed
-tags: [[embed]]
-description:: See [[Block embed]] for block version of this
----
+title:: Page embed
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+alias:: term/embedded page
+tags:: [[embed]]
+description:: Allows an entire page to be displayed within another. Also known as transclusion. See [[Block embed]] for block version of this
 
-- Also commonly known as transclusion, page embedding allows an entire page to be displayed within another.
-- Create a page embed by:
-	- Typing `{{{embed [[page name]]}}}`
-- #+BEGIN_TIP
-  - Edits made to the embedded content are also made to the referenced content.
-  - Embedding does not contribute to a page's [[Linked References]]
-   #+END_TIP
+## Usage
+	- Create a page embed by typing `{{{embed [[page name]]}}}` or by using the `/Page embed` command:
+	  collapsed:: true
+		- type:: [[Command]]
+		  name:: Page embed
+		  description:: Embeds a page with autocompletion ready for the page
+	- For example, embedding [[term/page]] looks like this:
+		- {{embed [[term/page]]}}
+## Functionality
+	- Edits made to the embedded content are also made to the referenced content.
+	- Embedded page is marked by a different colored background.
+	- Embedding does not contribute to a page's [[Linked References]]
\ No newline at end of file
diff --git a/pages/term___embedded block.md b/pages/term___embedded block.md
deleted file mode 100644
index e9251e2..0000000
--- a/pages/term___embedded block.md	
+++ /dev/null
@@ -1,7 +0,0 @@
-- description:
-	- shows a block from one Logseq page within a block of a different page and is marked by a different colored background.
-- produced by:
-	- an embedded block is produced by typing /embed, selecting Block embed, and pasting the block ref at the default cursor location. The result, in editing mode, will be something like this: `{{embed ((60011009-ddd9-4a8c-8925-37249791f525))}}`
-- example:
-	- type `/Block Embed`
-	- {{embed ((60a77d63-7340-4c1d-8bbc-68bd4e49fc6c)) }}
\ No newline at end of file
diff --git a/pages/term___embedded page.md b/pages/term___embedded page.md
deleted file mode 100644
index 0766d5a..0000000
--- a/pages/term___embedded page.md	
+++ /dev/null
@@ -1,7 +0,0 @@
-- description:
-  - shows one Logseq page within a block of a different page and is marked by a different colored background
-- produced by:
-  - an embedded page is produced by typing /embed, selecting Page embed, and pasting the page reference at the default cursor location. The result, in editing mode, will be something like this: `{{embed [[term/page]]}}`
-- example:
-  - type `/Page Embed`
-  - {{embed [[term/page]]}}
\ No newline at end of file

From 8dc5687d95f26f9aebe72c1eaea15fb5434936b1 Mon Sep 17 00:00:00 2001
From: Konstantinos Kaloutas <konstantinos@logseq.com>
Date: Wed, 28 Jun 2023 18:13:33 +0300
Subject: [PATCH 052/196] add PDF docs

---
 pages/Whiteboard.md                     | 3 ++-
 pages/Whiteboard___Action Bar___Edit.md | 3 +++
 pages/Whiteboard___Object.md            | 5 ++++-
 pages/Whiteboard___Object___PDF.md      | 6 ++++++
 4 files changed, 15 insertions(+), 2 deletions(-)
 create mode 100644 pages/Whiteboard___Action Bar___Edit.md
 create mode 100644 pages/Whiteboard___Object___PDF.md

diff --git a/pages/Whiteboard.md b/pages/Whiteboard.md
index 138c2a3..472180c 100644
--- a/pages/Whiteboard.md
+++ b/pages/Whiteboard.md
@@ -53,7 +53,8 @@ alias:: Whiteboards
 			- [[Global color swatch]]
 			- [[Global scale select]]
 		- You can drag and drop [[Pages]] and [[Blocks]] from both sidebars to the canvas to create [[Page and block embeds]] . Dropping images from your local filesystem is also supported. You can also select a particular block of text, and then drag it to the canvas to create a new block.
-		- Embeds can also be created by copy pasting block references, images and urls. Depending on the domain and the structure of the url, a special [[Whiteboard/Object]] might be created. [[Whiteboards]] currently support [[Youtube videos]] and [[Tweets]]. The rest will be embedded as an iFrame object.
+		- Embeds can also be created by copy pasting block references and urls. Depending on the domain and the structure of the url, a special [[Whiteboard/Object]] might be created. [[Whiteboards]] currently support [[Youtube videos]] and [[Tweets]]. The rest will be embedded as an iFrame object.
+		- Dragging and dropping a file could also create [[Whiteboard/Object]]. The currently supported formats are PDFs, images and videos.
 - # Functionality
 	- Logseq [[Whiteboards]] are local-first like the rest of the software.
 	  collapsed:: true
diff --git a/pages/Whiteboard___Action Bar___Edit.md b/pages/Whiteboard___Action Bar___Edit.md
new file mode 100644
index 0000000..17d1e5e
--- /dev/null
+++ b/pages/Whiteboard___Action Bar___Edit.md	
@@ -0,0 +1,3 @@
+alias:: Edit
+type:: [[Tool]]
+platforms:: [[All Platforms]] except [[Publish Web]]
diff --git a/pages/Whiteboard___Object.md b/pages/Whiteboard___Object.md
index 6b06d76..bb41ea7 100644
--- a/pages/Whiteboard___Object.md
+++ b/pages/Whiteboard___Object.md
@@ -75,4 +75,7 @@ url:: {{docs-base-url Whiteboard%2FObject}}
 				- [[Url input]]
 				- [[Open embedded url]]
 				- [[Link]]
--
+		- [[PDF]]
+			- supports:
+				- [[Edit]]
+				- [[Open embedded url]]
\ No newline at end of file
diff --git a/pages/Whiteboard___Object___PDF.md b/pages/Whiteboard___Object___PDF.md
new file mode 100644
index 0000000..13997c9
--- /dev/null
+++ b/pages/Whiteboard___Object___PDF.md
@@ -0,0 +1,6 @@
+alias:: PDF
+type:: [[Whiteboard/Object]]
+description:: Embedded PDF
+supports::  Edit PDF, Link to page/block
+
+-
\ No newline at end of file

From ecc8c6199b19aa841c07beaf55bed34bd443f2a9 Mon Sep 17 00:00:00 2001
From: Konstantinos Kaloutas <konstantinos@logseq.com>
Date: Thu, 29 Jun 2023 09:36:18 +0300
Subject: [PATCH 053/196] add warning to custom css/js docs

---
 pages/custom.css.md | 2 ++
 pages/custom.js.md  | 1 +
 2 files changed, 3 insertions(+)

diff --git a/pages/custom.css.md b/pages/custom.css.md
index 5fb58c3..f507285 100644
--- a/pages/custom.css.md
+++ b/pages/custom.css.md
@@ -3,6 +3,8 @@ type:: [[Feature]]
 platforms:: [[All Platforms]] 
 description:: Local config file, logseq/custom.css, loads custom css for a graph on startup
 
+- ## Usage
+	- > **Please use this feature with caution.** Introducing custom css rules might result in unexpected behavior. You are responsible for the implementation and the maintenance of the code. Avoid pasting css code that you don't fully understand, for security and stability reasons.
 - ## Functionality
 	- Define a `logseq/custom.css` file in order to have any custom css load
 - ## Additional Links
diff --git a/pages/custom.js.md b/pages/custom.js.md
index 6fa2fa1..a5907d4 100644
--- a/pages/custom.js.md
+++ b/pages/custom.js.md
@@ -5,5 +5,6 @@ description:: Local config file, logseq/custom.js, loads custom js for a graph o
 
 - ## Usage
 	- First time you load a custom.js file, you are prompted to confirm you want to load it.
+	- > **Please use this feature with caution.** Introducing custom javascript might result in unexpected behavior. You are responsible for the implementation and the maintenance of the code. Avoid pasting javascript code that you don't fully understand, for security and stability reasons.
 - ## Functionality
 	- Define a `logseq/custom.js` to have any custom js load
\ No newline at end of file

From 360edd43618d3a968e2f8315ad207ef381722565 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 4 Jul 2023 10:23:01 -0400
Subject: [PATCH 054/196] Fix page links from last commit

---
 pages/Whiteboard.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Whiteboard.md b/pages/Whiteboard.md
index 132bd42..fb19392 100644
--- a/pages/Whiteboard.md
+++ b/pages/Whiteboard.md
@@ -52,7 +52,7 @@ alias:: Whiteboards
 				- [[Triangle]]
 			- [[Global color swatch]]
 			- [[Global scale select]]
-		- You can drag and drop [[Pages]] and [[Blocks]] from both sidebars to the canvas to create [[Page and block embeds]] . Dropping images from your local filesystem is also supported. You can also select a particular block of text, and then drag it to the canvas to create a new block.
+		- You can drag and drop [[Pages]] and [[Blocks]] from both sidebars to the canvas to create [[Page embed]]s and [[Block embed]]s. Dropping images from your local filesystem is also supported. You can also select a particular block of text, and then drag it to the canvas to create a new block.
 		- Embeds can also be created by copy pasting block references and urls. Depending on the domain and the structure of the url, a special [[Whiteboard/Object]] might be created. [[Whiteboards]] currently support [[Youtube videos]] and [[Tweets]]. The rest will be embedded as an iFrame object.
 		- Dragging and dropping a file could also create a [[Whiteboard/Object]]. The currently supported formats are PDFs, images and videos.
 - # Functionality

From 168087f918d5c32471290fe92d4150d4666ad0af Mon Sep 17 00:00:00 2001
From: Danny Garside <dannygarside@outlook.com>
Date: Mon, 17 Jul 2023 11:35:25 -0400
Subject: [PATCH 055/196] Minor typos and wording tweaks

---
 CONTRIBUTING.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index a68d6e6..b51f7d1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -16,7 +16,7 @@ We also have [documentation tasks](https://github.com/orgs/logseq/projects/5/vie
 
 A feature page has a specific format as described in
 https://docs.logseq.com/#/page/Feature. Use the `Feature` template when starting
-a new page. Please filling in as many of the properties and headers as you can.
+a new page. Please fill in as many of the properties and headers as you can.
 If you only know enough to fill in parts of a page, that's fine. Just add a
 `TODO Write Something Descriptive Here #docs` with what's left to do.
 
@@ -37,10 +37,10 @@ file in Github](https://docs.github.com/en/repositories/working-with-files/manag
 For any other contribution it helps to make changes locally so you see you can how it looks in Logseq. In order to do this you should:
 
 1. Ensure you have [git](https://git-scm.com/downloads) installed.
-2. Fork and Clone THIS REPO. The upstream should be set to the FORKED REPO. If you have no idea to do, check:
+2. Fork and Clone THIS REPO. The upstream should be set to the FORKED REPO. If you need more information on what this means, read:
 * [About forks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)
 * [Cloning and forking repositories from GitHub Desktop](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop)
-3. Add the cloned local repo (of your FORKED REPO) to Logseq via the `Add new graph`button on the top left dropdown menu. Select the directory where you cloned the repo.
+3. Add the cloned local repo (of your FORKED REPO) to Logseq via the `Add new graph` button on the top left dropdown menu. Select the directory where you cloned the repo.
 4. Create a branch off of master. The following two commands create a branch called `branch-name` and navigates onto it.
 
 ```git

From 6423f3100b67d6cf9423c4d9723ca7279ade7187 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 19 Jul 2023 22:40:22 +0800
Subject: [PATCH 056/196] chore(release): release 0.9.11

---
 pages/Changelog.md | 52 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 52 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index a2de239..961f9ce 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,3 +1,55 @@
+- ## Beta 0.9.11 [[Jul 19th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.11>
+	- [[Breaking Changes]]
+		- Upgrade Electron to 24 [#9482](https://github.com/logseq/logseq/pull/9482) #[[minor change]]. Windows 7/8/8.1 users should upgrade their OS or stick to an old version of Logseq.
+	- [[Features]]
+		- Add PDF shape to Whiteboards [#9743](https://github.com/logseq/logseq/pull/9743) ![Demo Recording](https://github.com/logseq/logseq/assets/10744960/53454656-861f-4607-bf7c-78a22c4e88cd#demo.mp4)
+	- [[Thanks]]
+		- [[Allan Chain]]
+			- Include katex resources from npm in [#9712](https://github.com/logseq/logseq/pull/9712)
+		- [[Bad3r]]
+			- Fix CVE-2023-2931 in Electron 24 in [#9854](https://github.com/logseq/logseq/pull/9854) #[[minor change]]
+			- Fix CI stale actions in [#9777](https://github.com/logseq/logseq/pull/9777)
+		- [[gfgafn]]
+			- Fix delete character which has more than one UTF-16 code unit using Delete key in [#9837](https://github.com/logseq/logseq/pull/9837)
+		- [[Rui Sun]]
+			- Add Chinese i18n translations and make more of right-sidebar, query, slide, and bug-report translatable in [#9801](https://github.com/logseq/logseq/pull/9801)
+		- [[ingepettersen]]
+			- Update Norwegian translation in [#9771](https://github.com/logseq/logseq/pull/9771)
+		- [[jihuayu]]
+			- Fix unable to change theme mode in theme row for zh-cn lang in [#9884](https://github.com/logseq/logseq/pull/9884)
+		- [[Lewis Sparlin]]
+			- Fix positioning of swipe-left action bar on iOS mobile app in [#9853](https://github.com/logseq/logseq/pull/9853)
+			- Use flex-col for schedule modal on smaller screens in [#9776](https://github.com/logseq/logseq/pull/9776)
+		- [[megayu]]
+			- Enhance cut and copy blocks in [#9094](https://github.com/logseq/logseq/pull/9094)
+		- [[Johan Penttinen]]
+			- Add support for Android 13 themed icons in [#9862](https://github.com/logseq/logseq/pull/9862)
+		- [[phlet]]
+			- Fix About dialog shows the version number twice (macOS) in [#9786](https://github.com/logseq/logseq/pull/9786)
+		- [[queeup]]
+			- Update Turkish translation in [#9773](https://github.com/logseq/logseq/pull/9773), [#9813](https://github.com/logseq/logseq/pull/9813)
+		- [[ROCKTAKEY]]
+			- Add additional Japanise translation in [#9792](https://github.com/logseq/logseq/pull/9792)
+	- [[Fixed issues]]
+		- Whiteboards
+			- Blur on empty title and select all on shape labels [#9793](https://github.com/logseq/logseq/pull/9793)
+		- Fix positioning of swipe-left action bar on iOS mobile app [#9853](https://github.com/logseq/logseq/pull/9853)
+		- Content overwritten caused by smart merge on mobile platforms [#9856](https://github.com/logseq/logseq/pull/9856)
+		- Fix header button drag region [#9861](https://github.com/logseq/logseq/pull/9861)
+		- Fix unable to change theme mode in theme row for zh-cn  [#9884](https://github.com/logseq/logseq/pull/9884)
+		- Fix delete character which has more than one UTF-16 code unit using `Delete` key [#9837](https://github.com/logseq/logseq/pull/9837)
+		- Mobile startup fixes [#9828](https://github.com/logseq/logseq/pull/9828) [#9795](https://github.com/logseq/logseq/pull/9795)
+		- Plugin API: hook fenced code renderer for multiple providers [#9847](https://github.com/logseq/logseq/pull/9847)
+		- Fix sometimes the API server autostart not working [#9878](https://github.com/logseq/logseq/pull/9878)
+		- Fix smart merge for Logseq Sync [#9840](https://github.com/logseq/logseq/pull/9840) [#9831](https://github.com/logseq/logseq/pull/9831)
+		- Close context menu when page navigates [#9882](https://github.com/logseq/logseq/pull/9882)
+		- Fix graph name in dropdown for android [#9704](https://github.com/logseq/logseq/pull/9704)
+		- Use flex-col for schedule modal on smaller screens [#9776](https://github.com/logseq/logseq/pull/9776)
+	- [[Enhancement]]
+		- Enhance cut and copy blocks [#9094](https://github.com/logseq/logseq/pull/9094)
+		- Android 13 themed icons support [#9862](https://github.com/logseq/logseq/pull/9862)
+		- I18n: Japanise [#9792](https://github.com/logseq/logseq/pull/9792), Chinese [#9801](https://github.com/logseq/logseq/pull/9801), Norwegian [#9771](https://github.com/logseq/logseq/pull/9771), Turkish [#9773](https://github.com/logseq/logseq/pull/9773) [#9813](https://github.com/logseq/logseq/pull/9813)
 - ## Beta 0.9.10 [[Jun 28th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.10>
 	- [[Features]]

From 735312546edd9177fe904fd8fa0badbc84bb4e3d Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 19 Jul 2023 22:41:27 +0800
Subject: [PATCH 057/196] fix typo

---
 pages/Changelog.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 961f9ce..8a4845d 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -30,7 +30,7 @@
 		- [[queeup]]
 			- Update Turkish translation in [#9773](https://github.com/logseq/logseq/pull/9773), [#9813](https://github.com/logseq/logseq/pull/9813)
 		- [[ROCKTAKEY]]
-			- Add additional Japanise translation in [#9792](https://github.com/logseq/logseq/pull/9792)
+			- Add additional Japanese translation in [#9792](https://github.com/logseq/logseq/pull/9792)
 	- [[Fixed issues]]
 		- Whiteboards
 			- Blur on empty title and select all on shape labels [#9793](https://github.com/logseq/logseq/pull/9793)
@@ -49,7 +49,7 @@
 	- [[Enhancement]]
 		- Enhance cut and copy blocks [#9094](https://github.com/logseq/logseq/pull/9094)
 		- Android 13 themed icons support [#9862](https://github.com/logseq/logseq/pull/9862)
-		- I18n: Japanise [#9792](https://github.com/logseq/logseq/pull/9792), Chinese [#9801](https://github.com/logseq/logseq/pull/9801), Norwegian [#9771](https://github.com/logseq/logseq/pull/9771), Turkish [#9773](https://github.com/logseq/logseq/pull/9773) [#9813](https://github.com/logseq/logseq/pull/9813)
+		- I18n: Japanese [#9792](https://github.com/logseq/logseq/pull/9792), Chinese [#9801](https://github.com/logseq/logseq/pull/9801), Norwegian [#9771](https://github.com/logseq/logseq/pull/9771), Turkish [#9773](https://github.com/logseq/logseq/pull/9773) [#9813](https://github.com/logseq/logseq/pull/9813)
 - ## Beta 0.9.10 [[Jun 28th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.10>
 	- [[Features]]

From 37a2abbeebea2451a82360f9efe76b094670cdd3 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 25 Jul 2023 09:54:14 -0400
Subject: [PATCH 058/196] Add basic docs for math typesetting

---
 pages/Code block.md |  2 +-
 pages/Math Block.md | 28 ++++++++++++++++++++++++++++
 2 files changed, 29 insertions(+), 1 deletion(-)
 create mode 100644 pages/Math Block.md

diff --git a/pages/Code block.md b/pages/Code block.md
index b6aa4b5..09111d8 100644
--- a/pages/Code block.md	
+++ b/pages/Code block.md	
@@ -14,5 +14,5 @@ description:: Renders a block of code with [[Codemirror]] support for a variety
 	  ```
 ## Functionality
 	- This feature provides support for languages through [CodeMirror's modes](https://codemirror.net/5/mode/index.html)
-- ## Additional Links
+## Additional Links
 	- See [[Calculator]] and [[ClojureScript Eval in a Block]] features which rely on code blocks
\ No newline at end of file
diff --git a/pages/Math Block.md b/pages/Math Block.md
new file mode 100644
index 0000000..afcba3e
--- /dev/null
+++ b/pages/Math Block.md	
@@ -0,0 +1,28 @@
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+description:: Write and render math using https://katex.org/ syntax
+
+## Usage
+	- Inline math is written in a block by wrapping text with `$`. For example:
+		- #+BEGIN_EXAMPLE
+		  $\ce{Hg^2+ ->[I-] HgI2 ->[I-] [Hg^{II}I4]^2-}$
+		  #+END_EXAMPLE
+		  becomes
+		  $\ce{Hg^2+ ->[I-] HgI2 ->[I-] [Hg^{II}I4]^2-}$
+	- Multi-line math is written in a block by wrapping text with `$$`. For example:
+		- #+BEGIN_EXAMPLE
+		  $$
+		  \frac{1}{\Bigl(\sqrt{\phi \sqrt{5}}-\phi\Bigr) e^{\frac25 \pi}} = 1+\frac{e^{-2\pi}}
+		  {1+\frac{e^{-4\pi}} {1+\frac{e^{-6\pi}} {1+\frac{e^{-8\pi}} {1+\cdots} } } }
+		  $$
+		  #+END_EXAMPLE
+		  becomes
+		  $$
+		  \frac{1}{\Bigl(\sqrt{\phi \sqrt{5}}-\phi\Bigr) e^{\frac25 \pi}} = 1+\frac{e^{-2\pi}}
+		  {1+\frac{e^{-4\pi}} {1+\frac{e^{-6\pi}} {1+\frac{e^{-8\pi}} {1+\cdots} } } }
+		  $$
+## Functionality
+	- For documentation of what is supported, see https://katex.org/docs/supported.html and https://katex.org/docs/support_table.html.
+	- In addition to math support, chemistry support is provided by the [mchem package](https://github.com/KaTeX/KaTeX/tree/main/contrib/mhchem).
+## Additional Links
+	- https://github.com/xyhp915/logseq-extensions-plus - Plugin that provides physics support for katex
\ No newline at end of file

From f30830679c0889314c5c4aa19d8bcc3f1ac4bb29 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 2 Aug 2023 09:19:03 +0800
Subject: [PATCH 059/196] chore: release 0.9.13, revoke 0.9.12

---
 pages/Changelog.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 8a4845d..cb8eb49 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,3 +1,25 @@
+## Beta 0.9.13 [[Aug 2nd, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.13>
+	- [[Thanks]]
+		- [[atxulo]]
+			- Improvements in Spanish translation in [#9896](https://github.com/logseq/logseq/pull/9896)
+		- [[einmeterhecht]]
+			- Translate all missing entries for German in [#9948](https://github.com/logseq/logseq/pull/9948)
+		- [[Ulices]]
+			- Spanish translation update in [#9732](https://github.com/logseq/logseq/pull/9732)
+		- [[ingepettersen]]
+			- Norwegian translation update in [#9905](https://github.com/logseq/logseq/pull/9905)
+		- [[ROCKTAKEY]]
+			- Add additional Japanese translation in [#9909](https://github.com/logseq/logseq/pull/9909)
+	- [[Fixed issues]]
+		- Draw: persist when updating existing elements [#9919](https://github.com/logseq/logseq/pull/9919)
+		- Setting default sidebar pages on config [#9959](https://github.com/logseq/logseq/pull/9959)
+		- Editing of global config on Windows [#9932](https://github.com/logseq/logseq/pull/9932)
+		- Image URL tag referrer policy fix for mobile platforms [#9895](https://github.com/logseq/logseq/pull/9895)
+		- Page history of Logseq Sync on mobile platforms [#9933](https://github.com/logseq/logseq/pull/9933)
+		- Cold start merge strategy of Smart Merge [#9953](https://github.com/logseq/logseq/pull/9953)
+	- [[Enhancement]]
+		- I18n updates: Spanish [#9896](https://github.com/logseq/logseq/pull/9896) [#9732](https://github.com/logseq/logseq/pull/9732), German [#9948](https://github.com/logseq/logseq/pull/9948), Norwegian [#9905](https://github.com/logseq/logseq/pull/9905), Japanese [#9909](https://github.com/logseq/logseq/pull/9909)
 - ## Beta 0.9.11 [[Jul 19th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.11>
 	- [[Breaking Changes]]

From d265dbcd7cb2c35d92c7dd45c4eba1d7251c0d7c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Horacio=20Mijail=20Ant=C3=B3n=20Quiles?=
 <4139546+hmijail@users.noreply.github.com>
Date: Tue, 8 Aug 2023 23:52:47 +1000
Subject: [PATCH 060/196] Update PDF highlights.md

Add a warning about PDFs not being removed automatically.
---
 pages/PDF highlights.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pages/PDF highlights.md b/pages/PDF highlights.md
index de667af..cfdfd9c 100644
--- a/pages/PDF highlights.md	
+++ b/pages/PDF highlights.md	
@@ -7,6 +7,7 @@ platforms:: [[Desktop]]
   This only works on the desktop app at the moment.
   #+END_NOTE
 - **How to add a PDF file?**
+	- NOTE: PDF files get stored inside your graph's assets folder. There's currently no automated way to remove them even if unlinked. You might be able to remove them manually to reclaim space.
 	- There're two ways to add PDF files to your graph:
 		- 1. Create a new block in any page, drag your PDF file to the new block.
 		- 2. Type '/upload an asset' and choose your PDF file.

From b9458cad5b2bb93471d51d84134987c3199e8046 Mon Sep 17 00:00:00 2001
From: da5nsy <dannygarside@outlook.com>
Date: Thu, 10 Aug 2023 11:54:22 +0100
Subject: [PATCH 061/196] add info on CANCELLED etc, and minor wording changes

---
 pages/Tasks.md | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/pages/Tasks.md b/pages/Tasks.md
index f5cb982..e682a42 100644
--- a/pages/Tasks.md
+++ b/pages/Tasks.md
@@ -3,18 +3,25 @@ alias:: Todos
 platforms:: [[All Platforms]]
 
 - ## Usage
-	- Logseq comes with two built-in flavors to mark your block with built-in workflow mark keywords and manage your tasks:
+	- Logseq comes with two built-in flavors to mark your block with built-in workflow marker keywords and manage your tasks:
 	  + `LATER` -> `NOW` -> `DONE` flavor (default)
 	  + `TODO` -> `DOING` -> `DONE` flavor 
-	  + You can toggle between those two flavors in setting page
-	- There are two ways to attach workflow mark to your task(block)
-		- when editing the block, press `Ctrl/Cmd+enter` to cycle through the workflow mark
-		- type these mark as command directly, eg `/LATER` `/NOW` `/DONE` `/TODO` etc..
+	  + You can toggle between those two flavors in the settings page
+	- There are two ways to attach workflow markers to your task block:
+		- when editing the block, press `Ctrl/Cmd+enter` to cycle through the workflow markers
+		- type these command directly, eg "LATER" "NOW" "DONE" "TODO" etc.
 		- Some examples:
 		  todo:: 1621908710666
 			- LATER do grocery
 			- NOW play with Logseq
 			- DONE watch Doctor Who
+				- (_this is how `DONE` renders_)
+	- In addition to the workflows described above, there's also `CANCELED`/`CANCELLED`, `IN-PROGRESS`,  and `WAIT`/`WAITING` markers which can be typed directly.
+		- Some examples:
+			- CANCELLED the boring thing
+				- (_this is how `CANCELLED` renders_)
+			- IN-PROGRESS the fun thing
+			- WAIT the slow thing
 - ## Functionality
 	- ### Priorities
 		- Logseq comes with three optional, built-in priorities that can be set with commands (`/A`, `/B`, `/C`):
@@ -28,8 +35,9 @@ platforms:: [[All Platforms]]
 			  name:: C
 			  description:: Lowest priority
 			- Example:
-				- LATER [#A] research balalah is a top priority
-				- LATER [#C] do grocery has lowest priority
+				- LATER [#A] big important and urgent thing
+				- LATER [#C] the lower priority thing
+			- Again, these can either be added by using the commands (typing `/A`), or manually added by writing `[#A]` at the start of the block after the marker.
 	- ### Deadline and Scheduled
 		- There are two commands for setting dates on a block:
 			- type:: [[Command]]
@@ -42,7 +50,7 @@ platforms:: [[All Platforms]]
 			  description:: Type command `/Scheduled` to setup a scheduled date for a block
 				- eg: send John a birthday card Monday
 				  SCHEDULED: <2021-05-31 Mon>
-		- Both of the above commands work on blocks, not just tasks.
+		- Both of the above commands work on regular blocks too, not just tasks.
 		- Both of the above commands default to displaying blocks that are coming up soon. You can configure how soon with `:scheduled/future-days`  in [[config.edn]].
 		- Both of above commands support to mark the task as repeated:
 		  after typing the command and click `Add repeater` in the date picker

From 6327c90eb9bca598101457cb79bd358d7454117e Mon Sep 17 00:00:00 2001
From: da5nsy <dannygarside@outlook.com>
Date: Thu, 10 Aug 2023 11:59:50 +0100
Subject: [PATCH 062/196] clarify distinction between command and direct input

---
 pages/Tasks.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Tasks.md b/pages/Tasks.md
index e682a42..d1e330b 100644
--- a/pages/Tasks.md
+++ b/pages/Tasks.md
@@ -9,7 +9,7 @@ platforms:: [[All Platforms]]
 	  + You can toggle between those two flavors in the settings page
 	- There are two ways to attach workflow markers to your task block:
 		- when editing the block, press `Ctrl/Cmd+enter` to cycle through the workflow markers
-		- type these command directly, eg "LATER" "NOW" "DONE" "TODO" etc.
+		- type these commands directly (eg `/LATER`) anywhere in the block, or manually write the keyword at the start of the block (eg `LATER do grocery`)
 		- Some examples:
 		  todo:: 1621908710666
 			- LATER do grocery

From 846344006488374677578d16fb7a79f63790288b Mon Sep 17 00:00:00 2001
From: da5nsy <dannygarside@outlook.com>
Date: Thu, 10 Aug 2023 12:07:48 +0100
Subject: [PATCH 063/196] add note about manually clicking to change to DONE

---
 pages/Tasks.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pages/Tasks.md b/pages/Tasks.md
index d1e330b..a35a78d 100644
--- a/pages/Tasks.md
+++ b/pages/Tasks.md
@@ -22,6 +22,7 @@ platforms:: [[All Platforms]]
 				- (_this is how `CANCELLED` renders_)
 			- IN-PROGRESS the fun thing
 			- WAIT the slow thing
+	- Once the block has been created, if it shows an empty tick-box at the start of the block you can manually click on that box to get it to change to `DONE`, which can be rather satisfying to do.
 - ## Functionality
 	- ### Priorities
 		- Logseq comes with three optional, built-in priorities that can be set with commands (`/A`, `/B`, `/C`):

From 682a8ed7ef1cc37f3f533fe0f7e03ccd6acbf753 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 15 Aug 2023 14:31:07 -0400
Subject: [PATCH 064/196] Queries are easy to use with the builder

and shouldn't be considered advanced. Made this change partially
inspired by https://mastodon.social/@alxlg/110884528706340089
---
 pages/contents.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/contents.md b/pages/contents.md
index de73c7d..3da9861 100644
--- a/pages/contents.md
+++ b/pages/contents.md
@@ -42,6 +42,7 @@
 	- [[Zotero]] integration
 	- [[Embed Media - Audio, Photos, Videos]]
 	- [[Plugins]]
+	- [[Queries]] and [[Query Builder]]
 	- [[Whiteboard]]
 	- [[Tables]]
 - [[Logseq School]]
@@ -53,7 +54,6 @@
 - ✨ [[Tips and Tricks]]
 - [[Advanced Logseq]]
 	- [[Keyboard shortcuts]]
-	- [[Queries]]
 	- [[Advanced Queries]]
 	- [[Hiccup]]
 	- [[Filename format]]

From 22e1fa3ad0211313eca152c35f6d51eef636bc0e Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 17 Aug 2023 21:11:55 +0800
Subject: [PATCH 065/196] chore(release): release 0.9.14

---
 pages/Changelog.md | 34 ++++++++++++++++++++++++++++++++--
 1 file changed, 32 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index cb8eb49..e24e2fb 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,35 @@
-## Beta 0.9.13 [[Aug 2nd, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.13>
+## Beta 0.9.14 [[Aug 17th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.14>
+#+BEGIN_NOTE
+This version introduces left sidebar and right sidebar enhancements, if you encounter some style issues, please revert to the default theme.
+#+END_NOTE
+	- [[Thanks]]
+		- [[HikoriHawky]]
+			- Add Whiteboards pen pressure support in [#9988](https://github.com/logseq/logseq/pull/9988)
+		- [[jomanhattan]]
+			- Update French translation in [#9981](https://github.com/logseq/logseq/pull/9981)
+		- [[matheusfrancisco]]
+			- Fix right sidebar empty string error caused by whiteboards names in [#10018](https://github.com/logseq/logseq/pull/10018)
+		- [[ROCKTAKEY]]
+			- Update Japanese translation in [#10004](https://github.com/logseq/logseq/pull/10004)
+		- [[situ2001]]
+			- Add drag threshold for graph view in [#9989](https://github.com/logseq/logseq/pull/9989)
+	- [[Fixed issues]]
+		- Add sub-pixel anti-aliasing for Electron [#10032](https://github.com/logseq/logseq/pull/10032)
+		- Add drag threshold for graph view [#9989](https://github.com/logseq/logseq/pull/9989)
+		- Display of embedded drawing [#9969](https://github.com/logseq/logseq/pull/9969)
+		- Sometimes template expansion inserts an additional slash [#9972](https://github.com/logseq/logseq/pull/9972)
+		- PDF Viewer: highlighted text layer is overlaid by the PDF.js built-in annotation layer [#9982](https://github.com/logseq/logseq/pull/9982)
+		- Rendering error caused by empty string of whiteboards in the right sidebar [#10018](https://github.com/logseq/logseq/pull/10018)
+	- [[Enhancement]]
+		- Left sidebar enhancements [#9880](https://github.com/logseq/logseq/pull/9880)
+		- Right sidebar enhancements #[[minor change]] [#9846](https://github.com/logseq/logseq/pull/9846)
+		- I18n: French [#9981](https://github.com/logseq/logseq/pull/9981) Japanese [#10004](https://github.com/logseq/logseq/pull/10004)
+		- Whiteboards drawing pen pressure support [#9988](https://github.com/logseq/logseq/pull/9988)
+		- PDF Viewer: support `shift + enter` to pick the previous searching results highlight [#10002](https://github.com/logseq/logseq/pull/10002)
+		- Polish UI details of the zotero search component [#10011](https://github.com/logseq/logseq/pull/10011)
+- ## Beta 0.9.13 [[Aug 2nd, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.13>
 	- [[Thanks]]
 		- [[atxulo]]
 			- Improvements in Spanish translation in [#9896](https://github.com/logseq/logseq/pull/9896)

From d970e325ae0297db3d4c08da317d6d1e07e200d4 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 22 Aug 2023 23:05:55 +0800
Subject: [PATCH 066/196] chore: release 0.9.15

---
 pages/Changelog.md | 25 ++++++++++++++++++++-----
 1 file changed, 20 insertions(+), 5 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index e24e2fb..68ca361 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,8 +1,23 @@
-## Beta 0.9.14 [[Aug 17th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.14>
-#+BEGIN_NOTE
-This version introduces left sidebar and right sidebar enhancements, if you encounter some style issues, please revert to the default theme.
-#+END_NOTE
+## Beta 0.9.15 [[Aug 22nd, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.15>
+	- [[Thanks]]
+		- [[ingepettersen]]
+			- Update Norwegian translations in [#10068](https://github.com/logseq/logseq/pull/10068)
+		- [[Ulices]]
+			- Update Spanish translations in [#10065](https://github.com/logseq/logseq/pull/10065)
+	- [[Fixed issues]]
+		- Right sidebar pane menu overflow [#10046](https://github.com/logseq/logseq/pull/10046)
+		- Disable sidebar pane content scrolling [#10071](https://github.com/logseq/logseq/pull/10071)
+		- Fix right sidebar pane header wrap and content padding [#10072](https://github.com/logseq/logseq/pull/10072)
+	- [[Enhancement]]
+		- PDF password support [#10034](https://github.com/logseq/logseq/pull/10034)
+		- Plugin API enhancements [#10034](https://github.com/logseq/logseq/pull/10034)
+		- I18n: Norwegian [#10068](https://github.com/logseq/logseq/pull/10068), Spanish [#10065](https://github.com/logseq/logseq/pull/10065)
+- ## Beta 0.9.14 [[Aug 17th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.14>
+  #+BEGIN_NOTE
+  This version introduces left sidebar and right sidebar enhancements, if you encounter some style issues, please revert to the default theme.
+  #+END_NOTE
 	- [[Thanks]]
 		- [[HikoriHawky]]
 			- Add Whiteboards pen pressure support in [#9988](https://github.com/logseq/logseq/pull/9988)

From 02b621aa3b9cae64c5616e79cdf31b3d1dc5b3fa Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 22 Aug 2023 23:09:18 +0800
Subject: [PATCH 067/196] fix: typo in link

---
 pages/Changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 68ca361..0338ef9 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -11,7 +11,7 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- Fix right sidebar pane header wrap and content padding [#10072](https://github.com/logseq/logseq/pull/10072)
 	- [[Enhancement]]
 		- PDF password support [#10034](https://github.com/logseq/logseq/pull/10034)
-		- Plugin API enhancements [#10034](https://github.com/logseq/logseq/pull/10034)
+		- Plugin API enhancements [#10022](https://github.com/logseq/logseq/pull/10022)
 		- I18n: Norwegian [#10068](https://github.com/logseq/logseq/pull/10068), Spanish [#10065](https://github.com/logseq/logseq/pull/10065)
 - ## Beta 0.9.14 [[Aug 17th, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.14>

From 090c38dfc26f0f8c29d6af3b25be03b2e5ac13ac Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 22 Aug 2023 23:21:13 +0800
Subject: [PATCH 068/196] chore: minor release intro update

---
 pages/Changelog.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 0338ef9..caf3b8f 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,6 @@
 ## Beta 0.9.15 [[Aug 22nd, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.15>
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.15>.
+This version fixes right sidebar regressions introduced in the previous version.
 	- [[Thanks]]
 		- [[ingepettersen]]
 			- Update Norwegian translations in [#10068](https://github.com/logseq/logseq/pull/10068)

From 81162d4fa69fa23c0c7a1150f3741f904cae48cb Mon Sep 17 00:00:00 2001
From: sudo-nano <cwg1231@gmail.com>
Date: Tue, 22 Aug 2023 15:19:26 -0700
Subject: [PATCH 069/196] Edited macro usage section for clarity

---
 pages/Macros.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/pages/Macros.md b/pages/Macros.md
index e2ddfc5..5a61c76 100644
--- a/pages/Macros.md
+++ b/pages/Macros.md
@@ -5,10 +5,13 @@ description:: Provides a way to write and maintain reusable text. This text can
 - ## Usage
 	- ### Creating a macro
 		- Open the [[config.edn]] file.
-		- Scroll down to the `:macros` section. Inside the curly brackets, add your macro's name in curly brackets followed by the text template, e.g.:
+		- Scroll down to the `:macros` section. Each macro should be enclosed in curly brackets, with two strings enclosed in quotations.
+		- The first string `"foo"` is the macro name. The second string `"Hello $1"` is the text template.
+		- Variables such as `$1` and `$2` can be used to place parameters in the template.
 		- ```edn
 		  :macros {
-		  "foo" "Hello $1"
+		  {"foo" "Hello $1"}
+		  {"bar" "Goodbye $1"}
 		  }
 		  ```
 		- For readability, use a line break to separate each macro

From c3ad250804100cc69d0e34b9541bf358c70cf649 Mon Sep 17 00:00:00 2001
From: sudo-nano <cwg1231@gmail.com>
Date: Tue, 22 Aug 2023 15:46:10 -0700
Subject: [PATCH 070/196] Fixed a typo in the macro config example

---
 pages/Macros.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/pages/Macros.md b/pages/Macros.md
index 5a61c76..abdb651 100644
--- a/pages/Macros.md
+++ b/pages/Macros.md
@@ -5,13 +5,12 @@ description:: Provides a way to write and maintain reusable text. This text can
 - ## Usage
 	- ### Creating a macro
 		- Open the [[config.edn]] file.
-		- Scroll down to the `:macros` section. Each macro should be enclosed in curly brackets, with two strings enclosed in quotations.
-		- The first string `"foo"` is the macro name. The second string `"Hello $1"` is the text template.
+		- Scroll down to the `:macros` section. Add your macro's name in quotation marks `"foo"`, followed by its text template `"Hello $1"`, also in quotation marks. Separate them with a space.
 		- Variables such as `$1` and `$2` can be used to place parameters in the template.
 		- ```edn
 		  :macros {
-		  {"foo" "Hello $1"}
-		  {"bar" "Goodbye $1"}
+		  "foo" "Hello $1"
+		  "bar" "Goodbye $1"
 		  }
 		  ```
 		- For readability, use a line break to separate each macro

From 4ed485157dd58070216524185d3a8c9dd0c0354b Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 7 Sep 2023 00:41:17 +0800
Subject: [PATCH 071/196] chore: release 0.9.16

---
 pages/Changelog.md | 48 +++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 45 insertions(+), 3 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index caf3b8f..b069f89 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,6 +1,48 @@
-## Beta 0.9.15 [[Aug 22nd, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.15>.
-This version fixes right sidebar regressions introduced in the previous version.
+## Beta 0.9.16 [[Sep 6th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.16>
+	- [[Thanks]]
+		- [[Allan Chain]]
+			- Fix `input-selection-end` event is not firing correctly in [#10113](https://github.com/logseq/logseq/pull/10113)
+			- Fix plugins can't be disabled if any error is thrown in beforeunload [#10114](https://github.com/logseq/logseq/pull/10114)
+		- [[Affif Mukhlashin]]
+			- Add Bahasa Indonesia translation in [#10148](https://github.com/logseq/logseq/pull/10148)
+		- [[djm2k]]
+			- Update develop-logseq-on-windows.md doc to warn about Choco in [#10075](https://github.com/logseq/logseq/pull/10075)
+		- [[Zhizhen He]]
+			- Update typos CI actions in [#10143](https://github.com/logseq/logseq/pull/10143)
+		- [[omahs]]
+			- Fix typos [#10143](https://github.com/logseq/logseq/pull/10143)
+		- [[Leonardo Salgueiro]]
+			- Fix `logseq.updateSettings` API doesn't update existing settings in [#10111](https://github.com/logseq/logseq/pull/10111)
+		- [[toymil]]
+			- Remove `word-spacing` CSS rule for inline monospace code in [#10077](https://github.com/logseq/logseq/pull/10077)
+	- [[Fixed issues]]
+		- Should Focus draw container when click [#10116](https://github.com/logseq/logseq/pull/10116)
+		- Copy keyboard shortcut not working in PDF view [#10092](https://github.com/logseq/logseq/pull/10092)
+		- PDF pane becomes blank after zooming or resizing [#10115](https://github.com/logseq/logseq/pull/10115)
+		- Annotation of a PDF of different page sizes [#10121](https://github.com/logseq/logseq/pull/10121)
+		- Incorrect path of PDF.js cmaps resources [#10084](https://github.com/logseq/logseq/pull/10084)
+		- Fix Close button visibility of right side panel [#10145](https://github.com/logseq/logseq/pull/10145)
+		- In Plugin API, `input-selection-end` event is not firing correctly [#10113](https://github.com/logseq/logseq/pull/10113)
+		- `logseq.updateSettings` API doesn't update existing settings [#10111](https://github.com/logseq/logseq/pull/10111)
+		- Plugins can't be disabled if any error is thrown in beforeunload [#10114](https://github.com/logseq/logseq/pull/10114)
+		- Fixes for Logseq Sync: Download progress for iOS [#10090](https://github.com/logseq/logseq/pull/10090)
+		- iOS App Crash caused by memory management [#10097](https://github.com/logseq/logseq/pull/10097)
+		- Remove `word-spacing` CSS rule for inline monospace code [#10077](https://github.com/logseq/logseq/pull/10077)
+		- Make linked references filters reactive when the page properties changed [#9638](https://github.com/logseq/logseq/pull/9638)
+	- [[Enhancement]]
+		- New shortcuts(keymap) editing UI [#9803](https://github.com/logseq/logseq/pull/9803)
+		- Enhancements of Plugin APIs [#10127](https://github.com/logseq/logseq/pull/10127)
+		- I18n: Add Bahasa Indonesia translation [#10148](https://github.com/logseq/logseq/pull/10148)
+		- Refine Electron loading [#10049](https://github.com/logseq/logseq/pull/10049)
+		- Add graph folder checking for bad folder names and nested graph [#10141](https://github.com/logseq/logseq/pull/10141)
+		- Add connectivity testing for Logseq Sync [#10112](https://github.com/logseq/logseq/pull/10112) [#10147](https://github.com/logseq/logseq/pull/10147)
+		- Enhancements for Logseq Sync: avoid logging out, reconnect when online [#10134](https://github.com/logseq/logseq/pull/10134)
+		- Remove legacy shortcuts entry from the general settings [#10154](https://github.com/logseq/logseq/pull/10154)
+		- Disable default close window shortcut [#10096](https://github.com/logseq/logseq/pull/10096)
+- ## Beta 0.9.15 [[Aug 22nd, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.15>.
+  This version fixes right sidebar regressions introduced in the previous version.
 	- [[Thanks]]
 		- [[ingepettersen]]
 			- Update Norwegian translations in [#10068](https://github.com/logseq/logseq/pull/10068)

From 4af799037fd7d69698d108c396b19ef8bd3bc3e2 Mon Sep 17 00:00:00 2001
From: mschiff <marc@schiffbauer.net>
Date: Wed, 6 Sep 2023 10:30:47 -1000
Subject: [PATCH 072/196] Update Tasks.md

Add missing documentation bits for repeated tasks as described in the [changelog 2020](https://docs.logseq.com/#/page/changelog%202020)
---
 pages/Tasks.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/pages/Tasks.md b/pages/Tasks.md
index a35a78d..b657fa4 100644
--- a/pages/Tasks.md
+++ b/pages/Tasks.md
@@ -57,7 +57,11 @@ platforms:: [[All Platforms]]
 		  after typing the command and click `Add repeater` in the date picker
 			- eg: daily exercise routine at 7am
 			  SCHEDULED: <2021-05-26 Wed 7:00 .+1d>
+     			- You can change the repeater kind to:
+				- `.+`: It'll repeat from the last time you marked the block done.
+				- `++`: It'll keep it on the same day of the week.
+				- `+: It'll repeat in X y/m/w/d/h from when you originally scheduled it.
 	- ### Time tracker
 	  id:: 60af74c1-62f8-434a-827c-abc6d2a71734
 		- {{embed ((60acdeba-b3fd-4f90-ab54-3093caa4d5fa))}}
-		- you can toggle this off by [[setting/enable timetracking]]
\ No newline at end of file
+		- you can toggle this off by [[setting/enable timetracking]]

From ac83ff227d9374dd1732fcf804a10de3b69f0518 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 7 Sep 2023 12:31:18 +0800
Subject: [PATCH 073/196] chore: release 0.9.17

---
 pages/Changelog.md | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index b069f89..5acb2e6 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,11 @@
-## Beta 0.9.16 [[Sep 6th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.16>
+## Beta 0.9.17 [[Sep 7th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.17>.
+	- [[Fixed issues]]
+		- iOS network checking issue for Logseq Sync [#10163](https://github.com/logseq/logseq/pull/10163)
+		- Electron App maximize bug [#10165](https://github.com/logseq/logseq/pull/10165)
+- ## Beta 0.9.16 [[Sep 6th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.16>.
+  This version is revoked due to severe bugs.
 	- [[Thanks]]
 		- [[Allan Chain]]
 			- Fix `input-selection-end` event is not firing correctly in [#10113](https://github.com/logseq/logseq/pull/10113)

From 9b508655ebcead407fe3a83a762c340832e5c76f Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 7 Sep 2023 08:33:25 -0400
Subject: [PATCH 074/196] Fix typo

---
 pages/Tasks.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Tasks.md b/pages/Tasks.md
index b657fa4..6e11754 100644
--- a/pages/Tasks.md
+++ b/pages/Tasks.md
@@ -5,7 +5,7 @@ platforms:: [[All Platforms]]
 - ## Usage
 	- Logseq comes with two built-in flavors to mark your block with built-in workflow marker keywords and manage your tasks:
 	  + `LATER` -> `NOW` -> `DONE` flavor (default)
-	  + `TODO` -> `DOING` -> `DONE` flavor 
+	  + `TODO` -> `DOING` -> `DONE` flavor
 	  + You can toggle between those two flavors in the settings page
 	- There are two ways to attach workflow markers to your task block:
 		- when editing the block, press `Ctrl/Cmd+enter` to cycle through the workflow markers
@@ -60,7 +60,7 @@ platforms:: [[All Platforms]]
      			- You can change the repeater kind to:
 				- `.+`: It'll repeat from the last time you marked the block done.
 				- `++`: It'll keep it on the same day of the week.
-				- `+: It'll repeat in X y/m/w/d/h from when you originally scheduled it.
+				- `+`: It'll repeat in X y/m/w/d/h from when you originally scheduled it.
 	- ### Time tracker
 	  id:: 60af74c1-62f8-434a-827c-abc6d2a71734
 		- {{embed ((60acdeba-b3fd-4f90-ab54-3093caa4d5fa))}}

From 963e07e0a2cc8086b77e8f793527e0be837204b0 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 21 Sep 2023 00:31:45 +0800
Subject: [PATCH 075/196] chore: release 0.9.18

---
 pages/Changelog.md | 32 ++++++++++++++++++++++++++++++--
 1 file changed, 30 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 5acb2e6..58acfc8 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,33 @@
-## Beta 0.9.17 [[Sep 7th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.17>.
+## Beta 0.9.18 [[Sep 20th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.18>
+	- [[Thanks]]
+		- [[Jack Case]]
+			- Allow writing to files with group permission without chmod on Linux in [#9297](https://github.com/logseq/logseq/pull/9297)
+		- [[Ulices]]
+			- Update Spanish translations in [#10195](https://github.com/logseq/logseq/pull/10195)
+		- [[jf]]
+			- Allow for single-digit minutes and seconds in youtube-timestamp in [#9930](https://github.com/logseq/logseq/pull/9930)
+		- [[queeup]]
+			- Update Turkish translation in [#10180](https://github.com/logseq/logseq/pull/10180)
+		- [[WsinGithub]]
+			- Disable Bilibili autoplay in [#10207](https://github.com/logseq/logseq/pull/10207)
+	- [[Fixed issues]]
+		- Update rewrite-edn to fix backslash characters unable to be keyboard shortcut [#10224](https://github.com/logseq/logseq/pull/10224)
+		- Disable Bilibili autoplay [#10207](https://github.com/logseq/logseq/pull/10207)
+		- Disable graph name warning [#10253](https://github.com/logseq/logseq/pull/10253)
+		- Support asset filenames with wrong percent encoding [#10191](https://github.com/logseq/logseq/pull/10191)
+		- Incorrect asset resource path for custom CSS on iOS [#10232](https://github.com/logseq/logseq/pull/10232)
+		- Incorrect mouse point payload for the plugin hook of the editor input selection [#10175](https://github.com/logseq/logseq/pull/10175)
+		- Avoid checking network connectivity for non-sync graph [#10171](https://github.com/logseq/logseq/pull/10171)
+	- [[Enhancement]]
+		- Electron loading [#10201](https://github.com/logseq/logseq/pull/10201)
+		- Allow for single-digit minutes and seconds in youtube-timestamp (addresses #9920) [#9930](https://github.com/logseq/logseq/pull/9930)
+		- New option to allow writing to files with group permission without chmod on Linux [#9297](https://github.com/logseq/logseq/pull/9297)
+		- Introduce customizable close window shortcut [#10190](https://github.com/logseq/logseq/pull/10190)
+		- Support Socks5 proxy for Desktop App [#10199](https://github.com/logseq/logseq/pull/10199)
+		- I18n: Spanish [#10195](https://github.com/logseq/logseq/pull/10195), Turkish [#10180](https://github.com/logseq/logseq/pull/10180)
+- ## Beta 0.9.17 [[Sep 7th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.17>.
 	- [[Fixed issues]]
 		- iOS network checking issue for Logseq Sync [#10163](https://github.com/logseq/logseq/pull/10163)
 		- Electron App maximize bug [#10165](https://github.com/logseq/logseq/pull/10165)

From 818c2aaf3010452513b50f7115b5890a819f380d Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 21 Sep 2023 01:00:19 +0800
Subject: [PATCH 076/196] chore: minor wording change

---
 pages/Changelog.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 58acfc8..16bb2e8 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -10,10 +10,10 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- [[queeup]]
 			- Update Turkish translation in [#10180](https://github.com/logseq/logseq/pull/10180)
 		- [[WsinGithub]]
-			- Disable Bilibili autoplay in [#10207](https://github.com/logseq/logseq/pull/10207)
+			- Disable Bilibili video autoplay in [#10207](https://github.com/logseq/logseq/pull/10207)
 	- [[Fixed issues]]
 		- Update rewrite-edn to fix backslash characters unable to be keyboard shortcut [#10224](https://github.com/logseq/logseq/pull/10224)
-		- Disable Bilibili autoplay [#10207](https://github.com/logseq/logseq/pull/10207)
+		- Disable Bilibili video autoplay [#10207](https://github.com/logseq/logseq/pull/10207)
 		- Disable graph name warning [#10253](https://github.com/logseq/logseq/pull/10253)
 		- Support asset filenames with wrong percent encoding [#10191](https://github.com/logseq/logseq/pull/10191)
 		- Incorrect asset resource path for custom CSS on iOS [#10232](https://github.com/logseq/logseq/pull/10232)

From 1ef7dd9bc7593ae44e69ef7d26a04285e0cb79ab Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 11 Oct 2023 23:11:54 +0800
Subject: [PATCH 077/196] chore: release 0.9.19

---
 pages/Changelog.md | 37 +++++++++++++++++++++++++++++++++++--
 1 file changed, 35 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 16bb2e8..47aa7e0 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,38 @@
-## Beta 0.9.18 [[Sep 20th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.18>
+## Beta 0.9.19 [[Oct 11th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.19>
+	- [[Thanks]]
+		- [[Alan Roe]]
+			- Move cursor to end or beginning of line when boundary limit reached in [#10244](https://github.com/logseq/logseq/pull/10244)
+			- Use `cmd/ctrl` + `=` to zoom in [#10241](https://github.com/logseq/logseq/pull/10241)
+		- [[Bad3r]]
+			- Bump CodeMirror version in [#9822](https://github.com/logseq/logseq/pull/9822)
+		- [[Ulices]]
+			- Update Spanish translations in [#10320](https://github.com/logseq/logseq/pull/10320)
+		- [[hkgnp]]
+			- Add marker prop to BlockEntity interface in [#10312](https://github.com/logseq/logseq/pull/10312)
+		- [[jionkitten]]
+			- Fix too frequent highlights saving in PDF view in [#10238](https://github.com/logseq/logseq/pull/10238)
+		- [[Sander]]
+			- Allow plugins to access custom format clipboard data in [#10225](https://github.com/logseq/logseq/pull/10225)
+	- [[Fixed issues]]
+		- Can't close window on macOS with `cmd`+`w` [#10325](https://github.com/logseq/logseq/pull/10325)
+		- The first window does not close when there're multiple windows [#10336](https://github.com/logseq/logseq/pull/10336)
+		- Capture all `logseq://` links on Android [#10266](https://github.com/logseq/logseq/pull/10266)
+		- Allow drag and drop to dummy page [#10292](https://github.com/logseq/logseq/pull/10292)
+		- Bypass corrupted SQLite search index when App starts [#10286](https://github.com/logseq/logseq/pull/10286)
+		- Missing the initial ref highlight block sometimes for PDF view [#10333](https://github.com/logseq/logseq/pull/10333)
+		- Avoid too frequent highlights saving in PDF view [#10238](https://github.com/logseq/logseq/pull/10238)
+		- Fix incorrect auto-complete modal position for overflow editor content input [#10298](https://github.com/logseq/logseq/pull/10298)
+		- Incorrect API call for the electron production bundle [#10329](https://github.com/logseq/logseq/pull/10329)
+	- [[Enhancement]]
+		- Whiteboards: Pen mode (palm rejection) [#10222](https://github.com/logseq/logseq/pull/10222)
+		- Move cursor to end or beginning of line when boundary limit reached [#10244](https://github.com/logseq/logseq/pull/10244)
+		- Upgrade to Capacitor v5 for mobile platforms [#10278](https://github.com/logseq/logseq/pull/10278)
+		- Use `cmd/ctrl` + `=` to zoom [#10241](https://github.com/logseq/logseq/pull/10241)
+		- Allow plugins to access custom format clipboard data [#10225](https://github.com/logseq/logseq/pull/10225)
+		- I18n: Update Spanish translations [#10320](https://github.com/logseq/logseq/pull/10320)
+- ## Beta 0.9.18 [[Sep 20th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.18>
 	- [[Thanks]]
 		- [[Jack Case]]
 			- Allow writing to files with group permission without chmod on Linux in [#9297](https://github.com/logseq/logseq/pull/9297)

From a9677c05df046e1ca3e7e48e33335bee4961baaf Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 1 Nov 2023 22:26:10 +0800
Subject: [PATCH 078/196] chore: release 0.9.20

---
 pages/Changelog.md | 32 ++++++++++++++++++++++++++++++--
 1 file changed, 30 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 47aa7e0..b4438d5 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,33 @@
-## Beta 0.9.19 [[Oct 11th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.19>
+## Beta 0.9.20 [[Nov 1st, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.20>
+	- [[Features]]
+		- New handbook [#8524](https://github.com/logseq/logseq/pull/8524)
+	- [[Thanks]]
+		- [[CorrectRoadH]]
+			- Support zoom via touchpad in [#10435](https://github.com/logseq/logseq/pull/10435)
+		- [[Ulices]]
+			- Update Spanish translation in [#10431](https://github.com/logseq/logseq/pull/10431)
+		- [[ingepettersen]]
+			- Update Norwegian translation in [#10361](https://github.com/logseq/logseq/pull/10361)
+		- [[SylvainDuran]]
+			- Update French translations in [#10427](https://github.com/logseq/logseq/pull/10427)
+		- [[udkl]]
+			- Fix `#card` should only be appended to the title in [#10387](https://github.com/logseq/logseq/pull/10387)
+	- [[Fixed issues]]
+		- Fix android back button closing order [#10345](https://github.com/logseq/logseq/pull/10345)
+		- Fix journal name judgement [#10350](https://github.com/logseq/logseq/pull/10350) [#10422](https://github.com/logseq/logseq/pull/10422) [#10434](https://github.com/logseq/logseq/pull/10434)
+		- Refine drag and drop of assets. Fix not being about to save assets sometimes [#10351](https://github.com/logseq/logseq/pull/10351)
+		- `#card` should only be appended to the title [#10387](https://github.com/logseq/logseq/pull/10387)
+		- On Android, activity restarts when a Bluetooth keyboard gets connected [#10444](https://github.com/logseq/logseq/pull/10444)
+		- Shortcuts editor can't edit disabled keymap [#10290](https://github.com/logseq/logseq/pull/10290)
+		- Refine Logseq Sync login box tips [#10443](https://github.com/logseq/logseq/pull/10443)
+	- [[Enhancement]]
+		- Upgrade electron to v25 [#10440](https://github.com/logseq/logseq/pull/10440)
+		- Make Smart Merge the default option for Logseq Sync [#10428](https://github.com/logseq/logseq/pull/10428)
+		- I18n: Spanish [#10431](https://github.com/logseq/logseq/pull/10431), French [#10427](https://github.com/logseq/logseq/pull/10427), Norwegian [#10361](https://github.com/logseq/logseq/pull/10361)
+		- Add toggle option for PDF view: auto opening the highlight context menu from new text selection [#10390](https://github.com/logseq/logseq/pull/10390)
+- ## Beta 0.9.19 [[Oct 11th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.19>
 	- [[Thanks]]
 		- [[Alan Roe]]
 			- Move cursor to end or beginning of line when boundary limit reached in [#10244](https://github.com/logseq/logseq/pull/10244)

From 76d75aed6edbff5507fa3fe769216d0bf172a9f4 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 2 Nov 2023 10:38:38 -0400
Subject: [PATCH 079/196] Add tip from #114

close #114
---
 pages/Advanced Queries.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pages/Advanced Queries.md b/pages/Advanced Queries.md
index 6c2f5b6..3a6c607 100644
--- a/pages/Advanced Queries.md	
+++ b/pages/Advanced Queries.md	
@@ -43,6 +43,7 @@ description:: Advanced queries are written with [Datalog](https://en.wikipedia.o
 	  2. Page names are stored as lower case in the database.
 	  3. Most simple query operators are available as [rules](https://docs.datomic.com/on-prem/query/query.html#rules) in queries
 	  4. Titles can be be hiccups or double-quoted strings. For example, if you want to put custom macros into the query title, you can write something like `"{{poem foo,bar}}"`.
+	  5. When [[Developer mode]] is enabled, page and block data can be viewed by running the respective commands `(Dev) Show page data` and `(Dev) Show block data` .
 	  #+END_TIP
 	- ### Query Options
 		- #### remove-block-children?

From 1eee74ed75a36d6684c1d73619aabea804d01ac9 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 2 Nov 2023 11:21:18 -0400
Subject: [PATCH 080/196] Add basic doc for the handbook

---
 pages/Changelog.md |  2 +-
 pages/Handbook.md  | 11 +++++++++++
 2 files changed, 12 insertions(+), 1 deletion(-)
 create mode 100644 pages/Handbook.md

diff --git a/pages/Changelog.md b/pages/Changelog.md
index b4438d5..1a6546f 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,7 @@
 ## Beta 0.9.20 [[Nov 1st, 2023]]
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.20>
 	- [[Features]]
-		- New handbook [#8524](https://github.com/logseq/logseq/pull/8524)
+		- New handbook [#8524](https://github.com/logseq/logseq/pull/8524) - [Documentation]([[Handbook]])
 	- [[Thanks]]
 		- [[CorrectRoadH]]
 			- Support zoom via touchpad in [#10435](https://github.com/logseq/logseq/pull/10435)
diff --git a/pages/Handbook.md b/pages/Handbook.md
new file mode 100644
index 0000000..ebeae33
--- /dev/null
+++ b/pages/Handbook.md
@@ -0,0 +1,11 @@
+type:: [[Feature]]
+platforms:: [[All Platforms]]
+description:: Provides in app documentation in the form of short tutorials 
+initial-version:: 0.9.20
+
+- ## Usage
+	- In the lower right corner of the app, there is a `?` icon. Click it and then choose the `Handbook` menu item.
+- ## Functionality
+	- This features provides in app documentation for the most important concepts and common questions. The documentation is usually in the form of short tutorials and not meant to be complete, reference documentation like on https://docs.logseq.com/.
+- ## Additional Links
+	- https://github.com/logseq/handbooks - Source code for the handbook docs and where to start if you're interested in contributing to it
\ No newline at end of file

From f99c912dc5780d2e08683d7689b59136445250e1 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 2 Nov 2023 11:35:46 -0400
Subject: [PATCH 081/196] forgot to omit one platform for handbook

---
 pages/Handbook.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Handbook.md b/pages/Handbook.md
index ebeae33..675e389 100644
--- a/pages/Handbook.md
+++ b/pages/Handbook.md
@@ -1,5 +1,5 @@
 type:: [[Feature]]
-platforms:: [[All Platforms]]
+platforms:: [[All Platforms]] except [[Publish Web]]
 description:: Provides in app documentation in the form of short tutorials 
 initial-version:: 0.9.20
 

From 26d1fcf092f7c7fd75e9a3b4fac9b04ea3b1e7ea Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 21 Nov 2023 01:30:40 +0800
Subject: [PATCH 082/196] Release note for v0.10.0

---
 pages/Changelog.md | 24 ++++++++++++++++++++++--
 1 file changed, 22 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 1a6546f..dc10534 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,25 @@
-## Beta 0.9.20 [[Nov 1st, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.20>
+## Beta 0.10.0 [[Nov 21st, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.0>
+	- [[Features]]
+		- The new cmdk [#10132](https://github.com/logseq/logseq/pull/10132)
+	- [[Thanks]]
+		- [[cosmo9able]]
+			- Update Brazilian Portuguese translation in [#10461](https://github.com/logseq/logseq/pull/10461)
+		- [[e-zz]]
+			- Fix wrong bounding coordinates for PDF highlights in [#10426](https://github.com/logseq/logseq/pull/10426)
+		- [[eliovir]]
+			- Update French translation [#10454](https://github.com/logseq/logseq/pull/10454)
+	- [[Fixed issues]]
+		- Remove the need to add a space to trigger search command [#10506](https://github.com/logseq/logseq/pull/10506)
+		- Fix background color for some UI buttons [#10512](https://github.com/logseq/logseq/pull/10512)
+		- Fix demo page creation for browser version [#10497](https://github.com/logseq/logseq/pull/10497)
+		- Fix wrong bounding coordinates for PDF highlights [#10426](https://github.com/logseq/logseq/pull/10426)
+	- [[Enhancement]]
+		- Export asset ref link as dataset value for the pdf asset [#10488](https://github.com/logseq/logseq/pull/10488)
+		- I18n: Brazilian Portuguese [#10461](https://github.com/logseq/logseq/pull/10461), French [#10454](https://github.com/logseq/logseq/pull/10454)
+		- Polish accent color details [#10520](https://github.com/logseq/logseq/pull/10520)
+- ## Beta 0.9.20 [[Nov 1st, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.20>
 	- [[Features]]
 		- New handbook [#8524](https://github.com/logseq/logseq/pull/8524) - [Documentation]([[Handbook]])
 	- [[Thanks]]

From a8b9658dc2e90208fedd2761100cdfbfbcfb5881 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 20 Nov 2023 17:01:09 -0500
Subject: [PATCH 083/196] Update search page to reflect new abilities of cmd-k

---
 pages/Search.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/pages/Search.md b/pages/Search.md
index cf607e1..25ad060 100644
--- a/pages/Search.md
+++ b/pages/Search.md
@@ -2,9 +2,12 @@ type:: [[Feature]]
 platforms:: [[All Platforms]]
 
 - ## Usage
-	- Search pages and full text search blocks by clicking on the search bar at the top or press `Cmd-k`.
-	- To search blocks within a page, run the command `Search in the current page` or press `Cmd-shift-k`.
-	- Pages can also be created from search by typing a new unique string and pressing `Enter`.
+	- Search pages, blocks, files and commands by clicking on the search bar in the top left or press `Cmd-k`.
+		- While in the search modal, type `/` to start setting a filter for pages, blocks, file or commands. Press `Esc` to unset the current filter.
+		- Pressing `Enter` will search a result. Pressing `Shift+Enter` will open the search result in the sidebar.
+		- Pressing `Cmd/Ctrl` + `Enter` will move the search to the sidebar.
+		- Creates pages or whiteboards from this modal by typing a new unique string and pressing `Enter`.
+	- When in a page, search blocks within a page by running the command `Search in the current page` or press `Cmd-shift-k`.
 - ## Functionality
 	- Page search can find any page under `journals` or `pages`.
 	- Block search _only_ finds blocks within pages. It does not find blocks _anywhere_ else in the app e.g. linked references, sidebar, settings, etc.

From f35b35af8349e3e5faf1fbea9844fd0ca6a8353b Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 20 Nov 2023 17:05:51 -0500
Subject: [PATCH 084/196] Update changelog to link to doc and mention design
 separately since it is user facing

---
 pages/Changelog.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index dc10534..124e7ff 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,8 @@
 ## Beta 0.10.0 [[Nov 21st, 2023]]
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.0>
 	- [[Features]]
-		- The new cmdk [#10132](https://github.com/logseq/logseq/pull/10132)
+		- A new and improved [[Search]]! [#10132](https://github.com/logseq/logseq/pull/10132)
+		- Design core enhancements including the ability to set an "Accent color" from Settings [#10132](https://github.com/logseq/logseq/pull/10132)
 	- [[Thanks]]
 		- [[cosmo9able]]
 			- Update Brazilian Portuguese translation in [#10461](https://github.com/logseq/logseq/pull/10461)

From 6d265cd34ab6ba45b2b8aaa624093dee5aa0f23b Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 28 Nov 2023 21:01:19 +0800
Subject: [PATCH 085/196] chore: add new item to changelog

---
 pages/Changelog.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 124e7ff..a555817 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,4 +1,4 @@
-## Beta 0.10.0 [[Nov 21st, 2023]]
+## Beta 0.10.0 [[Nov 28th, 2023]] 
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.0>
 	- [[Features]]
 		- A new and improved [[Search]]! [#10132](https://github.com/logseq/logseq/pull/10132)
@@ -9,15 +9,21 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- [[e-zz]]
 			- Fix wrong bounding coordinates for PDF highlights in [#10426](https://github.com/logseq/logseq/pull/10426)
 		- [[eliovir]]
-			- Update French translation [#10454](https://github.com/logseq/logseq/pull/10454)
+			- Update French translation in [#10454](https://github.com/logseq/logseq/pull/10454)
+		- [[ormai]]
+			- Update Italian translation in [#10557](https://github.com/logseq/logseq/pull/10557)
+		- [[queeup]]
+			- Update Turkish translation in [#10492](https://github.com/logseq/logseq/pull/10492)
 	- [[Fixed issues]]
 		- Remove the need to add a space to trigger search command [#10506](https://github.com/logseq/logseq/pull/10506)
 		- Fix background color for some UI buttons [#10512](https://github.com/logseq/logseq/pull/10512)
 		- Fix demo page creation for browser version [#10497](https://github.com/logseq/logseq/pull/10497)
 		- Fix wrong bounding coordinates for PDF highlights [#10426](https://github.com/logseq/logseq/pull/10426)
+		- Fix filesystem path handling, add missing Windows UNC path support [#10525](https://github.com/logseq/logseq/pull/10525)
+		- Fix query builder construction [#10485](https://github.com/logseq/logseq/pull/10485)
 	- [[Enhancement]]
 		- Export asset ref link as dataset value for the pdf asset [#10488](https://github.com/logseq/logseq/pull/10488)
-		- I18n: Brazilian Portuguese [#10461](https://github.com/logseq/logseq/pull/10461), French [#10454](https://github.com/logseq/logseq/pull/10454)
+		- I18n: Brazilian Portuguese [#10461](https://github.com/logseq/logseq/pull/10461), French [#10454](https://github.com/logseq/logseq/pull/10454), Italian [#10557](https://github.com/logseq/logseq/pull/10557), Turkish [#10492](https://github.com/logseq/logseq/pull/10492)
 		- Polish accent color details [#10520](https://github.com/logseq/logseq/pull/10520)
 - ## Beta 0.9.20 [[Nov 1st, 2023]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.9.20>

From da29160752406249e6c948eb75b8b5ca6bc87ef2 Mon Sep 17 00:00:00 2001
From: Ramses Oudt <96059866+logseqramses@users.noreply.github.com>
Date: Tue, 28 Nov 2023 14:17:18 +0100
Subject: [PATCH 086/196] Update Search.md

Added shortcuts for Windows and Linux users, and made all shortcut descriptions match (using `-` instead of `+` in some places).
---
 pages/Search.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/pages/Search.md b/pages/Search.md
index 25ad060..1f953a6 100644
--- a/pages/Search.md
+++ b/pages/Search.md
@@ -2,12 +2,12 @@ type:: [[Feature]]
 platforms:: [[All Platforms]]
 
 - ## Usage
-	- Search pages, blocks, files and commands by clicking on the search bar in the top left or press `Cmd-k`.
+	- Search pages, blocks, files and commands by clicking on the search bar in the top left or press `Cmd-k` (macOS)/`Ctrl-k` (Windows and Linux).
 		- While in the search modal, type `/` to start setting a filter for pages, blocks, file or commands. Press `Esc` to unset the current filter.
-		- Pressing `Enter` will search a result. Pressing `Shift+Enter` will open the search result in the sidebar.
-		- Pressing `Cmd/Ctrl` + `Enter` will move the search to the sidebar.
+		- Pressing `Enter` will search a result. Pressing `Shift-Enter` will open the search result in the sidebar.
+		- Pressing `Cmd-Enter` (macOS)/`Ctrl-Enter` (Windows and Linux) will move the search to the sidebar.
 		- Creates pages or whiteboards from this modal by typing a new unique string and pressing `Enter`.
-	- When in a page, search blocks within a page by running the command `Search in the current page` or press `Cmd-shift-k`.
+	- When in a page, search blocks within a page by running the command `Search in the current page` or press `Cmd-Shift-k` (macOS) or `Ctrl-Shift-k` (Windows and Linus).
 - ## Functionality
 	- Page search can find any page under `journals` or `pages`.
 	- Block search _only_ finds blocks within pages. It does not find blocks _anywhere_ else in the app e.g. linked references, sidebar, settings, etc.
@@ -15,4 +15,4 @@ platforms:: [[All Platforms]]
 	- By default, search removes accents from results e.g. `räämat` -> `raamat`. This feature can be turned off by setting the `:feature/enable-search-remove-accents?` option to `false` in [[config.edn]] . After toggling this feature, please run the command `Rebuild search index`.
 	- Search functionality is powered by a search index. If the index is ever out of date or seems buggy, run the command `Rebuild search index`.
 - TODO More specific name for this feature #docs
-	- Possible names include Global search, quick search, general search, omni search, search or create
\ No newline at end of file
+	- Possible names include Global search, quick search, general search, omni search, search or create

From 97a0ec1260ead5ed9bb92b8db7657283a48f487f Mon Sep 17 00:00:00 2001
From: Ramses Oudt <96059866+logseqramses@users.noreply.github.com>
Date: Tue, 28 Nov 2023 14:19:35 +0100
Subject: [PATCH 087/196] Remove TODO from Search page

We decided to call it "Search" so the TODO has been removed.
---
 pages/Search.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/pages/Search.md b/pages/Search.md
index 1f953a6..7ddbcda 100644
--- a/pages/Search.md
+++ b/pages/Search.md
@@ -14,5 +14,3 @@ platforms:: [[All Platforms]]
 	- On [[Desktop]], there is full text search which searches across multiple blocks and also matches on search terms that are out of order.
 	- By default, search removes accents from results e.g. `räämat` -> `raamat`. This feature can be turned off by setting the `:feature/enable-search-remove-accents?` option to `false` in [[config.edn]] . After toggling this feature, please run the command `Rebuild search index`.
 	- Search functionality is powered by a search index. If the index is ever out of date or seems buggy, run the command `Rebuild search index`.
-- TODO More specific name for this feature #docs
-	- Possible names include Global search, quick search, general search, omni search, search or create

From 07dfed6832232637d976eb52188b69d19af5b31a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 30 Nov 2023 09:26:06 -0500
Subject: [PATCH 088/196] Try updated publish-spa with color

---
 .github/workflows/gh-pages.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/gh-pages.yml b/.github/workflows/gh-pages.yml
index a3e0cd7..6c62364 100644
--- a/.github/workflows/gh-pages.yml
+++ b/.github/workflows/gh-pages.yml
@@ -17,7 +17,7 @@ jobs:
         uses: logseq/publish-spa@main
         with:
           output-directory: www
-          version: 0.9.9
+          accent-color: indigo
 
       - name: Add .nojekyll file
         run: touch www/.nojekyll

From 052936ea76b72d6d0b48b53f6df2fb4e1774cbcc Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 7 Dec 2023 01:18:27 +0800
Subject: [PATCH 089/196] chore: release note of 0.10.1 (#118)

---
 pages/Changelog.md | 32 ++++++++++++++++++++++++++++++--
 1 file changed, 30 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index a555817..6c10e76 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,33 @@
-## Beta 0.10.0 [[Nov 28th, 2023]] 
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.0>
+## Beta 0.10.1 [[Dec 6th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.1>
+	- [[Thanks]]
+		- [[Blezur]]
+			- Polish translations in [#10604](https://github.com/logseq/logseq/pull/10604)
+		- [[Ulices]]
+			- Update Spanish translation in [#10594](https://github.com/logseq/logseq/pull/10594)
+		- [[ksqsf]]
+			- Fix and-or simple query that contains string literals in [#10632](https://github.com/logseq/logseq/pull/10632)
+		- [[ROCKTAKEY]]
+			- Update Japanese translation in [#10612](https://github.com/logseq/logseq/pull/10612)
+		- [[queeup]]
+			- Update Turkish translation in [#10595](https://github.com/logseq/logseq/pull/10595)
+		- [[Vivianne]]
+			- Fixed missing space in fr and es i18n files in [#10644](https://github.com/logseq/logseq/pull/10644)
+	- [[Fixed issues]]
+		- New Search related issues [#10584](https://github.com/logseq/logseq/pull/10584), [#10634](https://github.com/logseq/logseq/pull/10634)
+			- Cross-platform shortcut icons [#10590](https://github.com/logseq/logseq/pull/10590)
+			- Increase the default search length [#10570](https://github.com/logseq/logseq/pull/10570)
+			- Search does not navigate to block of interest if collapsed [#10633](https://github.com/logseq/logseq/pull/10633)
+			- Add whiteboards to search filters [#10630](https://github.com/logseq/logseq/pull/10630)
+		- Theme color related issues [#10581](https://github.com/logseq/logseq/pull/10581), [#10638](https://github.com/logseq/logseq/pull/10638)
+		- Block UUID shouldn't be added to recents [#10616](https://github.com/logseq/logseq/pull/10616)
+		- Incorrect background color for the left sidebar on mobile [#10582](https://github.com/logseq/logseq/pull/10582)
+		- Incorrect node edge color for the global graph view [#10585](https://github.com/logseq/logseq/pull/10585)
+		- Fix and-or simple query that contains string literals [#10632](https://github.com/logseq/logseq/pull/10632)
+	- [[Enhancement]]
+		- I18n: Turkish translation [#10595](https://github.com/logseq/logseq/pull/10595), Polish translations [#10604](https://github.com/logseq/logseq/pull/10604), Spanish translation [#10594](https://github.com/logseq/logseq/pull/10594), Japanese translation [#10612](https://github.com/logseq/logseq/pull/10612)
+- ## Beta 0.10.0 [[Nov 28th, 2023]] 
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.0>
 	- [[Features]]
 		- A new and improved [[Search]]! [#10132](https://github.com/logseq/logseq/pull/10132)
 		- Design core enhancements including the ability to set an "Accent color" from Settings [#10132](https://github.com/logseq/logseq/pull/10132)

From e7faa520334883272a85403701356607942035a9 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Fri, 22 Dec 2023 11:07:02 +0800
Subject: [PATCH 090/196] chore: release note of 0.10.2 (#119)

* chore: release note of 0.10.2

* chore: minor wording change
---
 pages/Changelog.md | 36 ++++++++++++++++++++++++++++++++++--
 1 file changed, 34 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 6c10e76..ccb047b 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,37 @@
-## Beta 0.10.1 [[Dec 6th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.1>
+## Beta 0.10.2 [[Dec 22nd, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.2>
+	- [[Features]]
+		- Clone handles for quickly cloning existing shapes in Whiteboards [#10637](https://github.com/logseq/logseq/pull/10637)
+		  ![Screencast](https://github.com/logseq/logseq/assets/10744960/f05a1de8-4c87-4a94-ab0b-928141261789#screencast.webm)
+	- [[Thanks]]
+		- [[eliovir]]
+			- Update French translation in [#10647](https://github.com/logseq/logseq/pull/10647), [#10706](https://github.com/logseq/logseq/pull/10706)
+		- [[jiyi]]
+			- Update Chinese translation in [#10668](https://github.com/logseq/logseq/pull/10668)
+		- [[queeup]]
+			- Update Turkish translation in [#10718](https://github.com/logseq/logseq/pull/10718)
+		- [[Richard Garčár]]
+			- Update Slovak translation in [#10673](https://github.com/logseq/logseq/pull/10673)
+		- [[Vivianne]]
+			- Add more localization support for linked references view in [#10643](https://github.com/logseq/logseq/pull/10643)
+	- [[Fixed issues]]
+		- Full page content search [#10645](https://github.com/logseq/logseq/pull/10645)
+		- Missing current-page search [#10662](https://github.com/logseq/logseq/pull/10662)
+		- Don't treat blocks with headings as pre-blocks [#10710](https://github.com/logseq/logseq/pull/10710)
+		- Save inline images in excalidraw [#10652](https://github.com/logseq/logseq/pull/10652)
+		- Sync navbar and action bar color for Android when theme change [#10653](https://github.com/logseq/logseq/pull/10653)
+		- Incorrect auto-save state when paste batch blocks [#10672](https://github.com/logseq/logseq/pull/10672)
+		- Incorrect handling of pasting html list [#10674](https://github.com/logseq/logseq/pull/10674)
+		- Incorrect node edge color for Graph view [#10693](https://github.com/logseq/logseq/pull/10693)
+		- Incorrect IME composition detection [#10654](https://github.com/logseq/logseq/pull/10654)
+		- Detached PDF viewer does not open HTTP links in default browser [#10724](https://github.com/logseq/logseq/pull/10724)
+	- [[Enhancement]]
+		- I18n: French [#10706](https://github.com/logseq/logseq/pull/10706) [#10647](https://github.com/logseq/logseq/pull/10647), Slovak [#10673](https://github.com/logseq/logseq/pull/10673), Turkish [#10718](https://github.com/logseq/logseq/pull/10718), Chinese [#10668](https://github.com/logseq/logseq/pull/10668)
+		- Plugin APIs [#10399](https://github.com/logseq/logseq/pull/10399)
+		- Release .zip package build for Windows [#10678](https://github.com/logseq/logseq/pull/10678)
+		- Add more localization support for linked references view [#10643](https://github.com/logseq/logseq/pull/10643)
+- ## Beta 0.10.1 [[Dec 6th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.1>
 	- [[Thanks]]
 		- [[Blezur]]
 			- Polish translations in [#10604](https://github.com/logseq/logseq/pull/10604)

From b20eecf6d266043e2ef4f304c53b76e4bd3bad2a Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Mon, 25 Dec 2023 22:33:17 +0800
Subject: [PATCH 091/196] chore: release note of 0.10.3

---
 pages/Changelog.md | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index ccb047b..6bad5dc 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,19 @@
-## Beta 0.10.2 [[Dec 22nd, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.2>
+## Beta 0.10.3 [[Dec 25th, 2023]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.3>
+This bug-fix release addresses the bundled Git bug introduced in 0.10.2.
+	- [[Thanks]]
+		- [[Vivianne]]
+			- Fix French translation in [#10749](https://github.com/logseq/logseq/pull/10749)
+		- [[Hidekazu Kubota]]
+			- Add percent encoding file names with leading dots in [#10746](https://github.com/logseq/logseq/pull/10746)
+	- [[Fixed issues]]
+		- Safety key string for the simple command key value in Plugin API [#10741](https://github.com/logseq/logseq/pull/10741)
+		- Fix missing bundled Git [#10751](https://github.com/logseq/logseq/pull/10751)
+		- Percent encoding file names with leading dots [#10746](https://github.com/logseq/logseq/pull/10746)
+	- [[Enhancement]]
+		- I18n: French translation [#10749](https://github.com/logseq/logseq/pull/10749)
+- ## Beta 0.10.2 [[Dec 22nd, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.2>
 	- [[Features]]
 		- Clone handles for quickly cloning existing shapes in Whiteboards [#10637](https://github.com/logseq/logseq/pull/10637)
 		  ![Screencast](https://github.com/logseq/logseq/assets/10744960/f05a1de8-4c87-4a94-ab0b-928141261789#screencast.webm)

From 9d391dfe29acbeb81e6a4054826ee6b39cb4fc74 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Wed, 17 Jan 2024 21:13:46 +0800
Subject: [PATCH 092/196] chore: release note of 0.10.4 (#120)

---
 pages/Changelog.md | 47 +++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 44 insertions(+), 3 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 6bad5dc..f350ac4 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,6 +1,47 @@
-## Beta 0.10.3 [[Dec 25th, 2023]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.3>
-This bug-fix release addresses the bundled Git bug introduced in 0.10.2.
+## Beta 0.10.4 [[Jan 17th, 2024]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.4>
+	- [[Thanks]]
+		- [[alan-roe]]
+			- Fix docker build in [#10287](https://github.com/logseq/logseq/pull/10287)
+		- [[aurnik]]
+			- Add highlighted page aliases in search results in [#10761](https://github.com/logseq/logseq/pull/10761)
+			- Prevent jumping when hovering over left sidebar items in [#10760](https://github.com/logseq/logseq/pull/10760)
+		- [[e-zz]]
+			- Fix area highlights in PDF view don't blink in [#10732](https://github.com/logseq/logseq/pull/10732)
+		- [[eliovir]]
+			- Update French translations in [#10810](https://github.com/logseq/logseq/pull/10810)
+		- [[hasecilu]]
+			- Update Spanish translation in [#10840](https://github.com/logseq/logseq/pull/10840)
+		- [[ingepettersen]]
+			- Update Norwegian translation in [#10849](https://github.com/logseq/logseq/pull/10849)
+		- [[megayu]]
+			- Enhance block selection in [#10745](https://github.com/logseq/logseq/pull/10745)
+		- [[situ2001]]
+			- Prevent button in modal from being clicked twice when pressing enter key in [#10820](https://github.com/logseq/logseq/pull/10820)
+		- [[ZerdoX-x]]
+			- Update project deps in [#10857](https://github.com/logseq/logseq/pull/10857)
+	- [[Fixed issues]]
+		- Highlight page aliases in search results [#10761](https://github.com/logseq/logseq/pull/10761)
+		- Prevent jumping when hovering over left sidebar items [#10760](https://github.com/logseq/logseq/pull/10760)
+		- Android App crash caused by special filenames [#10845](https://github.com/logseq/logseq/pull/10845)
+		- Missing Git SDK in Plugin API [#10767](https://github.com/logseq/logseq/pull/10767)
+		- Remove prefix spaces when no-indent is used in exporting [#10807](https://github.com/logseq/logseq/pull/10807)
+		- Accept video as mobile shared content [#10797](https://github.com/logseq/logseq/pull/10797)
+		- PDF view's area highlights don't blink [#10732](https://github.com/logseq/logseq/pull/10732)
+		- Cannot toggle updated-at and created-at in query view [#10759](https://github.com/logseq/logseq/pull/10759)
+		- Add support for older GLIBC on Linux [#10832](https://github.com/logseq/logseq/pull/10832), note that search index is still not available on old Linux
+		- Do not notify network status when logged out [#10813](https://github.com/logseq/logseq/pull/10813)
+		- Fix incorrect position for the filter modal on the iOS platform [#10798](https://github.com/logseq/logseq/pull/10798)
+		- Prevent button in modal from being clicked twice when pressing enter key [#10820](https://github.com/logseq/logseq/pull/10820)
+	- [[Enhancement]]
+		- New UI components [#10694](https://github.com/logseq/logseq/pull/10694)
+		- Better block selection [#10745](https://github.com/logseq/logseq/pull/10745)
+		- Enhancement of Plugin APIs [#10782](https://github.com/logseq/logseq/pull/10782)
+		- Enhancement of left sidebar UI [#10765](https://github.com/logseq/logseq/pull/10765)
+		- I18n: French translations [#10810](https://github.com/logseq/logseq/pull/10810), Norwegian translation [#10849](https://github.com/logseq/logseq/pull/10849), Spanish translation [#10840](https://github.com/logseq/logseq/pull/10840)
+- ## Beta 0.10.3 [[Dec 25th, 2023]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.3>
+  This bug-fix release addresses the bundled Git bug introduced in 0.10.2.
 	- [[Thanks]]
 		- [[Vivianne]]
 			- Fix French translation in [#10749](https://github.com/logseq/logseq/pull/10749)

From e1de834d79fbffdbd4e39bc4a55c1ef0bd931c71 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 18 Jan 2024 22:20:19 +0800
Subject: [PATCH 093/196] chore: release 0.10.5

---
 pages/Changelog.md | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index f350ac4..c916dd8 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,14 @@
-## Beta 0.10.4 [[Jan 17th, 2024]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.4>
+## Beta 0.10.5 [[Jan 18th, 2024]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.5>
+This version fixes a language-specific App crash in the French translation file. This bug does not affect non-French users.
+	- [[Thanks]]
+		- [[DavidLapous]]
+			- Fix typo in French translation in [10874](https://github.com/logseq/logseq/pull/10874)
+	- [[Fixed issues]]
+		- A language-specific app crash occurred due to an incorrect French translation file [#10876](https://github.com/logseq/logseq/pull/10876)
+		- Typo in French translation [10874](https://github.com/logseq/logseq/pull/10874)
+- ## Beta 0.10.4 [[Jan 17th, 2024]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.4>
 	- [[Thanks]]
 		- [[alan-roe]]
 			- Fix docker build in [#10287](https://github.com/logseq/logseq/pull/10287)

From f03458c05b743914bbde06c0e88a07ea2ca7a61b Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 25 Jan 2024 01:59:25 +0800
Subject: [PATCH 094/196] chore: add logseq sync encryption doc

---
 pages/Logseq Sync Encryption.md | 38 +++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 pages/Logseq Sync Encryption.md

diff --git a/pages/Logseq Sync Encryption.md b/pages/Logseq Sync Encryption.md
new file mode 100644
index 0000000..ac962e2
--- /dev/null
+++ b/pages/Logseq Sync Encryption.md	
@@ -0,0 +1,38 @@
+type:: #Feature
+
+- > This doc describes the #[[Logseq Sync]] encryption scheme.
+- ## Client-side Encryption in Logseq File Sync
+	- Basic algorithm: [Age Encryption](https://github.com/FiloSottile/age) and [ChaCha20-Poly1305](https://en.wikipedia.org/wiki/ChaCha20-Poly1305)
+	- Implementation: <https://github.com/logseq/rsapi/tree/master/lsq-encryption>
+- ### File Encryption
+	- Use standard Age Encryption.
+	- File content is encrypted and decrypted with a pair of age encryption keys
+	- The Age encryption key is encrypted with user's passphrase. This is where the "Graph unlocking" comes from.
+	- ```
+	  ("AGE-SECRET-KEY-1YR7DJEF0LYKW8Z5MCW3.......TMWF0ZY7P2QGU4UY9", 
+	   "age1m74wwsxtj.......w4drsvsyrjvuqlpga92")
+	  ```
+- ### Filename Encryption
+	- A modified version of ChaCha20-Poly1305. Weaker, bug good enough for filenames.
+	- In short
+		- Use the raw x25519 key from above Age encryption. It's a 256-bit key.
+		- The `nonce` in `ChaCha20-Poly1305` is filled with zero bytes, for non-random result
+		- Join `e.` prefix and hex-encoded ciphertext
+	- Demo:
+		- ```
+		  We start from an age encryption private key:
+		  
+		  "AGE-SECRET-KEY-1KZEJZYUPL49REUU985P.......RRQX9MJF8DXQRRA7J0"
+		  
+		  Convert it to Raw x25519 Key:
+		  
+		  "...(some 32 bytes binary)...."
+		  
+		  To encrypt "pages/contents.md"(nonce = 96bits, all zeros):
+		  
+		  Got a ciphertext binary: "6dd3a5340dd904be0e509ff824c32cdc1db108166bf58a4a8f3f5299651282ffca"
+		  
+		  Prefix it with "e."
+		  
+		  "e.6dd3a5340dd904be0e509ff824c32cdc1db108166bf58a4a8f3f5299651282ffca"
+		  ```
\ No newline at end of file

From 6980e66d2c80e14e5bdc6eca37e862fe77bd340c Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 25 Jan 2024 01:59:43 +0800
Subject: [PATCH 095/196] chore: add link to encryption doc

---
 pages/Logseq Sync.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Logseq Sync.md b/pages/Logseq Sync.md
index b7f1caf..2011c4c 100644
--- a/pages/Logseq Sync.md	
+++ b/pages/Logseq Sync.md	
@@ -13,7 +13,7 @@ description:: Paid feature that provides encrypted synchronization of graphs bet
 - ## Functionality
 	- Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.
 	- Syncing is a choice that is made per graph and thus allows for some graphs to be local only.
-	- Each graph is encrypted with a password.
+	- Each graph is encrypted with a password. The contents of the file as well as its name are all encrypted. See [[Logseq Sync Encryption]].
 	- Sync automatically happens in the background. Click on the cloud icon and the `Sync now` button to force a sync.
 - ## FAQ
 	- **Question**: Can I use Sync with git?

From 8e11b5e19e16a648c9c90368036ee8eb1fbc42df Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Mon, 5 Feb 2024 23:35:28 +0800
Subject: [PATCH 096/196] Add release note of 0.10.6 (#121)

* Add release note of 0.10.6

* try fix ci

* update changelog for 0.10.6

* chore: minor update

* chore: minor spell change
---
 pages/Changelog.md              | 41 ++++++++++++++++++++++++++++++---
 pages/Logseq Sync Encryption.md |  3 ++-
 2 files changed, 40 insertions(+), 4 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index c916dd8..b6079ae 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,6 +1,41 @@
-## Beta 0.10.5 [[Jan 18th, 2024]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.5>
-This version fixes a language-specific App crash in the French translation file. This bug does not affect non-French users.
+## Beta 0.10.6 [[Feb 5th, 2024]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.6>
+	- [[Thanks]]
+		- [[ChristianAvila]]
+			- Adding larger auto-commit interval in [#10536](https://github.com/logseq/logseq/pull/10536)
+		- [[mfenniak]]
+			- Fix outdent-then-delete removing incorrect block in [#10790](https://github.com/logseq/logseq/pull/10790)
+		- [[ReillyBrogan]]
+			- Update better-sqlite3 to v9.3.0 in [#10884](https://github.com/logseq/logseq/pull/10884)
+		- [[TaylorHo]]
+			- Enhance Brazilian Portuguese translations in [#10891](https://github.com/logseq/logseq/pull/10891)
+		- [[Mostafa Ahangarha]]
+			- Minor typo fixes and grammar improvements in docs in [#10940](https://github.com/logseq/logseq/pull/10940)
+		- [[CNLHC]]
+			- Add support for closing history panel after selecting a version in [#10530](https://github.com/logseq/logseq/pull/10530)
+		- [[linsui]]
+			- Add fastlane structure for F-Droid in [#10925](https://github.com/logseq/logseq/pull/10925)
+		- [[Morgan Plain]]
+			- Support changing graph forces via UI in [#10755](https://github.com/logseq/logseq/pull/10755)
+		- [[queeup]]
+			- Update Turkish translation in [#10937](https://github.com/logseq/logseq/pull/10937)
+	- [[Fixed issues]]
+		- Publishing not working [#10911](https://github.com/logseq/logseq/pull/10911)
+		- Logseq Sync crash on Android [#10922](https://github.com/logseq/logseq/pull/10922)
+		- Performance of Search on mobile platforms [#10924](https://github.com/logseq/logseq/pull/10924)
+		- Outdent-then-delete removing incorrect block [#10790](https://github.com/logseq/logseq/pull/10790)
+		- Wrong new page button click handling in graph view [#10962](https://github.com/logseq/logseq/pull/10962)
+		- Save composing text when clicking mobile bar buttons [#10921](https://github.com/logseq/logseq/pull/10921)
+	- [[Enhancement]]
+		- Git auto-commit: support commit on close, allow changing settings on-the-fly, allowing larger auto-commit interval [#10536](https://github.com/logseq/logseq/pull/10536)
+		- Trigger on-change for slider when mouse up instead of input value change [#10972](https://github.com/logseq/logseq/pull/10972)
+		- Support time offset of YouTube links [#10945](https://github.com/logseq/logseq/pull/10945)
+		- Support changing graph forces via UI [#10755](https://github.com/logseq/logseq/pull/10755)
+		- Support for closing history panel after selecting a version [#10530](https://github.com/logseq/logseq/pull/10530)
+		- I18n: Brazilian Portuguese translations [#10891](https://github.com/logseq/logseq/pull/10891), Turkish translation [#10937](https://github.com/logseq/logseq/pull/10937)
+- ## Beta 0.10.5 [[Jan 18th, 2024]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.5>
+  This version fixes a language-specific App crash in the French translation file. This bug does not affect non-French users.
 	- [[Thanks]]
 		- [[DavidLapous]]
 			- Fix typo in French translation in [10874](https://github.com/logseq/logseq/pull/10874)
diff --git a/pages/Logseq Sync Encryption.md b/pages/Logseq Sync Encryption.md
index ac962e2..8b9d464 100644
--- a/pages/Logseq Sync Encryption.md	
+++ b/pages/Logseq Sync Encryption.md	
@@ -1,4 +1,5 @@
-type:: #Feature
+type:: [[Feature]]
+platforms:: [[All Platforms]]
 
 - > This doc describes the #[[Logseq Sync]] encryption scheme.
 - ## Client-side Encryption in Logseq File Sync

From a70851fa7da4b7c5f0b77fee402d9f99f0368cd7 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Fri, 1 Mar 2024 00:33:12 +0800
Subject: [PATCH 097/196] Update changelog of 0.10.7

---
 pages/Changelog.md | 32 ++++++++++++++++++++++++++++++--
 1 file changed, 30 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index b6079ae..9f0dbc1 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,33 @@
-## Beta 0.10.6 [[Feb 5th, 2024]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.6>
+## Beta 0.10.7 [[Feb 29th, 2024]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.7>
+	- [[Thanks]]
+		- [[Mostafa Ahangarha]]
+			- Add partial Persian translation in [#10938](https://github.com/logseq/logseq/pull/10938)
+		- [[Vladimir Pouzanov]]
+			- Fix :graph/current usage in the electron state in [#11013](https://github.com/logseq/logseq/pull/11013)
+		- [[Puneeth Chaganti]]
+			- Fix typo in mldoc package name in [#10995](https://github.com/logseq/logseq/pull/10995)
+		- [[Tobias Domhan]]
+			- Fix preserve root node block refs when cutting + pasting in [#10841](https://github.com/logseq/logseq/pull/10841)
+		- [[Topher Hunt]]
+			- Add new keybinding for "toggle expand/collapse this block" in [#10980](https://github.com/logseq/logseq/pull/10980)
+		- [[YU000jp]]
+			- Fix main scrollbar jumps in [#10037](https://github.com/logseq/logseq/pull/10037)
+	- [[Fixed issues]]
+		- Add .heic to media type [#11017](https://github.com/logseq/logseq/pull/11017)
+		- Preserve root node block refs when cutting + pasting. [#10841](https://github.com/logseq/logseq/pull/10841)
+		- Fix main scrollbar jumps [#10037](https://github.com/logseq/logseq/pull/10037)
+		- Fix wrong `:command/toggle-favorite` handling in config [#10998](https://github.com/logseq/logseq/pull/10998)
+		- Fix search term query highlight performance [#11030](https://github.com/logseq/logseq/pull/11030)
+	- [[Enhancement]]
+		- New keybinding for "toggle expand/collapse this block" [#10980](https://github.com/logseq/logseq/pull/10980)
+		- I18n: Persian [#10938](https://github.com/logseq/logseq/pull/10938),
+		- Add share/open asset file for Android App [#10977](https://github.com/logseq/logseq/pull/10977)
+		- Enhance accent color related details [#10986](https://github.com/logseq/logseq/pull/10986)
+		- refactoring dropdown/context menu with the new components [#10897](https://github.com/logseq/logseq/pull/10897)
+		- Better handling for macOS scrollbar system setting of auto scrolling mode [#11048](https://github.com/logseq/logseq/pull/11048)
+- ## Beta 0.10.6 [[Feb 5th, 2024]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.6>
 	- [[Thanks]]
 		- [[ChristianAvila]]
 			- Adding larger auto-commit interval in [#10536](https://github.com/logseq/logseq/pull/10536)

From 397b2d373a0a7067bb3a3ff3636b173ddb8d1651 Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Thu, 28 Mar 2024 17:46:59 +0800
Subject: [PATCH 098/196] chore: release 0.10.8

---
 pages/Changelog.md | 31 +++++++++++++++++++++++++++++--
 1 file changed, 29 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 9f0dbc1..3bd5464 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,32 @@
-## Beta 0.10.7 [[Feb 29th, 2024]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.7>
+## Beta 0.10.8 [[Mar 28th, 2024]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.8>
+	- [[Thanks]]
+		- [[albanobattistella]]
+			- Update Italian translation in [#11154](https://github.com/logseq/logseq/pull/11154)
+		- [[e-zz]]
+			- Fix shift+mouse click on PDF View not invoking area highlight on Linux in [#10973](https://github.com/logseq/logseq/pull/10973)
+		- [[Liu Cheng]]
+			- Fix missing newline after multiline block when exporting a page in [#10934](https://github.com/logseq/logseq/pull/10934)
+		- [[Jon Ramos]]
+			- Fix toggling of task list in [#11079](https://github.com/logseq/logseq/pull/11079)
+		- [[liymike]]
+			- Update Simplified Chinese) translation in [#11119](https://github.com/logseq/logseq/pull/11119)
+		- [[queeup]]
+			- Update Turkish translation in [#11063](https://github.com/logseq/logseq/pull/11063)
+		- [[yannicka]]
+			- Remove obsolete "@tailwindcss/line-clamp" dependency in [#11130](https://github.com/logseq/logseq/pull/11130)
+	- [[Fixed issues]]
+		- Fix toggling of task list [#11079](https://github.com/logseq/logseq/pull/11079)
+		- Missing newline after multiline block when exporting a page [#10934](https://github.com/logseq/logseq/pull/10934)
+		- Incorrect cursor move for the emoji from the line head [#11112](https://github.com/logseq/logseq/pull/11112)
+		- Shift+mouse click on PDF View not invoking area highlight on Linux [#10973](https://github.com/logseq/logseq/pull/10973)
+		- Fine tune page title search strategy [#11147](https://github.com/logseq/logseq/pull/11147)
+		- Logout and clear keys for Logseq Sync [#11111](https://github.com/logseq/logseq/pull/11111)
+		- Fix ui button component's click handling [#11068](https://github.com/logseq/logseq/pull/11068)
+	- [[Enhancement]]
+		- I18n: Simplified Chinese [#11119](https://github.com/logseq/logseq/pull/11119), Turkish [#11063](https://github.com/logseq/logseq/pull/11063), Italian [#11154](https://github.com/logseq/logseq/pull/11154)
+- ## Beta 0.10.7 [[Feb 29th, 2024]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.7>
 	- [[Thanks]]
 		- [[Mostafa Ahangarha]]
 			- Add partial Persian translation in [#10938](https://github.com/logseq/logseq/pull/10938)

From 6ec6852e8cd1b64c78eb1442abc43feb637bafbe Mon Sep 17 00:00:00 2001
From: Andelf <andelf@gmail.com>
Date: Tue, 23 Apr 2024 22:01:07 +0800
Subject: [PATCH 099/196] chore: release 0.10.9

---
 pages/Changelog.md | 25 +++++++++++++++++++++++--
 1 file changed, 23 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 3bd5464..2c1f8f0 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,26 @@
-## Beta 0.10.8 [[Mar 28th, 2024]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.8>
+## Beta 0.10.9 [[Apr 23rd, 2024]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.9>
+	- [[Thanks]]
+		- [[desk7]]
+			- Update Italian translation in [#11179](https://github.com/logseq/logseq/pull/11179)
+		- [[KaMeHb-UA]]
+			- Add Linux ARM64 build support in [#11183](https://github.com/logseq/logseq/pull/11183)
+		- [[Sun-Wukung]]
+			- Update tutorial-sk.md in #11226
+		- [[thief-sty]]
+			- Update docs/develop-logseq.md in [#11218](https://github.com/logseq/logseq/pull/11218)
+			- Fix e2e-test command in [#11217](https://github.com/logseq/logseq/pull/11217)
+	- [[Fixed issues]]
+		- Fix missing refs for property text values when creating a page [#11208](https://github.com/logseq/logseq/pull/11208)
+		- Fix incorrect behavior of the delete key for deleting the last char [#11190](https://github.com/logseq/logseq/pull/11190)
+		- Fix missing default colors for highlight mark tag [#11247](https://github.com/logseq/logseq/pull/11247)
+	- [[Enhancement]]
+		- New block placeholder should accept tab and enter key [#11255](https://github.com/logseq/logseq/pull/11255)
+		- Restore App window at current workspace [#11246](https://github.com/logseq/logseq/pull/11246)
+		- I18n: Italian [#11179](https://github.com/logseq/logseq/pull/11179), Slovak [#11226](https://github.com/logseq/logseq/pull/11226)
+		- Linux ARM64 build support [#11183](https://github.com/logseq/logseq/pull/11183)
+- ## Beta 0.10.8 [[Mar 28th, 2024]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.8>
 	- [[Thanks]]
 		- [[albanobattistella]]
 			- Update Italian translation in [#11154](https://github.com/logseq/logseq/pull/11154)

From 8edaf11cb1a1171e8f1ee9ecf446ad4d0220db02 Mon Sep 17 00:00:00 2001
From: Cerecero <105999339+Cerecero@users.noreply.github.com>
Date: Sat, 4 May 2024 12:52:18 -0600
Subject: [PATCH 100/196] Update Plugins 02 - Build a mind map plugin.md

Added a missing greater than '>'
---
 pages/Plugins 02 - Build a mind map plugin.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Plugins 02 - Build a mind map plugin.md b/pages/Plugins 02 - Build a mind map plugin.md
index 32a92d2..018256d 100644
--- a/pages/Plugins 02 - Build a mind map plugin.md	
+++ b/pages/Plugins 02 - Build a mind map plugin.md	
@@ -15,7 +15,7 @@
 	  ```html 
 	    <script src="https://cdn.jsdelivr.net/npm/@logseq/libs/dist/lsplugin.user.min.js"></script>
 	    <script src="https://cdn.jsdelivr.net/npm/regenerator-runtime"></script>
-	    <script src="https://cdn.jsdelivr.net/npm/mind-elixir/dist/mind-elixir.js"></script
+	    <script src="https://cdn.jsdelivr.net/npm/mind-elixir/dist/mind-elixir.js"></script>
 	  ```
 	- The `@logseq/libs` should be obvious. We will use async/await in our JavaScript, hence the regenerator-runtime is needed. Finally, we load the wonderful mind-elixir library to actually draw our mind map.
 ## Build the Map
@@ -86,4 +86,4 @@
 	- `logseq.Editor` includes APIs to interact with the Logseq editor and `getCurrentPageBlocksTree` is a powerful one to get back all the blocks of the current page as a tree structure. The tree of blocks is a fundamental data structure of Logseq, with which you can do many powerful things in your plugin.
 	- After we get back the blocks tree, we just walk the whole tree and use the elixir-mind APIs to build a connected mind map. The details are not relevant here and are therefore left out. Feel free to check the finished code. Also, load the plugin in your Logseq app and enjoy the beautiful mind map generating from your pages!
 ## Conclusion
-	- In this guide, we walk through building a simple but powerful mind map plugin for Logseq. While the plugin APIs are still work-in-progress, they can already do many powerful things. We invite you to hack them with your imagination. Feedbacks are super welcomed - we will improve the plugin APIs through listening to your voices!
\ No newline at end of file
+	- In this guide, we walk through building a simple but powerful mind map plugin for Logseq. While the plugin APIs are still work-in-progress, they can already do many powerful things. We invite you to hack them with your imagination. Feedbacks are super welcomed - we will improve the plugin APIs through listening to your voices!

From 74bff536832f3ef1e2a3b8f69c8131821bcc7b88 Mon Sep 17 00:00:00 2001
From: Muhammad Talal Anwar <mail@talal.io>
Date: Fri, 7 Jun 2024 11:22:58 +0200
Subject: [PATCH 101/196] fix: typo

---
 pages/Start here.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Start here.md b/pages/Start here.md
index 01a7d07..a0a367a 100644
--- a/pages/Start here.md	
+++ b/pages/Start here.md	
@@ -20,7 +20,7 @@
 	- ### Task management
 		- As you write in Logseq, you might think of tasks you need to do later. While you may use a dedicated tasks tool, a common use case for Logseq is task management.
 		- **Combining your notes and tasks is a breeze in Logseq.** Not only can you create tasks, you can also track how much time you spend on them, and even create automated workflows using priorities or other tags.
-		- Are your tasks mixed with your notes? No problem! [[Queries]] are a powerful way to resurface tasks and other information. But even as a beginning Logseq user can you benefit from tasks as you write on your daily Journals. To send a task to your future self, simply add a date link to quickly offload things from your mind (hint: type `/date picker` and hit `Enter` to easily add a future date to a task).
+		- Are your tasks mixed with your notes? No problem! [[Queries]] are a powerful way to resurface tasks and other information. But even as a beginning Logseq user you can benefit from tasks as you write on your daily Journals. To send a task to your future self, simply add a date link to quickly offload things from your mind (hint: type `/date picker` and hit `Enter` to easily add a future date to a task).
 		- Once tasks start to cluster around projects, Logseq also has you covered. With the block-based approach, creating pages for projects is as easy as stacking blocks. And when you learn to use Logseq's powerful queries, you can effortlessly create dynamic indexes or task dashboards.
 	- After seeing how others leverage Logseq's feature, you've hopefully started thinking of some of your own use cases. We recommend you continue following the rest of this starter guide to learn the core 20% functionality that will provide you with 80% of your wanted returns.
 	- If you get stuck at any moment or if you just want to connect with fellow Logseq enthusiasts, [**join the Logseq Discord server**](https://discord.gg/sVsJdzJghp). There you'll always find someone friendly who's willing to help you better understand a Logseq feature or workflow. We look forward to getting to know you!

From 67d58c035f800719b8274d225c9973dd4e4c6d87 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 12 Jul 2024 18:04:33 -0400
Subject: [PATCH 102/196] Add a basic db-version doc

---
 db-version.md | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)
 create mode 100644 db-version.md

diff --git a/db-version.md b/db-version.md
new file mode 100644
index 0000000..dbecdf9
--- /dev/null
+++ b/db-version.md
@@ -0,0 +1,60 @@
+## Description
+
+This is a brief description of DB graph functionality as of July 12th.
+
+## Properties
+
+### Add and Edit Property Values 
+
+Properties can be added to any block or page.
+
+To create your first property:
+* Create a new block
+* Press `cmd-p` and type the name of a new property
+* Select `Text` as the property type and then type some property value
+
+`cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
+
+`cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
+
+### Configure a Property
+
+Properties are configurable from any block or page they appear on by clicking on its name. Alternatively, navigate to any property with `cmd-k` and then click on `Configure` above its name.
+
+Property fields in the Configure modal:
+
+* Name: Name to visually identify the property
+* Icon: Choose one and it will appear wherever its name appears
+* Schema type: There are 7 types of properties: Text, Number, Checkbox, Url, Page, Date and Object. If you're unsure of what type to choose, use Text as it behaves like a block.
+* Multiple values: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox.
+* Available choices: Use this to limit a property to specific values. Once a choice is defined, a user can only select from one of the defined choices. Each choice has a value, a description and an optional icon.
+* UI position: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
+* Hide by default: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
+* Description: A description for the property that is mainly displayed on the property's page
+
+
+TODO:
+- Built in properties and what can be modified
+- Property types
+- Drag and drop
+- Querying
+- idents?
+
+## Classes
+
+To create your first class:
+* Press `cmd-k` and then type `#NAME` where NAME is the name of the Class
+* A dialog pops up that lets you create and/or add properties to the class. 
+
+
+Classes are configurable by navigating to their page e.g. via `cmd-k` or clicking on their `#` name. Then click on the `Configure` link above its name.
+
+Class fields in the Configure modal:
+* Parent class: Use this to allow the class to inherit the parent classes properties. By default the parent class is the `Root class` which doesn't have any properties.
+* Class properties: Add or remove existing properties to associate them with a class
+
+TODO:
+- Root class
+- More about inheritance
+- Drag n drop
+- Tags vs classes
\ No newline at end of file

From 4b9e589795412c8214f9ee14777efadcfa9f1952 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 12 Aug 2024 13:13:58 -0400
Subject: [PATCH 103/196] Add docs on db importer and more on new tags

---
 db-version.md | 46 ++++++++++++++++++++++++++++++++--------------
 1 file changed, 32 insertions(+), 14 deletions(-)

diff --git a/db-version.md b/db-version.md
index dbecdf9..7134a5c 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,8 @@
 ## Description
 
-This is a brief description of DB graph functionality as of July 12th.
+This is a description of DB graph functionality as of Aug 12th.
+
+NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
 ## Properties
 
@@ -40,21 +42,37 @@ TODO:
 - Querying
 - idents?
 
-## Classes
+## New Tags
 
-To create your first class:
-* Press `cmd-k` and then type `#NAME` where NAME is the name of the Class
-* A dialog pops up that lets you create and/or add properties to the class. 
+NOTE: New tags are currently labeled as tags in the app and do not behave like the previous tags. These `new tags` are also known as classes, types or supertags. Feedback is welcome on names for `new tags`.
 
+To create your first new tag:
+* Press `cmd-k` and then type `#NAME` where NAME is new tag name.
+* A dialog pops up that lets you create and/or add properties to the new tag. 
 
-Classes are configurable by navigating to their page e.g. via `cmd-k` or clicking on their `#` name. Then click on the `Configure` link above its name.
+For example, say we created a new tag `Person` and added `lastName` and `birthday` properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are associated to it. A useful thing about new tags is that when its properties change those changes are immediately made to all tagged blocks and pages.
 
-Class fields in the Configure modal:
-* Parent class: Use this to allow the class to inherit the parent classes properties. By default the parent class is the `Root class` which doesn't have any properties.
-* Class properties: Add or remove existing properties to associate them with a class
+### Parent Tags
 
-TODO:
-- Root class
-- More about inheritance
-- Drag n drop
-- Tags vs classes
\ No newline at end of file
+New tags can have a parent tag. By default new tags have the `Root tag` as a parent. Allowing new tags to have or be a parent is useful as it allows tags to organized in a hierachy. This is similar to directories on your computer or the previous namespace feature. A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
+
+### Configure a New Tag
+
+New tags are configurable by navigating to their page e.g. via `cmd-k` or clicking on their `#` name. Then click on the `Configure` link above its name.
+
+In the Configure modal:
+* Parent tag: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
+* Properties: Below `Parent tag`, you can add or remove existing properties to associate them with a new tag. These properties can be sorted by dragging one above or below the other. These properties will then display sorted when a new tag is used on a block or page.
+
+## Convert File Graph to DB graph
+
+To convert your file graph to a DB graph:
+
+* Click on the three dots menu in the upper right corner and select `Import`.
+* Click on the `File to DB graph` button.
+* This brings up a dialog. For larger graphs it takes longer for the dialog to display.
+* The dialog requires you to input a name for your graph. On desktop this new graph will be located under `~/logseq/graphs/GRAPH-NAME` so it is ok to give it the same name it currently has.
+* The dialog has the following optional inputs:
+    * `Tags to import ...` - This input converts any of your old tags to the [new tags](#new-tags). This is helpful if you've been using a particular tag like a new tag. You can also convert pages later by right clicking on a page's name.
+    * `Properties whose values are imported as new tags` - This input converts property values for the specified property to the new tags. For example, in the official docs graph the [type property](https://docs.logseq.com/#/page/type) is used this way. This means that all `type` property values like [Feature](https://docs.logseq.com/#/page/feature) on [this page](https://docs.logseq.com/#/page/code%20block) would get converted to the new tag.
+    * `Properties whose values are imported as parents of ...` - This input converts property values for the specified property to be [a parent of a new tag](#parent-tags). For example, in the official docs graph the [parent property](https://docs.logseq.com/#/page/parent) is used this way. This means that all `parent` property values like [Thing](https://docs.logseq.com/#/page/thing) on [this page](https://docs.logseq.com/#/page/feature) would get converted to the new tag.
\ No newline at end of file

From afe595bd5988605459de910ce3177e8acf97263d Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 12 Aug 2024 13:36:14 -0400
Subject: [PATCH 104/196] Mention child tags

---
 db-version.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 7134a5c..b8fe675 100644
--- a/db-version.md
+++ b/db-version.md
@@ -54,7 +54,9 @@ For example, say we created a new tag `Person` and added `lastName` and `birthda
 
 ### Parent Tags
 
-New tags can have a parent tag. By default new tags have the `Root tag` as a parent. Allowing new tags to have or be a parent is useful as it allows tags to organized in a hierachy. This is similar to directories on your computer or the previous namespace feature. A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
+New tags can have a parent tag, defaulting to `Root tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Child tags` section.
+
+A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
 
 ### Configure a New Tag
 

From 6bac7e3fa40b39cce888eb652a9b6b948f502586 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 14 Aug 2024 10:43:29 -0400
Subject: [PATCH 105/196] Add overview links and importer intro

---
 db-version.md | 18 +++++++++++++-----
 1 file changed, 13 insertions(+), 5 deletions(-)

diff --git a/db-version.md b/db-version.md
index b8fe675..c1eae86 100644
--- a/db-version.md
+++ b/db-version.md
@@ -4,6 +4,12 @@ This is a description of DB graph functionality as of Aug 12th.
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
+## Overview
+
+* [Properties](#properties)
+* [New Tags](#new-tags)
+* [DB Graph Importer](#db-graph-importer)
+
 ## Properties
 
 ### Add and Edit Property Values 
@@ -66,15 +72,17 @@ In the Configure modal:
 * Parent tag: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
 * Properties: Below `Parent tag`, you can add or remove existing properties to associate them with a new tag. These properties can be sorted by dragging one above or below the other. These properties will then display sorted when a new tag is used on a block or page.
 
-## Convert File Graph to DB graph
+## DB Graph Importer
+
+The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because tags are now used for new tag features while page references handle inline referencing functionality. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.
 
-To convert your file graph to a DB graph:
+### Convert File Graph to DB graph
 
 * Click on the three dots menu in the upper right corner and select `Import`.
 * Click on the `File to DB graph` button.
 * This brings up a dialog. For larger graphs it takes longer for the dialog to display.
 * The dialog requires you to input a name for your graph. On desktop this new graph will be located under `~/logseq/graphs/GRAPH-NAME` so it is ok to give it the same name it currently has.
 * The dialog has the following optional inputs:
-    * `Tags to import ...` - This input converts any of your old tags to the [new tags](#new-tags). This is helpful if you've been using a particular tag like a new tag. You can also convert pages later by right clicking on a page's name.
-    * `Properties whose values are imported as new tags` - This input converts property values for the specified property to the new tags. For example, in the official docs graph the [type property](https://docs.logseq.com/#/page/type) is used this way. This means that all `type` property values like [Feature](https://docs.logseq.com/#/page/feature) on [this page](https://docs.logseq.com/#/page/code%20block) would get converted to the new tag.
-    * `Properties whose values are imported as parents of ...` - This input converts property values for the specified property to be [a parent of a new tag](#parent-tags). For example, in the official docs graph the [parent property](https://docs.logseq.com/#/page/parent) is used this way. This means that all `parent` property values like [Thing](https://docs.logseq.com/#/page/thing) on [this page](https://docs.logseq.com/#/page/feature) would get converted to the new tag.
\ No newline at end of file
+    1. `Tags to import ...` - This input converts any of your old tags to the [new tags](#new-tags). This is helpful if you've been using a particular tag like a new tag. You can also convert pages later by right clicking on a page's name.
+    2. `Properties whose values are imported as new tags` - This input converts property values for the specified property to the new tags. For example, in the official docs graph the [type property](https://docs.logseq.com/#/page/type) is used this way. This means that all `type` property values like [Feature](https://docs.logseq.com/#/page/feature) on [this page](https://docs.logseq.com/#/page/code%20block) would get converted to the new tag.
+    3. `Properties whose values are imported as parents of ...` - This input converts property values for the specified property to be [a parent of a new tag](#parent-tags). For example, in the official docs graph the [parent property](https://docs.logseq.com/#/page/parent) is used this way. This means that all `parent` property values like [Thing](https://docs.logseq.com/#/page/thing) on [this page](https://docs.logseq.com/#/page/feature) would get converted to the new tag.

From c8536f2ad690e302615bb70aa12d0b9489806406 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 15 Aug 2024 00:57:13 -0400
Subject: [PATCH 106/196] Add nodes intro

---
 db-version.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/db-version.md b/db-version.md
index c1eae86..40a3503 100644
--- a/db-version.md
+++ b/db-version.md
@@ -6,10 +6,15 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 
 ## Overview
 
+* [Nodes](#nodes)
 * [Properties](#properties)
 * [New Tags](#new-tags)
 * [DB Graph Importer](#db-graph-importer)
 
+## Nodes
+
+Pages or blocks are now called nodes because the two behave more similarly. A block can be named like a page when it is used with a new tag e.g. the block `Inception #Movie` has Inception as the block name. This block name can then be referenced e.g. `[[Inception]]`. Blocks also have a Linked References section like pages. You can see this by zooming into a block or clicking on a block link. Blocks and pages still have some differences that we are hoping to unify like their name and property display and editing as well as the blocks under a page/block.
+
 ## Properties
 
 ### Add and Edit Property Values 

From b831f27dfa1f08b73556dd266bc7b8d1ec25db29 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 21 Aug 2024 17:24:09 -0400
Subject: [PATCH 107/196] Add docs on tasks

---
 db-version.md | 41 +++++++++++++++++++++++++++++++++++++++--
 1 file changed, 39 insertions(+), 2 deletions(-)

diff --git a/db-version.md b/db-version.md
index 40a3503..df991d4 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This is a description of DB graph functionality as of Aug 12th.
+This is a description of DB graph functionality as of Aug 21st.
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
@@ -9,6 +9,7 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 * [Nodes](#nodes)
 * [Properties](#properties)
 * [New Tags](#new-tags)
+* [Tasks](#tasks)
 * [DB Graph Importer](#db-graph-importer)
 
 ## Nodes
@@ -77,9 +78,45 @@ In the Configure modal:
 * Parent tag: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
 * Properties: Below `Parent tag`, you can add or remove existing properties to associate them with a new tag. These properties can be sorted by dragging one above or below the other. These properties will then display sorted when a new tag is used on a block or page.
 
+## Tasks
+
+Tasks are improved from the previous version as they more powerful and customizable. All tasks are blocks with the built-in new tag `#Task`. When a task is created it has the properties status, priority and deadline.
+
+### Create a Task
+
+A new task can be created in a number of ways:
+* Set the status of a block i.e. by typing `/STATUS` where `STATUS` is one of the status values e.g. `/todo`.
+* Type text in a block and end it with `#Task`.
+* When on the `Task` page, create a new row in the Task table.
+
+### Task Shortcuts
+
+Any block can have a task property value set with a command or a keybinding. The commands start with `Add task` and the keybindings are:
+
+* To set property `status`, press `p s`.
+* To set property `priority`, press `p p`.
+* To set property `deadline`, press `p d`.
+
+### Task Status
+
+The status property is probably the most often used task property and thus it has been simplified and made customizable. The `TODO/DOING` and `NOW/LATER` workflows have been merged into `TODO/DOING` and some of the other TODO keywords have been converted to built-in status values. The default built-in values for status are:
+
+* `Backlog`
+* `Todo`
+* `Doing`
+* `In Review`
+* `Done`
+* `Canceled`
+
 ## DB Graph Importer
 
-The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because tags are now used for new tag features while page references handle inline referencing functionality. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.
+The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.
+
+All tasks are imported as new [tasks](#tasks). Since tasks only have statuses for the one default workflow, the following statuses from alternate workflows have been remapped as follows:
+
+* `LATER` -> `Todo`
+* `IN-PROGRESS` and `NOW` -> `Doing`
+* `WAIT` and `WAITING` -> `Backlog`
 
 ### Convert File Graph to DB graph
 

From 07d7e4f5b8dac058999666c4c0aa42a6585fdad2 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 22 Aug 2024 10:19:05 -0400
Subject: [PATCH 108/196] document task cycling

---
 db-version.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index df991d4..e9d55bd 100644
--- a/db-version.md
+++ b/db-version.md
@@ -97,6 +97,8 @@ Any block can have a task property value set with a command or a keybinding. The
 * To set property `priority`, press `p p`.
 * To set property `deadline`, press `p d`.
 
+The statuses `Todo`, `Doing` and `Done` can be cycled through with `cmd-enter`.
+
 ### Task Status
 
 The status property is probably the most often used task property and thus it has been simplified and made customizable. The `TODO/DOING` and `NOW/LATER` workflows have been merged into `TODO/DOING` and some of the other TODO keywords have been converted to built-in status values. The default built-in values for status are:
@@ -112,7 +114,7 @@ The status property is probably the most often used task property and thus it ha
 
 The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.
 
-All tasks are imported as new [tasks](#tasks). Since tasks only have statuses for the one default workflow, the following statuses from alternate workflows have been remapped as follows:
+All tasks are imported as new [tasks](#tasks). Some task statuses have been remapped to avoid duplicates e.g. `TODO` and `LATER`. The following statuses have been remapped:
 
 * `LATER` -> `Todo`
 * `IN-PROGRESS` and `NOW` -> `Doing`

From a531da171be7cfcc15a8e052b921559ec6a0c88a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 22 Aug 2024 12:08:18 -0400
Subject: [PATCH 109/196] document customizing tasks and task / commands

---
 db-version.md | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index e9d55bd..42bb5a5 100644
--- a/db-version.md
+++ b/db-version.md
@@ -85,7 +85,7 @@ Tasks are improved from the previous version as they more powerful and customiza
 ### Create a Task
 
 A new task can be created in a number of ways:
-* Set the status of a block i.e. by typing `/STATUS` where `STATUS` is one of the status values e.g. `/todo`.
+* Set the status of a block by typing the status choice e.g. `/todo` or cyling status with `cmd-enter`.
 * Type text in a block and end it with `#Task`.
 * When on the `Task` page, create a new row in the Task table.
 
@@ -99,6 +99,8 @@ Any block can have a task property value set with a command or a keybinding. The
 
 The statuses `Todo`, `Doing` and `Done` can be cycled through with `cmd-enter`.
 
+The `/STATUS` commands can set a status where `STATUS` is one of the status choices e.g. `/todo`. Similarly, priority choices can be set with `/PRIORITY` commands. `/Deadline` sets the deadline property.
+
 ### Task Status
 
 The status property is probably the most often used task property and thus it has been simplified and made customizable. The `TODO/DOING` and `NOW/LATER` workflows have been merged into `TODO/DOING` and some of the other TODO keywords have been converted to built-in status values. The default built-in values for status are:
@@ -110,6 +112,15 @@ The status property is probably the most often used task property and thus it ha
 * `Done`
 * `Canceled`
 
+### Customizing Tasks
+
+Since tasks are now powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
+
+1. The `Status` property choices can be customized by going to the `Status` page with `cmd-k`. From the property's [configuration modal](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
+2. Task properties can be configured by going to the property's [configuration modal](#configure-a-property). From this modal, you can customize the property's icon and ui position.
+3. `#Task` can be configured to have additional properties from the new tag's [configuration modal](#configure-a-new-tag).
+4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from `cmd-k` and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
+
 ## DB Graph Importer
 
 The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.

From e78b92a92887d3354f58dcdf5af45dcf4ca43a3a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 26 Aug 2024 16:58:33 -0400
Subject: [PATCH 110/196] Add more docs on properties

---
 db-version.md | 31 +++++++++++++++++++------------
 1 file changed, 19 insertions(+), 12 deletions(-)

diff --git a/db-version.md b/db-version.md
index 42bb5a5..88cdd94 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This is a description of DB graph functionality as of Aug 21st.
+This is a description of DB graph functionality as of Aug 26th.
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
@@ -37,22 +37,29 @@ Properties are configurable from any block or page they appear on by clicking on
 
 Property fields in the Configure modal:
 
-* Name: Name to visually identify the property
-* Icon: Choose one and it will appear wherever its name appears
-* Schema type: There are 7 types of properties: Text, Number, Checkbox, Url, Page, Date and Object. If you're unsure of what type to choose, use Text as it behaves like a block.
+* `Name`: Name to visually identify the property
+* `Icon`: Choose one and it will appear wherever its name appears
+* `Property type`: This determines what type a property's property values will have. Once a property is used this field cannot change. If you're unsure of what type to choose, use `Text`. See [property-types](#property-types) for more.
 * Multiple values: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox.
-* Available choices: Use this to limit a property to specific values. Once a choice is defined, a user can only select from one of the defined choices. Each choice has a value, a description and an optional icon.
+* Available choices: Use this to limit a property to specific values. Once a choice is defined, a user can only select from one of the defined choices. Each choice has a value, a description and an optional icon. Drag the choices up and down to order how they appear.
 * UI position: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
 * Hide by default: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
-* Description: A description for the property that is mainly displayed on the property's page
+* Description: A description for the property that is mainly displayed on the property's page.
 
+### Built-in Properties
 
-TODO:
-- Built in properties and what can be modified
-- Property types
-- Drag and drop
-- Querying
-- idents?
+Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use `cmd-k`. For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page's, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are, `Icon`, `UI position`, `Hide by default` and `Available choices`.
+
+### Property Types
+
+A property type determines what type a property's property values can have. There are 6 types of property values: Text, Number, Date, Checkbox, Url, and Node. Here is more info on each:
+
+* `Text`: This is the recommended default as it allows for any text and behaves like a block. This means that node references work here and children blocks can be created under the block.
+* `Number`: This is for numbers including negative numbers and floats e.g. 3.5. Unlike file graph properties, these are stored as actual numbers. This means that all features and queries that use this property type correctly sort as numbers by default.
+* `Date`: This is for dates and is editable with a date picker. When a date property value is used, it correctly links to the journal page.
+* `Checkbox`: This is used to set or unset a property value and displays as a checkbox. To engineers this type is known as a boolean.
+* `Url`: This limits text to only allow urls e.g. `https://logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
+* `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if there was an `#Actor` that is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
 
 ## New Tags
 

From 46c275c5dfa90585c496e55cf2df773ea5315a00 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 26 Aug 2024 17:00:08 -0400
Subject: [PATCH 111/196] tweak last commit

---
 db-version.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/db-version.md b/db-version.md
index 88cdd94..9362513 100644
--- a/db-version.md
+++ b/db-version.md
@@ -40,11 +40,11 @@ Property fields in the Configure modal:
 * `Name`: Name to visually identify the property
 * `Icon`: Choose one and it will appear wherever its name appears
 * `Property type`: This determines what type a property's property values will have. Once a property is used this field cannot change. If you're unsure of what type to choose, use `Text`. See [property-types](#property-types) for more.
-* Multiple values: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox.
-* Available choices: Use this to limit a property to specific values. Once a choice is defined, a user can only select from one of the defined choices. Each choice has a value, a description and an optional icon. Drag the choices up and down to order how they appear.
-* UI position: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
-* Hide by default: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
-* Description: A description for the property that is mainly displayed on the property's page.
+* `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox.
+* `Available choices`: Use this to limit a property to specific values. Once a choice is defined, a user can only select from one of the defined choices. Each choice has a value, a description and an optional icon. Drag the choices up and down to order how they appear.
+* `UI position`: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
+* `Hide by default`: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
+* `Description`: A description for the property that is mainly displayed on the property's page.
 
 ### Built-in Properties
 
@@ -59,7 +59,7 @@ A property type determines what type a property's property values can have. Ther
 * `Date`: This is for dates and is editable with a date picker. When a date property value is used, it correctly links to the journal page.
 * `Checkbox`: This is used to set or unset a property value and displays as a checkbox. To engineers this type is known as a boolean.
 * `Url`: This limits text to only allow urls e.g. `https://logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
-* `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if there was an `#Actor` that is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
+* `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if `#Actor` is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
 
 ## New Tags
 

From d416aa4742f27ddefe5359eafcd15bc380fe61ce Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 26 Aug 2024 17:34:26 -0400
Subject: [PATCH 112/196] fix typo

---
 db-version.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 9362513..3a07010 100644
--- a/db-version.md
+++ b/db-version.md
@@ -48,7 +48,7 @@ Property fields in the Configure modal:
 
 ### Built-in Properties
 
-Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use `cmd-k`. For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page's, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are, `Icon`, `UI position`, `Hide by default` and `Available choices`.
+Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use `cmd-k`. For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are, `Icon`, `UI position`, `Hide by default` and `Available choices`.
 
 ### Property Types
 

From 82220a1d5dc43aa3cd3183b274fa270e45feb80a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 29 Aug 2024 14:34:34 -0400
Subject: [PATCH 113/196] Update docs to describe new property dropdown

Also document property choices
---
 db-version.md | 34 +++++++++++++++++++++-------------
 1 file changed, 21 insertions(+), 13 deletions(-)

diff --git a/db-version.md b/db-version.md
index 3a07010..16c4d4d 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This is a description of DB graph functionality as of Aug 26th.
+This is a description of DB graph functionality as of Aug 29th.
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
@@ -14,7 +14,7 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 
 ## Nodes
 
-Pages or blocks are now called nodes because the two behave more similarly. A block can be named like a page when it is used with a new tag e.g. the block `Inception #Movie` has Inception as the block name. This block name can then be referenced e.g. `[[Inception]]`. Blocks also have a Linked References section like pages. You can see this by zooming into a block or clicking on a block link. Blocks and pages still have some differences that we are hoping to unify like their name and property display and editing as well as the blocks under a page/block.
+Nodes is a new term for pages or blocks because the two now behave similarly. Nodes are both referenced by using `[[]]`. Nodes have a similar editing experience as they can set properties, use `/` commands, and use the [new tags](#new-tags). Like pages, blocks have a `Linked References` section when you zoom into a block.. Blocks and pages still have some differences that we are hoping to unify like the block view when it is zoomed in.
 
 ## Properties
 
@@ -27,28 +27,28 @@ To create your first property:
 * Press `cmd-p` and type the name of a new property
 * Select `Text` as the property type and then type some property value
 
+A property itself can have properties on its property page. By default the `Description` property is available for adding a description to a property.
+
 `cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
 
 `cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
 
 ### Configure a Property
 
-Properties are configurable from any block or page they appear on by clicking on its name. Alternatively, navigate to any property with `cmd-k` and then click on `Configure` above its name.
+Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with `cmd-k` and then clicking on the `Configure property` link below its name.
 
-Property fields in the Configure modal:
+Property fields in the dropdown menu:
 
 * `Name`: Name to visually identify the property
-* `Icon`: Choose one and it will appear wherever its name appears
 * `Property type`: This determines what type a property's property values will have. Once a property is used this field cannot change. If you're unsure of what type to choose, use `Text`. See [property-types](#property-types) for more.
+* `Available choices`: This limits a property to only have one of the defined choices. See [property choices](#property-choices) for more.
 * `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox.
-* `Available choices`: Use this to limit a property to specific values. Once a choice is defined, a user can only select from one of the defined choices. Each choice has a value, a description and an optional icon. Drag the choices up and down to order how they appear.
 * `UI position`: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
 * `Hide by default`: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
-* `Description`: A description for the property that is mainly displayed on the property's page.
 
 ### Built-in Properties
 
-Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use `cmd-k`. For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are, `Icon`, `UI position`, `Hide by default` and `Available choices`.
+Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use `cmd-k`. For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are its icon, `UI position`, `Hide by default` and `Available choices`.
 
 ### Property Types
 
@@ -61,6 +61,12 @@ A property type determines what type a property's property values can have. Ther
 * `Url`: This limits text to only allow urls e.g. `https://logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
 * `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if `#Actor` is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
 
+### Property Choices
+
+Property choices allow a property to only have one of the defined choices. Only the property types `Text`, `Url` and `Number` support this. From the [configuration dropdown](#configure-a-property), a property choice can be added, deleted and edited to have a required value, an optional description and an optional icon. Drag the choices up and down to order how they appear. For a good example of choices see the `Status` property.
+
+If a property has already been used, it is possible to convert it to use choices. After clicking `Add choice`, a panel displays to convert all existing property values to choices. If a property is using choices, it is possible to stop using choices by deleting them from the property. Caution: deleting a choice from a property also currently deletes the choice from all blocks it is used.
+
 ## New Tags
 
 NOTE: New tags are currently labeled as tags in the app and do not behave like the previous tags. These `new tags` are also known as classes, types or supertags. Feedback is welcome on names for `new tags`.
@@ -71,6 +77,8 @@ To create your first new tag:
 
 For example, say we created a new tag `Person` and added `lastName` and `birthday` properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are associated to it. A useful thing about new tags is that when its properties change those changes are immediately made to all tagged blocks and pages.
 
+A new tag can have properties on its own page. By default the `Description` property is available for adding a description to a new tag.
+
 ### Parent Tags
 
 New tags can have a parent tag, defaulting to `Root tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Child tags` section.
@@ -79,9 +87,9 @@ A powerful feature of using a parent tag is that the new tag inherits the proper
 
 ### Configure a New Tag
 
-New tags are configurable by navigating to their page e.g. via `cmd-k` or clicking on their `#` name. Then click on the `Configure` link above its name.
+New tags are configurable by navigating to their page e.g. via `cmd-k` or clicking on their `#` name. Then click on the `Configure tag` link below its name.
 
-In the Configure modal:
+In the Configure panel:
 * Parent tag: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
 * Properties: Below `Parent tag`, you can add or remove existing properties to associate them with a new tag. These properties can be sorted by dragging one above or below the other. These properties will then display sorted when a new tag is used on a block or page.
 
@@ -123,9 +131,9 @@ The status property is probably the most often used task property and thus it ha
 
 Since tasks are now powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
 
-1. The `Status` property choices can be customized by going to the `Status` page with `cmd-k`. From the property's [configuration modal](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
-2. Task properties can be configured by going to the property's [configuration modal](#configure-a-property). From this modal, you can customize the property's icon and ui position.
-3. `#Task` can be configured to have additional properties from the new tag's [configuration modal](#configure-a-new-tag).
+1. The `Status` property choices can be customized by going to the `Status` page with `cmd-k`. From the property's [configuration dropdown](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
+2. Task properties can be configured by going to the property's page. From this page you can configure its icon or the ui position via the [configuration dropdown](#configure-a-property).
+3. `#Task` can be configured to have additional properties from the new tag's [configuration panel](#configure-a-new-tag).
 4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from `cmd-k` and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
 
 ## DB Graph Importer

From bac4ba81835e3b5e8085f35f3654e7ed309932a5 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 30 Aug 2024 21:51:40 -0400
Subject: [PATCH 114/196] start a db changes page

---
 db-version-changes.md | 69 +++++++++++++++++++++++++++++++++++++++++++
 db-version.md         |  2 +-
 2 files changed, 70 insertions(+), 1 deletion(-)
 create mode 100644 db-version-changes.md

diff --git a/db-version-changes.md b/db-version-changes.md
new file mode 100644
index 0000000..a0a7952
--- /dev/null
+++ b/db-version-changes.md
@@ -0,0 +1,69 @@
+## Description
+
+This page describes changes for existing Logseq features on the [database version](https://github.com/logseq/logseq/pull/9858). Some of these changes may change depending on user feedback.
+
+## Overview
+
+* [Changes for All Graphs](#changes-for-all-graphs)
+* [DB Graph Changes](#db-graph-changes)
+* [File Graph Changes](#file-graph-changes)
+
+## Changes for All Graphs
+
+The following changes affect both file and the new db graphs:
+* To simplify editor `/` commands, [Commands](https://docs.logseq.com/#/page/commands) and [Advanced Commands](https://docs.logseq.com/#/page/advanced%20commands) are merged together under `/`.
+* A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
+* On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
+
+## DB Graph Changes
+
+High level changes:
+* Blocks and pages are united as [nodes](./db-version.md#nodes). They are referenced as `[[]]` and blocks no longer use `(())` for referencing.
+* Properties have a lot more functionality with the [new properties](./db-version.md#properties)!
+* Previous tags should behave like before that an inline tag is entered using `Cmd-Enter`.
+    * NOTE: Pressing enter on a `#` input triggers a powerful [new tags](./db-version.md#new-tags) feature.
+* The application loads should load _much_ faster. Our last performance test exercised 30k+ pages.
+* All blocks and pages have created-at and updated-at timestamps! With this built-in dimension of time, time powered features are possible.
+*  The [previous tables](https://docs.logseq.com/#/page/tables) including version 2 are replaced by a shadcn based table. The new tables have inline editing like spreadsheets by default. Currently these tables are seen on pages of properties, new tags and the `All pages` page.
+* Markdown is the only supported format. Org mode file graphs will be able to convert to DB graphs.
+* Zotero integration isn't planned to be a built-in feature and will hopefully moved to a plugin.
+
+WIP changes:
+* Namespaces don't exist for now. This is likely to change. In the meantime, use [new tags](./db-version.md#new-tags) and their ability to have child tags to recreate most of it.
+* Queries are to be updated to use the new tables and have more powerful filters.
+* Whiteboards are disabled for now and will be enabled later.
+* Flashcards are disabled for now and will be enabled later.
+* Exports only partially work.
+
+### Changes by Feature
+
+#### Tasks
+
+* Using terms from the [previous tasks](https://docs.logseq.com/#/page/tasks), a task marker, priority and deadline are respectively now `Status`, `Priority` and `Deadline` properties on a task.
+* [Scheduled](https://docs.logseq.com/#/page/tasks/block/deadline%20and%20scheduled) has been deprecated.
+* Logbook timestamps have been deprecated.
+* Read more about the [new tasks](./db-version.md#tasks).
+
+#### Queries
+
+* Since block timestamps are available, they display in table view where possible.
+* Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
+* Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
+
+#### Config.edn
+
+* The following config options are no longer used: `:block-hidden-properties, :favorites, :hidden, :ignored-page-references-keywords, :preferred-format, :preferred-workflow, :feature/enable-block-timestamps?, :file/name-format, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist`. See [this code](https://github.com/logseq/logseq/blob/043927031e11053a837d8289e3334368e6647bea/src/main/frontend/handler/common/config_edn.cljs#L89-L115) for more details.
+
+#### DB Graph Directories
+
+* Graphs have a convention of `~/logseq/graphs/GRAPH-NAME` where `GRAPH-NAME` is the graph name. 
+* Inside a graph directory:
+    * `db.sqlite` - Stores all your graph's data including user configs.
+    * `assets/` - Stores assets like before
+    * `logseq/` no longer exists
+* It's still a TODO to sync markdown files to these graph directories.
+
+## File Graph Changes
+
+* There is no longer a [conversion feature for filename formats](https://docs.logseq.com/#/page/filename%20format)
+* The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
\ No newline at end of file
diff --git a/db-version.md b/db-version.md
index 16c4d4d..6887057 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This is a description of DB graph functionality as of Aug 29th.
+This page describes DB (database) graph functionality as of Aug 30th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 

From f46c2c13228345bfb5fba3dbf5d939b3bd9c63dd Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 2 Sep 2024 10:09:45 -0400
Subject: [PATCH 115/196] change tweaks

---
 db-version-changes.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index a0a7952..f197111 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -13,6 +13,7 @@ This page describes changes for existing Logseq features on the [database versio
 The following changes affect both file and the new db graphs:
 * To simplify editor `/` commands, [Commands](https://docs.logseq.com/#/page/commands) and [Advanced Commands](https://docs.logseq.com/#/page/advanced%20commands) are merged together under `/`.
 * A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
+* The application performance is better - loading faster and handling larger graphs. For DB graphs, our last performance test exercised 30k+ pages.
 * On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
 
 ## DB Graph Changes
@@ -22,7 +23,6 @@ High level changes:
 * Properties have a lot more functionality with the [new properties](./db-version.md#properties)!
 * Previous tags should behave like before that an inline tag is entered using `Cmd-Enter`.
     * NOTE: Pressing enter on a `#` input triggers a powerful [new tags](./db-version.md#new-tags) feature.
-* The application loads should load _much_ faster. Our last performance test exercised 30k+ pages.
 * All blocks and pages have created-at and updated-at timestamps! With this built-in dimension of time, time powered features are possible.
 *  The [previous tables](https://docs.logseq.com/#/page/tables) including version 2 are replaced by a shadcn based table. The new tables have inline editing like spreadsheets by default. Currently these tables are seen on pages of properties, new tags and the `All pages` page.
 * Markdown is the only supported format. Org mode file graphs will be able to convert to DB graphs.
@@ -35,6 +35,10 @@ WIP changes:
 * Flashcards are disabled for now and will be enabled later.
 * Exports only partially work.
 
+Miscelleanous changes:
+* There is no re-index like in file graphs.
+* For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
+
 ### Changes by Feature
 
 #### Tasks

From 5e4b3e6f54182deeeaaf33bb83ed5525fe50b9df Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 2 Sep 2024 10:48:19 -0400
Subject: [PATCH 116/196] fix: mention page properties in changes and

Should help for logseq/db-test#46. Also consistently refer to a new tag's properties as "tag properties"
---
 db-version-changes.md | 1 +
 db-version.md         | 9 +++++----
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index f197111..871c51d 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -36,6 +36,7 @@ WIP changes:
 * Exports only partially work.
 
 Miscelleanous changes:
+* Page properties are no longer set by using the first block of a page. Rather, a page property is [set the same way a block property is](./db-version.md#add-and-edit-property-values) - by editing from the page title (block content).
 * There is no re-index like in file graphs.
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
 
diff --git a/db-version.md b/db-version.md
index 6887057..86dad4c 100644
--- a/db-version.md
+++ b/db-version.md
@@ -24,7 +24,8 @@ Properties can be added to any block or page.
 
 To create your first property:
 * Create a new block
-* Press `cmd-p` and type the name of a new property
+* Press `cmd-p` and type the name of a new property.
+    * Alternatively, if your cursor is in the block, type `/pro<ENTER>` to kick off the same `Add new property` command
 * Select `Text` as the property type and then type some property value
 
 A property itself can have properties on its property page. By default the `Description` property is available for adding a description to a property.
@@ -73,9 +74,9 @@ NOTE: New tags are currently labeled as tags in the app and do not behave like t
 
 To create your first new tag:
 * Press `cmd-k` and then type `#NAME` where NAME is new tag name.
-* A dialog pops up that lets you create and/or add properties to the new tag. 
+* A dialog pops up that lets you create and/or add tag properties to the new tag. These tag properties are inherited by every node that uses the new tag.
 
-For example, say we created a new tag `Person` and added `lastName` and `birthday` properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are associated to it. A useful thing about new tags is that when its properties change those changes are immediately made to all tagged blocks and pages.
+For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all tagged nodes.
 
 A new tag can have properties on its own page. By default the `Description` property is available for adding a description to a new tag.
 
@@ -91,7 +92,7 @@ New tags are configurable by navigating to their page e.g. via `cmd-k` or clicki
 
 In the Configure panel:
 * Parent tag: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
-* Properties: Below `Parent tag`, you can add or remove existing properties to associate them with a new tag. These properties can be sorted by dragging one above or below the other. These properties will then display sorted when a new tag is used on a block or page.
+* Properties: Below `Parent tag`, you can add tag properties or remove them. These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted when a new tag is used on a block or page.
 
 ## Tasks
 

From 858463135c0e17d30825e296a356a1a406a6f29c Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 3 Sep 2024 16:52:21 -0400
Subject: [PATCH 117/196] update new tag configuration with latest changes

---
 db-version.md | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/db-version.md b/db-version.md
index 86dad4c..d4e7536 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Aug 30th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Sep 3rd. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
@@ -88,11 +88,10 @@ A powerful feature of using a parent tag is that the new tag inherits the proper
 
 ### Configure a New Tag
 
-New tags are configurable by navigating to their page e.g. via `cmd-k` or clicking on their `#` name. Then click on the `Configure tag` link below its name.
+New tags are configurable from their page. Navigate to their page by using `cmd-k` or clicking on their `#` name links. On their page below their title, two important properties display by default and are editable:
 
-In the Configure panel:
-* Parent tag: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
-* Properties: Below `Parent tag`, you can add tag properties or remove them. These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted when a new tag is used on a block or page.
+* `Parent`: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
+* `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
 
 ## Tasks
 
@@ -134,7 +133,7 @@ Since tasks are now powered by properties and [new tags](#new-tags), they can be
 
 1. The `Status` property choices can be customized by going to the `Status` page with `cmd-k`. From the property's [configuration dropdown](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
 2. Task properties can be configured by going to the property's page. From this page you can configure its icon or the ui position via the [configuration dropdown](#configure-a-property).
-3. `#Task` can be configured to have additional properties from the new tag's [configuration panel](#configure-a-new-tag).
+3. `#Task` can be configured to have additional properties from the new tag's [page](#configure-a-new-tag).
 4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from `cmd-k` and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
 
 ## DB Graph Importer

From 00a50b5972a01ad6fb6b8a6c94b48d7b1dabeba0 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 4 Sep 2024 12:12:50 -0400
Subject: [PATCH 118/196] add tagged node section

Also consistently refer to Search feature and consistently capitalize
keybindings
---
 db-version.md | 38 ++++++++++++++++++++++++--------------
 1 file changed, 24 insertions(+), 14 deletions(-)

diff --git a/db-version.md b/db-version.md
index d4e7536..ab7af24 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Sep 3rd. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Sep 4th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
@@ -24,19 +24,20 @@ Properties can be added to any block or page.
 
 To create your first property:
 * Create a new block
-* Press `cmd-p` and type the name of a new property.
+* Press `Cmd-p` and type the name of a new property.
+    * The keybinding is `Ctrl-alt-p` for Windows and Linux.
     * Alternatively, if your cursor is in the block, type `/pro<ENTER>` to kick off the same `Add new property` command
 * Select `Text` as the property type and then type some property value
 
 A property itself can have properties on its property page. By default the `Description` property is available for adding a description to a property.
 
-`cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
+`Cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
 
-`cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
+`Cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `Cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
 
 ### Configure a Property
 
-Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with `cmd-k` and then clicking on the `Configure property` link below its name.
+Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` link below its name.
 
 Property fields in the dropdown menu:
 
@@ -49,7 +50,7 @@ Property fields in the dropdown menu:
 
 ### Built-in Properties
 
-Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use `cmd-k`. For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are its icon, `UI position`, `Hide by default` and `Available choices`.
+Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use [Search](https://docs.logseq.com/#/page/search). For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are its icon, `UI position`, `Hide by default` and `Available choices`.
 
 ### Property Types
 
@@ -73,26 +74,35 @@ If a property has already been used, it is possible to convert it to use choices
 NOTE: New tags are currently labeled as tags in the app and do not behave like the previous tags. These `new tags` are also known as classes, types or supertags. Feedback is welcome on names for `new tags`.
 
 To create your first new tag:
-* Press `cmd-k` and then type `#NAME` where NAME is new tag name.
+* Open [Search](https://docs.logseq.com/#/page/search) and type `#NAME` where NAME is new tag name.
 * A dialog pops up that lets you create and/or add tag properties to the new tag. These tag properties are inherited by every node that uses the new tag.
 
-For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all tagged nodes.
+For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all [tagged nodes](#tagged-node).
 
 A new tag can have properties on its own page. By default the `Description` property is available for adding a description to a new tag.
 
 ### Parent Tags
 
-New tags can have a parent tag, defaulting to `Root tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Child tags` section.
+New tags can have a parent tag, defaulting to `Root tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Children` section.
 
 A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
 
 ### Configure a New Tag
 
-New tags are configurable from their page. Navigate to their page by using `cmd-k` or clicking on their `#` name links. On their page below their title, two important properties display by default and are editable:
+New tags are configurable from their page. Navigate to their page by using [Search](https://docs.logseq.com/#/page/search) or clicking on their `#` name links. On their page below their title, two important properties display by default and are editable:
 
 * `Parent`: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
 * `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
 
+### Tagged Node
+
+A tagged node is a page or block that has a new tag. A tagged node is also known as an object or a new tag instance. There are a couple of ways to create tagged nodes:
+* In the current block or page title, type `#` at the end and select a new tag.
+* In [Search](https://docs.logseq.com/#/page/search), type `PAGE #TAG` to create a page named `PAGE` with new tag `TAG`.
+* In a block after `[[]]`, type `#` and select a new tag. For example `[[block content]]#TAG` links to the block with `block content` and adds `#TAG`. For existing references, a new tag is added to the node. For new references, a new page is created with the new tag.
+
+A tagged node can have multiple new tags. Once a node is tagged it displays all tags' properties as empty off the node in positions configured by each property. The only properties that don't display are ones hidden via `Hide by default`.
+
 ## Tasks
 
 Tasks are improved from the previous version as they more powerful and customizable. All tasks are blocks with the built-in new tag `#Task`. When a task is created it has the properties status, priority and deadline.
@@ -100,7 +110,7 @@ Tasks are improved from the previous version as they more powerful and customiza
 ### Create a Task
 
 A new task can be created in a number of ways:
-* Set the status of a block by typing the status choice e.g. `/todo` or cyling status with `cmd-enter`.
+* Set the status of a block by typing the status choice e.g. `/todo` or cyling status with `Cmd-Enter`.
 * Type text in a block and end it with `#Task`.
 * When on the `Task` page, create a new row in the Task table.
 
@@ -112,7 +122,7 @@ Any block can have a task property value set with a command or a keybinding. The
 * To set property `priority`, press `p p`.
 * To set property `deadline`, press `p d`.
 
-The statuses `Todo`, `Doing` and `Done` can be cycled through with `cmd-enter`.
+The statuses `Todo`, `Doing` and `Done` can be cycled through with `Cmd-Enter`.
 
 The `/STATUS` commands can set a status where `STATUS` is one of the status choices e.g. `/todo`. Similarly, priority choices can be set with `/PRIORITY` commands. `/Deadline` sets the deadline property.
 
@@ -131,10 +141,10 @@ The status property is probably the most often used task property and thus it ha
 
 Since tasks are now powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
 
-1. The `Status` property choices can be customized by going to the `Status` page with `cmd-k`. From the property's [configuration dropdown](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
+1. The `Status` property choices can be customized by going to the `Status` page with [Search](https://docs.logseq.com/#/page/search). From the property's [configuration dropdown](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
 2. Task properties can be configured by going to the property's page. From this page you can configure its icon or the ui position via the [configuration dropdown](#configure-a-property).
 3. `#Task` can be configured to have additional properties from the new tag's [page](#configure-a-new-tag).
-4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from `cmd-k` and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
+4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from [Search](https://docs.logseq.com/#/page/search) and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
 
 ## DB Graph Importer
 

From a1bc307dbcfc0c6abcb3f1922ea1441c890e1c04 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 4 Sep 2024 16:30:42 -0400
Subject: [PATCH 119/196] Improve node section and add pages one

Also update recent changes and undocumented Cmd-click
---
 db-version-changes.md | 13 +++++++++++--
 db-version.md         | 20 ++++++++++++++++++--
 2 files changed, 29 insertions(+), 4 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 871c51d..f24c51e 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -29,23 +29,26 @@ High level changes:
 * Zotero integration isn't planned to be a built-in feature and will hopefully moved to a plugin.
 
 WIP changes:
-* Namespaces don't exist for now. This is likely to change. In the meantime, use [new tags](./db-version.md#new-tags) and their ability to have child tags to recreate most of it.
 * Queries are to be updated to use the new tables and have more powerful filters.
 * Whiteboards are disabled for now and will be enabled later.
 * Flashcards are disabled for now and will be enabled later.
 * Exports only partially work.
 
 Miscelleanous changes:
-* Page properties are no longer set by using the first block of a page. Rather, a page property is [set the same way a block property is](./db-version.md#add-and-edit-property-values) - by editing from the page title (block content).
 * There is no re-index like in file graphs.
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
 
 ### Changes by Feature
 
+#### Pages
+* Page properties are no longer set by using the first block of a page. Rather, a page property is [set the same way a block property is](./db-version.md#add-and-edit-property-values) - by editing from the page title (block content).
+* Clicking on a page title edits it instead of navigating to the page. To navigate to the page, press `Cmd` and click.
+
 #### Tasks
 
 * Using terms from the [previous tasks](https://docs.logseq.com/#/page/tasks), a task marker, priority and deadline are respectively now `Status`, `Priority` and `Deadline` properties on a task.
 * [Scheduled](https://docs.logseq.com/#/page/tasks/block/deadline%20and%20scheduled) has been deprecated.
+* Recurring tasks aren't ported and are a TODO.
 * Logbook timestamps have been deprecated.
 * Read more about the [new tasks](./db-version.md#tasks).
 
@@ -55,6 +58,12 @@ Miscelleanous changes:
 * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
 * Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
 
+#### Namespaces
+* There is partial support for namespaces but it's still a TODO to port over popular workflows.
+* Pages can have hierarchy by using the `Parent` property. For example, create a page `block`. Add a `Parent` property page and create a page called `term` in it. There is now a `term > block` hierarchy.
+* A namespace page like `term` above has its children pages listed on its page under the `Children` section.
+* Children pages like `block` above link back to its namespace with the `Parent` property.
+
 #### Config.edn
 
 * The following config options are no longer used: `:block-hidden-properties, :favorites, :hidden, :ignored-page-references-keywords, :preferred-format, :preferred-workflow, :feature/enable-block-timestamps?, :file/name-format, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist`. See [this code](https://github.com/logseq/logseq/blob/043927031e11053a837d8289e3334368e6647bea/src/main/frontend/handler/common/config_edn.cljs#L89-L115) for more details.
diff --git a/db-version.md b/db-version.md
index ab7af24..3f0a8e1 100644
--- a/db-version.md
+++ b/db-version.md
@@ -14,7 +14,21 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 
 ## Nodes
 
-Nodes is a new term for pages or blocks because the two now behave similarly. Nodes are both referenced by using `[[]]`. Nodes have a similar editing experience as they can set properties, use `/` commands, and use the [new tags](#new-tags). Like pages, blocks have a `Linked References` section when you zoom into a block.. Blocks and pages still have some differences that we are hoping to unify like the block view when it is zoomed in.
+A node is a new term for a page or block because the two now behave similarly. Nodes have the following common behaviors:
+
+* Nodes are referenced by using `[[]]`
+* Nodes have a pretty similar editing experience whether changing block content or a page title. In the editing block, properties can be set, `/` commands are available and [new tags](#new-tags) can be set.
+* Nodes have `Linked References` and `Unlinked References` sections. Blocks need to be zoomed in to see this.
+* Nodes can be favorited. For a zoomed in block, use the `Add to/remove from favorites` command.
+* Nodes share the same keybindings for properties including [adding and editing them](#add-and-edit-property-values) and toggling their visibility with `Cmd-;`.
+
+Blocks and pages still have some differences that we are hoping to unify like the block view when it is zoomed in.
+
+### Pages
+
+While pages and blocks have become more unified as explained above, there are some unique things to pages:
+* Press `Cmd` and click on a page title to navigate to it.
+* Hovering over a page title shows common features like `Set Property` to add a property to the page.
 
 ## Properties
 
@@ -37,7 +51,7 @@ A property itself can have properties on its property page. By default the `Desc
 
 ### Configure a Property
 
-Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` link below its name.
+Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Press `Cmd` and click to navigate to a property page. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` link below its name.
 
 Property fields in the dropdown menu:
 
@@ -103,6 +117,8 @@ A tagged node is a page or block that has a new tag. A tagged node is also known
 
 A tagged node can have multiple new tags. Once a node is tagged it displays all tags' properties as empty off the node in positions configured by each property. The only properties that don't display are ones hidden via `Hide by default`.
 
+A tagged node can have an icon. When it does have an icon, it will appear to the left of its name or in a reference.
+
 ## Tasks
 
 Tasks are improved from the previous version as they more powerful and customizable. All tasks are blocks with the built-in new tag `#Task`. When a task is created it has the properties status, priority and deadline.

From c316ab3e474a3472eddf893b7137efa28b63ee49 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 4 Sep 2024 16:35:46 -0400
Subject: [PATCH 120/196] Forgot to mention tag property descriptions

---
 db-version.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version.md b/db-version.md
index 3f0a8e1..78b8d36 100644
--- a/db-version.md
+++ b/db-version.md
@@ -107,6 +107,7 @@ New tags are configurable from their page. Navigate to their page by using [Sear
 
 * `Parent`: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
 * `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
+  * To the right of each tag property there is an optional block for describing the property. This description also shows up on the property's page.
 
 ### Tagged Node
 

From fbb19dbb5c7467afbdf566459217be3eed48988f Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 6 Sep 2024 18:54:30 -0400
Subject: [PATCH 121/196] Document new journal class, two newish shortcuts

and newish class property
---
 db-version.md | 19 ++++++++++++++-----
 1 file changed, 14 insertions(+), 5 deletions(-)

diff --git a/db-version.md b/db-version.md
index 78b8d36..8a9511d 100644
--- a/db-version.md
+++ b/db-version.md
@@ -10,6 +10,7 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 * [Properties](#properties)
 * [New Tags](#new-tags)
 * [Tasks](#tasks)
+* [Journals](#journals)
 * [DB Graph Importer](#db-graph-importer)
 
 ## Nodes
@@ -20,7 +21,8 @@ A node is a new term for a page or block because the two now behave similarly. N
 * Nodes have a pretty similar editing experience whether changing block content or a page title. In the editing block, properties can be set, `/` commands are available and [new tags](#new-tags) can be set.
 * Nodes have `Linked References` and `Unlinked References` sections. Blocks need to be zoomed in to see this.
 * Nodes can be favorited. For a zoomed in block, use the `Add to/remove from favorites` command.
-* Nodes share the same keybindings for properties including [adding and editing them](#add-and-edit-property-values) and toggling their visibility with `Cmd-;`.
+* Nodes share the same keybindings for [properties](#property-shortcuts) and blocks e.g. toggling block properties visibility with `Cmd-;`.
+* Nodes are embedded with the same `/Node embed` command.
 
 Blocks and pages still have some differences that we are hoping to unify like the block view when it is zoomed in.
 
@@ -45,9 +47,12 @@ To create your first property:
 
 A property itself can have properties on its property page. By default the `Description` property is available for adding a description to a property.
 
-`Cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
+### Property Shortcuts
 
-`Cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `Cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
+* `Cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
+* `Cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `Cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
+* `p t` toggles displaying all the current node's properties below it. This is useful to quickly view properties that are hidden or in a different position.
+* `p i` opens the icon picker to set an icon for the current node.
 
 ### Configure a Property
 
@@ -93,7 +98,7 @@ To create your first new tag:
 
 For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all [tagged nodes](#tagged-node).
 
-A new tag can have properties on its own page. By default the `Description` property is available for adding a description to a new tag.
+A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right.
 
 ### Parent Tags
 
@@ -156,13 +161,17 @@ The status property is probably the most often used task property and thus it ha
 
 ### Customizing Tasks
 
-Since tasks are now powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
+Since tasks are powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
 
 1. The `Status` property choices can be customized by going to the `Status` page with [Search](https://docs.logseq.com/#/page/search). From the property's [configuration dropdown](#configure-a-property) edit the name and icon of built-in choices. You can add new choices but not delete the built-in ones.
 2. Task properties can be configured by going to the property's page. From this page you can configure its icon or the ui position via the [configuration dropdown](#configure-a-property).
 3. `#Task` can be configured to have additional properties from the new tag's [page](#configure-a-new-tag).
 4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from [Search](https://docs.logseq.com/#/page/search) and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
 
+## Journals
+
+A journal page has the [new tag](#new-tags) `#Journal`. Like tasks, journals can be customized by adding properties to its tag. For example, navigate to the `#Journal` page and add a property. This property now shows up on all journals!
+
 ## DB Graph Importer
 
 The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.

From 5c0e8eee3347e42f2d82acaae5677b9b1e3ebf4a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 11 Sep 2024 08:28:42 -0400
Subject: [PATCH 122/196] remove outdated title differences and note
 collapsible node

---
 db-version-changes.md | 1 -
 db-version.md         | 4 ++--
 2 files changed, 2 insertions(+), 3 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index f24c51e..84ebc40 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -42,7 +42,6 @@ Miscelleanous changes:
 
 #### Pages
 * Page properties are no longer set by using the first block of a page. Rather, a page property is [set the same way a block property is](./db-version.md#add-and-edit-property-values) - by editing from the page title (block content).
-* Clicking on a page title edits it instead of navigating to the page. To navigate to the page, press `Cmd` and click.
 
 #### Tasks
 
diff --git a/db-version.md b/db-version.md
index 8a9511d..abd54d9 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Sep 4th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Sep 11th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
 
@@ -23,13 +23,13 @@ A node is a new term for a page or block because the two now behave similarly. N
 * Nodes can be favorited. For a zoomed in block, use the `Add to/remove from favorites` command.
 * Nodes share the same keybindings for [properties](#property-shortcuts) and blocks e.g. toggling block properties visibility with `Cmd-;`.
 * Nodes are embedded with the same `/Node embed` command.
+* Nodes are collapsible with an arrow on the left that appears on hover.
 
 Blocks and pages still have some differences that we are hoping to unify like the block view when it is zoomed in.
 
 ### Pages
 
 While pages and blocks have become more unified as explained above, there are some unique things to pages:
-* Press `Cmd` and click on a page title to navigate to it.
 * Hovering over a page title shows common features like `Set Property` to add a property to the page.
 
 ## Properties

From 7285a47831673bdd57ff3559086ddfd0e0990bf2 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 11 Sep 2024 11:28:22 -0400
Subject: [PATCH 123/196] link two shortcut sections

---
 db-version.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version.md b/db-version.md
index abd54d9..c90ebc2 100644
--- a/db-version.md
+++ b/db-version.md
@@ -53,6 +53,7 @@ A property itself can have properties on its property page. By default the `Desc
 * `Cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `Cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
 * `p t` toggles displaying all the current node's properties below it. This is useful to quickly view properties that are hidden or in a different position.
 * `p i` opens the icon picker to set an icon for the current node.
+* See [task shortcuts](#task-shortcuts) for task specific ones.
 
 ### Configure a Property
 

From 5dc91791803d53ef4592dd2a15a8434b170dbf7e Mon Sep 17 00:00:00 2001
From: Bad3r <bad3r@pm.me>
Date: Wed, 11 Sep 2024 20:08:54 +0300
Subject: [PATCH 124/196] add clarification for cmd-p for win/linux (cmd+alt+p)
 (#126)

* add clarification for cmd-p for win/linux (cmd+alt+p)

https://github.com/logseq/db-test/issues/64#issuecomment-2338382956

* Fix: typo
---
 db-version.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version.md b/db-version.md
index c90ebc2..9a3885b 100644
--- a/db-version.md
+++ b/db-version.md
@@ -50,6 +50,7 @@ A property itself can have properties on its property page. By default the `Desc
 ### Property Shortcuts
 
 * `Cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
+   * `Ctrl+Alt+p` on Linux and Windows
 * `Cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `Cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
 * `p t` toggles displaying all the current node's properties below it. This is useful to quickly view properties that are hidden or in a different position.
 * `p i` opens the icon picker to set an icon for the current node.

From 2638ef613e21f43c68dc6e4632dacfb88b4c4087 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 12 Sep 2024 10:53:13 -0400
Subject: [PATCH 125/196] updates to mention page types and uniqueness

---
 db-version.md | 24 +++++++++++++++++++-----
 1 file changed, 19 insertions(+), 5 deletions(-)

diff --git a/db-version.md b/db-version.md
index 9a3885b..ddbc659 100644
--- a/db-version.md
+++ b/db-version.md
@@ -17,21 +17,36 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 
 A node is a new term for a page or block because the two now behave similarly. Nodes have the following common behaviors:
 
-* Nodes are referenced by using `[[]]`
+* Nodes are referenced by using `[[]]`.
 * Nodes have a pretty similar editing experience whether changing block content or a page title. In the editing block, properties can be set, `/` commands are available and [new tags](#new-tags) can be set.
 * Nodes have `Linked References` and `Unlinked References` sections. Blocks need to be zoomed in to see this.
 * Nodes can be favorited. For a zoomed in block, use the `Add to/remove from favorites` command.
 * Nodes share the same keybindings for [properties](#property-shortcuts) and blocks e.g. toggling block properties visibility with `Cmd-;`.
+* Nodes can be tagged to become a [tagged node](#tagged-node).
 * Nodes are embedded with the same `/Node embed` command.
 * Nodes are collapsible with an arrow on the left that appears on hover.
 
 Blocks and pages still have some differences that we are hoping to unify like the block view when it is zoomed in.
+However, blocks and pages will have some differences as noted in the [pages](#pages) and [blocks](#blocks) sections.
 
 ### Pages
 
-While pages and blocks have become more unified as explained above, there are some unique things to pages:
+Things that are specific to pages:
+* Pages have a dedicated view called `All pages`.
+* As seen on `All pages`, pages have different page types: `Page, Property, Tag, Journal and Whiteboard`. Think of these as directories on a file system.
+* Pages are unique as follows:
+  * Page names of type 'page' are unique by tag e.g. there can be `Apple #Company` and `Apple #Fruit`.
+  * Property names are unique and can have the same names as built-in property names.
+  * Page names of other types are unique for their page type e.g. there can be a `#Journal` and a Journal page.
+  * The uniqueness of these pages should be visible everywhere in the app with icons for page types and the display of a page's tag(s).
 * Hovering over a page title shows common features like `Set Property` to add a property to the page.
 
+### Blocks
+
+Things that are specific to blocks:
+* Blocks are created in a page.
+* Tagged blocks a.k.a. blocks with names do not have unique names.
+
 ## Properties
 
 ### Add and Edit Property Values 
@@ -41,7 +56,7 @@ Properties can be added to any block or page.
 To create your first property:
 * Create a new block
 * Press `Cmd-p` and type the name of a new property.
-    * The keybinding is `Ctrl-alt-p` for Windows and Linux.
+    * The keybinding is `Ctrl-alt-p` on Linux and Windows.
     * Alternatively, if your cursor is in the block, type `/pro<ENTER>` to kick off the same `Add new property` command
 * Select `Text` as the property type and then type some property value
 
@@ -49,8 +64,7 @@ A property itself can have properties on its property page. By default the `Desc
 
 ### Property Shortcuts
 
-* `Cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it.
-   * `Ctrl+Alt+p` on Linux and Windows
+* `Cmd-p` is useful for quickly adding properties to a block or a page. You can create or select existing properties from it. Keybinding is `Ctrl-Alt-p` on Linux and Windows.
 * `Cmd-j` is useful for quickly editing block or page properties from the keyboard. After pressing `Cmd-j`, choose which property or property value by typing the letters in the bubble next to it e.g. `c` or `ab`.
 * `p t` toggles displaying all the current node's properties below it. This is useful to quickly view properties that are hidden or in a different position.
 * `p i` opens the icon picker to set an icon for the current node.

From 3646a0100cb77ed42c15658a3a9039aa93c9d02a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 17 Sep 2024 10:18:02 -0400
Subject: [PATCH 126/196] Doc tables, queries, backup, nlp calendar

and more changes
---
 db-version-changes.md | 18 ++++++++++++------
 db-version.md         | 34 ++++++++++++++++++++++++++++++++--
 2 files changed, 44 insertions(+), 8 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 84ebc40..cc787a6 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -24,19 +24,22 @@ High level changes:
 * Previous tags should behave like before that an inline tag is entered using `Cmd-Enter`.
     * NOTE: Pressing enter on a `#` input triggers a powerful [new tags](./db-version.md#new-tags) feature.
 * All blocks and pages have created-at and updated-at timestamps! With this built-in dimension of time, time powered features are possible.
-*  The [previous tables](https://docs.logseq.com/#/page/tables) including version 2 are replaced by a shadcn based table. The new tables have inline editing like spreadsheets by default. Currently these tables are seen on pages of properties, new tags and the `All pages` page.
+*  The [previous tables](https://docs.logseq.com/#/page/tables) including version 2 are replaced by a shadcn based table. The new tables have inline editing like spreadsheets by default. See [here](./db-version.md#tables) for more.
 * Markdown is the only supported format. Org mode file graphs will be able to convert to DB graphs.
-* Zotero integration isn't planned to be a built-in feature and will hopefully moved to a plugin.
+* Zotero integration isn't planned to be a built-in feature and will hopefully be moved to a plugin.
 
 WIP changes:
-* Queries are to be updated to use the new tables and have more powerful filters.
+* Advanced queries are to be updated to use the new tables and `#Query`. Query filters are likely to be changed.
 * Whiteboards are disabled for now and will be enabled later.
 * Flashcards are disabled for now and will be enabled later.
 * Exports only partially work.
 
 Miscelleanous changes:
+* Embedded pages and blocks look almost the same as other nodes. The main indicator of an embed will be an icon to the left of the block.
+* Default date picker now has an input for typing a date in natural language.
 * There is no re-index like in file graphs.
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
+* `All Pages` view can toggle between table and list view.
 
 ### Changes by Feature
 
@@ -56,6 +59,8 @@ Miscelleanous changes:
 * Since block timestamps are available, they display in table view where possible.
 * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
 * Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
+* The `sort-by` query filter no longer exists. Sorting is done via the table component.
+* When using the query builder, the resulting query's text is not meant to be easily read as internal ids are used for some concepts e.g. properties.
 
 #### Namespaces
 * There is partial support for namespaces but it's still a TODO to port over popular workflows.
@@ -63,9 +68,10 @@ Miscelleanous changes:
 * A namespace page like `term` above has its children pages listed on its page under the `Children` section.
 * Children pages like `block` above link back to its namespace with the `Parent` property.
 
-#### Config.edn
+#### User Config
 
-* The following config options are no longer used: `:block-hidden-properties, :favorites, :hidden, :ignored-page-references-keywords, :preferred-format, :preferred-workflow, :feature/enable-block-timestamps?, :file/name-format, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist`. See [this code](https://github.com/logseq/logseq/blob/043927031e11053a837d8289e3334368e6647bea/src/main/frontend/handler/common/config_edn.cljs#L89-L115) for more details.
+* A graph's config.edn, custom.js and custom.css files are only editable within Logseq from `Settings`.
+* The following config.edn options are no longer used: `:block-hidden-properties, :favorites, :hidden, :ignored-page-references-keywords, :preferred-format, :preferred-workflow, :feature/enable-block-timestamps?, :file/name-format, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist`. See [this code](https://github.com/logseq/logseq/blob/043927031e11053a837d8289e3334368e6647bea/src/main/frontend/handler/common/config_edn.cljs#L89-L115) for more details.
 
 #### DB Graph Directories
 
@@ -73,7 +79,7 @@ Miscelleanous changes:
 * Inside a graph directory:
     * `db.sqlite` - Stores all your graph's data including user configs.
     * `assets/` - Stores assets like before
-    * `logseq/` no longer exists
+* `logseq/` inside a directory no longer exists.
 * It's still a TODO to sync markdown files to these graph directories.
 
 ## File Graph Changes
diff --git a/db-version.md b/db-version.md
index ddbc659..53f8f63 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,8 +1,8 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Sep 11th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Sep 17th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
-NOTE: There is currently no automated graph backup for the DB version. Recommend only using this for testing purposes.
+NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using this for testing purposes.
 
 ## Overview
 
@@ -11,7 +11,10 @@ NOTE: There is currently no automated graph backup for the DB version. Recommend
 * [New Tags](#new-tags)
 * [Tasks](#tasks)
 * [Journals](#journals)
+* [Queries](#queries)
+* [Tables](#tables)
 * [DB Graph Importer](#db-graph-importer)
+* [Automated Backup](#automated-backup)
 
 ## Nodes
 
@@ -188,6 +191,29 @@ Since tasks are powered by properties and [new tags](#new-tags), they can be cus
 
 A journal page has the [new tag](#new-tags) `#Journal`. Like tasks, journals can be customized by adding properties to its tag. For example, navigate to the `#Journal` page and add a property. This property now shows up on all journals!
 
+Journals are automatically created for the current day in the Journals view. There are a couple of ways to create a journal:
+* Use the `/Date picker` command to insert a specific date. The date picker is keyboard friendly as arrow keys change calendar days and `Tab` focuses the input. The input takes natural language e.g. `next week` and converts it to a date. See [the library we use](https://github.com/wanasit/chrono#readme) for other natural language examples.
+* Properties with the :date property type e.g. `Deadline` create journals for their property values.
+* When on a journal day, create a journal for the next day or previous day by using the keybindings `g n` or `g p` respectively.
+
+## Queries
+
+A [query](https://docs.logseq.com/#/page/queries) has the [new tag](#new-tags) `#Query`. Queries are created by using the `/Query` command. Like other new tags, go to the `#Query` page to see a table to manage queries. Query results are displayed with the new [tables](#tables).
+
+## Tables
+
+A table displays a group of nodes as rows and a node's properties as columns. A table behaves like a spreadsheet as table cells are editable by default. A node has the following special columns which are available by default: `Name`, `Created At` and `Updated At`. Tables have the following features:
+* Sort rows by any column, ascending or descending.
+* Filter rows by multiple columns by clicking on the filter icon. For columns with a specific property type e.g. :number and :date, there are specific filters for that type.
+* Hide columns by clicking on the three dots menu and selecting `Columns visibility`.
+* Drag columns to sort their order.
+* Switch between `Table View` and `List View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages.
+* Click on the magnifying glass icon to live search a table. This is the only feature that doesn't persist when switching away from a table.
+
+A powerful new feature of tables is the ability to create a table view. This is currently enabled for tag pages. To use it, click the `+` icon in the upper left to create a new tab in the table. Click on the tab's header to rename or delete this new view. Within this view, all of the above persisting features will save!
+
+Tables are currently found on new tag pages, property pages, query results and the `All Pages` view.
+
 ## DB Graph Importer
 
 The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.
@@ -208,3 +234,7 @@ All tasks are imported as new [tasks](#tasks). Some task statuses have been rema
     1. `Tags to import ...` - This input converts any of your old tags to the [new tags](#new-tags). This is helpful if you've been using a particular tag like a new tag. You can also convert pages later by right clicking on a page's name.
     2. `Properties whose values are imported as new tags` - This input converts property values for the specified property to the new tags. For example, in the official docs graph the [type property](https://docs.logseq.com/#/page/type) is used this way. This means that all `type` property values like [Feature](https://docs.logseq.com/#/page/feature) on [this page](https://docs.logseq.com/#/page/code%20block) would get converted to the new tag.
     3. `Properties whose values are imported as parents of ...` - This input converts property values for the specified property to be [a parent of a new tag](#parent-tags). For example, in the official docs graph the [parent property](https://docs.logseq.com/#/page/parent) is used this way. This means that all `parent` property values like [Thing](https://docs.logseq.com/#/page/thing) on [this page](https://docs.logseq.com/#/page/feature) would get converted to the new tag.
+
+## Automated Backup
+
+An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
\ No newline at end of file

From 7e2205afab2fe976912a5014b369dd72392d9758 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 17 Sep 2024 16:52:19 -0400
Subject: [PATCH 127/196] fix prop and class names

---
 db-version.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/db-version.md b/db-version.md
index 53f8f63..225d702 100644
--- a/db-version.md
+++ b/db-version.md
@@ -52,7 +52,7 @@ Things that are specific to blocks:
 
 ## Properties
 
-### Add and Edit Property Values 
+### Add and Edit Property Values
 
 Properties can be added to any block or page.
 
@@ -121,7 +121,7 @@ A new tag can have properties on its own page. By default the `Description` prop
 
 ### Parent Tags
 
-New tags can have a parent tag, defaulting to `Root tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Children` section.
+New tags can have a parent tag, defaulting to `Root Tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Children` section.
 
 A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
 
@@ -129,7 +129,7 @@ A powerful feature of using a parent tag is that the new tag inherits the proper
 
 New tags are configurable from their page. Navigate to their page by using [Search](https://docs.logseq.com/#/page/search) or clicking on their `#` name links. On their page below their title, two important properties display by default and are editable:
 
-* `Parent`: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root tag` which doesn't have any properties.
+* `Parent`: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root Tag` which doesn't have any properties.
 * `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
   * To the right of each tag property there is an optional block for describing the property. This description also shows up on the property's page.
 
@@ -216,7 +216,7 @@ Tables are currently found on new tag pages, property pages, query results and t
 
 ## DB Graph Importer
 
-The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `pageTags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `pageTags`. The importer also provides two options to convert property related pages to new tags.
+The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `Page Tags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `Page Tags`. The importer also provides two options to convert property related pages to new tags.
 
 All tasks are imported as new [tasks](#tasks). Some task statuses have been remapped to avoid duplicates e.g. `TODO` and `LATER`. The following statuses have been remapped:
 
@@ -237,4 +237,4 @@ All tasks are imported as new [tasks](#tasks). Some task statuses have been rema
 
 ## Automated Backup
 
-An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
\ No newline at end of file
+An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.

From 1a303afc209dfe14380b23134fff7e8c82e621d5 Mon Sep 17 00:00:00 2001
From: sudo-nano <cwg1231@gmail.com>
Date: Wed, 18 Sep 2024 16:31:10 -0700
Subject: [PATCH 128/196] Organized contents into subsections

---
 pages/contents.md | 107 ++++++++++++++++++++++++----------------------
 1 file changed, 57 insertions(+), 50 deletions(-)

diff --git a/pages/contents.md b/pages/contents.md
index 3da9861..b12f69f 100644
--- a/pages/contents.md
+++ b/pages/contents.md
@@ -1,64 +1,71 @@
-- 🌟 [[New to Logseq?]]
-	- [[Start here]]
-	- [[How to create a new graph]]
-	- [[How to create a Logseq graph using existing Markdown files]]
-	- [[Getting started with the Journals page]]
-	- [[How to create pages in Logseq]]
-	- [[Why linking matters]]
-	- [[Aliases and external links]]
-	- [[What is indentation and why does it matter?]]
-	- [[How to filter linked references]]
-	- [[The basics of block references]]
-	- [[The difference between block embeds and block references]]
-	- [[The difference between block embeds and page embeds]]
-	- [[How to work with the right-hand sidebar]]
-	- [[How to sync your Logseq graph across devices]]
-- Miscellaneous
+## 🌟[[New to Logseq?]]
+	- ### Basics
+		- [[Start here]]
+		- [[How to create a new graph]]
+		- [[How to create a Logseq graph using existing Markdown files]]
+		- [[Getting started with the Journals page]]
+		- [[How to create pages in Logseq]]
+		- [[What is indentation and why does it matter?]]
+	- ### Linking
+		- [[Why linking matters]]
+		- [[Aliases and external links]]
+		- [[How to filter linked references]]
+	- ### References and Embeds
+		- [[The basics of block references]]
+		- [[The difference between block embeds and block references]]
+		- [[The difference between block embeds and page embeds]]
+	- ### Extra
+		- [[How to work with the right-hand sidebar]]
+		- [[How to sync your Logseq graph across devices]]
+- ## Miscellaneous
 	- [Roadmap](https://trello.com/b/8txSM12G/logseq-roadmap)
 	- [[Changelog]]
 	- [[Videos]]
 	- [[FAQ]]
 	- [[Glossary]]
 	- [[Testimonials]]
-	- [Awesome Logseq](https://github.com/logseq/awesome-logseq) (community contributions)
-- [[Features]]
-	- [Backlink]([[term/backlink]])
-	- [[Knowledge Graph]]
-	- [[Page and block references]]
-	- [[Page embed]] and [[Block embed]]
-	- [[Tasks]]
-	- [[Commands]]
-	- [[Advanced commands]]
-	- [[Templates]]
-	- [Page alias]([[term/alias]])
-	- [[Properties]]
-	- [[Publishing]]
-	- [[PDF highlights]]
-	- [[Flashcards]]
-	- [[Draw]]
-	- [[Slide]]
-	- [[Calculator]]
-	- [[Custom theme]]
-	- [[Zotero]] integration
-	- [[Embed Media - Audio, Photos, Videos]]
-	- [[Plugins]]
-	- [[Queries]] and [[Query Builder]]
-	- [[Whiteboard]]
-	- [[Tables]]
-- [[Logseq School]]
-	- [[Plugins 101]]
-- [[Document syntax]]
-	- [[Markdown]]
-	- [[Org Mode]]
-- 👤 [[Settings]]
-- ✨ [[Tips and Tricks]]
-- [[Advanced Logseq]]
+	- [Awesome Logseq](https://github.com/logseq/awesome-logseq) (community extensions and resources)
+- ## [[Features]]
+	- ### Basic Features
+		- [[Document syntax]]
+			- [[Markdown]]
+			- [[Org Mode]]
+		- [Backlink]([[term/backlink]])
+		- [[Knowledge Graph]]
+		- [[Page and block references]]
+		- [[Page embed]] and [[Block embed]]
+		- [Page alias]([[term/alias]])
+		- [[Properties]]
+	- ### Productivity
+		- [[Tasks]]
+		- [[Commands]]
+		- [[Advanced commands]]
+		- [[Templates]]
+	- ### Media
+		- [[Draw]]
+		- [[Whiteboard]]
+		- [[PDF highlights]]
+		- [[Embed Media - Audio, Photos, Videos]]
+		- [[Zotero]] integration
+	- ### Tools
+		- [[Flashcards]]
+		- [[Slide]]
+		- [[Calculator]]
+		- [[Queries]] and [[Query Builder]]
+		- [[Tables]]
+		- [[Publishing]]
+	- ### Customization
+		- [[Custom theme]]
+		- [[Plugins]]
+		- 👤 [[Settings]]
+- ## [[Advanced Logseq]]
+	- ✨ [[Tips and Tricks]]
 	- [[Keyboard shortcuts]]
 	- [[Advanced Queries]]
 	- [[Hiccup]]
 	- [[Filename format]]
 	- [[Migrate to Logseq Beta]]
-- [[Contribute]]
+- ## [[Contribute]]
 	- Make a [Feature Request](https://discuss.logseq.com/)
 	- [Check us out on Github](https://github.com/logseq/logseq)
 	- [Contribute to Our Docs](https://github.com/logseq/docs)

From 5af10c8f7b9a52354db1c935bbad2c55b9a11bf1 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 23 Sep 2024 17:33:21 -0400
Subject: [PATCH 129/196] add note about finding commands for shortcuts

---
 db-version.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/db-version.md b/db-version.md
index 225d702..a56f0ea 100644
--- a/db-version.md
+++ b/db-version.md
@@ -73,6 +73,8 @@ A property itself can have properties on its property page. By default the `Desc
 * `p i` opens the icon picker to set an icon for the current node.
 * See [task shortcuts](#task-shortcuts) for task specific ones.
 
+NOTE: Most shortcuts have a corresponding search command. You can find the command for a given shortcut's keys keybinding by using `Settings > Keymap`, clicking the keystroke filter and typing the keys.
+
 ### Configure a Property
 
 Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Press `Cmd` and click to navigate to a property page. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` link below its name.

From 5c1b3e5d6688af71fdb1fea76ed78f53d2e61073 Mon Sep 17 00:00:00 2001
From: rcmerci <rcmerci@gmail.com>
Date: Sat, 28 Sep 2024 17:12:03 +0800
Subject: [PATCH 130/196] doc cards

---
 db-version.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/db-version.md b/db-version.md
index a56f0ea..5aaa082 100644
--- a/db-version.md
+++ b/db-version.md
@@ -15,6 +15,7 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
 * [Tables](#tables)
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
+* [Cards](#cards)
 
 ## Nodes
 
@@ -240,3 +241,18 @@ All tasks are imported as new [tasks](#tasks). Some task statuses have been rema
 ## Automated Backup
 
 An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
+
+## Cards
+SRS Cards feature has been re-implemented in DB-version based on [cljc-fsrs](https://github.com/open-spaced-repetition/cljc-fsrs).
+
+### Create new cards
+* Tag blocks with `#Card` to create new cards.
+* To convert multiple blocks into cards at once, select them, right-click and choose `Make a flashcard`.
+
+### View cards
+All cards are accessible on the `#Card` page within the tagged-nodes table.  
+The `Due` column indicates when the next review is scheduled.
+  
+### Review cards
+Select `Flashcards` from the left sidebar to view all cards due for review.  
+you can rating them using 4 levels to arrange their next review date.

From c8183f8bfcd999d98d945d4e0d9729343dd69466 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 1 Oct 2024 09:07:03 -0400
Subject: [PATCH 131/196] add docs for queries, namespaces, commands, nlp refs

datetime, etc.
---
 db-version-changes.md | 27 ++++++++++---
 db-version.md         | 88 ++++++++++++++++++++++++++++---------------
 2 files changed, 78 insertions(+), 37 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index cc787a6..e731c25 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -25,14 +25,19 @@ High level changes:
     * NOTE: Pressing enter on a `#` input triggers a powerful [new tags](./db-version.md#new-tags) feature.
 * All blocks and pages have created-at and updated-at timestamps! With this built-in dimension of time, time powered features are possible.
 *  The [previous tables](https://docs.logseq.com/#/page/tables) including version 2 are replaced by a shadcn based table. The new tables have inline editing like spreadsheets by default. See [here](./db-version.md#tables) for more.
+* Flashcards have been re-implemented with [a new algorithm](https://github.com/open-spaced-repetition/free-spaced-repetition-scheduler). It isn't compatible with the previous flashcards so none of the properties and srs data from the previous version is imported.
 * Markdown is the only supported format. Org mode file graphs will be able to convert to DB graphs.
 * Zotero integration isn't planned to be a built-in feature and will hopefully be moved to a plugin.
+* A few [Advanced Commands](https://docs.logseq.com/#/page/advanced%20commands) are available. More may become available as requested. The available commands are:
+  * `>Query` is now `/Advanced Query`
+  * `>Src` is now `/Code block`
+  * `>Quote` is `/Quote`
 
 WIP changes:
-* Advanced queries are to be updated to use the new tables and `#Query`. Query filters are likely to be changed.
+* Query filters are likely to be changed.
 * Whiteboards are disabled for now and will be enabled later.
-* Flashcards are disabled for now and will be enabled later.
 * Exports only partially work.
+* Sync and RTC will be enabled later.
 
 Miscelleanous changes:
 * Embedded pages and blocks look almost the same as other nodes. The main indicator of an embed will be an icon to the left of the block.
@@ -40,11 +45,17 @@ Miscelleanous changes:
 * There is no re-index like in file graphs.
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
 * `All Pages` view can toggle between table and list view.
+* Run the command `Customize appearance` to display a modal of appearance related settings.
 
 ### Changes by Feature
 
 #### Pages
 * Page properties are no longer set by using the first block of a page. Rather, a page property is [set the same way a block property is](./db-version.md#add-and-edit-property-values) - by editing from the page title (block content).
+* `#` and `/` are disallowered characters for page names.
+
+#### Tags
+* Tags have [a lot of new functionality](./db-version.md#new-tags).
+* When a tag is added on a block, it now displays to the right of the block. To inline a tag like before, press `Cmd-Enter` in the tag dropdown.
 
 #### Tasks
 
@@ -56,6 +67,8 @@ Miscelleanous changes:
 
 #### Queries
 
+* Simple queries can now have titles.
+* Advanced queries are now edited in a code block which means queries are syntax highlighted.
 * Since block timestamps are available, they display in table view where possible.
 * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
 * Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
@@ -63,10 +76,12 @@ Miscelleanous changes:
 * When using the query builder, the resulting query's text is not meant to be easily read as internal ids are used for some concepts e.g. properties.
 
 #### Namespaces
-* There is partial support for namespaces but it's still a TODO to port over popular workflows.
-* Pages can have hierarchy by using the `Parent` property. For example, create a page `block`. Add a `Parent` property page and create a page called `term` in it. There is now a `term > block` hierarchy.
-* A namespace page like `term` above has its children pages listed on its page under the `Children` section.
-* Children pages like `block` above link back to its namespace with the `Parent` property.
+* Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`.
+* Namespaced pages no longer have their namespace embedded in their page name. The big advantage of this is that renaming any part of the namespace does not affect all the pages under a namespace.
+* Pages can manage their namespace explicitly by using the `Parent` property. Previously managing a namespace could only be done by renaming a namespace. Using a property allows for easier management of namespace relationships.
+* The `Hierarchy` section is called `Children` for DB graphs. It now displays as a collapsible tree as this allows for viewing large namespaces more easily.
+* Children pages like `baz` above link back to its parent(namespace) with the `Parent` property.
+* The macro `{{namespace}}` is TODO.
 
 #### User Config
 
diff --git a/db-version.md b/db-version.md
index 5aaa082..d2fa014 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Sep 17th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Oct 1st. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using this for testing purposes.
 
@@ -9,13 +9,14 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
 * [Nodes](#nodes)
 * [Properties](#properties)
 * [New Tags](#new-tags)
-* [Tasks](#tasks)
-* [Journals](#journals)
-* [Queries](#queries)
+* [Tag Based Features](#tag-based-features)
+  * [Tasks](#tasks)
+  * [Journals](#journals)
+  * [Queries](#queries)
+  * [Cards](#cards)
 * [Tables](#tables)
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
-* [Cards](#cards)
 
 ## Nodes
 
@@ -100,6 +101,7 @@ A property type determines what type a property's property values can have. Ther
 * `Text`: This is the recommended default as it allows for any text and behaves like a block. This means that node references work here and children blocks can be created under the block.
 * `Number`: This is for numbers including negative numbers and floats e.g. 3.5. Unlike file graph properties, these are stored as actual numbers. This means that all features and queries that use this property type correctly sort as numbers by default.
 * `Date`: This is for dates and is editable with a date picker. When a date property value is used, it correctly links to the journal page.
+* `DateTime`: This is for date times and is editable with a datetime picker. See the `Due` property in [cards](#cards) for an example property that uses this.
 * `Checkbox`: This is used to set or unset a property value and displays as a checkbox. To engineers this type is known as a boolean.
 * `Url`: This limits text to only allow urls e.g. `https://logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
 * `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if `#Actor` is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
@@ -112,7 +114,7 @@ If a property has already been used, it is possible to convert it to use choices
 
 ## New Tags
 
-NOTE: New tags are currently labeled as tags in the app and do not behave like the previous tags. These `new tags` are also known as classes, types or supertags. Feedback is welcome on names for `new tags`.
+NOTE: New tags are currently labeled as tags in the app and should be backwards compatible with the previous tags. These `new tags` are also known as classes, types or supertags. Feedback is welcome on names for `new tags`.
 
 To create your first new tag:
 * Open [Search](https://docs.logseq.com/#/page/search) and type `#NAME` where NAME is new tag name.
@@ -122,9 +124,20 @@ For example, say we created a new tag `Person` and added `lastName` and `birthda
 
 A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right.
 
+### Create Tags
+
+Ways to create tags:
+* Open search and type `#NAME` where `NAME` is the new tag name.
+* In any block including a page name, type `#NAME` and press `Enter`. The tag floats to the right of the block.
+* In a block type `#NAME` and press `Cmd-Enter`. An inline tag is created.
+* Paste text in a block that includes `#NAME`. An inline tag is created for tag `NAME`.
+* Configure a `Node` property type to have a new tag config.
+* Configure a new tag to have a `Parent`, the new `Parent` value becomes a tag.
+* In a block type `#NAME` and press `Esc`. An inline tag is created. Not recommended as it doesn't work for all use cases.
+
 ### Parent Tags
 
-New tags can have a parent tag, defaulting to `Root Tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer or the previous namespace feature. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Children` section.
+New tags can have a parent tag, defaulting to `Root Tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Children` section.
 
 A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
 
@@ -147,18 +160,22 @@ A tagged node can have multiple new tags. Once a node is tagged it displays all
 
 A tagged node can have an icon. When it does have an icon, it will appear to the left of its name or in a reference.
 
-## Tasks
+## Tag Based Features
+
+The features in this section use [new tags](#new-tags). Each of these features have built-in [tables](#tables) (dashboards) to view and manage them on their tag page!
+
+### Tasks
 
 Tasks are improved from the previous version as they more powerful and customizable. All tasks are blocks with the built-in new tag `#Task`. When a task is created it has the properties status, priority and deadline.
 
-### Create a Task
+#### Create a Task
 
 A new task can be created in a number of ways:
 * Set the status of a block by typing the status choice e.g. `/todo` or cyling status with `Cmd-Enter`.
 * Type text in a block and end it with `#Task`.
 * When on the `Task` page, create a new row in the Task table.
 
-### Task Shortcuts
+#### Task Shortcuts
 
 Any block can have a task property value set with a command or a keybinding. The commands start with `Add task` and the keybindings are:
 
@@ -170,7 +187,7 @@ The statuses `Todo`, `Doing` and `Done` can be cycled through with `Cmd-Enter`.
 
 The `/STATUS` commands can set a status where `STATUS` is one of the status choices e.g. `/todo`. Similarly, priority choices can be set with `/PRIORITY` commands. `/Deadline` sets the deadline property.
 
-### Task Status
+#### Task Status
 
 The status property is probably the most often used task property and thus it has been simplified and made customizable. The `TODO/DOING` and `NOW/LATER` workflows have been merged into `TODO/DOING` and some of the other TODO keywords have been converted to built-in status values. The default built-in values for status are:
 
@@ -181,7 +198,7 @@ The status property is probably the most often used task property and thus it ha
 * `Done`
 * `Canceled`
 
-### Customizing Tasks
+#### Customizing Tasks
 
 Since tasks are powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
 
@@ -190,18 +207,41 @@ Since tasks are powered by properties and [new tags](#new-tags), they can be cus
 3. `#Task` can be configured to have additional properties from the new tag's [page](#configure-a-new-tag).
 4. Custom types of tasks can be created by creating a new tag that has `#Task` as the [parent tag](#parent-tags). For example, create a `#ProjectTask` from [Search](https://docs.logseq.com/#/page/search) and configure it to have `Task` as the parent. Then add a property on the `project` property on `#ProjectTask`. You now have a task for projects!
 
-## Journals
+### Journals
 
 A journal page has the [new tag](#new-tags) `#Journal`. Like tasks, journals can be customized by adding properties to its tag. For example, navigate to the `#Journal` page and add a property. This property now shows up on all journals!
 
 Journals are automatically created for the current day in the Journals view. There are a couple of ways to create a journal:
+* Natural language that autocompletes within `[[]]` can reference specific days e.g. `[[Today]]`. A specific day this week, last week or next week can be described e.g. `[[This Friday]]`, `[[Last Friday]]` or `[[Next Friday]]`.
 * Use the `/Date picker` command to insert a specific date. The date picker is keyboard friendly as arrow keys change calendar days and `Tab` focuses the input. The input takes natural language e.g. `next week` and converts it to a date. See [the library we use](https://github.com/wanasit/chrono#readme) for other natural language examples.
 * Properties with the :date property type e.g. `Deadline` create journals for their property values.
 * When on a journal day, create a journal for the next day or previous day by using the keybindings `g n` or `g p` respectively.
 
-## Queries
+### Queries
+
+A [query](https://docs.logseq.com/#/page/queries) and [advanced query](https://docs.logseq.com/#/page/advanced%20queries) have the [new tag](#new-tags) `#Query`. Queries are created in one of the following ways:
+* Type the `/Query` command to create a query through the [query builder](https://docs.logseq.com/#/page/query%20builder).
+* Type a simple query in a block and then type the `/Query` command to run the query.
+* Type the `/Advanced Query` command to create an advanced query.
+
+Like other new tags, go to the `#Query` page to see a table to manage queries. Query results are displayed with the new [tables](#tables).
+
+### Cards
+
+A [(flash)card](https://docs.logseq.com/#/page/flashcards) has the new tag `#Card`. This feature has been re-implemented to use a [new algorithm](https://github.com/open-spaced-repetition/free-spaced-repetition-scheduler).
+
+#### Create Cards
+* Tag blocks with `#Card` to create new cards.
+* To convert multiple blocks into cards at once, select them, right-click and choose `Make a flashcard`.
+
+#### View Cards
+All cards are accessible on the `#Card` page within the tagged-nodes table.
+The `Due` column indicates when the next review is scheduled.
 
-A [query](https://docs.logseq.com/#/page/queries) has the [new tag](#new-tags) `#Query`. Queries are created by using the `/Query` command. Like other new tags, go to the `#Query` page to see a table to manage queries. Query results are displayed with the new [tables](#tables).
+#### Review Cards
+
+Select `Flashcards` from the left sidebar to view all cards due for review.
+You can rate them using 4 levels to arrange their next review date.
 
 ## Tables
 
@@ -211,6 +251,7 @@ A table displays a group of nodes as rows and a node's properties as columns. A
 * Hide columns by clicking on the three dots menu and selecting `Columns visibility`.
 * Drag columns to sort their order.
 * Switch between `Table View` and `List View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages.
+* Resize columns by dragging the resize handle at a column header's border.
 * Click on the magnifying glass icon to live search a table. This is the only feature that doesn't persist when switching away from a table.
 
 A powerful new feature of tables is the ability to create a table view. This is currently enabled for tag pages. To use it, click the `+` icon in the upper left to create a new tab in the table. Click on the tab's header to rename or delete this new view. Within this view, all of the above persisting features will save!
@@ -240,19 +281,4 @@ All tasks are imported as new [tasks](#tasks). Some task statuses have been rema
 
 ## Automated Backup
 
-An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
-
-## Cards
-SRS Cards feature has been re-implemented in DB-version based on [cljc-fsrs](https://github.com/open-spaced-repetition/cljc-fsrs).
-
-### Create new cards
-* Tag blocks with `#Card` to create new cards.
-* To convert multiple blocks into cards at once, select them, right-click and choose `Make a flashcard`.
-
-### View cards
-All cards are accessible on the `#Card` page within the tagged-nodes table.  
-The `Due` column indicates when the next review is scheduled.
-  
-### Review cards
-Select `Flashcards` from the left sidebar to view all cards due for review.  
-you can rating them using 4 levels to arrange their next review date.
+An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
\ No newline at end of file

From d00f1f4fa0fefbd3fc2cf6d448983fb595c83d8d Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 1 Oct 2024 11:20:06 -0400
Subject: [PATCH 132/196] Add advanced query option deprecations

---
 db-version-changes.md | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index e731c25..1040969 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -67,13 +67,16 @@ Miscelleanous changes:
 
 #### Queries
 
-* Simple queries can now have titles.
-* Advanced queries are now edited in a code block which means queries are syntax highlighted.
+* [Simple queries](https://docs.logseq.com/#/page/queries)
+  * Simple queries can now have titles.
+  * Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
+  * The `sort-by` query filter no longer exists. Sorting is done via the table component.
+  * When using the query builder, the resulting query's text is not meant to be easily read as internal ids are used for some concepts e.g. properties.
+* [Advanced queries](https://docs.logseq.com/#/page/advanced%20queries)
+  * Advanced queries are now edited in a code block which means queries are syntax highlighted.
+  * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
+  * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.
 * Since block timestamps are available, they display in table view where possible.
-* Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
-* Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
-* The `sort-by` query filter no longer exists. Sorting is done via the table component.
-* When using the query builder, the resulting query's text is not meant to be easily read as internal ids are used for some concepts e.g. properties.
 
 #### Namespaces
 * Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`.

From 01f36239358a2aed4436e46dfeebb7a865c14c86 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 2 Oct 2024 16:26:49 -0400
Subject: [PATCH 133/196] tweaks to yesterday's update

---
 db-version-changes.md | 2 +-
 db-version.md         | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 1040969..1275ace 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -79,7 +79,7 @@ Miscelleanous changes:
 * Since block timestamps are available, they display in table view where possible.
 
 #### Namespaces
-* Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`.
+* Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`. Unlike before, the reference will turn into `[[baz]]` after it is created.
 * Namespaced pages no longer have their namespace embedded in their page name. The big advantage of this is that renaming any part of the namespace does not affect all the pages under a namespace.
 * Pages can manage their namespace explicitly by using the `Parent` property. Previously managing a namespace could only be done by renaming a namespace. Using a property allows for easier management of namespace relationships.
 * The `Hierarchy` section is called `Children` for DB graphs. It now displays as a collapsible tree as this allows for viewing large namespaces more easily.
diff --git a/db-version.md b/db-version.md
index d2fa014..5b13c04 100644
--- a/db-version.md
+++ b/db-version.md
@@ -86,7 +86,7 @@ Property fields in the dropdown menu:
 * `Name`: Name to visually identify the property
 * `Property type`: This determines what type a property's property values will have. Once a property is used this field cannot change. If you're unsure of what type to choose, use `Text`. See [property-types](#property-types) for more.
 * `Available choices`: This limits a property to only have one of the defined choices. See [property choices](#property-choices) for more.
-* `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox.
+* `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox and datetime.
 * `UI position`: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
 * `Hide by default`: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
 

From bad24f90d3b278282b8cca5b2e2fb63ccd9cd6d3 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 15 Oct 2024 23:54:12 -0400
Subject: [PATCH 134/196] add docs for new tags, gallery view, export, etc.

---
 db-version-changes.md | 12 ++++++++++--
 db-version.md         | 45 ++++++++++++++++++++++++++++++++++---------
 2 files changed, 46 insertions(+), 11 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 1275ace..8380c92 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -32,11 +32,13 @@ High level changes:
   * `>Query` is now `/Advanced Query`
   * `>Src` is now `/Code block`
   * `>Quote` is `/Quote`
+* Code blocks, quote blocks and math blocks [have tags](./db-version.md#more-new-tags). Since properties are not are a part of the block content, properties can more naturally be added to these blocks.
+* Pdf annotations [have a tag](./db-version.md#more-new-tags). This allows annotations to be viewed across pdfs and to have custom views of annotations while using the pdf viewer.
 
 WIP changes:
 * Query filters are likely to be changed.
 * Whiteboards are disabled for now and will be enabled later.
-* Exports only partially work.
+* Exports to more formats including markdown.
 * Sync and RTC will be enabled later.
 
 Miscelleanous changes:
@@ -65,9 +67,15 @@ Miscelleanous changes:
 * Logbook timestamps have been deprecated.
 * Read more about the [new tasks](./db-version.md#tasks).
 
+#### Assets
+* Assets can have custom user properties.
+* Assets are blocks and thus can show their linked references when zoomed in on the asset block.
+
 #### Queries
 
+* Read more about the [new queries](./db-version.md#queries).
 * [Simple queries](https://docs.logseq.com/#/page/queries)
+  * Simple queries are created via the `/Query` command and not the `{{query}}` macro This means that user macros cannot be used to create specialized queries.
   * Simple queries can now have titles.
   * Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
   * The `sort-by` query filter no longer exists. Sorting is done via the table component.
@@ -96,7 +104,7 @@ Miscelleanous changes:
 * Graphs have a convention of `~/logseq/graphs/GRAPH-NAME` where `GRAPH-NAME` is the graph name. 
 * Inside a graph directory:
     * `db.sqlite` - Stores all your graph's data including user configs.
-    * `assets/` - Stores assets like before
+    * `assets/` - Stores assets like before.
 * `logseq/` inside a directory no longer exists.
 * It's still a TODO to sync markdown files to these graph directories.
 
diff --git a/db-version.md b/db-version.md
index 5b13c04..3309f22 100644
--- a/db-version.md
+++ b/db-version.md
@@ -14,9 +14,12 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
   * [Journals](#journals)
   * [Queries](#queries)
   * [Cards](#cards)
+  * [Assets](#assets)
+  * [More New Tags](#more-new-tags)
 * [Tables](#tables)
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
+* [Export and Import](#export-and-import)
 
 ## Nodes
 
@@ -235,7 +238,7 @@ A [(flash)card](https://docs.logseq.com/#/page/flashcards) has the new tag `#Car
 * To convert multiple blocks into cards at once, select them, right-click and choose `Make a flashcard`.
 
 #### View Cards
-All cards are accessible on the `#Card` page within the tagged-nodes table.
+All cards are accessible on the `#Card` page within the `Tagged Nodes` table.
 The `Due` column indicates when the next review is scheduled.
 
 #### Review Cards
@@ -243,6 +246,20 @@ The `Due` column indicates when the next review is scheduled.
 Select `Flashcards` from the left sidebar to view all cards due for review.
 You can rate them using 4 levels to arrange their next review date.
 
+### Assets
+
+An asset has the new tag `#Asset`. Assets are created by dragging and dropping a file onto a block. They can also be batch uploaded by going to the `#Asset` page and clicking the `+` icon from the `Tagged Nodes` table. Asset files are stored under a graph's `assets/` directory. Manage assets from the `#Asset` page's `Tagged Nodes` section. The `Gallery View` is a helpful way to view assets.
+
+### More New Tags
+
+Here are more new tags that are built-in, most of which are created with `/` commands:
+* `#Code` - Create a code block with the `/Code block` command or by typing the backtick ` three times.
+* `#Quote` - Create a quote block with the `/Quote` command or by typing `>`.
+* `#Math` - Create a math block written as LaTeX with the `/Math block` command.
+* `#Pdf Annotation` - A node with this tag is created each a [pdf is annotated or highlighted](https://docs.logseq.com/#/page/pdf%20highlights).
+
+Like other tags, go to their tag pages to view and manage all of them in one place. Also like other tags, extend any tag by adding more properties to it. For example, add an author property to `#Quote` to optionally add authors to quotes.
+
 ## Tables
 
 A table displays a group of nodes as rows and a node's properties as columns. A table behaves like a spreadsheet as table cells are editable by default. A node has the following special columns which are available by default: `Name`, `Created At` and `Updated At`. Tables have the following features:
@@ -250,7 +267,7 @@ A table displays a group of nodes as rows and a node's properties as columns. A
 * Filter rows by multiple columns by clicking on the filter icon. For columns with a specific property type e.g. :number and :date, there are specific filters for that type.
 * Hide columns by clicking on the three dots menu and selecting `Columns visibility`.
 * Drag columns to sort their order.
-* Switch between `Table View` and `List View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages.
+* Switch between `Table View`, `List View` or `Gallery View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages. The `Gallery View` is useful for viewing blocks as square tiles, especially for assets.
 * Resize columns by dragging the resize handle at a column header's border.
 * Click on the magnifying glass icon to live search a table. This is the only feature that doesn't persist when switching away from a table.
 
@@ -260,13 +277,17 @@ Tables are currently found on new tag pages, property pages, query results and t
 
 ## DB Graph Importer
 
-The DB Graph Importer converts a file graph to a DB graph. Currently it imports markdown files and assets like images. Import of org mode files will be added later. For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP. For pages the importer imports the previous tags to a `Page Tags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `Page Tags`. The importer also provides two options to convert property related pages to new tags.
+The DB Graph Importer converts a file graph to a DB graph. Some of the main things it does:
+* It imports markdown files and assets like images. Import of org mode files will be added later.
+* All tasks are imported as new [tasks](#tasks). Some task statuses have been remapped to avoid duplicates e.g. `TODO` and `LATER`. The following statuses have been remapped:
+  * `LATER` -> `Todo`
+  * `IN-PROGRESS` and `NOW` -> `Doing`
+  * `WAIT` and `WAITING` -> `Backlog`
+* Tags are handled as follows:
+  * For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP.
+  * For pages the importer imports the previous tags to a `Page Tags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `Page Tags`. The importer also provides two options to convert property related pages to new tags.
+* Property types are automatically detected for Number, Date, Checkbox, Url, Node and Text. If a property value has two conflicting but compatible types like Number and Text, it will choose the more lenient Text type.
 
-All tasks are imported as new [tasks](#tasks). Some task statuses have been remapped to avoid duplicates e.g. `TODO` and `LATER`. The following statuses have been remapped:
-
-* `LATER` -> `Todo`
-* `IN-PROGRESS` and `NOW` -> `Doing`
-* `WAIT` and `WAITING` -> `Backlog`
 
 ### Convert File Graph to DB graph
 
@@ -281,4 +302,10 @@ All tasks are imported as new [tasks](#tasks). Some task statuses have been rema
 
 ## Automated Backup
 
-An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
\ No newline at end of file
+An automated backup of graphs is available by clicking on the upper right three dots menu and selecting `Export Graph`. Within this modal, you can specify a folder (directory) to save backups. A backup folder can be reused across graphs as each graph gets its own folder within a backup folder. After choosing this folder, hourly backups begin. The last 12 backups are saved. This backup feature is currently only for the browser.
+
+## Export and Import
+
+Currently the graph can only be exported as a [SQLite](https://sqlite.org/) DB file. To do so, click on the three dots menu in the upper right corner, select `Export Graph` and click the `Export SQLite DB` item. This creates a .sqlite file for use with Logseq. From that same menu, you can also select `Export both SQLite DB and assets` to create a .zip file which contains the .sqlite file and any asset files packaged as a .zip file.
+
+To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.
\ No newline at end of file

From e45a600ff84daaf7e95fe29d48fae9e6db8c69b2 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 15 Oct 2024 23:55:16 -0400
Subject: [PATCH 135/196] bump date

---
 db-version.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/db-version.md b/db-version.md
index 3309f22..8c94fc3 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Oct 1st. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Oct 15th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using this for testing purposes.
 
@@ -308,4 +308,4 @@ An automated backup of graphs is available by clicking on the upper right three
 
 Currently the graph can only be exported as a [SQLite](https://sqlite.org/) DB file. To do so, click on the three dots menu in the upper right corner, select `Export Graph` and click the `Export SQLite DB` item. This creates a .sqlite file for use with Logseq. From that same menu, you can also select `Export both SQLite DB and assets` to create a .zip file which contains the .sqlite file and any asset files packaged as a .zip file.
 
-To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.
\ No newline at end of file
+To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.

From 7437a65d7b52982da08df296e19d4203f98a62d7 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 23 Oct 2024 09:27:12 -0400
Subject: [PATCH 136/196] wording

---
 db-version.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 8c94fc3..2a6c333 100644
--- a/db-version.md
+++ b/db-version.md
@@ -2,7 +2,7 @@
 
 This page describes DB (database) graph functionality as of Oct 15th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
-NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using this for testing purposes.
+NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
 ## Overview
 

From 3a40982a9beda278d7170ffba953f74dc1454478 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 23 Oct 2024 14:44:29 -0400
Subject: [PATCH 137/196] link to test site

---
 db-version.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 2a6c333..636c898 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Oct 15th. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Oct 15th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 

From da6af2db99e6a6e9de483a1c887640df28a37e22 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 6 Nov 2024 15:59:34 -0500
Subject: [PATCH 138/196] Update docs with recent import options and features

---
 db-version-changes.md |  1 +
 db-version.md         | 13 ++++++++-----
 2 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 8380c92..7751eec 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -70,6 +70,7 @@ Miscelleanous changes:
 #### Assets
 * Assets can have custom user properties.
 * Assets are blocks and thus can show their linked references when zoomed in on the asset block.
+* Assets are resized by hovering over them and then dragging the left-right arrows that are visible over the scrollbars.
 
 #### Queries
 
diff --git a/db-version.md b/db-version.md
index 636c898..e05b615 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Oct 15th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Nov 6th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -92,6 +92,7 @@ Property fields in the dropdown menu:
 * `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox and datetime.
 * `UI position`: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
 * `Hide by default`: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
+* `Hide empty value`: When selected, a property won't be visible on a block if it is has an empty property value.
 
 ### Built-in Properties
 
@@ -294,11 +295,13 @@ The DB Graph Importer converts a file graph to a DB graph. Some of the main thin
 * Click on the three dots menu in the upper right corner and select `Import`.
 * Click on the `File to DB graph` button.
 * This brings up a dialog. For larger graphs it takes longer for the dialog to display.
-* The dialog requires you to input a name for your graph. On desktop this new graph will be located under `~/logseq/graphs/GRAPH-NAME` so it is ok to give it the same name it currently has.
+* The dialog requires you to input a name for your graph.
 * The dialog has the following optional inputs:
-    1. `Tags to import ...` - This input converts any of your old tags to the [new tags](#new-tags). This is helpful if you've been using a particular tag like a new tag. You can also convert pages later by right clicking on a page's name.
-    2. `Properties whose values are imported as new tags` - This input converts property values for the specified property to the new tags. For example, in the official docs graph the [type property](https://docs.logseq.com/#/page/type) is used this way. This means that all `type` property values like [Feature](https://docs.logseq.com/#/page/feature) on [this page](https://docs.logseq.com/#/page/code%20block) would get converted to the new tag.
-    3. `Properties whose values are imported as parents of ...` - This input converts property values for the specified property to be [a parent of a new tag](#parent-tags). For example, in the official docs graph the [parent property](https://docs.logseq.com/#/page/parent) is used this way. This means that all `parent` property values like [Thing](https://docs.logseq.com/#/page/thing) on [this page](https://docs.logseq.com/#/page/feature) would get converted to the new tag.
+    1. `Import all tags` - This checkbox convert all existing tags to be [new tags](#new-tags).
+    1. `Import specific tags` - This input is an alternative to `Import all tags` in which you only convert specific tags to be [new tags](#new-tags). This is helpful if you don't want most of your existing tags to behave like new tags. You can also convert pages later by right clicking on a page's name.
+    1. `Remove inline tags` - This checkbox removes inline tags from block content for any converted tags. This matches the DB graph behavior since all tags are now visible to the right of a block.
+    1. `Import additional tags from property values` - This input converts property values for the specified property/properties to the new tags. For example, in the official docs graph the [type property](https://docs.logseq.com/#/page/type) is used this way. This means that all `type` property values like [Feature](https://docs.logseq.com/#/page/feature) on [this page](https://docs.logseq.com/#/page/code%20block) would get converted to a new tag.
+    1. `Import tag parents from property values` - This input converts property values for the specified property to be [a parent of a new tag](#parent-tags). For example, in the official docs graph the [parent property](https://docs.logseq.com/#/page/parent) is used this way. This means that all `parent` property values like [Thing](https://docs.logseq.com/#/page/thing) on [this page](https://docs.logseq.com/#/page/feature) would get converted to a new tag.
 
 ## Automated Backup
 

From 5fe6218286355931eaea0810f99d45e58dfc9926 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 19 Nov 2024 10:49:23 -0500
Subject: [PATCH 139/196] mention keyword deprecation for tasks

---
 db-version-changes.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 7751eec..6a26898 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -65,6 +65,7 @@ Miscelleanous changes:
 * [Scheduled](https://docs.logseq.com/#/page/tasks/block/deadline%20and%20scheduled) has been deprecated.
 * Recurring tasks aren't ported and are a TODO.
 * Logbook timestamps have been deprecated.
+* Tasks are no longer created by typing keywords like `TODO` but instead with commands like '/todo'.
 * Read more about the [new tasks](./db-version.md#tasks).
 
 #### Assets
@@ -102,7 +103,7 @@ Miscelleanous changes:
 
 #### DB Graph Directories
 
-* Graphs have a convention of `~/logseq/graphs/GRAPH-NAME` where `GRAPH-NAME` is the graph name. 
+* Graphs have a convention of `~/logseq/graphs/GRAPH-NAME` where `GRAPH-NAME` is the graph name.
 * Inside a graph directory:
     * `db.sqlite` - Stores all your graph's data including user configs.
     * `assets/` - Stores assets like before.
@@ -112,4 +113,4 @@ Miscelleanous changes:
 ## File Graph Changes
 
 * There is no longer a [conversion feature for filename formats](https://docs.logseq.com/#/page/filename%20format)
-* The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
\ No newline at end of file
+* The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`

From f60647e1cd4b596b02b9e084d383097ebe4cbe70 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 27 Nov 2024 11:27:22 -0500
Subject: [PATCH 140/196] docs for property default values, query filters,
 importing updates

and new Scripting section
---
 db-version-changes.md | 15 ++++++++++-----
 db-version.md         | 32 +++++++++++++++++++++++++++-----
 2 files changed, 37 insertions(+), 10 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 6a26898..08d973b 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -36,12 +36,12 @@ High level changes:
 * Pdf annotations [have a tag](./db-version.md#more-new-tags). This allows annotations to be viewed across pdfs and to have custom views of annotations while using the pdf viewer.
 
 WIP changes:
-* Query filters are likely to be changed.
 * Whiteboards are disabled for now and will be enabled later.
 * Exports to more formats including markdown.
 * Sync and RTC will be enabled later.
 
 Miscelleanous changes:
+* Scripts using [nbb-logseq](https://github.com/logseq/nbb-logseq) can read and write graphs. Previously with file graphs, scripts could only read graphs.
 * Embedded pages and blocks look almost the same as other nodes. The main indicator of an embed will be an icon to the left of the block.
 * Default date picker now has an input for typing a date in natural language.
 * There is no re-index like in file graphs.
@@ -77,11 +77,16 @@ Miscelleanous changes:
 
 * Read more about the [new queries](./db-version.md#queries).
 * [Simple queries](https://docs.logseq.com/#/page/queries)
-  * Simple queries are created via the `/Query` command and not the `{{query}}` macro This means that user macros cannot be used to create specialized queries.
-  * Simple queries can now have titles.
-  * Some old simple queries for tasks will no longer work and must be manually converted e.g. `(priority A)` -> `(priority high)`.
-  * The `sort-by` query filter no longer exists. Sorting is done via the table component.
+  * Simple queries are created via the `/Query` command and not the `{{query}}` macro. This means that user macros cannot be used to create specialized queries.
+  * Simple queries can have titles.
   * When using the query builder, the resulting query's text is not meant to be easily read as internal ids are used for some concepts e.g. properties.
+  * The query builder's queries run against all [nodes](./db-version.md#nodes) instead of forcing the user to choose between blocks or pages.
+  * Query filter changes:
+    * These previous query filters will no longer work and should be manually converted:
+      * `(page-tags)` -> `(tags)`
+      * `(page-property)` -> `(property)`
+      * `(priority A)` -> `(priority high)`
+    * The `all-page-tags` and `sort-by` query filters no longer exists. Sorting is done via the table component.
 * [Advanced queries](https://docs.logseq.com/#/page/advanced%20queries)
   * Advanced queries are now edited in a code block which means queries are syntax highlighted.
   * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
diff --git a/db-version.md b/db-version.md
index e05b615..58038fd 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Nov 6th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Nov 27th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -20,6 +20,7 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
 * [Export and Import](#export-and-import)
+* [Scripting](#scripting)
 
 ## Nodes
 
@@ -88,6 +89,7 @@ Property fields in the dropdown menu:
 
 * `Name`: Name to visually identify the property
 * `Property type`: This determines what type a property's property values will have. Once a property is used this field cannot change. If you're unsure of what type to choose, use `Text`. See [property-types](#property-types) for more.
+* `Default value`: This sets the default value for a property. See [property-default-values](#property-default-values) for more.
 * `Available choices`: This limits a property to only have one of the defined choices. See [property choices](#property-choices) for more.
 * `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox and datetime.
 * `UI position`: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
@@ -116,6 +118,14 @@ Property choices allow a property to only have one of the defined choices. Only
 
 If a property has already been used, it is possible to convert it to use choices. After clicking `Add choice`, a panel displays to convert all existing property values to choices. If a property is using choices, it is possible to stop using choices by deleting them from the property. Caution: deleting a choice from a property also currently deletes the choice from all blocks it is used.
 
+### Property Default Values
+
+Properties can have default values, currently just for the types Text, Number and Checkbox. A property's default value takes effect for these two use cases:
+* When a property is added to a node, it defaults to the default value.
+* When a property is a tag property for a tag and that tag is added to a node, the node defaults to having the default value for that property.
+
+When using simple queries, properties for the above two use cases will have that default value. When using property choices, one of them can be set as a default value by checking the default choice box in the list of property choices.
+
 ## New Tags
 
 NOTE: New tags are currently labeled as tags in the app and should be backwards compatible with the previous tags. These `new tags` are also known as classes, types or supertags. Feedback is welcome on names for `new tags`.
@@ -223,7 +233,7 @@ Journals are automatically created for the current day in the Journals view. The
 
 ### Queries
 
-A [query](https://docs.logseq.com/#/page/queries) and [advanced query](https://docs.logseq.com/#/page/advanced%20queries) have the [new tag](#new-tags) `#Query`. Queries are created in one of the following ways:
+A [(simple) query](https://docs.logseq.com/#/page/queries) and [advanced query](https://docs.logseq.com/#/page/advanced%20queries) have the [new tag](#new-tags) `#Query`. Queries are created in one of the following ways:
 * Type the `/Query` command to create a query through the [query builder](https://docs.logseq.com/#/page/query%20builder).
 * Type a simple query in a block and then type the `/Query` command to run the query.
 * Type the `/Advanced Query` command to create an advanced query.
@@ -284,9 +294,13 @@ The DB Graph Importer converts a file graph to a DB graph. Some of the main thin
   * `LATER` -> `Todo`
   * `IN-PROGRESS` and `NOW` -> `Doing`
   * `WAIT` and `WAITING` -> `Backlog`
-* Tags are handled as follows:
-  * For blocks the importer converts all uses of [new tags](#new-tags) to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference) because ~~tags are now used for new tag features while page references handle inline referencing functionality~~ this behavior is still WIP.
-  * For pages the importer imports the previous tags to a `Page Tags` property. If you'd like some previous tags to behave like new tags, you can specify them in the first optional input. Using this option also results in those converted tags not being imported as `Page Tags`. The importer also provides two options to convert property related pages to new tags.
+* Tags are imported as follows:
+  * By default, all tags are imported as [new tags](#new-tags) using the `Import all tags` input. This allows you to use all your tags as you have previously, along with the new capabilities they have.
+  * Alternatively you can import only specific tags to [new tags](#new-tags) using the `Import specific tags` input. Tags that aren't specified in this input are then imported as follows:
+    * All such tags become pages.
+    * Tags in a block are converted to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference).
+    * Tags associated with a page are associated to that page with a `Page Tags` property.
+  * Tags are removed from their blocks when the `Remove inline tags` checkbox is checked. This matches the behavior of the DB version.
 * Property types are automatically detected for Number, Date, Checkbox, Url, Node and Text. If a property value has two conflicting but compatible types like Number and Text, it will choose the more lenient Text type.
 
 
@@ -312,3 +326,11 @@ An automated backup of graphs is available by clicking on the upper right three
 Currently the graph can only be exported as a [SQLite](https://sqlite.org/) DB file. To do so, click on the three dots menu in the upper right corner, select `Export Graph` and click the `Export SQLite DB` item. This creates a .sqlite file for use with Logseq. From that same menu, you can also select `Export both SQLite DB and assets` to create a .zip file which contains the .sqlite file and any asset files packaged as a .zip file.
 
 To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.
+
+## Scripting
+
+DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db. Scripts can both read and _write any_ data in a DB graph. To write your own script, you'll need a package.json and nbb.edn. Use [this example package.json](https://github.com/logseq/publish-spa/blob/feat/db/package.json) and [this example nbb.edn](https://github.com/logseq/publish-spa/blob/feat/db/nbb.edn). Some example scripts:
+
+* https://github.com/logseq/logseq/tree/feat/db/deps/db/script - Scripts to query, validate and create any graph
+* https://github.com/logseq/logseq/blob/feat/db/deps/outliner/script/transact.cljs - Script to transact (modify) nodes queried from the commandline
+* https://github.com/logseq/logseq/tree/feat/db/scripts/src/logseq/tasks/db_graph - More complex scripts to generate graphs with all property types or with schema.org's ontology. See [this readme](https://github.com/logseq/logseq/tree/feat/db/scripts#nbb-scripts) for using these.
\ No newline at end of file

From bd40d0ddf45cfb4888f6f37daadd585a07a411d5 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 5 Dec 2024 15:09:23 -0500
Subject: [PATCH 141/196] Organize feature section

Followup to #127
---
 pages/Document syntax.md |  1 -
 pages/contents.md        | 23 ++++++++++-------------
 2 files changed, 10 insertions(+), 14 deletions(-)
 delete mode 100644 pages/Document syntax.md

diff --git a/pages/Document syntax.md b/pages/Document syntax.md
deleted file mode 100644
index 77a97f9..0000000
--- a/pages/Document syntax.md	
+++ /dev/null
@@ -1 +0,0 @@
-- Logseq currently supports [[Markdown]] and [[Org Mode]] syntaxes.
\ No newline at end of file
diff --git a/pages/contents.md b/pages/contents.md
index b12f69f..598be20 100644
--- a/pages/contents.md
+++ b/pages/contents.md
@@ -1,4 +1,4 @@
-## 🌟[[New to Logseq?]]
+- ## 🌟[[New to Logseq?]]
 	- ### Basics
 		- [[Start here]]
 		- [[How to create a new graph]]
@@ -25,45 +25,42 @@
 	- [[Glossary]]
 	- [[Testimonials]]
 	- [Awesome Logseq](https://github.com/logseq/awesome-logseq) (community extensions and resources)
-- ## [[Features]]
+- ## [Features]([[Feature]])
 	- ### Basic Features
-		- [[Document syntax]]
-			- [[Markdown]]
-			- [[Org Mode]]
 		- [Backlink]([[term/backlink]])
-		- [[Knowledge Graph]]
 		- [[Page and block references]]
 		- [[Page embed]] and [[Block embed]]
-		- [Page alias]([[term/alias]])
 		- [[Properties]]
+		- [Page alias]([[term/alias]])
 	- ### Productivity
 		- [[Tasks]]
-		- [[Commands]]
-		- [[Advanced commands]]
+		- [[Commands]] and [[Advanced commands]]
+		- [[Queries]] and [[Query Builder]]
 		- [[Templates]]
 	- ### Media
-		- [[Draw]]
-		- [[Whiteboard]]
 		- [[PDF highlights]]
+		- [[Whiteboard]]
 		- [[Embed Media - Audio, Photos, Videos]]
+		- [[Draw]]
 		- [[Zotero]] integration
 	- ### Tools
 		- [[Flashcards]]
 		- [[Slide]]
 		- [[Calculator]]
-		- [[Queries]] and [[Query Builder]]
 		- [[Tables]]
 		- [[Publishing]]
+		- [[Knowledge Graph]]
 	- ### Customization
+		- [[User configuration]]
 		- [[Custom theme]]
 		- [[Plugins]]
 		- 👤 [[Settings]]
+		- Document formats: [[Markdown]] and [[Org Mode]]
 - ## [[Advanced Logseq]]
 	- ✨ [[Tips and Tricks]]
 	- [[Keyboard shortcuts]]
 	- [[Advanced Queries]]
 	- [[Hiccup]]
-	- [[Filename format]]
 	- [[Migrate to Logseq Beta]]
 - ## [[Contribute]]
 	- Make a [Feature Request](https://discuss.logseq.com/)

From c0a087f01121f299d37157d94c946cd13dd765f4 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 6 Dec 2024 10:37:46 -0500
Subject: [PATCH 142/196] Add TODO importer items

---
 db-version.md | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/db-version.md b/db-version.md
index 58038fd..43272bd 100644
--- a/db-version.md
+++ b/db-version.md
@@ -267,7 +267,7 @@ Here are more new tags that are built-in, most of which are created with `/` com
 * `#Code` - Create a code block with the `/Code block` command or by typing the backtick ` three times.
 * `#Quote` - Create a quote block with the `/Quote` command or by typing `>`.
 * `#Math` - Create a math block written as LaTeX with the `/Math block` command.
-* `#Pdf Annotation` - A node with this tag is created each a [pdf is annotated or highlighted](https://docs.logseq.com/#/page/pdf%20highlights).
+* `#PDF Annotation` - A node with this tag is created each a [pdf is annotated or highlighted](https://docs.logseq.com/#/page/pdf%20highlights).
 
 Like other tags, go to their tag pages to view and manage all of them in one place. Also like other tags, extend any tag by adding more properties to it. For example, add an author property to `#Quote` to optionally add authors to quotes.
 
@@ -288,8 +288,8 @@ Tables are currently found on new tag pages, property pages, query results and t
 
 ## DB Graph Importer
 
-The DB Graph Importer converts a file graph to a DB graph. Some of the main things it does:
-* It imports markdown files and assets like images. Import of org mode files will be added later.
+The DB Graph Importer converts a file graph to a DB graph. An overview of what it does:
+* It imports markdown files.
 * All tasks are imported as new [tasks](#tasks). Some task statuses have been remapped to avoid duplicates e.g. `TODO` and `LATER`. The following statuses have been remapped:
   * `LATER` -> `Todo`
   * `IN-PROGRESS` and `NOW` -> `Doing`
@@ -303,6 +303,12 @@ The DB Graph Importer converts a file graph to a DB graph. Some of the main thin
   * Tags are removed from their blocks when the `Remove inline tags` checkbox is checked. This matches the behavior of the DB version.
 * Property types are automatically detected for Number, Date, Checkbox, Url, Node and Text. If a property value has two conflicting but compatible types like Number and Text, it will choose the more lenient Text type.
 
+There are existing features that have a database equivalent that are still a TODO for the importer:
+  * Import assets as `#Asset` and pdf annotations as `#PDF Annotation`
+  * Import org mode files
+  * Import text files e.g. *.txt or *.edn
+  * Import advanced command blocks that begin with `#+BEGIN`
+  * Query macros and related query filters that have changed
 
 ### Convert File Graph to DB graph
 

From 8e5d4b0114d0e3e1915d2603507620dcd5dde257 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 13 Jan 2025 10:44:29 -0500
Subject: [PATCH 143/196] add header/permalink for importer todos

---
 db-version.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/db-version.md b/db-version.md
index 43272bd..298d239 100644
--- a/db-version.md
+++ b/db-version.md
@@ -303,6 +303,8 @@ The DB Graph Importer converts a file graph to a DB graph. An overview of what i
   * Tags are removed from their blocks when the `Remove inline tags` checkbox is checked. This matches the behavior of the DB version.
 * Property types are automatically detected for Number, Date, Checkbox, Url, Node and Text. If a property value has two conflicting but compatible types like Number and Text, it will choose the more lenient Text type.
 
+### Importer Todos
+
 There are existing features that have a database equivalent that are still a TODO for the importer:
   * Import assets as `#Asset` and pdf annotations as `#PDF Annotation`
   * Import org mode files

From f5004d6935901443121042695dc8ee9fa7eb19e3 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 13 Jan 2025 16:17:16 -0500
Subject: [PATCH 144/196] add known importer todo

---
 db-version.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version.md b/db-version.md
index 298d239..0327bbd 100644
--- a/db-version.md
+++ b/db-version.md
@@ -311,6 +311,7 @@ There are existing features that have a database equivalent that are still a TOD
   * Import text files e.g. *.txt or *.edn
   * Import advanced command blocks that begin with `#+BEGIN`
   * Query macros and related query filters that have changed
+  * Page and block embeds
 
 ### Convert File Graph to DB graph
 

From ec7b753076ace791779c58719164ff6e5731dbf7 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 22 Jan 2025 17:30:25 -0500
Subject: [PATCH 145/196] add docs for repeated nodes, changes in page types

status history, left sidebar, web plugins, new property fields, new export/import options,
conversion commands, UI changes
---
 db-version-changes.md |  6 +++-
 db-version.md         | 67 +++++++++++++++++++++++++++++++------------
 2 files changed, 53 insertions(+), 20 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 08d973b..c10e4b6 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -15,6 +15,8 @@ The following changes affect both file and the new db graphs:
 * A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
 * The application performance is better - loading faster and handling larger graphs. For DB graphs, our last performance test exercised 30k+ pages.
 * On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
+* Plugins can be used from the web.
+* The visibility of left sidebar items are configurable. To configure, hover over the `Navigations` header and click on the filter icon to open a dropdown for toggling visibility of sidebar items.
 
 ## DB Graph Changes
 
@@ -48,6 +50,7 @@ Miscelleanous changes:
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
 * `All Pages` view can toggle between table and list view.
 * Run the command `Customize appearance` to display a modal of appearance related settings.
+* For developers, there is a `Validate current graph` command.
 
 ### Changes by Feature
 
@@ -118,4 +121,5 @@ Miscelleanous changes:
 ## File Graph Changes
 
 * There is no longer a [conversion feature for filename formats](https://docs.logseq.com/#/page/filename%20format)
-* The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
+* The attribute `:block/content` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
+* The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
\ No newline at end of file
diff --git a/db-version.md b/db-version.md
index 0327bbd..b91f344 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Nov 27th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Jan 22nd. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -42,13 +42,12 @@ However, blocks and pages will have some differences as noted in the [pages](#pa
 
 Things that are specific to pages:
 * Pages have a dedicated view called `All pages`.
-* As seen on `All pages`, pages have different page types: `Page, Property, Tag, Journal and Whiteboard`. Think of these as directories on a file system.
+* When a property, new tag, journal or whiteboard are created, they are created as a page.
 * Pages are unique as follows:
-  * Page names of type 'page' are unique by tag e.g. there can be `Apple #Company` and `Apple #Fruit`.
+  * Page names are unique by tag e.g. there can be `Apple #Company` and `Apple #Fruit`.
   * Property names are unique and can have the same names as built-in property names.
-  * Page names of other types are unique for their page type e.g. there can be a `#Journal` and a Journal page.
   * The uniqueness of these pages should be visible everywhere in the app with icons for page types and the display of a page's tag(s).
-* Hovering over a page title shows common features like `Set Property` to add a property to the page.
+* Hovering over a page title shows common features like `Set page property` to add a property to the page.
 
 ### Blocks
 
@@ -83,7 +82,7 @@ NOTE: Most shortcuts have a corresponding search command. You can find the comma
 
 ### Configure a Property
 
-Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Press `Cmd` and click to navigate to a property page. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` link below its name.
+Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Press `Cmd` and click to navigate to a property page. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` button below its name.
 
 Property fields in the dropdown menu:
 
@@ -91,11 +90,15 @@ Property fields in the dropdown menu:
 * `Property type`: This determines what type a property's property values will have. Once a property is used this field cannot change. If you're unsure of what type to choose, use `Text`. See [property-types](#property-types) for more.
 * `Default value`: This sets the default value for a property. See [property-default-values](#property-default-values) for more.
 * `Available choices`: This limits a property to only have one of the defined choices. See [property choices](#property-choices) for more.
+* `Checkbox state mapping`: For properties that have [property choices](#property-choices), this defines mapping two choices to be checked or unchecked on a checkbox. To enable seeing the checkbox, configure the `Show as checkbox on ...` field.
 * `Multiple values`: When selected, a property can have multiple values associated with it. All property types can have multiple values except for checkbox and datetime.
 * `UI position`: This determines where the property values are displayed. By default the values are displayed as a row-like block under a block (`Block properties`). You can also choose to display property values at the beginning like task status, under a block like deadline date, or at the end of a block.
 * `Hide by default`: When selected, a property won't be visible on any of its blocks by default. But it will be visible if you zoom in on its blocks or display them in the sidebar.
 * `Hide empty value`: When selected, a property won't be visible on a block if it is has an empty property value.
 
+Some property fields are only configurable from certain contexts:
+* `Show as checkbox on ...`: This appears when clicked from a node or from a tag's `Tag properties`. When selected, a checkbox will show on that node or any node with that tag respectively. For this to take affect, the property must have configured `Checkbox state mapping`.
+
 ### Built-in Properties
 
 Logseq uses built-in properties to provide core features. A few of these properties are public and editable by the user. To navigate to a public built-in property use [Search](https://docs.logseq.com/#/page/search). For example, type `status` to go to the `Status` property used by [tasks](#tasks). When on a built-in property page, only some of its property fields are editable as allowing all fields to be edited could break functionality. The property fields that can be edited are its icon, `UI position`, `Hide by default` and `Available choices`.
@@ -106,15 +109,15 @@ A property type determines what type a property's property values can have. Ther
 
 * `Text`: This is the recommended default as it allows for any text and behaves like a block. This means that node references work here and children blocks can be created under the block.
 * `Number`: This is for numbers including negative numbers and floats e.g. 3.5. Unlike file graph properties, these are stored as actual numbers. This means that all features and queries that use this property type correctly sort as numbers by default.
-* `Date`: This is for dates and is editable with a date picker. When a date property value is used, it correctly links to the journal page.
-* `DateTime`: This is for date times and is editable with a datetime picker. See the `Due` property in [cards](#cards) for an example property that uses this.
+* `Date`: This is for dates and is editable with a date picker. When a date property value is used, it correctly links to the journal page. This property type can be used with [repeated nodes](#repeated-tasks-and-nodes).
+* `DateTime`: This is for date times and is editable with a datetime picker. See the `Due` property in [cards](#cards) for an example property that uses this. This property type can be used with [repeated nodes](#repeated-tasks-and-nodes).
 * `Checkbox`: This is used to set or unset a property value and displays as a checkbox. To engineers this type is known as a boolean.
 * `Url`: This limits text to only allow urls e.g. `https://logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
 * `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if `#Actor` is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
 
 ### Property Choices
 
-Property choices allow a property to only have one of the defined choices. Only the property types `Text`, `Url` and `Number` support this. From the [configuration dropdown](#configure-a-property), a property choice can be added, deleted and edited to have a required value, an optional description and an optional icon. Drag the choices up and down to order how they appear. For a good example of choices see the `Status` property.
+Property choices allow a property to only have one of the defined choices. Only the property types `Text`, `Url` and `Number` support this. From the [configuration dropdown](#configure-a-property), a property choice can be added, deleted and edited to have a required value, an optional description and an optional icon. Drag the choices up and down to order how they appear. For a good example of choices see the `Status` property. A property with property choices can be used with [repeated nodes](#repeated-tasks-and-nodes).
 
 If a property has already been used, it is possible to convert it to use choices. After clicking `Add choice`, a panel displays to convert all existing property values to choices. If a property is using choices, it is possible to stop using choices by deleting them from the property. Caution: deleting a choice from a property also currently deletes the choice from all blocks it is used.
 
@@ -136,7 +139,7 @@ To create your first new tag:
 
 For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all [tagged nodes](#tagged-node).
 
-A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right.
+A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right. To set these properties you must be on the tag's page, hover over the tag's name and click on `Set page property`.
 
 ### Create Tags
 
@@ -148,6 +151,9 @@ Ways to create tags:
 * Configure a `Node` property type to have a new tag config.
 * Configure a new tag to have a `Parent`, the new `Parent` value becomes a tag.
 * In a block type `#NAME` and press `Esc`. An inline tag is created. Not recommended as it doesn't work for all use cases.
+* Convert any page to a tag by clicking on the three dots menu in the upper right corner and clicking `Convert to Tag`.
+
+Any tag can be converted to a page by clicking on the three dots menu and clicking `Convert Tag to Page`.
 
 ### Parent Tags
 
@@ -157,9 +163,9 @@ A powerful feature of using a parent tag is that the new tag inherits the proper
 
 ### Configure a New Tag
 
-New tags are configurable from their page. Navigate to their page by using [Search](https://docs.logseq.com/#/page/search) or clicking on their `#` name links. On their page below their title, two important properties display by default and are editable:
+New tags are configurable from their page. Navigate to their page by using [Search](https://docs.logseq.com/#/page/search) or clicking on their `#` name links. On their page, hover over their name to see the rotating triangle icon to the left. Click on it to see the tag page's properties. Two important properties you'll see for configuring a tag:
 
-* `Parent`: Use this to allow the class to inherit the parent classes properties. By default the parent tag is the `Root Tag` which doesn't have any properties.
+* `Parent`: Use this to allow the new tag to inherit its parent's tag properties. By default the parent tag is the `Root Tag` which doesn't have any properties.
 * `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
   * To the right of each tag property there is an optional block for describing the property. This description also shows up on the property's page.
 
@@ -180,7 +186,7 @@ The features in this section use [new tags](#new-tags). Each of these features h
 
 ### Tasks
 
-Tasks are improved from the previous version as they more powerful and customizable. All tasks are blocks with the built-in new tag `#Task`. When a task is created it has the properties status, priority and deadline.
+Tasks are improved from the previous version as they more powerful and customizable. All tasks are blocks with the built-in new tag `#Task`. When a task is created it has the properties `Status`, `Priority`, `Deadline` and `Scheduled`.
 
 #### Create a Task
 
@@ -193,13 +199,13 @@ A new task can be created in a number of ways:
 
 Any block can have a task property value set with a command or a keybinding. The commands start with `Add task` and the keybindings are:
 
-* To set property `status`, press `p s`.
-* To set property `priority`, press `p p`.
-* To set property `deadline`, press `p d`.
+* To set property `Status`, press `p s`.
+* To set property `Priority`, press `p p`.
+* To set property `Deadline`, press `p d`.
 
 The statuses `Todo`, `Doing` and `Done` can be cycled through with `Cmd-Enter`.
 
-The `/STATUS` commands can set a status where `STATUS` is one of the status choices e.g. `/todo`. Similarly, priority choices can be set with `/PRIORITY` commands. `/Deadline` sets the deadline property.
+The `/STATUS` commands can set a status where `STATUS` is one of the status choices e.g. `/todo`. Similarly, priority choices can be set with `/PRIORITY` commands. `/Deadline` sets the `Deadline` property. `/Scheduled` sets the `Scheduled` property.
 
 #### Task Status
 
@@ -212,6 +218,18 @@ The status property is probably the most often used task property and thus it ha
 * `Done`
 * `Canceled`
 
+This property keeps a history of status changes for each block. Once this property changes from `Todo` to another status, its history is available by clicking on the task's spent time e.g. `9s` on the right side of a block.
+
+#### Repeated Tasks and Nodes
+
+Repeating works for tasks as well as for user defined properties. Read to the end to define your own repeated nodes.
+
+Repeated tasks are available on any task that has a `Deadline` (or `Scheduled`) property. When setting the values for these properties in a popup, check `Repeat task` to enable repeating. The datetime interval for repeating is customizable. Click on the number or time interval e.g. `Day` to change it. Once repetition is enabled on a node, it works as follows:
+* When `Status` changes to `Done`, the `Status` resets to `Todo`.
+* When `Status` changes to `Done`, the `Deadline` (or `Scheduled`) property changes to the current day/time plus the current repeated interval. For example, if it's currently 12:20 and the interval is 1 hr, the new value is 13:20.
+
+To define your own repeated nodes, create a `Date` or `DateTime` property and a property with [property choices](#property-choices) that has `Checkbox state mapping` configured. To configure a node with your user properties, re-read the previous paragraph replacing `Status`, `Deadline`, `Todo` and `Done` with your properties and checkbox mapping. One additional configuration you'll want to choose in a date/datetime popup is the property dropdown next to `When`.
+
 #### Customizing Tasks
 
 Since tasks are powered by properties and [new tags](#new-tags), they can be customized in a number of ways. Some parts of a task can't be customized because tasks are built into core features like the [Query Builder](https://docs.logseq.com/#/page/query%20builder) and queries on today's journal. Here are ways to customize tasks:
@@ -332,9 +350,20 @@ An automated backup of graphs is available by clicking on the upper right three
 
 ## Export and Import
 
-Currently the graph can only be exported as a [SQLite](https://sqlite.org/) DB file. To do so, click on the three dots menu in the upper right corner, select `Export Graph` and click the `Export SQLite DB` item. This creates a .sqlite file for use with Logseq. From that same menu, you can also select `Export both SQLite DB and assets` to create a .zip file which contains the .sqlite file and any asset files packaged as a .zip file.
+To export a DB graph, click on the three dots menu in the upper right corner, select `Export graph` and then choose one of the following options:
+
+1. `Export SQLite DB` - Export graph as a [SQLite](https://sqlite.org/) .db file.
+2. `Export both SQLite DB and assets` - Export graph as a .zip file containing the DB file and the graph's assets.
+3. `Export debug transit file` - Export graph as a transit file to be shared with the Logseq team for debugging. Any personal sensitive data is removed.
+4. `Export public pages` - Export graph in order to publish it on the web. See https://docs.logseq.com/#/page/publishing for more.
+
+To import a DB graph, click on the three dots menu in the upper right corner, selecting `Export graph` and then choose one of the following options:
+
+To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and then choose one of the following options:
 
-To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and click the `SQLite` item.
+1. `SQLite` - Import using the SQLite DB file from export.
+2. `File to DB graph` - Import a markdown graph. See the [db graph importer](#db-graph-importer) for more on it.
+3. `Debug Transit` - Import a debug transit file from export.
 
 ## Scripting
 

From a1c07ac9042c75f30aa78e812f17e9a60bd645b3 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 23 Jan 2025 09:14:55 -0500
Subject: [PATCH 146/196] add more specifics on web plugins

---
 db-version-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index c10e4b6..db170b6 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -15,7 +15,7 @@ The following changes affect both file and the new db graphs:
 * A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
 * The application performance is better - loading faster and handling larger graphs. For DB graphs, our last performance test exercised 30k+ pages.
 * On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
-* Plugins can be used from the web.
+* Plugins can be used from the web. For security reasons only [plugins configured with no "effect"](https://github.com/logseq/marketplace#how-to-submit-your-plugin) are usable. We will gradually open up effect plugins to certified/trustworthy plugins.
 * The visibility of left sidebar items are configurable. To configure, hover over the `Navigations` header and click on the filter icon to open a dropdown for toggling visibility of sidebar items.
 
 ## DB Graph Changes

From 111eb3ce39177d77e60981256ac9361a74a5b0fe Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 23 Jan 2025 09:53:01 -0500
Subject: [PATCH 147/196] mention that history is queryable

---
 db-version.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index b91f344..3df62b8 100644
--- a/db-version.md
+++ b/db-version.md
@@ -218,7 +218,7 @@ The status property is probably the most often used task property and thus it ha
 * `Done`
 * `Canceled`
 
-This property keeps a history of status changes for each block. Once this property changes from `Todo` to another status, its history is available by clicking on the task's spent time e.g. `9s` on the right side of a block.
+This property keeps a history of status changes for each block. Once this property changes from `Todo` to another status, its history is available by clicking on the task's spent time e.g. `9s` on the right side of a block. This history is queryable through advanced queries.
 
 #### Repeated Tasks and Nodes
 

From e2065ff0c31266cd0a3d4c6f83d502bb0d262b24 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 23 Jan 2025 10:12:27 -0500
Subject: [PATCH 148/196] mention repeat intervals

---
 db-version.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/db-version.md b/db-version.md
index 3df62b8..1b5410f 100644
--- a/db-version.md
+++ b/db-version.md
@@ -224,11 +224,13 @@ This property keeps a history of status changes for each block. Once this proper
 
 Repeating works for tasks as well as for user defined properties. Read to the end to define your own repeated nodes.
 
-Repeated tasks are available on any task that has a `Deadline` (or `Scheduled`) property. When setting the values for these properties in a popup, check `Repeat task` to enable repeating. The datetime interval for repeating is customizable. Click on the number or time interval e.g. `Day` to change it. Once repetition is enabled on a node, it works as follows:
+Repeated tasks are available on any task that has a `Deadline` (or `Scheduled`) property. When setting the values for these properties in a popup, check `Repeat task` to enable repeating. The datetime interval for repeating is customizable. Click on the number or time interval e.g. `Day` to change it. For dates, the time interval ranges from `Day` to `Year`. For datetimes, the time interval ranges from `Minute` to `Year`.
+
+Once repetition is enabled on a node, it works as follows:
 * When `Status` changes to `Done`, the `Status` resets to `Todo`.
 * When `Status` changes to `Done`, the `Deadline` (or `Scheduled`) property changes to the current day/time plus the current repeated interval. For example, if it's currently 12:20 and the interval is 1 hr, the new value is 13:20.
 
-To define your own repeated nodes, create a `Date` or `DateTime` property and a property with [property choices](#property-choices) that has `Checkbox state mapping` configured. To configure a node with your user properties, re-read the previous paragraph replacing `Status`, `Deadline`, `Todo` and `Done` with your properties and checkbox mapping. One additional configuration you'll want to choose in a date/datetime popup is the property dropdown next to `When`.
+To define your own repeated nodes, create a `Date` or `DateTime` property and a property with [property choices](#property-choices) that has `Checkbox state mapping` configured. To configure a node with your user properties, re-read the previous paragraphs replacing `Status`, `Deadline`, `Todo` and `Done` with your properties and checkbox mapping. One additional configuration you'll want to choose in a date/datetime popup is the property dropdown next to `When`.
 
 #### Customizing Tasks
 

From 515bf7c5acebc45061f54c0d7be5025ba6502f09 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 24 Jan 2025 15:00:38 -0500
Subject: [PATCH 149/196] Be explicit about new rows on tables

---
 db-version.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version.md b/db-version.md
index 1b5410f..7e03197 100644
--- a/db-version.md
+++ b/db-version.md
@@ -301,6 +301,7 @@ A table displays a group of nodes as rows and a node's properties as columns. A
 * Switch between `Table View`, `List View` or `Gallery View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages. The `Gallery View` is useful for viewing blocks as square tiles, especially for assets.
 * Resize columns by dragging the resize handle at a column header's border.
 * Click on the magnifying glass icon to live search a table. This is the only feature that doesn't persist when switching away from a table.
+* Click `+ New` at the bottom of a table to create a new block. If in a property or tags table, the newly created block will be associated with the respective property or tag.
 
 A powerful new feature of tables is the ability to create a table view. This is currently enabled for tag pages. To use it, click the `+` icon in the upper left to create a new tab in the table. Click on the tab's header to rename or delete this new view. Within this view, all of the above persisting features will save!
 

From 420137e1cb5850eea6fa4c08c3d6288bb6b86b5a Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 4 Feb 2025 16:51:39 -0500
Subject: [PATCH 150/196] Add one bullet that also applies to db graphs

---
 db-version-changes.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index db170b6..7f79900 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -93,6 +93,7 @@ Miscelleanous changes:
 * [Advanced queries](https://docs.logseq.com/#/page/advanced%20queries)
   * Advanced queries are now edited in a code block which means queries are syntax highlighted.
   * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
+  * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
   * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.
 * Since block timestamps are available, they display in table view where possible.
 
@@ -121,5 +122,5 @@ Miscelleanous changes:
 ## File Graph Changes
 
 * There is no longer a [conversion feature for filename formats](https://docs.logseq.com/#/page/filename%20format)
-* The attribute `:block/content` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
+  * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
 * The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
\ No newline at end of file

From daa4a0a2d94238db1e7e80637a7b0910cecb8039 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 10 Feb 2025 09:38:20 -0500
Subject: [PATCH 151/196] Link to published graphs

---
 pages/Publishing.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pages/Publishing.md b/pages/Publishing.md
index 1c0708f..bd7685d 100644
--- a/pages/Publishing.md
+++ b/pages/Publishing.md
@@ -57,5 +57,6 @@ description:: This feature publishes a graph as a [[Publish Web]], single page a
 		- See [routes.cljs](https://github.com/logseq/logseq/blob/master/src/main/frontend/routes.cljs) for other possible routes.
 - ## Additional Links
 	- https://github.com/logseq/publish-spa - Github action and CLI to publish a graph as a SPA
+	- https://github.com/logseq/publish-spa/network/dependents?package_id=UGFja2FnZS0zNjYwNTQ0Njc0 - Published logseq graphs on Github
 	- https://github.com/pengx17/logseq-publish - Archived and previously popular github action to publish a graph as a SPA
 	- https://github.com/sawhney17/logseq-schrodinger - Plugin to export Logseq pages to Hugo
\ No newline at end of file

From 1e8d82140995f5dbf09a631aa25dc70fb4b2ee2e Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 12 Feb 2025 16:06:45 -0500
Subject: [PATCH 152/196] add table features, edn data export and task changes

---
 db-version.md | 36 +++++++++++++++++++++++++++++-------
 1 file changed, 29 insertions(+), 7 deletions(-)

diff --git a/db-version.md b/db-version.md
index 7e03197..e230264 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Jan 22nd. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of Feb 12th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -191,9 +191,10 @@ Tasks are improved from the previous version as they more powerful and customiza
 #### Create a Task
 
 A new task can be created in a number of ways:
-* Set the status of a block by typing the status choice e.g. `/todo` or cyling status with `Cmd-Enter`.
+* On a block without a tag, add the `Status` property by typing the status choice e.g. `/todo` or cyling status with `Cmd-Enter`.
 * Type text in a block and end it with `#Task`.
 * When on the `Task` page, create a new row in the Task table.
+* On a block without a tag, add the `Deadline` or `Scheduled` property by typing `/Deadline` or `/Scheduled`.
 
 #### Task Shortcuts
 
@@ -294,14 +295,21 @@ Like other tags, go to their tag pages to view and manage all of them in one pla
 ## Tables
 
 A table displays a group of nodes as rows and a node's properties as columns. A table behaves like a spreadsheet as table cells are editable by default. A node has the following special columns which are available by default: `Name`, `Created At` and `Updated At`. Tables have the following features:
-* Sort rows by any column, ascending or descending.
-* Filter rows by multiple columns by clicking on the filter icon. For columns with a specific property type e.g. :number and :date, there are specific filters for that type.
-* Hide columns by clicking on the three dots menu and selecting `Columns visibility`.
-* Drag columns to sort their order.
+* Sort rows by multiples columns, sorting each by ascending or descending. Click on the sort icon to remove a sorting.
+* Filter rows by multiple columns by clicking on the filter icon.
+  * Multiple filters can be applied. By default, only rows that match all filters display (AND the filters). To match on any filter (OR filters), change the dropdown on the right to `Match any filter`.
+  * For columns with a specific property type e.g. :number and :date, there are specific filters for that type.
+* Group rows by a column by clicking on the three dots menu and selecting `Group by`.
+  * Rows can be grouped by all property types except `DateTime`.
+  * While each group is displayed as a different table, they all obey the same column configurations.
 * Switch between `Table View`, `List View` or `Gallery View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages. The `Gallery View` is useful for viewing blocks as square tiles, especially for assets.
-* Resize columns by dragging the resize handle at a column header's border.
 * Click on the magnifying glass icon to live search a table. This is the only feature that doesn't persist when switching away from a table.
 * Click `+ New` at the bottom of a table to create a new block. If in a property or tags table, the newly created block will be associated with the respective property or tag.
+* Columns can be configured in a number of ways:
+  * Hide columns by clicking on the three dots menu and selecting `Columns visibility`.
+  * Drag columns to sort their order.
+  * Pin column(s) to ensure they appear first.
+  * Resize columns by dragging the resize handle at a column header's border.
 
 A powerful new feature of tables is the ability to create a table view. This is currently enabled for tag pages. To use it, click the `+` icon in the upper left to create a new tab in the table. Click on the tab's header to rename or delete this new view. Within this view, all of the above persisting features will save!
 
@@ -353,6 +361,8 @@ An automated backup of graphs is available by clicking on the upper right three
 
 ## Export and Import
 
+### Graph Export
+
 To export a DB graph, click on the three dots menu in the upper right corner, select `Export graph` and then choose one of the following options:
 
 1. `Export SQLite DB` - Export graph as a [SQLite](https://sqlite.org/) .db file.
@@ -368,6 +378,18 @@ To import the exported .sqlite file, click on the three dots menu in the upper r
 2. `File to DB graph` - Import a markdown graph. See the [db graph importer](#db-graph-importer) for more on it.
 3. `Debug Transit` - Import a debug transit file from export.
 
+### EDN Data Export
+
+Exported EDN data allows any DB graph content to be shared between users as text. With this text, a user can then import it to replicate the same visible and behavioral content including the content's properties, tags. This is important as it gives users control of their content and enables some workflows that aren't possible with file graphs. This feature is available with the following commands:
+
+* `Export block EDN data` - Run this command on the current block to copy it to the clipboard. When this data is imported, it will overwrite the current block.
+* `Export page EDN data` - Run this command on the current page to copy it to the clipboard. When this is imported to an existing page, it will append to the existing page.
+* `Export graph's tags and properties EDN data` - Run this command to copy the entire graph's tags and properties. This is useful for sharing your workflows with others without sharing your graph-specific data. This is an example of a workflow that was not possible with file graphs.
+* `Import EDN data` - Run this command to import any of the above exported data. If importing a block, you must have focus on the block you want to import into.
+
+For developers, this shareable EDN data can also be used in scripts to create or modify existing graphs. For example, a page's data could be passed to [this script](https://github.com/logseq/logseq/blob/feat/db/deps/db/script/create_graph.cljs) to create a new DB graph with that page.
+
+
 ## Scripting
 
 DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db. Scripts can both read and _write any_ data in a DB graph. To write your own script, you'll need a package.json and nbb.edn. Use [this example package.json](https://github.com/logseq/publish-spa/blob/feat/db/package.json) and [this example nbb.edn](https://github.com/logseq/publish-spa/blob/feat/db/nbb.edn). Some example scripts:

From 4bba8def4098310ac8b3910d116cc0bd6cb40cab Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 13 Feb 2025 08:47:53 -0500
Subject: [PATCH 153/196] Add more atribute changes

---
 db-version-changes.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 7f79900..cc8a17f 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -122,5 +122,8 @@ Miscelleanous changes:
 ## File Graph Changes
 
 * There is no longer a [conversion feature for filename formats](https://docs.logseq.com/#/page/filename%20format)
+* Attribute changes:
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
-* The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
\ No newline at end of file
+  * The attribute `:block/original-name` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/original-name "name"]` -> `[?b :block/title "name"]`
+  * The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
+  * The attribute `:block/left` no longer exists and has been replaced by `:block/order`. It is not recommended to write queries with this attribute.
\ No newline at end of file

From ba3ca392b5024ab3828bd8d9d15b6f5cfe9846e4 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 27 Feb 2025 11:33:51 -0500
Subject: [PATCH 154/196] Add doc for removing heading on block - for #130

---
 db-version-changes.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version-changes.md b/db-version-changes.md
index cc8a17f..766f76e 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -36,6 +36,7 @@ High level changes:
   * `>Quote` is `/Quote`
 * Code blocks, quote blocks and math blocks [have tags](./db-version.md#more-new-tags). Since properties are not are a part of the block content, properties can more naturally be added to these blocks.
 * Pdf annotations [have a tag](./db-version.md#more-new-tags). This allows annotations to be viewed across pdfs and to have custom views of annotations while using the pdf viewer.
+* Markdown syntax for blocks e.g. a heading or quote is no longer visible or editable. Removing a block's heading is done by right-click on a block and choosing the crossed out H icon.
 
 WIP changes:
 * Whiteboards are disabled for now and will be enabled later.

From 7d259f0e330269623ac11f783f8fd663f8d42918 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 24 Mar 2025 15:17:06 -0400
Subject: [PATCH 155/196] Add views section, templates, bulk actions and more
 export features

---
 db-version-changes.md |  5 ++-
 db-version.md         | 80 +++++++++++++++++++++++++++++++------------
 2 files changed, 63 insertions(+), 22 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 766f76e..eb00009 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -67,7 +67,6 @@ Miscelleanous changes:
 
 * Using terms from the [previous tasks](https://docs.logseq.com/#/page/tasks), a task marker, priority and deadline are respectively now `Status`, `Priority` and `Deadline` properties on a task.
 * [Scheduled](https://docs.logseq.com/#/page/tasks/block/deadline%20and%20scheduled) has been deprecated.
-* Recurring tasks aren't ported and are a TODO.
 * Logbook timestamps have been deprecated.
 * Tasks are no longer created by typing keywords like `TODO` but instead with commands like '/todo'.
 * Read more about the [new tasks](./db-version.md#tasks).
@@ -111,6 +110,10 @@ Miscelleanous changes:
 * A graph's config.edn, custom.js and custom.css files are only editable within Logseq from `Settings`.
 * The following config.edn options are no longer used: `:block-hidden-properties, :favorites, :hidden, :ignored-page-references-keywords, :preferred-format, :preferred-workflow, :feature/enable-block-timestamps?, :file/name-format, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist`. See [this code](https://github.com/logseq/logseq/blob/043927031e11053a837d8289e3334368e6647bea/src/main/frontend/handler/common/config_edn.cljs#L89-L115) for more details.
 
+#### Search
+* When search modal first opens, recently updated pages display at the top.
+* Tags can be created from the modal as described in [new tags](./db-version.md#new-tags).
+
 #### DB Graph Directories
 
 * Graphs have a convention of `~/logseq/graphs/GRAPH-NAME` where `GRAPH-NAME` is the graph name.
diff --git a/db-version.md b/db-version.md
index e230264..c16e57d 100644
--- a/db-version.md
+++ b/db-version.md
@@ -15,8 +15,11 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
   * [Queries](#queries)
   * [Cards](#cards)
   * [Assets](#assets)
+  * [Templates](#templates)
   * [More New Tags](#more-new-tags)
-* [Tables](#tables)
+* [Bulk Actions](#bulk-actions)
+* [Views](#views)
+  * [Tables](#tables)
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
 * [Export and Import](#export-and-import)
@@ -259,7 +262,7 @@ A [(simple) query](https://docs.logseq.com/#/page/queries) and [advanced query](
 * Type a simple query in a block and then type the `/Query` command to run the query.
 * Type the `/Advanced Query` command to create an advanced query.
 
-Like other new tags, go to the `#Query` page to see a table to manage queries. Query results are displayed with the new [tables](#tables).
+Like other new tags, go to the `#Query` page to see a table to manage queries. Query results are displayed in a [view](#views).
 
 ### Cards
 
@@ -282,6 +285,12 @@ You can rate them using 4 levels to arrange their next review date.
 
 An asset has the new tag `#Asset`. Assets are created by dragging and dropping a file onto a block. They can also be batch uploaded by going to the `#Asset` page and clicking the `+` icon from the `Tagged Nodes` table. Asset files are stored under a graph's `assets/` directory. Manage assets from the `#Asset` page's `Tagged Nodes` section. The `Gallery View` is a helpful way to view assets.
 
+### Template
+
+A template has the new tag `#Template`. A template allows for block(s) and their children to be easily copied. To create a template, write the name of the template in a new block and tag the block with `#Template`. Then add children blocks (however many levels deep) under the template block. To insert a copy of a template, use the `/Template` command.
+
+When creating a template block, there is an optional `Apply template to tags` property to use. This property provides interesting automation whenever a [tagged node](#tagged-node) is created for a configured tag. For example, create a template and configure the property to apply to `#Journal`. Now whenever a journal page is created, the template gets applied at the top of the page. If a tag is configured with multiple templates, the templates are applied in succession. When a tagged node is a block instead of a page e.g. `#Task`, the template is applied as the first child of the block. Templates can apply to built-in and user tags.
+
 ### More New Tags
 
 Here are more new tags that are built-in, most of which are created with `/` commands:
@@ -292,28 +301,53 @@ Here are more new tags that are built-in, most of which are created with `/` com
 
 Like other tags, go to their tag pages to view and manage all of them in one place. Also like other tags, extend any tag by adding more properties to it. For example, add an author property to `#Quote` to optionally add authors to quotes.
 
-## Tables
+## Bulk Actions
+
+Bulk actions are a powerful way to make changes across nodes. When multiple nodes are selected, bulk actions can be taken on them. To select nodes in a block context, use a mouse or the shift + arrow keys. Once nodes are selected, a bulk action header appears above the blocks. The bulk action header can be closed with `Esc`. The following bulk actions are available in the header:
+* `Tag`: Click on `#` icon to add/update/remove [new tags](#new-tags) for selected nodes.
+* `Copy`: Copy the block or page title of selected nodes.
+* `Set Property`: Add or update a [property](#properties) for selected nodes.
+* `Unset Property`: Remove a [property](#properties) for selected nodes.
+* `Delete`: Click on the trash icon to delete selected nodes.
+* `Three dots menu`: Click on the three dots icon to invoke additional actions to apply to selected nodes. These actions mostly consist of ones that are available when right clicking on a block.
+
+Nodes can also be selected and have bulk actions in [tables](#tables).
+
+## Views
+
+Views are a powerful way to visualize a group of nodes in different ways. A view can switch between the following view types: `Table View`, `List View` or `Gallery View`. Most views default to the [Table View](#tables). The `List View` displays nodes in an outliner with nodes grouped by pages. The `Gallery View` is useful for viewing blocks as square tiles, especially for assets.
+
+Views are used in a number of features including queries, (un)linked references, property and tag pages and `All pages`. For all these features except queries, multiple views can be created. Regardless of which view type you're in, a view's header has these common actions from left to right:
+
+* `View name`: A view's name is editable by clicking on it and renaming it. A view can also be deleted from here.
+* `New view`: Click on `+` to create a new view. Since a view is fairly customizable, this is useful for creating different views on the same nodes and to view a specific subgroup of nodes with filters.
+* `Filter`: Filter nodes by any properties/columns by clicking on the filter icon.
+  * Multiple filters can be created and applied.
+  * By default, only rows that match all filters display (AND the filters). To match on any filter (OR filters), change the dropdown on the right to `Match any filter`.
+  * There are different operators to filter values for every property value type e.g. `Date` and `DateTime`. For example, string values can have `is` or `is not` operators while numbers can also have `<, >, <=, >= and between` operators.
+* `Search`: Live search a view by clicking on the magnifying glass icon. This is the only feature that doesn't persist when switching away from a view.
+* `View type`: Click on the view type name to switch between different types.
+* `Three dots menu`: Click on the three dots menu to invoke additional actions. Some actions are specific to a view type. The following actions are common across view types:
+  * `Group by`: Group by a column/property and its values i.e. a different group for each property value. The different groups are vertically stacked.
+    * Nodes can be grouped by all property types except for `DateTime`.
+    * While each group is displayed as a different view, they all obey the same view-level configuration.
+  * `Export EDN`: Exports the currently viewable nodes to your clipboard as [EDN Data](#edn-data-export). The exported nodes are affected by `Search` or `Filter` usage.
+* `New node`: Click on the `+` icon to create a new node in the view. Different features will behave differently for this. For example, when clicked from a tag or property page, the new node will have that tag or property added to it.
+
+NOTE: All actions that alter what you see are saved except for `Search`!
+
+### Tables
 
 A table displays a group of nodes as rows and a node's properties as columns. A table behaves like a spreadsheet as table cells are editable by default. A node has the following special columns which are available by default: `Name`, `Created At` and `Updated At`. Tables have the following features:
-* Sort rows by multiples columns, sorting each by ascending or descending. Click on the sort icon to remove a sorting.
-* Filter rows by multiple columns by clicking on the filter icon.
-  * Multiple filters can be applied. By default, only rows that match all filters display (AND the filters). To match on any filter (OR filters), change the dropdown on the right to `Match any filter`.
-  * For columns with a specific property type e.g. :number and :date, there are specific filters for that type.
-* Group rows by a column by clicking on the three dots menu and selecting `Group by`.
-  * Rows can be grouped by all property types except `DateTime`.
-  * While each group is displayed as a different table, they all obey the same column configurations.
-* Switch between `Table View`, `List View` or `Gallery View` by selecting one in the table's header. The `List View` displays nodes in an outliner with nodes grouped by pages. The `Gallery View` is useful for viewing blocks as square tiles, especially for assets.
-* Click on the magnifying glass icon to live search a table. This is the only feature that doesn't persist when switching away from a table.
-* Click `+ New` at the bottom of a table to create a new block. If in a property or tags table, the newly created block will be associated with the respective property or tag.
-* Columns can be configured in a number of ways:
-  * Hide columns by clicking on the three dots menu and selecting `Columns visibility`.
+
+* `Sort`: Click on a column to sort it by ascending or descending. Multiples sorts can be applied. Click on the sort icon in the header to remove a sort.
+* `Columns visibility`: Under the three dots menu, this menu can toggle the visibility of any column.
+* `+ New`: At the bottom of the table, this creates a new node, like the `+` icon in the view header.
+* Column actions:
+  * Click on column(s) and select `Pin` to ensure they appear first.
   * Drag columns to sort their order.
-  * Pin column(s) to ensure they appear first.
   * Resize columns by dragging the resize handle at a column header's border.
-
-A powerful new feature of tables is the ability to create a table view. This is currently enabled for tag pages. To use it, click the `+` icon in the upper left to create a new tab in the table. Click on the tab's header to rename or delete this new view. Within this view, all of the above persisting features will save!
-
-Tables are currently found on new tag pages, property pages, query results and the `All Pages` view.
+* Bulk actions: When rows in the table are selected, bulk actions appear in the table header. All the bulk actions [described above](#bulk-actions) are available except for the `Three dots menu`.
 
 ## DB Graph Importer
 
@@ -368,7 +402,8 @@ To export a DB graph, click on the three dots menu in the upper right corner, se
 1. `Export SQLite DB` - Export graph as a [SQLite](https://sqlite.org/) .db file.
 2. `Export both SQLite DB and assets` - Export graph as a .zip file containing the DB file and the graph's assets.
 3. `Export debug transit file` - Export graph as a transit file to be shared with the Logseq team for debugging. Any personal sensitive data is removed.
-4. `Export public pages` - Export graph in order to publish it on the web. See https://docs.logseq.com/#/page/publishing for more.
+4. `Export EDN file` - Export graph as EDN described in [EDN Data Export](#edn-data-export).
+5. `Export public pages` - Export graph in order to publish it on the web. See https://docs.logseq.com/#/page/publishing for more.
 
 To import a DB graph, click on the three dots menu in the upper right corner, selecting `Export graph` and then choose one of the following options:
 
@@ -377,6 +412,7 @@ To import the exported .sqlite file, click on the three dots menu in the upper r
 1. `SQLite` - Import using the SQLite DB file from export.
 2. `File to DB graph` - Import a markdown graph. See the [db graph importer](#db-graph-importer) for more on it.
 3. `Debug Transit` - Import a debug transit file from export.
+4. `EDN to DB graph` - Import a DB graph that was exported as EDN into a new DB graph.
 
 ### EDN Data Export
 
@@ -387,6 +423,8 @@ Exported EDN data allows any DB graph content to be shared between users as text
 * `Export graph's tags and properties EDN data` - Run this command to copy the entire graph's tags and properties. This is useful for sharing your workflows with others without sharing your graph-specific data. This is an example of a workflow that was not possible with file graphs.
 * `Import EDN data` - Run this command to import any of the above exported data. If importing a block, you must have focus on the block you want to import into.
 
+This feature is also available for the whole graph using the `Export EDN file` and `EDN to DB graph` options described above.
+
 For developers, this shareable EDN data can also be used in scripts to create or modify existing graphs. For example, a page's data could be passed to [this script](https://github.com/logseq/logseq/blob/feat/db/deps/db/script/create_graph.cljs) to create a new DB graph with that page.
 
 

From 176528c0addc53207e2a4e6a94df2dc9c50f5ab4 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 24 Mar 2025 16:02:30 -0400
Subject: [PATCH 156/196] Add a scripting section on modifying db graph

Already had to reference this a couple times in chat
---
 db-version.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index c16e57d..2edbd33 100644
--- a/db-version.md
+++ b/db-version.md
@@ -434,4 +434,12 @@ DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db
 
 * https://github.com/logseq/logseq/tree/feat/db/deps/db/script - Scripts to query, validate and create any graph
 * https://github.com/logseq/logseq/blob/feat/db/deps/outliner/script/transact.cljs - Script to transact (modify) nodes queried from the commandline
-* https://github.com/logseq/logseq/tree/feat/db/scripts/src/logseq/tasks/db_graph - More complex scripts to generate graphs with all property types or with schema.org's ontology. See [this readme](https://github.com/logseq/logseq/tree/feat/db/scripts#nbb-scripts) for using these.
\ No newline at end of file
+* https://github.com/logseq/logseq/tree/feat/db/scripts/src/logseq/tasks/db_graph - More complex scripts to generate graphs with all property types or with schema.org's ontology. See [this readme](https://github.com/logseq/logseq/tree/feat/db/scripts#nbb-scripts) for using these.
+
+### Modify a DB Graph
+
+On desktop, it is easy to modify an existing DB graph with a script and see the change in Logseq. To do so:
+
+1. Press Cmd-S to persist a graph to `~/logseq/graphs/GRAPH-NAME/db.sqlite`.
+2. Modify the db.sqlite with a nbb-logseq script.
+3. Update the app to use the modified db.sqlite by using the `Replace graph with its db.sqlite file` dev command.
\ No newline at end of file

From fcb21ac228736f821b5daf4297aed05d7163bc9e Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 27 Mar 2025 09:47:38 -0400
Subject: [PATCH 157/196] add header for import

---
 db-version.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/db-version.md b/db-version.md
index 2edbd33..46b417c 100644
--- a/db-version.md
+++ b/db-version.md
@@ -23,6 +23,9 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
 * [Export and Import](#export-and-import)
+  * [Graph Export](#graph-export)
+  * [Graph Import](#graph-import)
+  * [EDN Data Export](#edn-data-export)
 * [Scripting](#scripting)
 
 ## Nodes
@@ -405,6 +408,8 @@ To export a DB graph, click on the three dots menu in the upper right corner, se
 4. `Export EDN file` - Export graph as EDN described in [EDN Data Export](#edn-data-export).
 5. `Export public pages` - Export graph in order to publish it on the web. See https://docs.logseq.com/#/page/publishing for more.
 
+### Graph Import
+
 To import a DB graph, click on the three dots menu in the upper right corner, selecting `Export graph` and then choose one of the following options:
 
 To import the exported .sqlite file, click on the three dots menu in the upper right corner, select `Import` and then choose one of the following options:

From aa441c6eb378ca065f055e3e3691ffdb9b8678e7 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 28 Mar 2025 14:44:12 -0400
Subject: [PATCH 158/196] Add note for feature with all the recent bug fixes

---
 db-version.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 46b417c..2caf877 100644
--- a/db-version.md
+++ b/db-version.md
@@ -405,7 +405,7 @@ To export a DB graph, click on the three dots menu in the upper right corner, se
 1. `Export SQLite DB` - Export graph as a [SQLite](https://sqlite.org/) .db file.
 2. `Export both SQLite DB and assets` - Export graph as a .zip file containing the DB file and the graph's assets.
 3. `Export debug transit file` - Export graph as a transit file to be shared with the Logseq team for debugging. Any personal sensitive data is removed.
-4. `Export EDN file` - Export graph as EDN described in [EDN Data Export](#edn-data-export).
+4. `Export EDN file` - Export graph as EDN described in [EDN Data Export](#edn-data-export). This feature is not yet recommended as the only means to backup a graph.
 5. `Export public pages` - Export graph in order to publish it on the web. See https://docs.logseq.com/#/page/publishing for more.
 
 ### Graph Import

From 771b0c7a851e65b98d3c380a6f4784bf67134957 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 31 Mar 2025 13:23:20 -0400
Subject: [PATCH 159/196] link to first shared graph on github

---
 db-version.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 2caf877..5b3714a 100644
--- a/db-version.md
+++ b/db-version.md
@@ -27,6 +27,7 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
   * [Graph Import](#graph-import)
   * [EDN Data Export](#edn-data-export)
 * [Scripting](#scripting)
+* [Additional Links](#additional-links)
 
 ## Nodes
 
@@ -447,4 +448,7 @@ On desktop, it is easy to modify an existing DB graph with a script and see the
 
 1. Press Cmd-S to persist a graph to `~/logseq/graphs/GRAPH-NAME/db.sqlite`.
 2. Modify the db.sqlite with a nbb-logseq script.
-3. Update the app to use the modified db.sqlite by using the `Replace graph with its db.sqlite file` dev command.
\ No newline at end of file
+3. Update the app to use the modified db.sqlite by using the `Replace graph with its db.sqlite file` dev command.
+
+## Additional Links
+* https://github.com/C0ntr0lledCha0s/logseq-template-graph - Example graph with useful properties and tags
\ No newline at end of file

From eee4c3cae967ea98c789fa82cfabffcd58c97547 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 30 Apr 2025 17:19:51 -0400
Subject: [PATCH 160/196] Update docs for april changes

---
 db-version-changes.md |  4 +++-
 db-version.md         | 18 +++++++++++-------
 2 files changed, 14 insertions(+), 8 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index eb00009..d8a4345 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -13,9 +13,10 @@ This page describes changes for existing Logseq features on the [database versio
 The following changes affect both file and the new db graphs:
 * To simplify editor `/` commands, [Commands](https://docs.logseq.com/#/page/commands) and [Advanced Commands](https://docs.logseq.com/#/page/advanced%20commands) are merged together under `/`.
 * A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
-* The application performance is better - loading faster and handling larger graphs. For DB graphs, our last performance test exercised 30k+ pages.
+* The application performance is better - loading faster, handling larger graphs and large tables. See https://github.com/logseq/logseq/pull/11774 for latest details.
 * On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
 * Plugins can be used from the web. For security reasons only [plugins configured with no "effect"](https://github.com/logseq/marketplace#how-to-submit-your-plugin) are usable. We will gradually open up effect plugins to certified/trustworthy plugins.
+* On browser, multiple tabs can be opened and kept in sync, even when offline. Syncing between tabs _does not_ require a sync server.
 * The visibility of left sidebar items are configurable. To configure, hover over the `Navigations` header and click on the filter icon to open a dropdown for toggling visibility of sidebar items.
 
 ## DB Graph Changes
@@ -125,6 +126,7 @@ Miscelleanous changes:
 
 ## File Graph Changes
 
+* File graphs are no longer supported in browser.
 * There is no longer a [conversion feature for filename formats](https://docs.logseq.com/#/page/filename%20format)
 * Attribute changes:
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
diff --git a/db-version.md b/db-version.md
index 5b3714a..0582a78 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of Feb 12th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of April 30th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -84,6 +84,7 @@ A property itself can have properties on its property page. By default the `Desc
 * `p t` toggles displaying all the current node's properties below it. This is useful to quickly view properties that are hidden or in a different position.
 * `p i` opens the icon picker to set an icon for the current node.
 * See [task shortcuts](#task-shortcuts) for task specific ones.
+* To navigate between property values across nodes, use the up and down arrow keys.
 
 NOTE: Most shortcuts have a corresponding search command. You can find the command for a given shortcut's keys keybinding by using `Settings > Keymap`, clicking the keystroke filter and typing the keys.
 
@@ -119,7 +120,7 @@ A property type determines what type a property's property values can have. Ther
 * `Date`: This is for dates and is editable with a date picker. When a date property value is used, it correctly links to the journal page. This property type can be used with [repeated nodes](#repeated-tasks-and-nodes).
 * `DateTime`: This is for date times and is editable with a datetime picker. See the `Due` property in [cards](#cards) for an example property that uses this. This property type can be used with [repeated nodes](#repeated-tasks-and-nodes).
 * `Checkbox`: This is used to set or unset a property value and displays as a checkbox. To engineers this type is known as a boolean.
-* `Url`: This limits text to only allow urls e.g. `https://logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
+* `Url`. This limits text to only allow urls e.g. `https.//logseq.com`. This does not behave like `Text` e.g. no referencing or child blocks.
 * `Node`: This allows a property value to link to other nodes i.e. pages or blocks. When first configuring this, you are prompted to select a new tag. You can choose to skip a tag if you don't care about limiting the available nodes. When a tag is selected or created, only nodes with that tag will appear as options for the property. For example, if you define the property `Author`, you could create a new tag `#Person` that only allows nodes tagged with `#Person` as values. Also worth noting that tag selection works for all child tags of the chosen new tag. Using the previous example, if `#Actor` is a child of `#Person`, nodes tagged with `#Person` or `#Actor` are allowed values.
 
 ### Property Choices
@@ -405,9 +406,10 @@ To export a DB graph, click on the three dots menu in the upper right corner, se
 
 1. `Export SQLite DB` - Export graph as a [SQLite](https://sqlite.org/) .db file.
 2. `Export both SQLite DB and assets` - Export graph as a .zip file containing the DB file and the graph's assets.
-3. `Export debug transit file` - Export graph as a transit file to be shared with the Logseq team for debugging. Any personal sensitive data is removed.
-4. `Export EDN file` - Export graph as EDN described in [EDN Data Export](#edn-data-export). This feature is not yet recommended as the only means to backup a graph.
+3. `Export EDN file` - Export graph as EDN described in [EDN Data Export](#edn-data-export). This is the only export type that fully captures a graph's data and is editable. This export is not yet recommended as the only means to backup a graph.
+4. `Export as standard Markdown (no block properties)` - Export graph as standard markdown, not Logseq markdown. Since this export is unlikely to ever export timestamps or all properties, it cannot capture all data in a graph. See the EDN export for an export type that captures all data and is editable.
 5. `Export public pages` - Export graph in order to publish it on the web. See https://docs.logseq.com/#/page/publishing for more.
+6. `Export debug transit file` - Export graph as a transit file to be shared with the Logseq team for debugging. Any personal sensitive data is removed.
 
 ### Graph Import
 
@@ -422,18 +424,20 @@ To import the exported .sqlite file, click on the three dots menu in the upper r
 
 ### EDN Data Export
 
-Exported EDN data allows any DB graph content to be shared between users as text. With this text, a user can then import it to replicate the same visible and behavioral content including the content's properties, tags. This is important as it gives users control of their content and enables some workflows that aren't possible with file graphs. This feature is available with the following commands:
+Exported [EDN data](https://github.com/edn-format/edn) allows any DB graph content to be shared between users as text. With this text, a user can then import it to replicate the same visible and behavioral content including the content's properties and tags. This is important as it gives users control of their content and enables some workflows that aren't possible with file graphs. This feature is available with the following commands:
 
 * `Export block EDN data` - Run this command on the current block to copy it to the clipboard. When this data is imported, it will overwrite the current block.
 * `Export page EDN data` - Run this command on the current page to copy it to the clipboard. When this is imported to an existing page, it will append to the existing page.
 * `Export graph's tags and properties EDN data` - Run this command to copy the entire graph's tags and properties. This is useful for sharing your workflows with others without sharing your graph-specific data. This is an example of a workflow that was not possible with file graphs.
 * `Import EDN data` - Run this command to import any of the above exported data. If importing a block, you must have focus on the block you want to import into.
 
-This feature is also available for the whole graph using the `Export EDN file` and `EDN to DB graph` options described above.
+This feature is also available:
+* for the whole graph using the `Export EDN file` and `EDN to DB graph` options described above.
+* from any [view](#views) as a header action. For example, go to the `All pages` view and filter it to only export the viewable pages.
+* for multiple selected nodes with the `Copy / Export as` modal.
 
 For developers, this shareable EDN data can also be used in scripts to create or modify existing graphs. For example, a page's data could be passed to [this script](https://github.com/logseq/logseq/blob/feat/db/deps/db/script/create_graph.cljs) to create a new DB graph with that page.
 
-
 ## Scripting
 
 DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db. Scripts can both read and _write any_ data in a DB graph. To write your own script, you'll need a package.json and nbb.edn. Use [this example package.json](https://github.com/logseq/publish-spa/blob/feat/db/package.json) and [this example nbb.edn](https://github.com/logseq/publish-spa/blob/feat/db/nbb.edn). Some example scripts:

From 9395c744c74356d85ef770fcd14fe882ec17dea7 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 1 May 2025 08:41:30 -0400
Subject: [PATCH 161/196] fix incorrect task changes

---
 db-version-changes.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index d8a4345..8e56925 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -66,9 +66,8 @@ Miscelleanous changes:
 
 #### Tasks
 
-* Using terms from the [previous tasks](https://docs.logseq.com/#/page/tasks), a task marker, priority and deadline are respectively now `Status`, `Priority` and `Deadline` properties on a task.
-* [Scheduled](https://docs.logseq.com/#/page/tasks/block/deadline%20and%20scheduled) has been deprecated.
-* Logbook timestamps have been deprecated.
+* Using terms from the [previous tasks](https://docs.logseq.com/#/page/tasks), a task marker, priority, deadline and scheduled are respectively now `Status`, `Priority`, `Deadline` and `Scheduled` properties on a task.
+* Logbook timestamps have been replaced with Status change history.
 * Tasks are no longer created by typing keywords like `TODO` but instead with commands like '/todo'.
 * Read more about the [new tasks](./db-version.md#tasks).
 
@@ -132,4 +131,4 @@ Miscelleanous changes:
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
   * The attribute `:block/original-name` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/original-name "name"]` -> `[?b :block/title "name"]`
   * The attribute `:block/journal?` no longer exists. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/type` e.g. `[?p :block/journal? true]` -> `[?p :block/type "journal"]`
-  * The attribute `:block/left` no longer exists and has been replaced by `:block/order`. It is not recommended to write queries with this attribute.
\ No newline at end of file
+  * The attribute `:block/left` no longer exists and has been replaced by `:block/order`. It is not recommended to write queries with this attribute.

From ea40a841025813e0d4b86338efb3a61fbc531b96 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 6 May 2025 12:17:28 -0400
Subject: [PATCH 162/196] fix header link

---
 db-version.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version.md b/db-version.md
index 0582a78..d855575 100644
--- a/db-version.md
+++ b/db-version.md
@@ -290,7 +290,7 @@ You can rate them using 4 levels to arrange their next review date.
 
 An asset has the new tag `#Asset`. Assets are created by dragging and dropping a file onto a block. They can also be batch uploaded by going to the `#Asset` page and clicking the `+` icon from the `Tagged Nodes` table. Asset files are stored under a graph's `assets/` directory. Manage assets from the `#Asset` page's `Tagged Nodes` section. The `Gallery View` is a helpful way to view assets.
 
-### Template
+### Templates
 
 A template has the new tag `#Template`. A template allows for block(s) and their children to be easily copied. To create a template, write the name of the template in a new block and tag the block with `#Template`. Then add children blocks (however many levels deep) under the template block. To insert a copy of a template, use the `/Template` command.
 

From 769a9562e6fe68a99a44cbfbf3b61876d7e6cba4 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:16:03 +0800
Subject: [PATCH 163/196] Auto saved by Logseq

---
 pages/Changelog.md | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 2c1f8f0..00ace42 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,17 @@
-## Beta 0.10.9 [[Apr 23rd, 2024]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.9>
+## Beta 0.10.10 [[May 7th, 2025]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>
+	- [[Features]]
+		-
+	- [[Thanks]]
+		-
+	- [[Fixed issues]]
+		- fix(sync): cannot delete some nested files
+		- fix(mobile): incorrect theme color for the android status bar
+		- Fix Twitter's rename breaking macro wrapping (#11325)
+	- [[Enhancement]]
+		-
+- ## Beta 0.10.9 [[Apr 23rd, 2024]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.9>
 	- [[Thanks]]
 		- [[desk7]]
 			- Update Italian translation in [#11179](https://github.com/logseq/logseq/pull/11179)

From 27579c0c26f157c0bf573d12501f6203558a476d Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:17:03 +0800
Subject: [PATCH 164/196] Auto saved by Logseq

---
 pages/Changelog.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 00ace42..76078ea 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -5,9 +5,14 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 	- [[Thanks]]
 		-
 	- [[Fixed issues]]
+		- fix: graph keep re-index when loading
 		- fix(sync): cannot delete some nested files
 		- fix(mobile): incorrect theme color for the android status bar
-		- Fix Twitter's rename breaking macro wrapping (#11325)
+		- Fix Twitter's rename breaking macro wrapping
+		- fix(mobile): invalid keyboard input for the `create account` pane form
+		- fix: Open as Page in sidebar does not work
+		- fix: cut/delete blocks should work in page-embed
+		- fix: drag-drop / copy-paste should work for multiple files
 	- [[Enhancement]]
 		-
 - ## Beta 0.10.9 [[Apr 23rd, 2024]]

From 5d788293f3a81f555a7746ca752113b4300381e1 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:18:03 +0800
Subject: [PATCH 165/196] Auto saved by Logseq

---
 pages/Changelog.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 76078ea..7957bf6 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,7 +1,5 @@
 ## Beta 0.10.10 [[May 7th, 2025]]
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>
-	- [[Features]]
-		-
 	- [[Thanks]]
 		-
 	- [[Fixed issues]]
@@ -14,6 +12,8 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- fix: cut/delete blocks should work in page-embed
 		- fix: drag-drop / copy-paste should work for multiple files
 	- [[Enhancement]]
+		- Upgrade Electron to 35.0.1
+		- enhance(ux): better highlights page name for the search result items
 		-
 - ## Beta 0.10.9 [[Apr 23rd, 2024]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.9>

From e5ace555d7e92ecc92673c54f6126f8eabf49de9 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:19:03 +0800
Subject: [PATCH 166/196] Auto saved by Logseq

---
 pages/Changelog.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 7957bf6..ce6fe9a 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -2,6 +2,7 @@
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>
 	- [[Thanks]]
 		-
+		- Fix Twitter's rename breaking macro wrapping
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading
 		- fix(sync): cannot delete some nested files
@@ -14,6 +15,7 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 	- [[Enhancement]]
 		- Upgrade Electron to 35.0.1
 		- enhance(ux): better highlights page name for the search result items
+		- Add MSI build for windows
 		-
 - ## Beta 0.10.9 [[Apr 23rd, 2024]]
   Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.9>

From 2f6c21f5f4d624697543db390bcd4921018ef212 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:20:03 +0800
Subject: [PATCH 167/196] Auto saved by Logseq

---
 pages/Changelog.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index ce6fe9a..4b5f896 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,8 +1,9 @@
 ## Beta 0.10.10 [[May 7th, 2025]]
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>
 	- [[Thanks]]
+		- [chiefnoah](https://github.com/chiefnoah)
+			- Fix Twitter's rename breaking macro wrapping [#11325](https://github.com/logseq/logseq/pull/11325)
 		-
-		- Fix Twitter's rename breaking macro wrapping
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading
 		- fix(sync): cannot delete some nested files

From 571f95a7b74682fb91ab5cf294414e969c573798 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:21:03 +0800
Subject: [PATCH 168/196] Auto saved by Logseq

---
 pages/Changelog.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 4b5f896..a540db8 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -3,7 +3,8 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 	- [[Thanks]]
 		- [chiefnoah](https://github.com/chiefnoah)
 			- Fix Twitter's rename breaking macro wrapping [#11325](https://github.com/logseq/logseq/pull/11325)
-		-
+		- [rappire](https://github.com/rappire)
+			- Update Korean translation [#11320](https://github.com/logseq/logseq/pull/11320)
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading
 		- fix(sync): cannot delete some nested files

From 0ff374c8286d30d337e2aca6db001fb41af11de3 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:22:03 +0800
Subject: [PATCH 169/196] Auto saved by Logseq

---
 pages/Changelog.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index a540db8..5a23a62 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -5,6 +5,9 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 			- Fix Twitter's rename breaking macro wrapping [#11325](https://github.com/logseq/logseq/pull/11325)
 		- [rappire](https://github.com/rappire)
 			- Update Korean translation [#11320](https://github.com/logseq/logseq/pull/11320)
+		- [AyushAgrawal-A2](https://github.com/AyushAgrawal-A2)
+			- fix: cut/delete blocks should work in page-embed [#11216](https://github.com/logseq/logseq/pull/11216)
+		-
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading
 		- fix(sync): cannot delete some nested files
@@ -12,7 +15,6 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- Fix Twitter's rename breaking macro wrapping
 		- fix(mobile): invalid keyboard input for the `create account` pane form
 		- fix: Open as Page in sidebar does not work
-		- fix: cut/delete blocks should work in page-embed
 		- fix: drag-drop / copy-paste should work for multiple files
 	- [[Enhancement]]
 		- Upgrade Electron to 35.0.1

From 8168a4a6c5362f535c63d71a72447355ddf4b955 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:23:03 +0800
Subject: [PATCH 170/196] Auto saved by Logseq

---
 pages/Changelog.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 5a23a62..9e8777f 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -7,6 +7,7 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 			- Update Korean translation [#11320](https://github.com/logseq/logseq/pull/11320)
 		- [AyushAgrawal-A2](https://github.com/AyushAgrawal-A2)
 			- fix: cut/delete blocks should work in page-embed [#11216](https://github.com/logseq/logseq/pull/11216)
+			- fix: drag-drop / copy-paste should work for multiple files [#11214](https://github.com/logseq/logseq/pull/11214)
 		-
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading
@@ -15,7 +16,6 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- Fix Twitter's rename breaking macro wrapping
 		- fix(mobile): invalid keyboard input for the `create account` pane form
 		- fix: Open as Page in sidebar does not work
-		- fix: drag-drop / copy-paste should work for multiple files
 	- [[Enhancement]]
 		- Upgrade Electron to 35.0.1
 		- enhance(ux): better highlights page name for the search result items

From 6635709a48c692f0030dbc0f66947650e022c0e1 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:24:03 +0800
Subject: [PATCH 171/196] Auto saved by Logseq

---
 pages/Changelog.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 9e8777f..f136dcd 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -8,6 +8,8 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 		- [AyushAgrawal-A2](https://github.com/AyushAgrawal-A2)
 			- fix: cut/delete blocks should work in page-embed [#11216](https://github.com/logseq/logseq/pull/11216)
 			- fix: drag-drop / copy-paste should work for multiple files [#11214](https://github.com/logseq/logseq/pull/11214)
+		- [scayuela](https://github.com/scayuela)
+			- Catalan translation [#11587](https://github.com/logseq/logseq/pull/11587)
 		-
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading

From 85e8e252492df5c396474cfddfeeb12aa8ecc297 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:25:03 +0800
Subject: [PATCH 172/196] Auto saved by Logseq

---
 pages/Changelog.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index f136dcd..a5fdd6e 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -10,6 +10,8 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 			- fix: drag-drop / copy-paste should work for multiple files [#11214](https://github.com/logseq/logseq/pull/11214)
 		- [scayuela](https://github.com/scayuela)
 			- Catalan translation [#11587](https://github.com/logseq/logseq/pull/11587)
+		- [xraysight](https://github.com/xraysight)
+			- PL translation update 100% [#11306](https://github.com/logseq/logseq/pull/11306)
 		-
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading

From 7bac951e2a11d9e12a122417bccc3ac0fcd6a0c8 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:26:03 +0800
Subject: [PATCH 173/196] Auto saved by Logseq

---
 pages/Changelog.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index a5fdd6e..b7ec362 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -12,6 +12,10 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 			- Catalan translation [#11587](https://github.com/logseq/logseq/pull/11587)
 		- [xraysight](https://github.com/xraysight)
 			- PL translation update 100% [#11306](https://github.com/logseq/logseq/pull/11306)
+		- [queeup](https://github.com/queeup)
+			- update Turkish translation [#11098](https://github.com/logseq/logseq/pull/11098)
+		- [keonu05](https://github.com/keonu05)
+			- Update Korean translation [#11454](https://github.com/logseq/logseq/pull/11454)
 		-
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading

From 50687ffe4e015b0633fc70ed1f39dd5dc94ed5c1 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:26:33 +0800
Subject: [PATCH 174/196] chore: 0.10.10

---
 pages/Changelog.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index b7ec362..bfba907 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -16,7 +16,6 @@ Desktop app and Android App download link: <https://github.com/logseq/logseq/rel
 			- update Turkish translation [#11098](https://github.com/logseq/logseq/pull/11098)
 		- [keonu05](https://github.com/keonu05)
 			- Update Korean translation [#11454](https://github.com/logseq/logseq/pull/11454)
-		-
 	- [[Fixed issues]]
 		- fix: graph keep re-index when loading
 		- fix(sync): cannot delete some nested files

From 595a283bb844d29fb3eec1fa4eb4252919601fb5 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Wed, 7 May 2025 21:45:32 +0800
Subject: [PATCH 175/196] persist block id

---
 pages/Changelog.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index bfba907..683ae44 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,4 +1,5 @@
 ## Beta 0.10.10 [[May 7th, 2025]]
+id:: 681b5cd1-444a-46a8-8b6f-2dd5e6ece3fd
 Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>
 	- [[Thanks]]
 		- [chiefnoah](https://github.com/chiefnoah)

From 3f7319a555fe3383b42a5076e731900885838dcf Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 7 May 2025 15:50:19 -0400
Subject: [PATCH 176/196] fix: links to graph schemas

---
 db-version-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 8e56925..649bc69 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -92,7 +92,7 @@ Miscelleanous changes:
     * The `all-page-tags` and `sort-by` query filters no longer exists. Sorting is done via the table component.
 * [Advanced queries](https://docs.logseq.com/#/page/advanced%20queries)
   * Advanced queries are now edited in a code block which means queries are syntax highlighted.
-  * Some old advanced queries will no longer work and need to be rewritten. For engineers, see [this file](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) and compare `schema` with `schema-for-db-based-graph` to see what has changed.
+  * Some old advanced queries will no longer work and need to be rewritten. For engineers, compare the [db graph `schema`](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) vs the [file graph `schema`](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/file_based/schema.cljs).
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
   * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.
 * Since block timestamps are available, they display in table view where possible.

From 24538fd83c94b7750fc830cacd6cfb29587fda5d Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 12 May 2025 10:57:47 -0400
Subject: [PATCH 177/196] Add a TODO and remove stale one

---
 db-version-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 649bc69..ef89756 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -96,6 +96,7 @@ Miscelleanous changes:
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
   * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.
 * Since block timestamps are available, they display in table view where possible.
+* `{{function}}` used with queries is a TODO.
 
 #### Namespaces
 * Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`. Unlike before, the reference will turn into `[[baz]]` after it is created.
@@ -121,7 +122,6 @@ Miscelleanous changes:
     * `db.sqlite` - Stores all your graph's data including user configs.
     * `assets/` - Stores assets like before.
 * `logseq/` inside a directory no longer exists.
-* It's still a TODO to sync markdown files to these graph directories.
 
 ## File Graph Changes
 

From 57e0426110db19f557e7129d5f7f74524bee217c Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 21 May 2025 10:47:05 -0400
Subject: [PATCH 178/196] add changes for 0.10.11

---
 pages/Changelog.md | 14 +++++++++++---
 1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 683ae44..3aa8cff 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,6 +1,14 @@
-## Beta 0.10.10 [[May 7th, 2025]]
-id:: 681b5cd1-444a-46a8-8b6f-2dd5e6ece3fd
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>
+- ## Beta 0.10.11 [[May 21st, 2025]]
+	- Includes all changes from ((681b5cd1-444a-46a8-8b6f-2dd5e6ece3fd)) and fixes major regressions with it.
+	- [[Fixed Issues]]
+		- Images and themes not working [#11486](https://github.com/logseq/logseq/issues/11846)
+		- Global search in blocks not working [#11851](https://github.com/logseq/logseq/issues/11851)
+		- Drag and drop of pdfs not working [#11850](https://github.com/logseq/logseq/issues/11850)
+	- [[Enhancement]]
+		- Upgrade Electron to 36.2.0
+- ## Beta 0.10.10 [[May 7th, 2025]]
+  id:: 681b5cd1-444a-46a8-8b6f-2dd5e6ece3fd
+  Release removed: ~~Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.10>~~
 	- [[Thanks]]
 		- [chiefnoah](https://github.com/chiefnoah)
 			- Fix Twitter's rename breaking macro wrapping [#11325](https://github.com/logseq/logseq/pull/11325)

From 1301fc1a4f1ae88ad701517fc40399a7f2f74248 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 21 May 2025 11:17:06 -0400
Subject: [PATCH 179/196] add link and useful note for one bug

---
 pages/Changelog.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index 3aa8cff..b86abb3 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,8 +1,10 @@
 - ## Beta 0.10.11 [[May 21st, 2025]]
+Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.11>
 	- Includes all changes from ((681b5cd1-444a-46a8-8b6f-2dd5e6ece3fd)) and fixes major regressions with it.
 	- [[Fixed Issues]]
 		- Images and themes not working [#11486](https://github.com/logseq/logseq/issues/11846)
 		- Global search in blocks not working [#11851](https://github.com/logseq/logseq/issues/11851)
+			- **NOTE**: You may need to run the command `Rebuild search index` for this fix.
 		- Drag and drop of pdfs not working [#11850](https://github.com/logseq/logseq/issues/11850)
 	- [[Enhancement]]
 		- Upgrade Electron to 36.2.0

From 9074335f1f84cc9da78c3100870537768be95978 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 21 May 2025 14:35:51 -0400
Subject: [PATCH 180/196] add templates to todos

---
 db-version.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version.md b/db-version.md
index d855575..b457dd8 100644
--- a/db-version.md
+++ b/db-version.md
@@ -380,6 +380,7 @@ There are existing features that have a database equivalent that are still a TOD
   * Import advanced command blocks that begin with `#+BEGIN`
   * Query macros and related query filters that have changed
   * Page and block embeds
+  * Import templates
 
 ### Convert File Graph to DB graph
 

From cf0a9e3c1ae8f583dbe46b8732720387f6b0eee1 Mon Sep 17 00:00:00 2001
From: Tienson Qin <tiensonqin@gmail.com>
Date: Mon, 26 May 2025 16:46:34 +0800
Subject: [PATCH 181/196] chore: bump 0.10.12

---
 pages/Changelog.md | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/pages/Changelog.md b/pages/Changelog.md
index b86abb3..0a2375b 100644
--- a/pages/Changelog.md
+++ b/pages/Changelog.md
@@ -1,5 +1,12 @@
+- ## Beta 0.10.12 [[May 26th, 2025]]
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.12>
+	- [[Fixed issues]]
+		- App freeze, high CPU/GPU usage, and frequent diff prompts [#11880](https://github.com/logseq/logseq/issues/11880)
+		- High CPU consumption [#11874](https://github.com/logseq/logseq/issues/11874)
+		- Using GTK 2/3 and GTK 4 in the same process is not supported [#11873](https://github.com/logseq/logseq/issues/11873)
+		- App crashes on Mac
 - ## Beta 0.10.11 [[May 21st, 2025]]
-Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.11>
+  Desktop app and Android App download link: <https://github.com/logseq/logseq/releases/tag/0.10.11>
 	- Includes all changes from ((681b5cd1-444a-46a8-8b6f-2dd5e6ece3fd)) and fixes major regressions with it.
 	- [[Fixed Issues]]
 		- Images and themes not working [#11486](https://github.com/logseq/logseq/issues/11846)

From 1fb831689d1b95018eed75321d0e7e3aa57874f5 Mon Sep 17 00:00:00 2001
From: Ramayen <106333136+VimYoung@users.noreply.github.com>
Date: Thu, 29 May 2025 17:58:42 +0530
Subject: [PATCH 182/196] SimpleHTTPServer module was moved to be the module
 http.server. (#131)

* SimpleHTTPServer module was moved to be the module http.server.

* Version specific fix, python.
---
 pages/Publishing (Desktop App Only).md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/Publishing (Desktop App Only).md b/pages/Publishing (Desktop App Only).md
index 5783747..afd0e74 100644
--- a/pages/Publishing (Desktop App Only).md	
+++ b/pages/Publishing (Desktop App Only).md	
@@ -9,10 +9,10 @@ tags:: [[Publishing]]
 			- ![image.png](../assets/image_1638393320509_0.png)
 	- 2. Click the top-right three-dots and select `Export graph`. Then select a folder, and Logseq will export all the files needed for publishing there.
 		- ![](../assets/pages_Publishing_1615917396171_0.png)
-	- 3. The exported assets basically make up a web application, when runs Logseq with your public pages, in read-only mode. After exporting, if you are on Linux-like environment, you can `cd` into the export folder and run `python -m SimpleHTTPServer`. Voilà🎉, you can now visit the published graph at `localhost:8000` in your browser.
+	- 3. The exported assets basically make up a web application, when runs Logseq with your public pages, in read-only mode. After exporting, if you are on Linux-like environment, you can `cd` into the export folder and run `python -m SimpleHTTPServer` if you have python 2.x or run `python3 -m http.server` if your python version is 3.x . Voilà🎉, you can now visit the published graph at `localhost:8000` in your browser.
 	- 4. Of course publishing your beautiful graph on localhost only is not that fun. Since we have all the assets now, publish them on platforms like [Github Pages](https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site) and [Vercel](https://vercel.com/docs) is straightforward. Below is a video tutorial on how to publish Logseq pages to Github Pages.
 		- {{youtube https://www.youtube.com/watch?v=nf9MyWRratI}}
 	- Here're some links that might be useful:
 		- 1. [Creating a GitHub Pages site](https://docs.github.com/en/github/working-with-github-pages/creating-a-github-pages-site)
 		- 2. [Introduction to Vercel](https://vercel.com/docs)
-		- 3. [Another video publishing tutorial](https://www.youtube.com/watch?v=fHc2cVNMNrA)
\ No newline at end of file
+		- 3. [Another video publishing tutorial](https://www.youtube.com/watch?v=fHc2cVNMNrA)

From e6b3091d91975f65a7a73895c34927e1f9ee81d0 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 30 May 2025 08:32:13 -0400
Subject: [PATCH 183/196] ignore db-version docs

---
 logseq/config.edn | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/logseq/config.edn b/logseq/config.edn
index 949cc93..e3076cd 100644
--- a/logseq/config.edn
+++ b/logseq/config.edn
@@ -12,7 +12,7 @@
 
  ;; The app will ignore those directories or files.
  ;; E.g. "/archived" "/test.md"
- :hidden ["script" "README.md" "CONTRIBUTING.md" "LICENSE.md"]
+ :hidden ["script" "README.md" "CONTRIBUTING.md" "LICENSE.md" "db-version.md" "db-version-changes.md"]
 
  ;; When creating the new journal page, the app will use your template content here.
  ;; Example for Markdown users: "## [[Work]]\n###\n## [[Family]]\n###\n

From 37a8f67b8bd8707ac7eb6007cb8f838080a53b80 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Tue, 3 Jun 2025 10:06:03 -0400
Subject: [PATCH 184/196] db-version updates for the past month

---
 db-version-changes.md | 16 ++++++++++------
 db-version.md         | 15 ++++++++-------
 2 files changed, 18 insertions(+), 13 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index ef89756..b39f25d 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -38,11 +38,12 @@ High level changes:
 * Code blocks, quote blocks and math blocks [have tags](./db-version.md#more-new-tags). Since properties are not are a part of the block content, properties can more naturally be added to these blocks.
 * Pdf annotations [have a tag](./db-version.md#more-new-tags). This allows annotations to be viewed across pdfs and to have custom views of annotations while using the pdf viewer.
 * Markdown syntax for blocks e.g. a heading or quote is no longer visible or editable. Removing a block's heading is done by right-click on a block and choosing the crossed out H icon.
+* Slides have been removed as a feature and we can support it as 3rd party plugin.
 
 WIP changes:
+* RTC a.k.a. DB version sync will be enabled later.
+* Add back support for dynamic variables.
 * Whiteboards are disabled for now and will be enabled later.
-* Exports to more formats including markdown.
-* Sync and RTC will be enabled later.
 
 Miscelleanous changes:
 * Scripts using [nbb-logseq](https://github.com/logseq/nbb-logseq) can read and write graphs. Previously with file graphs, scripts could only read graphs.
@@ -51,8 +52,11 @@ Miscelleanous changes:
 * There is no re-index like in file graphs.
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
 * `All Pages` view can toggle between table and list view.
-* Run the command `Customize appearance` to display a modal of appearance related settings.
-* For developers, there is a `Validate current graph` command.
+* New commands:
+  * Run the command `Customize appearance` to display a modal of appearance related settings.
+  * Commands from [property shortcuts](./db-version#property-shortcuts).
+  * Commands from [edn data export](./db-version.md#edn-data-export).
+  * For developers, there are `Validate current graph` and `Garbage collect graph` commands.
 
 ### Changes by Feature
 
@@ -96,7 +100,6 @@ Miscelleanous changes:
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
   * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.
 * Since block timestamps are available, they display in table view where possible.
-* `{{function}}` used with queries is a TODO.
 
 #### Namespaces
 * Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`. Unlike before, the reference will turn into `[[baz]]` after it is created.
@@ -109,7 +112,8 @@ Miscelleanous changes:
 #### User Config
 
 * A graph's config.edn, custom.js and custom.css files are only editable within Logseq from `Settings`.
-* The following config.edn options are no longer used: `:block-hidden-properties, :favorites, :hidden, :ignored-page-references-keywords, :preferred-format, :preferred-workflow, :feature/enable-block-timestamps?, :file/name-format, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist`. See [this code](https://github.com/logseq/logseq/blob/043927031e11053a837d8289e3334368e6647bea/src/main/frontend/handler/common/config_edn.cljs#L89-L115) for more details.
+* The following config.edn options are no longer used by any graphs: `:ref/linked-references-collapsed-threshold`.
+* The following config.edn options are no longer used: `:block-hidden-properties, :default-templates, :favorites, :hidden, :ignored-page-references-keywords, :journals-directory, :pages-directory, :preferred-format, :preferred-workflow, :whiteboards-directory, :feature/enable-block-timestamps?, :file/name-format, :file-sync/ignore-files, :journal/file-name-format, :journal/page-title-format, :logbook/settings, :org-mode/insert-file-link?, :property/separated-by-commas, :property-pages/enabled?, :property-pages/excludelist, :srs/initial-interval, :srs/learning-fraction` in DB graphs. See [this code](https://github.com/logseq/logseq/blob/b0a255f96bfd512d5b87acca52c8d9f958c6a593/deps/common/src/logseq/common/config.cljs#L124-L157) for more details.
 
 #### Search
 * When search modal first opens, recently updated pages display at the top.
diff --git a/db-version.md b/db-version.md
index b457dd8..75f49d8 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of April 30th. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of June 3rd. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -90,7 +90,7 @@ NOTE: Most shortcuts have a corresponding search command. You can find the comma
 
 ### Configure a Property
 
-Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Press `Cmd` and click to navigate to a property page. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure property` button below its name.
+Properties are configurable wherever they are used by clicking on its name to display a dropdown menu. Press `Cmd` and click to navigate to a property page. Property icons are set by clicking on the property's default icon to the left of its name. Properties can also be configured by navigating to their page with [Search](https://docs.logseq.com/#/page/search) and then clicking on the `Configure` button that appears above when hovering over the name.
 
 Property fields in the dropdown menu:
 
@@ -147,7 +147,7 @@ To create your first new tag:
 
 For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all [tagged nodes](#tagged-node).
 
-A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right. To set these properties you must be on the tag's page, hover over the tag's name and click on `Set page property`.
+A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right. To set these properties go to the tag's page and click on the `Add property` link.
 
 ### Create Tags
 
@@ -174,8 +174,7 @@ A powerful feature of using a parent tag is that the new tag inherits the proper
 New tags are configurable from their page. Navigate to their page by using [Search](https://docs.logseq.com/#/page/search) or clicking on their `#` name links. On their page, hover over their name to see the rotating triangle icon to the left. Click on it to see the tag page's properties. Two important properties you'll see for configuring a tag:
 
 * `Parent`: Use this to allow the new tag to inherit its parent's tag properties. By default the parent tag is the `Root Tag` which doesn't have any properties.
-* `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
-  * To the right of each tag property there is an optional block for describing the property. This description also shows up on the property's page.
+* `Tag Properties`: These tag properties are inherited by every node that uses the new tag.
 
 ### Tagged Node
 
@@ -353,6 +352,7 @@ A table displays a group of nodes as rows and a node's properties as columns. A
   * Drag columns to sort their order.
   * Resize columns by dragging the resize handle at a column header's border.
 * Bulk actions: When rows in the table are selected, bulk actions appear in the table header. All the bulk actions [described above](#bulk-actions) are available except for the `Three dots menu`.
+* Keyboard shortcuts: Use arrow keys to navigate between cells. Press `Enter` to edit a cell and `Esc` to exit editing.
 
 ## DB Graph Importer
 
@@ -451,9 +451,10 @@ DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db
 
 On desktop, it is easy to modify an existing DB graph with a script and see the change in Logseq. To do so:
 
-1. Press Cmd-S to persist a graph to `~/logseq/graphs/GRAPH-NAME/db.sqlite`.
+1. Press `Cmd-S` to persist a graph to `~/logseq/graphs/GRAPH-NAME/db.sqlite`.
 2. Modify the db.sqlite with a nbb-logseq script.
 3. Update the app to use the modified db.sqlite by using the `Replace graph with its db.sqlite file` dev command.
 
 ## Additional Links
-* https://github.com/C0ntr0lledCha0s/logseq-template-graph - Example graph with useful properties and tags
\ No newline at end of file
+* https://discuss.logseq.com/t/introducing-newtags-with-examples/32310 - Helpful tutorial on new tags
+* https://github.com/C0ntr0lledCha0s/logseq-template-graph - Example graph with useful properties and tags. Import graph as EDN.
\ No newline at end of file

From 4f3fedf5f6b118f8a6fa5b6667ccf2063600fda1 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Fri, 6 Jun 2025 13:58:52 -0400
Subject: [PATCH 185/196] Add ux improvement with pdf annotations

---
 db-version-changes.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/db-version-changes.md b/db-version-changes.md
index b39f25d..659f83a 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -79,6 +79,7 @@ Miscelleanous changes:
 * Assets can have custom user properties.
 * Assets are blocks and thus can show their linked references when zoomed in on the asset block.
 * Assets are resized by hovering over them and then dragging the left-right arrows that are visible over the scrollbars.
+* Pdf annotations are visible under an asset block by default. Previously this view was in a separate page and required clicking in the pdf viewer.
 
 #### Queries
 

From c2e08309e4760c5cba35bf5120dfd1a1d31083f8 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 9 Jun 2025 09:28:05 -0400
Subject: [PATCH 186/196] Update docs based on 2 user questions

---
 db-version-changes.md | 1 +
 db-version.md         | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 659f83a..f329605 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -99,6 +99,7 @@ Miscelleanous changes:
   * Advanced queries are now edited in a code block which means queries are syntax highlighted.
   * Some old advanced queries will no longer work and need to be rewritten. For engineers, compare the [db graph `schema`](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) vs the [file graph `schema`](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/file_based/schema.cljs).
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
+  * The task related properties `:block/marker`, `:block/priority`, `:block/deadline` and `:block/scheduled` have been respectively renamed to `:logseq.property/status`, `:logseq.property/priority`, `:logseq.property/deadline` and `:logseq.property/scheduled`. These properties should be queried via rules like `property` e.g. `(property :logseq.property/deadline ...)`.
   * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.
 * Since block timestamps are available, they display in table view where possible.
 
diff --git a/db-version.md b/db-version.md
index 75f49d8..5cac71c 100644
--- a/db-version.md
+++ b/db-version.md
@@ -363,7 +363,7 @@ The DB Graph Importer converts a file graph to a DB graph. An overview of what i
   * `IN-PROGRESS` and `NOW` -> `Doing`
   * `WAIT` and `WAITING` -> `Backlog`
 * Tags are imported as follows:
-  * By default, all tags are imported as [new tags](#new-tags) using the `Import all tags` input. This allows you to use all your tags as you have previously, along with the new capabilities they have.
+  * By default, all tags are imported as [new tags](#new-tags) using the `Import all tags` input. This allows you to use all your tags as you have previously, along with the new functionality they have. Any properties associated with a tag are added to tags to take advantage of the new functionality.
   * Alternatively you can import only specific tags to [new tags](#new-tags) using the `Import specific tags` input. Tags that aren't specified in this input are then imported as follows:
     * All such tags become pages.
     * Tags in a block are converted to [page references](https://docs.logseq.com/#/page/term%2Fpage%20reference).

From faedc7dec04f3f0ca971cde7f132b2f7e752782f Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Mon, 23 Jun 2025 14:25:29 -0400
Subject: [PATCH 187/196] update instructions for adding page property and
 macro deprecation

---
 db-version-changes.md | 2 +-
 db-version.md         | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index f329605..f412f4d 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -109,7 +109,7 @@ Miscelleanous changes:
 * Pages can manage their namespace explicitly by using the `Parent` property. Previously managing a namespace could only be done by renaming a namespace. Using a property allows for easier management of namespace relationships.
 * The `Hierarchy` section is called `Children` for DB graphs. It now displays as a collapsible tree as this allows for viewing large namespaces more easily.
 * Children pages like `baz` above link back to its parent(namespace) with the `Parent` property.
-* The macro `{{namespace}}` is TODO.
+* The macro `{{namespace}}` is deprecated. Use the Library feature instead.
 
 #### User Config
 
diff --git a/db-version.md b/db-version.md
index 5cac71c..b6e4227 100644
--- a/db-version.md
+++ b/db-version.md
@@ -147,7 +147,7 @@ To create your first new tag:
 
 For example, say we created a new tag `Person` and added `lastName` and `birthday` tag properties to it. Now when `#Person` is added to a block or page, those two properties automatically display and are editable for them. A powerful thing about new tags is that when its tag properties change those changes immediately show up on all [tagged nodes](#tagged-node).
 
-A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right. To set these properties go to the tag's page and click on the `Add property` link.
+A new tag can have properties on its own page. By default the `Description` property is available for adding a description and `Hide from node` is available to hide the new tag on tagged nodes that float to the far right. To set these properties, go to the tag's page and with the focus on the title press the add property shortcut from [property shortcuts](#property-shortcuts) e.g. `Cmd-p`.
 
 ### Create Tags
 

From dd8fe3a5d09466f233296a000f8e00de0b9d0dd1 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 3 Jul 2025 16:02:25 -0400
Subject: [PATCH 188/196] Add changes for past month

Library, multi-parent tags, Library and namespaces, more importer
todos done
---
 db-version-changes.md |  7 +++----
 db-version.md         | 31 ++++++++++++++++++++++---------
 2 files changed, 25 insertions(+), 13 deletions(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index f412f4d..48961db 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -51,7 +51,7 @@ Miscelleanous changes:
 * Default date picker now has an input for typing a date in natural language.
 * There is no re-index like in file graphs.
 * For browsers, currently only one tab can be open. This is a limitation we hope to remove later.
-* `All Pages` view can toggle between table and list view.
+* `All Pages` screen is renamed to `Pages`. Also it can toggle between table and list view.
 * New commands:
   * Run the command `Customize appearance` to display a modal of appearance related settings.
   * Commands from [property shortcuts](./db-version#property-shortcuts).
@@ -105,10 +105,9 @@ Miscelleanous changes:
 
 #### Namespaces
 * Creating namespaces through `/` in `[[]]` should work as before e.g. `[[foo/bar/baz]]` creates the hierarchy of `foo` > `bar` > `baz`. Unlike before, the reference will turn into `[[baz]]` after it is created.
+* Pages can edit their namespace explicitly by going to the `Library` page and moving it under the desired parent namespace. Previously managing a namespace could only be done by renaming a namespace.
+* The `Hierarchy` section displays above a namespaced page's blocks. It displays as a collapsible tree as this allows for viewing large namespaces more easily.
 * Namespaced pages no longer have their namespace embedded in their page name. The big advantage of this is that renaming any part of the namespace does not affect all the pages under a namespace.
-* Pages can manage their namespace explicitly by using the `Parent` property. Previously managing a namespace could only be done by renaming a namespace. Using a property allows for easier management of namespace relationships.
-* The `Hierarchy` section is called `Children` for DB graphs. It now displays as a collapsible tree as this allows for viewing large namespaces more easily.
-* Children pages like `baz` above link back to its parent(namespace) with the `Parent` property.
 * The macro `{{namespace}}` is deprecated. Use the Library feature instead.
 
 #### User Config
diff --git a/db-version.md b/db-version.md
index b6e4227..fe13afc 100644
--- a/db-version.md
+++ b/db-version.md
@@ -1,6 +1,6 @@
 ## Description
 
-This page describes DB (database) graph functionality as of June 3rd. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
+This page describes DB (database) graph functionality as of July 3rd. See [here](https://test.logseq.com/#/) to try the latest stable version. If you're an existing user of Logseq, you'll be interested in [changes with the db version](./db-version-changes.md).
 
 NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we recommend only using DB graphs for testing purposes.
 
@@ -20,6 +20,7 @@ NOTE: While there is an [automated backup](#automated-backup) for DB graphs, we
 * [Bulk Actions](#bulk-actions)
 * [Views](#views)
   * [Tables](#tables)
+* [Library](#library)
 * [DB Graph Importer](#db-graph-importer)
 * [Automated Backup](#automated-backup)
 * [Export and Import](#export-and-import)
@@ -157,7 +158,7 @@ Ways to create tags:
 * In a block type `#NAME` and press `Cmd-Enter`. An inline tag is created.
 * Paste text in a block that includes `#NAME`. An inline tag is created for tag `NAME`.
 * Configure a `Node` property type to have a new tag config.
-* Configure a new tag to have a `Parent`, the new `Parent` value becomes a tag.
+* Configure a new tag to have an `Extends` property, the new `Extends` value becomes a tag.
 * In a block type `#NAME` and press `Esc`. An inline tag is created. Not recommended as it doesn't work for all use cases.
 * Convert any page to a tag by clicking on the three dots menu in the upper right corner and clicking `Convert to Tag`.
 
@@ -165,16 +166,24 @@ Any tag can be converted to a page by clicking on the three dots menu and clicki
 
 ### Parent Tags
 
-New tags can have a parent tag, defaulting to `Root Tag` when none is specified. Allowing new tags to be related to each other as a parent to child is useful as it allows tags to organized in a hierarchy. This is similar to directories on your computer. When a new tag is used as a parent, you can see the tag hierarchy under it by navigating to the tag's page and seeing a `Children` section.
+New tags can have multiple parent tags via the `Extends` property and default to the `Root Tag` as a parent.  Parent tags are powerful as the new tag inherits the properties from each of its parent tags. For example, say we have `#Book` with property `author` and `#MediaObject` with property `duration`. If we create a new `#Audiobook` with property `readBy` and give it parents of `#Book` and `#MediaObject`, any node tagged with `#Audiobook` would have 3 properties: `author`, `duration` and `readBy`.
 
-A powerful feature of using a parent tag is that the new tag inherits the properties from its parent. For example, if we created a new `#Actor`, made its parent `#Person` from above and gave it an additional `actedIn` property. `#Actor` would display 3 properties when used, with two coming from the parent: `lastName`, `birthday` and `actedIn`.
+Parent tags also provide a way of organizing tags in a tree hierarchy. Since a new tag can have multiple parents, it can appear multiple times in a hierarchy. For example, here's the tree hierarchy of the example in the previous paragraph:
+
+- Root Tag
+  - Book
+    - AudioBook
+  - MediaObject
+    - AudioBook
+
+On any new tag page that is a parent tag, you can see this hierarchy under the `Children` section.
 
 ### Configure a New Tag
 
 New tags are configurable from their page. Navigate to their page by using [Search](https://docs.logseq.com/#/page/search) or clicking on their `#` name links. On their page, hover over their name to see the rotating triangle icon to the left. Click on it to see the tag page's properties. Two important properties you'll see for configuring a tag:
 
-* `Parent`: Use this to allow the new tag to inherit its parent's tag properties. By default the parent tag is the `Root Tag` which doesn't have any properties.
-* `Tag Properties`: These tag properties are inherited by every node that uses the new tag.
+* `Extends`: Use this to allow the new tag to inherit properties from one or more parent tags. This defaults to the `Root Tag` which doesn't have any properties.
+* `Tag Properties`: These tag properties are inherited by every node that uses the new tag. Drag one above or below the other to sort them. These properties will then display sorted on the tagged node.
 
 ### Tagged Node
 
@@ -354,6 +363,12 @@ A table displays a group of nodes as rows and a node's properties as columns. A
 * Bulk actions: When rows in the table are selected, bulk actions appear in the table header. All the bulk actions [described above](#bulk-actions) are available except for the `Three dots menu`.
 * Keyboard shortcuts: Use arrow keys to navigate between cells. Press `Enter` to edit a cell and `Esc` to exit editing.
 
+## Library
+
+The Library is a built-in page that displays and edits namespaced pages as if they were blocks on a page. This is powerful as it allows us to use an outliner to build and organize a hierarchy of pages. This is useful for those who want to organize their pages as if they were under folders on a computer. Pages that have no common properties are a good fit for namespaces. Pages that have common properties are better organized with [new tags](#new-tags).
+
+Pages that you want to namespace can be added to the Library with the `Add existing pages to Library` button.
+
 ## DB Graph Importer
 
 The DB Graph Importer converts a file graph to a DB graph. An overview of what it does:
@@ -374,12 +389,10 @@ The DB Graph Importer converts a file graph to a DB graph. An overview of what i
 ### Importer Todos
 
 There are existing features that have a database equivalent that are still a TODO for the importer:
-  * Import assets as `#Asset` and pdf annotations as `#PDF Annotation`
+  * Import pdf annotations as `#PDF Annotation`
   * Import org mode files
   * Import text files e.g. *.txt or *.edn
-  * Import advanced command blocks that begin with `#+BEGIN`
   * Query macros and related query filters that have changed
-  * Page and block embeds
   * Import templates
 
 ### Convert File Graph to DB graph

From 7e07ff28dada0c1adee87be7b873dcc18bc683af Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 9 Jul 2025 16:11:08 -0400
Subject: [PATCH 189/196] Update branch on scripting links

---
 db-version.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/db-version.md b/db-version.md
index fe13afc..9079ae4 100644
--- a/db-version.md
+++ b/db-version.md
@@ -450,15 +450,15 @@ This feature is also available:
 * from any [view](#views) as a header action. For example, go to the `All pages` view and filter it to only export the viewable pages.
 * for multiple selected nodes with the `Copy / Export as` modal.
 
-For developers, this shareable EDN data can also be used in scripts to create or modify existing graphs. For example, a page's data could be passed to [this script](https://github.com/logseq/logseq/blob/feat/db/deps/db/script/create_graph.cljs) to create a new DB graph with that page.
+For developers, this shareable EDN data can also be used in scripts to create or modify existing graphs. For example, a page's data could be passed to [this script](https://github.com/logseq/logseq/blob/master/deps/db/script/create_graph.cljs) to create a new DB graph with that page.
 
 ## Scripting
 
 DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db. Scripts can both read and _write any_ data in a DB graph. To write your own script, you'll need a package.json and nbb.edn. Use [this example package.json](https://github.com/logseq/publish-spa/blob/feat/db/package.json) and [this example nbb.edn](https://github.com/logseq/publish-spa/blob/feat/db/nbb.edn). Some example scripts:
 
-* https://github.com/logseq/logseq/tree/feat/db/deps/db/script - Scripts to query, validate and create any graph
-* https://github.com/logseq/logseq/blob/feat/db/deps/outliner/script/transact.cljs - Script to transact (modify) nodes queried from the commandline
-* https://github.com/logseq/logseq/tree/feat/db/scripts/src/logseq/tasks/db_graph - More complex scripts to generate graphs with all property types or with schema.org's ontology. See [this readme](https://github.com/logseq/logseq/tree/feat/db/scripts#nbb-scripts) for using these.
+* https://github.com/logseq/logseq/tree/master/deps/db/script - Scripts to query, validate and create any graph
+* https://github.com/logseq/logseq/blob/master/deps/outliner/script/transact.cljs - Script to transact (modify) nodes queried from the commandline
+* https://github.com/logseq/logseq/tree/master/scripts/src/logseq/tasks/db_graph - More complex scripts to generate graphs with all property types or with schema.org's ontology. See [this readme](https://github.com/logseq/logseq/tree/master/scripts#nbb-scripts) for using these.
 
 ### Modify a DB Graph
 

From e591e1cfabab4fbb666600b751b3b014d9bd8367 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 16 Jul 2025 09:56:23 -0400
Subject: [PATCH 190/196] fix: tag on old page

---
 pages/changelog_06.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/changelog_06.md b/pages/changelog_06.md
index 05b2e3d..f2e1737 100644
--- a/pages/changelog_06.md
+++ b/pages/changelog_06.md
@@ -77,7 +77,7 @@
 		- Alt-dragging to create a block reference
 	- [[Enhancement]]
 		- Open the second level children by default for linked references
-			- A new option `:ref/default-open-blocks-level` was added to `config.edn` #settings, the default value is `2`
+			- A new option `:ref/default-open-blocks-level` was added to `config.edn` #Settings, the default value is `2`
 			  #+BEGIN_EXAMPLE
 			  The default level to be opened for the linked references.
 			  For example, if we have some example blocks like this:
@@ -763,4 +763,4 @@
 	- [[Thanks]]
 		- 1. [kanru](https://github.com/logseq/logseq/pull/1073) is adding encryption support for GitHub Repos.
 		- 2. [karlicoss](https://github.com/logseq/logseq/pull/1076) add filetags support for org mode and fixed some issues.
-		- 3. [kailes](https://github.com/logseq/logseq/pull/1074) found and fixed a tricky issue when upgrading to latest shadow-cljs.
\ No newline at end of file
+		- 3. [kailes](https://github.com/logseq/logseq/pull/1074) found and fixed a tricky issue when upgrading to latest shadow-cljs.

From e758fdfe474e465939458a9e8ce26ed4b6f74715 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 16 Jul 2025 09:59:07 -0400
Subject: [PATCH 191/196] fix: update branch links on changes doc

---
 db-version-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index 48961db..9ab9393 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -97,7 +97,7 @@ Miscelleanous changes:
     * The `all-page-tags` and `sort-by` query filters no longer exists. Sorting is done via the table component.
 * [Advanced queries](https://docs.logseq.com/#/page/advanced%20queries)
   * Advanced queries are now edited in a code block which means queries are syntax highlighted.
-  * Some old advanced queries will no longer work and need to be rewritten. For engineers, compare the [db graph `schema`](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/frontend/schema.cljs) vs the [file graph `schema`](https://github.com/logseq/logseq/blob/feat/db/deps/db/src/logseq/db/file_based/schema.cljs).
+  * Some old advanced queries will no longer work and need to be rewritten. For engineers, compare the [db graph `schema`](https://github.com/logseq/logseq/blob/master/deps/db/src/logseq/db/frontend/schema.cljs) vs the [file graph `schema`](https://github.com/logseq/logseq/blob/master/deps/db/src/logseq/db/file_based/schema.cljs).
   * The attribute `:block/content` was renamed to `:block/title`. If used in an advanced query including in config.edn's `:default-queries`, change it to use `:block/title` e.g. `[?b :block/content "content"]` -> `[?b :block/title "content"]`
   * The task related properties `:block/marker`, `:block/priority`, `:block/deadline` and `:block/scheduled` have been respectively renamed to `:logseq.property/status`, `:logseq.property/priority`, `:logseq.property/deadline` and `:logseq.property/scheduled`. These properties should be queried via rules like `property` e.g. `(property :logseq.property/deadline ...)`.
   * These advanced query options are deprecated: :title, :group-by-page? and :collapsed?.

From 3b502cd377b7b512a0235e09ba317f1680a1f3a7 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 16 Jul 2025 16:39:26 -0400
Subject: [PATCH 192/196] Update scripting docs now that nbb-logseq

has db-version docs
---
 db-version.md | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/db-version.md b/db-version.md
index 9079ae4..1ecff17 100644
--- a/db-version.md
+++ b/db-version.md
@@ -454,11 +454,7 @@ For developers, this shareable EDN data can also be used in scripts to create or
 
 ## Scripting
 
-DB graphs are scriptable using https://github.com/logseq/nbb-logseq/tree/feat/db. Scripts can both read and _write any_ data in a DB graph. To write your own script, you'll need a package.json and nbb.edn. Use [this example package.json](https://github.com/logseq/publish-spa/blob/feat/db/package.json) and [this example nbb.edn](https://github.com/logseq/publish-spa/blob/feat/db/nbb.edn). Some example scripts:
-
-* https://github.com/logseq/logseq/tree/master/deps/db/script - Scripts to query, validate and create any graph
-* https://github.com/logseq/logseq/blob/master/deps/outliner/script/transact.cljs - Script to transact (modify) nodes queried from the commandline
-* https://github.com/logseq/logseq/tree/master/scripts/src/logseq/tasks/db_graph - More complex scripts to generate graphs with all property types or with schema.org's ontology. See [this readme](https://github.com/logseq/logseq/tree/master/scripts#nbb-scripts) for using these.
+DB graphs are scriptable using https://github.com/logseq/nbb-logseq. Scripts can both read and _write any_ data in a DB graph. See https://github.com/logseq/nbb-logseq#database-version to get started.
 
 ### Modify a DB Graph
 

From 3c2e2cfa5fb31b489747bcb901043b750640b3c1 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 16 Jul 2025 16:45:22 -0400
Subject: [PATCH 193/196] fix: graph-validator validation fails with latest
 logseq

---
 .graph-validator/schema.cljs | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.graph-validator/schema.cljs b/.graph-validator/schema.cljs
index ed0f8c1..ed0a5b5 100644
--- a/.graph-validator/schema.cljs
+++ b/.graph-validator/schema.cljs
@@ -2,7 +2,7 @@
   "Enforce schema constraints on page types"
   (:require [clojure.test :refer [deftest is]]
             [logseq.graph-validator.state :as state]
-            [logseq.db.rules :as rules]
+            [logseq.db.file-based.rules :as file-rules]
             [datascript.core :as d]))
 
 (defn- get-property-names-for-type [type']
@@ -11,7 +11,7 @@
               :where (page-property ?b :type ?type)]
             @state/db-conn
             type'
-            (vals rules/query-dsl-rules))
+            [(:page-property file-rules/query-dsl-rules)])
        (map (comp :block/properties first))
        (mapcat keys)
        set
@@ -24,7 +24,7 @@
               :where (page-property ?b :type ?type)]
             @state/db-conn
             type'
-            (vals rules/query-dsl-rules))
+            [(:page-property file-rules/query-dsl-rules)])
        (map (comp :block/properties first))))
 
 (deftest feature-schema

From f7961112b71c0699dc3147e70fa6bf2a915de745 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Thu, 24 Jul 2025 09:06:16 -0400
Subject: [PATCH 194/196] Start API section

---
 db-version-changes.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/db-version-changes.md b/db-version-changes.md
index 9ab9393..b47d871 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -128,6 +128,11 @@ Miscelleanous changes:
     * `assets/` - Stores assets like before.
 * `logseq/` inside a directory no longer exists.
 
+#### API
+* `logseq.db.*` methods like `logseq.db.q` are renamed to `logseq.app.q`
+* All property related calls like `upsertBlockProperty` work with DB graphs. Property values can now be numbers and booleans. Properties are namespaced to `:plugin.property._api`
+* See [this test file](https://github.com/logseq/logseq/blob/master/clj-e2e/test/logseq/e2e/plugins_basic_test.clj) for using the api with DB graphs.
+
 ## File Graph Changes
 
 * File graphs are no longer supported in browser.

From dea7cc77b7b38018ba5a6b83b4cbb7c76cfeb12c Mon Sep 17 00:00:00 2001
From: Charlie <xyhp915@qq.com>
Date: Fri, 25 Jul 2025 17:05:15 +0800
Subject: [PATCH 195/196] Update db-version-changes.md

---
 db-version-changes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index b47d871..f7a4012 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -129,7 +129,7 @@ Miscelleanous changes:
 * `logseq/` inside a directory no longer exists.
 
 #### API
-* `logseq.db.*` methods like `logseq.db.q` are renamed to `logseq.app.q`
+* ~~`logseq.db.*` methods like `logseq.db.q` are renamed to `logseq.app.q`~~
 * All property related calls like `upsertBlockProperty` work with DB graphs. Property values can now be numbers and booleans. Properties are namespaced to `:plugin.property._api`
 * See [this test file](https://github.com/logseq/logseq/blob/master/clj-e2e/test/logseq/e2e/plugins_basic_test.clj) for using the api with DB graphs.
 

From 6b091c8c32d29a80a6a6688199e84381e5d5ae04 Mon Sep 17 00:00:00 2001
From: Gabriel Horner <gabriel@logseq.com>
Date: Wed, 30 Jul 2025 14:54:55 -0400
Subject: [PATCH 196/196] fix: remove outdated change

---
 db-version-changes.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/db-version-changes.md b/db-version-changes.md
index f7a4012..ec9acea 100644
--- a/db-version-changes.md
+++ b/db-version-changes.md
@@ -129,7 +129,6 @@ Miscelleanous changes:
 * `logseq/` inside a directory no longer exists.
 
 #### API
-* ~~`logseq.db.*` methods like `logseq.db.q` are renamed to `logseq.app.q`~~
 * All property related calls like `upsertBlockProperty` work with DB graphs. Property values can now be numbers and booleans. Properties are namespaced to `:plugin.property._api`
 * See [this test file](https://github.com/logseq/logseq/blob/master/clj-e2e/test/logseq/e2e/plugins_basic_test.clj) for using the api with DB graphs.
 
