I’m building a web front end that supports editing, but I still think there is a use case for read-only.
Sometimes you want to only update your todo lists at the end of the day. In my case, I have a list of places I want to travel during the day. Things don’t go 100% as planned. You go places you didn’t intend, or you didn’t get a chance to do it all because you wanted to spend more time at one place. I prefer managing my todos when I’m back at accommodations, instead of being distracted from enjoying the present, even if that’s during transit.
Not at all! My blog (two-wrongs.org) is published from Org source files. I have previously published documentation from Org sources too, with no expectation that the viewers should edit.
Comments
Most use cases for org files would involve being able to edit them from within the web interface as well.
I’m building a web front end that supports editing, but I still think there is a use case for read-only.
Sometimes you want to only update your todo lists at the end of the day. In my case, I have a list of places I want to travel during the day. Things don’t go 100% as planned. You go places you didn’t intend, or you didn’t get a chance to do it all because you wanted to spend more time at one place. I prefer managing my todos when I’m back at accommodations, instead of being distracted from enjoying the present, even if that’s during transit.
Not at all! My blog (two-wrongs.org) is published from Org source files. I have previously published documentation from Org sources too, with no expectation that the viewers should edit.
two-wrongs.org and www.two-wrongs.org get me a DNS lookup failure.
https://two-wrongs.com/