frankel, 5 months ago to random

Using #AsciiDoc to write my two books

https://www.yieldcode.blog/post/asciidoc-for-book-writing/

I, for one, am also a happy AsciiDoc and #asciidoctor user

oblomov, 5 months ago (edited 5 months ago) to markdown

For historical reasons, I mostly use #Markdown for my writing, although I've started to use #AsciiDoc (through #AsciiDoctor) more and more these days.

One of the things I #amWriting is intended to be in a more “playwright” style, so I've been looking around for stuff more focused on #playwriting (for either theater or screen, I'm not picky at the moment.).

So I came across #FountainIO
https://fountain.io/ which is actually … pretty close to what I was thinking about.

schalken, 7 months ago to random

Pro-tip to anyone who has to write a document: give #AsciiDoc / #AsciiDoctor a try.

Writing a course syllabus with the AsciiDoc markup language, I get these benefits:

• Can write one sentence per line, which helps me with structure and clarity.

• Trivial to indicate what is a heading and what is body text, which is critical for accessibility and for...

• Automatic table of contents and section numbering

• Easy to do basic formatting like italics, but also more complex stuff, like links to specific sections.

• Works well with version control / diffing software.

• Comments

• Can tell what's going on at a glance (e.g., you can tell where hyperlinked text goes just by looking at it)

Using AsciiDoc requires a little more up-front learning than just using Word or whatever, but it's so much simpler in the long run.

Markdown would probably also work, but I think AsciiDoc is the sweet spot between features and simplicity.

giuseppebilotta, 8 months ago to random

For anyone who might be interested, I've just tagged v1.0 (and v1.1 ahem) of my #AsciiDoc #LiterateProgramming tool
https://github.com/Oblomov/asciidoctor-litprog

This is an #AsciiDoctor extension that tangles & weaves your source code & documentation with a single pass from an .adoc document.

It's self-hosted: the README is the module source.

(Obviously, a bootstrap version of the module is included to be able to build the actual module.)

#LitProg

tbroyer, 1 year ago to webdev

So, what do people use nowadays to make slideshows from Markdown, Asciidoc, or HTML that can ideally render to PDF in addition to HTML?
(if it doesn't do PDF, don't hesitate to suggest anyway!)

#slides #presentation #html #markdown #asciidoc #asciidoctor

ljoonika, 1 year ago to random

I was today years old when I learned that markdown languages and other things meant to mean one thing in multiple ways are now under a single codified umbrella called markdown.

Like, it's a new fucking language to learn. But also, I know HTML, CSS, and BBCode, so I will probably learn fast.

oblomov, 1 year ago to fediverse

So, my main website is currently based on #ikiwiki. I like it because it's #plainText (no #database), I can work on it on my laptop using my favorite tools (#vim, #git), preview it locally, and then “deploy” it to a static set of HTML on the hosting machine. But there are a couple of things I do not like about my current setup. Chiefly:

1. I've matured a preference for #asciidoctor over #markdown
2. there is, AFAICS, no chance it'll ever federate w/ #ActivityPub