scroll

> Maybe youre looking for a way to graph those nodes and relations? This is one thing I was thinking about, eventually. For now I'm just thinking about sort of a collection of writing prompts to help me think more clearly. > its definitely something i'd contribute to Cool! The eventual destination would probably be this folder: https://github.com/publicdomaincompany/scroll/tree/main/gram... For example, right now there is a "question" node. Often when writing I find it a good prompt to just start writing a bunch of questions on the journey to fleshing out an issue.

I found out that the author of this article wrote it using a markup language called (confusingly) Scroll: https://scroll.pub/. I'm not sure I want to bother learning another markup language when there are many extensions to Markdown already, but this author apparently favors the multi-column layout. I find scrolling all the way to the bottom of a thin column to get old fast, however, especially when the article is longer than can fit into a single page. It's pretty easy to constrain the height of the article text div element to be slightly less than screen height (using `height: 100vh`, or maybe slightly smaller if you have a header), which makes the columns fit vertically within the screen but causes more columns to appear off-screen to the right. However, you can override PageUp and PageDown to scroll left and right instead: https://git

Reading a single article is pretty bad on desktop, right? Here's the source for that article in the interim: https://github.com/breck7/breckyunits.com/blob/main/insist-o... I haven't yet gotten the time to improve the desktop experience but there are a few issues tracking it: https://github.com/publicdomaincompany/scroll/issues Sorry about that! Hope we get it fixed soon.

This is great! The whole "Git is eating the database world" trend is picking up steam. MDN/Yari, mentioned recently on here was another similar one https://github.com/mdn/yari I am planning on doing something similar to Offbase with Dub (https://github.com/treenotation/dumbdown/tree/master/dub). Each post will be written in Dumbdown, but then also a whole "blog" (posts, settings, pages, etc), you will be able to view/edit in a single textarea, and copy/paste the whole thing. So you should be able to write a whole site in the client side JS app, use local storage for persistence, and then copy/paste either the raw Tree Notation files to import/export the site, or just the compiled HTML. Then just need a one click "write this site to a Git repo", and then GitHub/GitLab/etc can handle long term persistence, version control, and site hosting.

Thanks for the feedback! Dumbdown is designed with future editors in mind that would always have autocomplete. Added that to the FAQ. https://github.com/treenotation/dumbdown/blob/master/README....

Thanks for the feedback! Dumbdown is designed with future editors in mind. I've added an FAQ to try and explain that a bit. https://github.com/treenotation/dumbdown/blob/master/README....

Yes. This is how my original prototype worked. I changed it to just target HTML directly. I forget why. Probably because it was just a prototype and I wanted to make it simpler. But super easy to have markdown as a target as well. Edit: Added this answer to the FAQ https://github.com/treenotation/dumbdown/blob/master/README....

Just started an FAQ with a more in-depth answer to the inline question: https://github.com/treenotation/dumbdown/blob/master/README....

Thanks for the feedback! Questions regarding inline have come up a lot. Just started an FAQ with a more in-depth answer to the inline question: https://github.com/treenotation/dumbdown/blob/master/README....

The very first issue "Make GitHub support readme.dumbdown" gave me a good chuckle. One man can dream, right? [0] https://github.com/treenotation/dumbdown/issues/1