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.
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.