home.social

#asciidoc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #asciidoc, aggregated by home.social.

  1. Could anyone give me any pointers on the tooling for the #FreeBSD Documentation Project?

    I really like its style (and its use of #AsciiDoc) and would like to do something similar for the #Psion Documentation Project.

    EDIT: I might already have my answer here: docs.freebsd.org/en/books/fdp-

  2. Has anyone any recommendations for tools / styling for #ebooks? I'm looking at #asciidoc to #epub but I'm wondering what the "right" way to style the epub should be

    -- edit: A very good solution has been found, but Mastodon can't add images to retoots, so here we are, using URLs: oldbytes.space/@Kroc/116346357

    #worldglass #writersofmastodon #ebook #writing #writingcommunity

  3. @nielsk Think of the Family Guy meme to remember it. Markdown is the weird one.

  4. Easy Online Profiles with Asciidoctor

    Want an online presence, but you don't want to build a website, or blog, or self-host? With really basic terminal dabbling and asciidoctor you can quickly make a minimal, simple profile where you own your data.

    readbeanicecream.surge.sh/2026

    #indieweb #smallweb #socialmedia #asciidoctor #plaintext #asciidoc

  5. I start to leverage the true potential of #codingassistants only now. So far, I crossposted my blog posts by first transforming them from #Asciidoc to #Markdown by hand. Feasible, but boring.

    I have created a #ClaudeCode command and my life is so much better.

  6. I've converted some random dev notes I had lying around from working on clojure-ts-mode, neocaml and asciidoc-mode to a blog post with some general advice for building #Emacs major modes powered by #TreeSitter batsov.com/articles/2026/02/27

    I hope some of you will find it useful! I certainly wish someone had written such an article a year ago when I started to get more serious about playing with TreeSitter.

    #Clojure #OCaml #AsciiDoc

  7. I've put together asciidoc-mode (github.com/bbatsov/asciidoc-mo) - a super lean major #Emacs mode for editing #AsciiDoc documents, powered by #TreeSitter

    It's a lighter and simpler alternative to the more established adoc-mode (also maintained by yours truly), that has been sitting in the back of my mind for a while and became possible recently when a TS grammar for AsciiDoc was created.

    I hope you'll find the new mode useful!

    @sanityinc Can you help me get it in MELPA? (github.com/melpa/melpa/pull/98)

  8. **Stella & Finn (see above) is now available FOR FREE!**

    For at least the following 24 months, you can read the whole story, in all its PDF or ePub glory, *without spending a penny.* *You are free to download and enjoy NOW*!

    Or, if you want, set a voluntary payment, which I would appreciate very much and would help me a lot in making even better stuff for you all to enjoy, like, who knows... a new *drawing tablet* for upcoming comics! See my Ko-fi goal for more on that :) - ko-fi.com/wallabra

    The context, before anyone asks, is that I'm about to enter a public office and I can't really engage in commercial activity, due to a strict anti-Conflict-of-Interest clause. To someone else, this might be a bit disheartening, but I never really wanted to see my art as a "job" in the first place anyway, so it's whatever :p

    #FurryArt
    #Furry
    #Romance
    #FurryErotica
    #Writing
    #Reading
    #IndieWriting
    #SelfPublish
    #SliceOfLife
    #Bookstodon
    #AsciiDoc
    #MadeWithFOSS
    #IndiePub
    #SelfPub
    #ShortStory
    #Erotica

  9. @david_chisnall I have only one minor criticism of GitHub's highlighting, and I don't know whether it is (or should be) fixable.

    In cases such as the one pictured below, it's necessary to scroll/page down hugely to bring a tiny change into sight.

    In other words, 'Show Diff' shows much, much more than the diff.

    A wild guess: maybe specific to AsciiDoc in GitHub, or the FreeBSD Documentation Project's use of AsciiDoc in cases such as this.

    @zev @bentolor

    #GitHub #AsciiDoc #preview #diff

  10. A rowdy jaguar can't keep herself off her roommate, a sweet Labrador gardener. Will he give in and sink into her fur, or will he manage to bribe her off with enough carrots?

    Find out, in this sweet and heartwarming piece of furry romance / gentle erotica.

    🐾*** *Stella & Finn is now also available FOR FREE on Itch.io, alongside Ko-fi!**

    The main story spans about 4,000 words.

    * Itch.io: wallabra.itch.io/stella-and-fi
    * Ko-fi: ko-fi.com/s/b1e25eca7f

    For fans of affectionate playfulness, gentle consensual eroticism, and emotional connections.

    Written using AsciiDoc. Cover image made in Inkscape.

    #FurryArt #Furry #Romance #FurryErotica #Writing #Reading #IndieWriting #SelfPublish #SliceOfLife #Bookstodon #AsciiDoc #MadeWithFOSS #IndiePub #SelfPub #ShortStory #Erotica

  11. 🆕 pandoc 3.8.3 🎉

    This release adds three new input formats (, , and ) and one new output format ( + variants).

    It also fixes a number of bugs (including some regressions in 3.8). See the changelog for full details.

    Thanks to all who contributed!

    github.com/jgm/pandoc/releases

  12. #Markdown Is a Disaster: Why and What to Do Instead
    karl-voit.at/2025/08/17/Markdo

    Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.

    #publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin

  13. #Markdown Is a Disaster: Why and What to Do Instead
    karl-voit.at/2025/08/17/Markdo

    Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.

    #publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin

  14. #Markdown Is a Disaster: Why and What to Do Instead
    karl-voit.at/2025/08/17/Markdo

    Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.

    #publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin

  15. #Markdown Is a Disaster: Why and What to Do Instead
    karl-voit.at/2025/08/17/Markdo

    Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.

    #publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin

  16. Как мы писали техдокументацию AsciiDoc нейронкой, экономя своё время и миллионы

    Я расскажу вам историю, в которой мы использовали нейронку, чтобы написать техническую документацию и архитектурный вижн для большого сложного проекта, теоретически сэкономив сумму из 8 цифр. Кто в здравом уме будет это делать? У вас должны быть веские причины, чтобы извернувшись изобрести решение, в котором документация напишет себя сама.

    habr.com/ru/companies/alfa/art

    #генеративный_ии #техническая_документация #цифровые_финансовые_активы #блокчейнплатформа #asciidoc #блокчейн_инвестиции #цфа #смартконтракты #токены #майнинг_в_россии

  17. Coming from on , I think about migrating our projects user manual to using and/or .

    But I wonder if there is a service like for based manuals available for or projects.

    Important is that those platforms do support @Codeberg ( aka ) code hosting, instead of Microsoft GitHub.

  18. Should I dare to do a "why #Markdown is one of the worst lightweight markup syntax languages there is"-session at a UX/UI-dominant #barcamp? 😜

    C'mon, do push me over that cliff! 😆

    Background: karl-voit.at/2017/09/23/orgmod 👉 it's related but would be a different focus since I won't push #orgdown that much - people can be happier with other LMLs as well as long as it's not the #MD hell. (Sneak preview: I'm writing a long article on all the MD issues in order to explain it once and for all since the Mastodon discussions are really annoying to me.)

    #LML #AsciiDoc #rSt #WikiText #orgmode

  19. @ajlewis2 @ellane @feralthoughts @hbowie @reichenstein

    Just for clarification: same holds true for any other markup supported by pandoc, not just #Markdown.

    However, if you stick with a syntax language that doesn't come with this explosion of flavors, you have less issues converting your data - in some cases you don't even have to convert at all any more.

    The issue with Markdown is that its original form defined a small minimum of elements and each tool defined its own potentially incompatible extensions. With other #LML, the "original" or its standard defines the maximum set of elements and therefore, there is no need for "flavors" and no data loss or conversion effort.

    HTH

    #AsciiDoc #orgmode #orgdown #Obsidian #PIM

  20. Switching to Antora for the OliveTin docs was the best thing ever for the docs. Now just added support for doc tabs with a simple extension :-) #asciidoc #antora thanks Dan Allen!

  21. PLUG's topic tonight is Using AsciiDoc to Create Presentations

    The meeting is online in a #BigBlueButton instance starting at 19:00 AZ time ( UTC -7 ), in about 30 minutes

    Online, so join from where ever you are :)

    gettogether.community/events/7

    The @FLOSS_Stammtisch is on Tuesday the 18th, it will meet in person at Boulders on Southern in Mesa, AZ

    #PLUG #FLOSSevent #BBB #LocalGroup #VirtualMeeting #Stammtisch @PLUG #AsciiDoc

  22. @david_megginson

    This opposition of org-mode vs. (LaTeX, SGML) XML in publishing is something that resonates very strongly with me - though I'm afraid it's hard for many org users to understand.

    I do almost all of my daily work in org-mode, but whenever I start a writing project that needs to be published, I use XML. There are all kinds of reasons for this, some very specific to my case of academic writing, where the handling of citations, footnotes and bibliography can get very complex and specific. But I feel that in the end it comes down to something much simpler.

    For decades I have been using docbook-xml for all my writing projects, starting with drafting in asciidoc (and this co-existence of asciidoc and org-mode as two "markdown" dialects still leaves me unsatisfied). The deeper reasons however seem to be that in org-mode you start designing your text from an outline. For me, this is the wrong approach, as I need to write a text as a stream-of-consciousness, adding paragraph after paragraph, and only later get to an outline. The way I'm used to using org-mode seems to make this impossible for me.

    #emacs #orgmode #docbook #asciidoc

  23. Moved instance, so time for a new #introduction!

    I'm Alex and I have a PDA problem.

    In 2018, after 16 years of using various #Psion portables, I decided to try my hand at developing hardware and software for my beloved Series 3c to help me with journalling and creative writing.

    6 years and repeated sidequests later, I've ended up doing a lot of research into the SIBO/EPOC16 platform, and done my best to document it when I can. I've also nudged former developers into open sourcing their old Psion apps.

    My current main projects are:

    • #PsiDrive, an #RP2040-based USB drive for SIBO SSDs.
    • Rewriting the Psion SIBO (16-bit 8086) C SDK, including updating the docs (with #AsciiDoc) and rewriting the original DOS tools as FOSS apps. I'm currently using #FreePascal to create a drop-in replacement for #CTRAN, the Psion OO C preprocessor. (I want to eventually write a new compiler targeting EPOC16. Eventually.)
    • Anything else that tickles my bouncy brain.

    Outside of #retrocomputing, I'm your common-or-garden British nerd. I'm a Linux user - mostly Arch, but I dabble with others. I also like a bit of #HaikuOS and I'm planning on giving #FreeBSD a go very soon.

    I used to be a senior computer monkey, specialising in on-prem SME infrastructure (I lament the loss of vSphere). Now I train others to become computer monkeys (for better or worse). As a result, sometimes you'll see me wrestling with old Cisco ASAs, Ubiquiti APs, or modded kit running #OpenWrt.

    Generally, I like making things do stuff, especially if it's stuff that the thing wasn't originally designed to do.

  24. #fedihelp & #fediask

    Hello #fedifriends, I've just realized that #asciidoc & #asciidoctor aren't the same thing, so I was using the documentation of asciidoctor and processing the my document with asciidoc… 🤦‍♂️

    I don't know who came late, but the choice of the name is very confused, so now I'd like to know what the #fediversians like to use if asciidoc or asciidoctor, or at least you recommend.

    The point is some stuff aren't working because perhaps aren't for ascidoc on the other end asciidoctor is very aggressive on the web search, so unless you don't exclude it from the search it completely eclipses the other one.

    Thanks! 🙏

    #opensource #markup

  25. Upcoming projects:

    ⏸️ Learn #Psion's proprietary 16-bit OO C.
    ⏸️ Rewrite more of the SIBO SDK.
    ⏸️ Learn about designing #compilers and #assemblers.
    ⏸️ New version of #PsiDrive PCB.
    ⏸️ Vine: A new #FOSS #EPOC16 word processor aimed at writers/authors, with Vim motions and #AsciiDoc compatibility.
    ⏸️ Converting the Psion SIBO C SDK to AsciiDoc.
    ⏸️ #fefstool: Like #mtools but for #Psion Flash (FEFS) volumes.
    ⏸️ #MAME null modem mod, so that it can talk properly to #DOSBox.
    ⏸️ psion.info redux.
    ⏸️ More docs!

  26. released IDE for writing... documentation! I'm just surprised it doesn't seem to support out-of-the-box jetbrains.com/writerside/

  27. Today I speed ran a small fibonacci number generator in #rust that is based on #iterators.
    Also, I used #asciidoc for readme instead of traditional #markdown .

    codeberg.org/atamakahere/fibte

  28. Projects waiting in the wings:

    - Learning #Psion's proprietary 16-bit OO C. (It's what drove me to start working on CTRAN.) Also leads on to...
    - Vine: A new #FOSS #EPOC16 word processor aimed at writers/authors, with #AsciiDoc compatibility. Plus new associated libraries and tools.
    - Converting the Psion SIBO C SDK to AsciiDoc.
    - #fefstool: Like #mtools, but for #Psion Flash (FEFS) volumes.
    - #MAME null modem mod, so that it can talk properly to #DOSBox.
    - Re-do psion.info.
    - More docs!

  29. So, now the MAME/Haiku project is essentially done (just waiting for my PR to be merged now), I'm thinking about what to work on next.

    Outstanding #Psion projects:
    - #FEFSgen (golang) to make flash SSD images
    - #libsibo: add write for RAM SSDs
    - #PsiDrive: add boost converter (set to ~17VDC) for writing to Flash SSDs
    - Psion SDK to #AsciiDoc: SO MUCH DOCUMENTATION TO CONVERT!
    - Blogging: SO MUCH DOCUMENTATION TO WRITE!
    - #EDisAsm: because there's always room for more features

  30. @AstridSawatzky The IntelliJ AsciiDoc Plugin by @ahus1 can be configured to use custom stylesheets for the preview pane, so you see exactly what your output will look like:

    intellij-asciidoc-plugin.ahus1

    If you use antora.org, you can even point to the stylesheets from your custom #Antora UI.

    #AsciiDoc #IntelliJ

  31. More #Psion documentation fun, this time with headings/sections.

    Psion made much of the SIBO/EPOC16 documentation in Microsoft Word. Looking at a .DOC file, I've realised that they often skipped "Heading 3", going straight from Heading 2 to Heading 4. They only used Heading 3 in specific circumstances, such as function and syscall names.

    Skipping section titles breaks #AsciiDoc's rules.

    I'm trying to work a way around it, but I have no idea how.

    #WinWord

  32. OPS4J Documentation is moving from Confluence to Git. Initial setup is done: ops4j.github.io

    #OPS4J #AsciiDoc #Antora #GitHub

  33. @plantarum @b0rk @pluralistic I edited some Emacs #texinfo files a couple of times and found it always a bit verbose and quirky, but not really worse than the newer #restructuredText or #asciidoc.

  34. @[email protected]: Für das #Debian-Paket-Management-Buch (dpmb.org/ #dpmb) — zugegeben, es ist ein Fachbuch und keine Belletristik — nehmen wir #Asciidoc. Wobei fürs PDF generieren dann untendrunter doch wieder ein #TeXLaTeX (Paket asciidoc-dblatex unter Debian und Derivaten) läuft.

  35. Algumas pessoas gostam de colecionar canetas, eu, por outro lado, gosto de testar e colecionar sistemas de processamento de documentos. A primeira vez que utilizei #LaTeX a sério foi em 2012 ou 2014, desde então, sempre que posso, evito processadores de texto convencionais (até gosto do #TextMaker, mas documentos longos e técnicos precisam de sistemas mais robustos, ainda que pouco ou nada visuais). Recentemente, passei um tempo lendo sobre #AsciiDoc e #ConTeXt também. E agora conheci o #Quarto.