And at least a couple of people were able to install the software and build a blog.
I made a mistake in the instructions, I didn't tell the user how to install Node. I just told them to run npm install as if everyone has it installed. One of our best users got stuck there.
I also need to help people debug incorrect JSON. The parser is not error-tolerant (which is good). I must include a pointer to jsonlint.com to give them a way to find out what their errors are.
If there is an error in config.json the app should exit, not proceed. There's no way anything good can come from going ahead at that point.
If someone leaves a trailing slash off a path that should not be the end of things. That's an "error" I can correct for them.
The Markdown functionality was a big win. I am using Drummer to edit this file, and it's mirrored in the LogSeq app, and using Markdown makes it look really nice over there. I now see why LS users expected Markdown support.
We need to get Windows and Linux E/D working asap.
It's a bootstrap, so the first rendition is going to be a nightmare for non-technical users. It has to be that way or else we wouldn't know what to do on the second step.
This functionality must be baked into Electric Drummer. It would be nice if it were baked into LogSeq as well. The code is MIT licensed so there is absolutely nothing standing in the way of it. They wouldn't be hard-coding something that only works with Drummer. The API is something that would be easily replicated by other CMSes. Along the way they would of course have to support OPML, which imho is a good thing.
And at least a couple of people were able to install the software and build a blog.
I made a mistake in the instructions, I didn't tell the user how to install Node. I just told them to run npm install as if everyone has it installed. One of our best users got stuck there.
I also need to help people debug incorrect JSON. The parser is not error-tolerant (which is good). I must include a pointer to jsonlint.com to give them a way to find out what their errors are.
If there is an error in config.json the app should exit, not proceed. There's no way anything good can come from going ahead at that point.
If someone leaves a trailing slash off a path that should not be the end of things. That's an "error" I can correct for them.
The Markdown functionality was a big win. I am using Drummer to edit this file, and it's mirrored in the LogSeq app, and using Markdown makes it look really nice over there. I now see why LS users expected Markdown support.
We need to get Windows and Linux E/D working asap.
It's a bootstrap, so the first rendition is going to be a nightmare for non-technical users. It has to be that way or else we wouldn't know what to do on the second step.
This functionality must be baked into Electric Drummer. It would be nice if it were baked into LogSeq as well. The code is MIT licensed so there is absolutely nothing standing in the way of it. They wouldn't be hard-coding something that only works with Drummer. The API is something that would be easily replicated by other CMSes. Along the way they would of course have to support OPML, which imho is a good thing.