Command Line to Export Pages and Data

[xaq_asdqwe]

Hi and thanks for the link to the GH Action.

Is there a roadmap maybe like Dynalist has on Trello, where people can vote on features?

Here are a couple of ideas/suggestions I had from a past post:

New and love Logseq.. have a couple of questions

I have been wanting something like Logseq for a long while… I was just about to start working on a open source repo of a Workflowy clone to add functionality after trying to get org-info.js to work. I’m using Dynalist right now, but it has a couple shortcomings and no way to extend functionality. I want to use a collapsible outliner for my main webpage and knowledge base system. I have this working now with Logseq and am using the git-auto script and a Netlify auto-deploy. A couple things I wou…

Re: command line, the two other replies had some great comments on why to use a more Unix like design philosophy. In short, interoperability is king, especially for utilities. You want Logseq to be able to be called by whatever means a user could dream of, and the most simple is from the command line. Well, APIs if it is webbased, but APIs are basically CLI commands over the web.

Cross-platform electron apps can still use CLI: Implementing CLI for Electron apps | Binary Studio These days Golang is becoming the most popular cross-platform basis and it is very CLI friendly. Also, since so many users will turn their notes into blogs and websites, and Linux is the backbone of 80% of servers in the world, the CLI is the first place to make this process more usable.