Explored using Markdown bullet list marker * or +

You can't use - for bullet list marke in Logseq block. It's already used by Logseq for outline hierarchy.

Explored using Markdown ordered list marker 1.

It's a digit, fullstop & space. The ending space is necessary. Ref GFM Ex 239.

Logseq Markdown doesn't interpret 1) , even though GFM says you can use that as ordered list marker.

First block in titled post

Second block in titled post

• A markdown sub in second block

• Another markdown sub in second block

  • A sub-sub

  • Another sub-sub

• Yet another markdown sub in second block

Third block in titled post

1. A markdown sub in second block

2. Another markdown sub in second block

3. Yet another markdown sub in second block

Configure Logseq for easier interop with Drummer

Change in Customize Keyboard Shortculs:

HTML to ctrl-k (instead of ctrl-l)

Full text search to alt-ctrl-k (instead of ctrl-k)

Change in Settings, Editor:

Show brackets = false

Logical outdenting = true

Use switch graph icon (2nd line top left) to switch between main graph and blog graph.

Configure Drummer for easier interop with Logseq

Use Chrome Profile feature to get two separate windows profiles, one with Drummer login to main drummer blog and another to logseq interop blog.

Clean up and update yesterday's Jan 14th, 2022 blog post with more information.

First block in titled post

Second block in titled post

A sub in second block

Another sub in second block

Yet another sub in second block

Third block in titled post

Done my feedback today on myLogseqBlog Issue 1. Update: Dave has responded.

Screenshots collage of Logseq's journal page that's transformed to Drummer blog post. Using img tag here.

I note the following are good places to see development and testing progress of myLogseqBlog:

myLogseqBlog's GitHub repo

mylogseqblog's My Outline Blog

Dave's Drummer Change Notes Blog

Dave's Scripting News Blog

Also good to look at Old School blogs using myLogseqBlog function.

Andrew's Logseq Blog via Dave

Ramses' Notes via Dave

Scott's Outline Blog via myLogseqBlog

I created KLTransitLogseq new Logseq graph. Ready with a fresh new journals folder to integrate with Dave's new myLogseqBlog project.

Then I followed the steps in myLogseqBlog README.md.

(1) Downloaded myLogseqBlog-main.zip

(2) Unzipped it into a folder .\Drummer\myLogseqBlog-main

(3) From that folder, tried to do npm install but not recognized by windows cmd shell. I didn't have NPM installed on my Windows. Downloaded/installed https://nodejs.org/dist/v16.13.2/node-v16.13.2-x64.msi from nodejs.org. Then npm install installed mylogseqblog v0.4.0.

(4) Configured config.json with KL Transit blog settings. Use of jsonlint.com is important for valid JSON file as Dave advised. In particular, I had to make sure to use \\ instead of \ in the "logSeqJournalFolder" path, and just "8" without "+" sign in "blogTimeZoneOffset". The following are extracts from my sanitised working config.json file.

"twScreenName": "KLTransit",

"logSeqJournalFolder": "d:\\Data\\Dropbox\\KLTransitLogseq\\journals\\",

"blogTitle": "KLTransit Outline Blog",

"blogDescription": "Journalling KLTransit from Logseq publishing to Drummer Old School",

"blogWhenCreated": "Wed, 14 Jan 2022 00:20:00 GMT",

"blogTimeZoneOffset": 8,

"blogCopyright": "Copyright 2022, S M Sabri Ismail", 

(5) I published the Logseq journal page by using the command node mylogseqblog.js from .\Drummer\myLogseqBlog-main in Windows cmd shell.

PS: On Jan 15th, 2022, I edited/cleaned up the above, for reference its Logseq Markdown file here.