joplin-plugin-collapsible-blocks 1.1.0 → 1.2.0

package/README.md

@@ -4,9 +4,9 @@ This Joplin plugin allows you to create collapsible blocks with a title and exte
 
 Although the blocks this plugin creates are only collapsible in the webview, not the editor, it seems to pair well with the "Extra Markdown Editor Settings" plugin, which does allow for collapsing text in the editor, if "Enable code folding" is enabled in its settings. The collapsible blocks made by this plugin are detected by it as code, and are editor-foldable. If you're nesting collapsible blocks, only the outermost one (in the editor) will be foldable with this method. 
 
-**Version**: 1.1.0
+**Version**: 1.2.0
 
-## Installation
+### Installation
 
 - Open Joplin and navigate to `Preferences > Plugins`
 - Search for `Collapsible blocks` and click install
@@ -30,13 +30,13 @@ In order to create a collapsible block, you can:
 
 ```
 :{Block title
-    Block body here
-    And here
-    And here...
+Block body here
+And here
+And here...
 }:
 ```
 
-Nothing but whitespace may come before the `:{`. The title of the block must always appear on the same line as the `:{`. A title may be omitted. You can choose to put the `}:` on the same line as the last line of body text, or on its own line, but nothing is allowed to come after the `}:`. Indenting the body text is optional but recommended. In general, this plugin is designed to be extremely forgiving with how things are formatted and indented. The following examples (and more!) are all valid: 
+Nothing but whitespace may come before the `:{`. The title of the block must always appear on the same line as the `:{`. A title may be omitted. You can choose to put the `}:` on the same line as the last line of body text, or on its own line, but nothing is allowed to come after the `}:`. In general, this plugin is designed to be extremely forgiving with how things are formatted and indented. The following examples (and more!) are all valid: 
 
 **Examples**:
 ```
@@ -64,24 +64,19 @@ Body
 :{Title
 Body}:
 
-:{Title
-    Body}:
-
 :{Title
 Body
 }:
-
-:{Title
-    Body
-}:
 ```
 (for readability, the last way is recommended)
 
+The text in the editor will use CSS to automatically indent blocks, based on how deeply nested the blocks are. This can be disabled or configured in the settings. 
+
 Blocks will remember if you left them opened or closed. They will do so by editing the opener in the editor from `:{` to `:{:{` when opened, or back to `:{` when closed. You may also do this manually. 
 
 If you don't want it to remember if you left a block opened or closed, you can turn this off globally in the plugin settings - or on a per-block basis by doubling the end token, from `}:` to `}:}:`. When you do this, you can still open and close the block in the webview, but they will not save their state in the editor - so the next time the note is loaded, they will be opened or closed again, depending on whether their opening token is `:{:{` or `:{`, respectively. So a block like `:{:{this}:}:` will always be initially open when you open a note, while a block like `:{this}:}:` will always be initially closed when you open a note. 
 
-When nesting blocks within blocks, they will be color-coded in the editor, and may also be color-coded in the webview. These can both be controlled in the plugin Settings tab. 
+When nesting blocks within blocks, they will be color-coded in the editor, and may also be color-coded in the webview. These can both be controlled (enabled or disabled) in the plugin Settings tab. 
 
 ## Screenshots
 
@@ -101,7 +96,18 @@ With a fourth one added, for three nesting levels, and webview colors enabled
 
 ![](screenshots/4.png)
 
-## Custom styles
+## Settings
+There is a settings page for the plugin in the Joplin options. There, you can:
+* Customize the start and end tokens away from the default `:{` and `}:`
+* Enable or disable the color coding in the webview and editor
+* Globally disable the plugin's ability to remember if a collapsible block's opened/closed status was changed in the webview
+* Disable automatic CSS indentation of collapsible block text in the editor, or configure it to indent more or less
+
+![](screenshots/settings.png)
+
+## Advanced
+
+### Custom styles
 
 If you would like to style the collapsible blocks to your preference, use the following in your `userstyle.css` file, which can be accessed in `Joplin` → `Options` → `Appearance` → `Show Advanced Settings` → `Custom stylesheet for rendered Markdown`:
 
@@ -130,8 +136,10 @@ be applied if "Do Webview Colors" is enabled in the plugin settings */
 }
 ```
 
-## Settings
-There is a settings page for the plugin in the Joplin options. There, you can customize the start and end tokens away from the default `:{` and `}:`, or enable/disable the color coding in the webview and editor. You can also disable the plugin's ability to remember if a collapsible block was last left open or closed in the webview, relying solely on how you define it in the editor. 
+## Troubleshooting
+If the collapsible block is not showing up, or is showing up but you're unable to toggle it opened or closed, then you're likely accidentally in the Rich Text Editor, instead of the Markdown Editor. Joplin's Rich Text Editor does [not support most Markdown plugins](https://joplinapp.org/help/apps/rich_text_editor/#limitations). To enter the Markdown editor, look for the controls in the image below, in the upper right of Joplin. Make sure the Markdown/Rich Text toggle is on the left (red) side, and then use the blue button to swap between the editor and webview. 
+
+![](screenshots/troubleshooting.png)
 
 ## Notes
 
@@ -139,7 +147,7 @@ There is a settings page for the plugin in the Joplin options. There, you can cu
 
 ## Acknowledgement
 
-Thanks to the creator of the [Joplin Spoilers](https://github.com/martinkorelic/joplin-plugin-spoilers) plugin, whose code helped me build this plugin. 
+Thanks to the creator of the [Joplin Spoilers](https://github.com/martinkorelic/joplin-plugin-spoilers) plugin, whose code helped me build this plugin. Our code bases and methodologies are wildly different at this point, but it got me started with Joplin plugins. 
 
 ## Other plugins
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "joplin-plugin-collapsible-blocks",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "scripts": {
     "dist": "webpack --env joplin-plugin-config=buildMain && webpack --env joplin-plugin-config=buildExtraScripts && webpack --env joplin-plugin-config=createArchive",
     "prepare": "npm run dist",

package/publish/joplin.plugin.collapsible.blocks.json

@@ -2,7 +2,7 @@
 	"manifest_version": 1,
 	"id": "joplin.plugin.collapsible.blocks",
 	"app_min_version": "3.2",
-	"version": "1.1.0",
+	"version": "1.2.0",
 	"name": "Collapsible blocks",
 	"description": "Create collapsible blocks with title and extendable body.",
 	"author": "ntczkjfg",
@@ -24,6 +24,6 @@
 		"desktop",
 		"mobile"
 	],
-	"_publish_hash": "sha256:ac51faca341b542b7e392e1836100d4782fc7da6679287b92d61deebfd0a6209",
-	"_publish_commit": "master:3e839324698256c44f70f6c574f6af2d26787183"
+	"_publish_hash": "sha256:0e7d4b4c8b04bc49754d57b56ebfa92974de7e0463ea97d8bbdb430f7b4fc1c7",
+	"_publish_commit": "master:84d8c3ea55950bed78ea3307eff89fb3ea397eb0"
 }