Home

Awesome

Sponsor this project on Github or get me a coffee if you like this plugin!

Overview

This plugin was created as I had some unique workflows that Logseq templates were not able to support. It allows the creation of 3 types of "PowerBlocks":

  1. Sticky button templates (buttons that remain on the page)
  2. Button templates
  3. Normal templates

Button templates allow the adding of templates using a button, while normal templates work like regular templates. A list of supported syntaxes can be found below.

Instructions

Creating the PowerBlocks

  1. From anywhere in Logseq, create a block like the below. #powerblocks, #powerblocks-stickybutton and #powerblocks-button cannot be changed.
### To create a sticky button template

- Buy milk #powerblocks-stickybutton
  - Today is <%DATE:5 days later%>

### To create a button template

- Buy milk #powerblocks-button
  - Today is <%DATE:5 days later%>

### To create a normal template

- testing #powerblocks
  - Today is <%DATE:5 days later%>
  1. The syntaxes currently available can be found in the next section.

Using the PowerBlocks

  1. Trigger the PowerBlocks menu by typing /Insert PowerBlock
  2. Select either a button/sticky button template (⏺ ) or a normal template (📃) that you have created.
  3. Button templates can be used within a Logseq template if you prefer..

Syntaxes (General)

Below is the list of available syntaxes. I may consider adding to the list, but as I am not sure how useful anyone will find this plugin, it is likely only syntaxes I use will be added.

Syntaxes (CONDITIONAL)

Below is the list of syntaxes that rely on conditions specified. Blocks with the conditions will only appear if it matches the parameters.

AND / OR Conditions

You can use AND OR conditions with the above conditional syntaxes. Below are some examples on how you can use it.

Credits

Big shoutout to David Vargas and the work he has done for Roam's Smart Blocks. Also thanks to R.J. Nestor for his sharing on how he used Smart Blocks and for inspiring me to do the same in Logseq.

Once again, chrono-node for supplying the date parser.