Verb docs in Markdown

[scripting]

Here's the change notes page.

And the new DocServer site on GitHub.

I wanted to see a list of all the Drummer verbs in a single list, and have man-pages in Markdown for all the verbs, so I wrote a Node app that generates the Markdown text from the outlines I use to edit the docs.

So now in addition to a colorful web app, there also is a boring but useful GitHub repo with the verb docs.

This is a good place to post comments or questions if you have them :smile:

[akaKenSmith]

Dave, the DocServer display is so readable and handy for a series of pages grouped by topic—very nice to see.

It made me think: pages grouped by topic is obviously what a book chapter is. It occurred to me that DocServer would be a very readable way to read an early or late draft of an opml-based book manuscript, to get the feel of the pages/blog posts that go into the draft. A writer could page right through the draft, just like reading the finished book.

I’m assuming that the verb list is an outline and that the drop-down menu shows the next level of that outline. If that’s true, then the verb outline might just as well be a chapter outline. The next level would be tentative chapter names. Then the further next level would be the pages/blog posts tentatively gathered for the chapters. I made this screen capture:

[akaKenSmith]

A further thought about the image I just posted: The "Tentative chapter titles" could end up in an early book draft just being search words in Daytona, entered by hand into the DocServer book manuscript outline. And the "Tentative blog posts in the chapter" could be the results of the Daytona search entered by hand into the DocServer book manuscript outline.

But possibly there is a way to automate that process, in effect bridging in some automated fashion between Daytona and DocServer?

[scripting]

Ken here's a post I wrote about this in September.

http://scripting.com/drummer/blog/2021/09/28/162837.html?title=yourOwnDocserver

One thing on my list of Daytona projects is to have it return query results in OPML, and that would just plug into DocServer, which eats OPML to churn out the docs, as you guessed.

I might have actually done it, not sure -- but I'm especially exhausted today. Time for a nap! :boom:

[akaKenSmith]

Dave, your September 28 post inspired me to create this quick test of concept outline for DocServer a few days later. It shows the visual concept, anyway--nothing more.

keyWords

[scripting]

Hah!

https://m.youtube.com/watch?v=I_e-RQZVwxg

[akaKenSmith]

I'm just brainstorming here. The two-column verb display template is really nice and serves its purpose very well. I had imagined working on a simpler DocServer template for posting one-column paragraph-style documents. Here's the question:

Maybe that same single template could serve both purposes if there was a script added that checked to see if the source outline had just the one layer, and if so render the left column as blank and post the one layer in the center-right column? I'm guessing that it would be very nice to support only one display template. (If that's the right word.)

This may be analogous to Drummer/Old School knowing, as they do, whether to post something as a title with paragraphs below or as a title-less paragraph.

[scripting]

@akaKenSmith -- it's worth considering if people use DocServer as a publishing platform beyond what we are doing with it now. I tend to invest where the users are, or at least I try to go by that rule. ;-)

[akaKenSmith]

I tinkered with the outline I tested for DocServer in September. Now it's almost completely functional in the way I was imagining in my earlier posts in this thread, so that's cool. View in DocServer here.

[scripting]

Put dots in your titles to have them show up properly in the nav links.

Like this: Reduced.Circumstances.

[akaKenSmith]

The dots make sense. For 20 years of radio essays, it's a lot of dots, but it makes sense.