#asciidoc — Public Fediverse posts

Is there really no way with AsciiDoctor of defining a macro that expands to some token sequence with substitutions of the arguments without writing some Ruby / Java / JavaScript that is then not portable across implementations?

#ASCIIDoc #ASCIIDoctor

Is there really no way with AsciiDoctor of defining a macro that expands to some token sequence with substitutions of the arguments without writing some Ruby / Java / JavaScript that is then not portable across implementations?

#ASCIIDoc #ASCIIDoctor

Is there really no way with AsciiDoctor of defining a macro that expands to some token sequence with substitutions of the arguments without writing some Ruby / Java / JavaScript that is then not portable across implementations?

#ASCIIDoc #ASCIIDoctor

Is there really no way with AsciiDoctor of defining a macro that expands to some token sequence with substitutions of the arguments without writing some Ruby / Java / JavaScript that is then not portable across implementations?

#ASCIIDoc #ASCIIDoctor

Is there really no way with AsciiDoctor of defining a macro that expands to some token sequence with substitutions of the arguments without writing some Ruby / Java / JavaScript that is then not portable across implementations?

#ASCIIDoc #ASCIIDoctor

New alpha release of the AsciiDoctrine #Python #AsciiDoc parser v0.2.0a8. In this release:
- Lossless roundtrip AsciiDoc Serializer
- Media block macros
- Ordered list styles, checklist states
- Closer schema alignment with the standard
- LRU cache

... and more!

Repo: https://github.com/webmaven/asciidoctrine/

Docs: https://webmaven.github.io/asciidoctrine/

Changelog: https://webmaven.github.io/asciidoctrine/changelog.html

Get the package: https://pypi.org/project/asciidoctrine/0.2.0a8/

New alpha release of the AsciiDoctrine #Python #AsciiDoc parser v0.2.0a8. In this release:
- Lossless roundtrip AsciiDoc Serializer
- Media block macros
- Ordered list styles, checklist states
- Closer schema alignment with the standard
- LRU cache

... and more!

Repo: https://github.com/webmaven/asciidoctrine/

Docs: https://webmaven.github.io/asciidoctrine/

Changelog: https://webmaven.github.io/asciidoctrine/changelog.html

Get the package: https://pypi.org/project/asciidoctrine/0.2.0a8/

New alpha release of the AsciiDoctrine #Python #AsciiDoc parser v0.2.0a8. In this release:
- Lossless roundtrip AsciiDoc Serializer
- Media block macros
- Ordered list styles, checklist states
- Closer schema alignment with the standard
- LRU cache

... and more!

Repo: https://github.com/webmaven/asciidoctrine/

Docs: https://webmaven.github.io/asciidoctrine/

Changelog: https://webmaven.github.io/asciidoctrine/changelog.html

Get the package: https://pypi.org/project/asciidoctrine/0.2.0a8/

New alpha release of the AsciiDoctrine #Python #AsciiDoc parser v0.2.0a8. In this release:
- Lossless roundtrip AsciiDoc Serializer
- Media block macros
- Ordered list styles, checklist states
- Closer schema alignment with the standard
- LRU cache

... and more!

Repo: https://github.com/webmaven/asciidoctrine/

Docs: https://webmaven.github.io/asciidoctrine/

Changelog: https://webmaven.github.io/asciidoctrine/changelog.html

Get the package: https://pypi.org/project/asciidoctrine/0.2.0a8/

New alpha release of the AsciiDoctrine #Python #AsciiDoc parser v0.2.0a8. In this release:
- Lossless roundtrip AsciiDoc Serializer
- Media block macros
- Ordered list styles, checklist states
- Closer schema alignment with the standard
- LRU cache

... and more!

Repo: https://github.com/webmaven/asciidoctrine/

Docs: https://webmaven.github.io/asciidoctrine/

Changelog: https://webmaven.github.io/asciidoctrine/changelog.html

Get the package: https://pypi.org/project/asciidoctrine/0.2.0a8/

My "AsciiDoc: plain text for fancy output" talk has been accepted by @SeaGL

In this time of uncertainty, I bring Power To The ASCII!

Well, power from the ASCII anyway :)

Friday and Saturday October 23rd and 24th in a time zone near you ( but based on daytime in Seattle ) as talks will be streamed

SeaGL's a great hybrid conference based out of Seattle, very much looking forward to it

#SeaGL #AsciiDoc #ASCII #PlainText #FLOSSconf #FLOSSevent #Seattle #Cascadia #HybridConf

My "AsciiDoc: plain text for fancy output" talk has been accepted by @SeaGL

In this time of uncertainty, I bring Power To The ASCII!

Well, power from the ASCII anyway :)

Friday and Saturday October 23rd and 24th in a time zone near you ( but based on daytime in Seattle ) as talks will be streamed

SeaGL's a great hybrid conference based out of Seattle, very much looking forward to it

#SeaGL #AsciiDoc #ASCII #PlainText #FLOSSconf #FLOSSevent #Seattle #Cascadia #HybridConf

My "AsciiDoc: plain text for fancy output" talk has been accepted by @SeaGL

In this time of uncertainty, I bring Power To The ASCII!

Well, power from the ASCII anyway :)

Friday and Saturday October 23rd and 24th in a time zone near you ( but based on daytime in Seattle ) as talks will be streamed

SeaGL's a great hybrid conference based out of Seattle, very much looking forward to it

#SeaGL #AsciiDoc #ASCII #PlainText #FLOSSconf #FLOSSevent #Seattle #Cascadia #HybridConf

My "AsciiDoc: plain text for fancy output" talk has been accepted by @SeaGL

In this time of uncertainty, I bring Power To The ASCII!

Well, power from the ASCII anyway :)

Friday and Saturday October 23rd and 24th in a time zone near you ( but based on daytime in Seattle ) as talks will be streamed

SeaGL's a great hybrid conference based out of Seattle, very much looking forward to it

#SeaGL #AsciiDoc #ASCII #PlainText #FLOSSconf #FLOSSevent #Seattle #Cascadia #HybridConf

My "AsciiDoc: plain text for fancy output" talk has been accepted by @SeaGL

In this time of uncertainty, I bring Power To The ASCII!

Well, power from the ASCII anyway :)

Friday and Saturday October 23rd and 24th in a time zone near you ( but based on daytime in Seattle ) as talks will be streamed

SeaGL's a great hybrid conference based out of Seattle, very much looking forward to it

#SeaGL #AsciiDoc #ASCII #PlainText #FLOSSconf #FLOSSevent #Seattle #Cascadia #HybridConf

Trying out writing my résumé in #AsciiDoc.

Trying out writing my résumé in #AsciiDoc.

Trying out writing my résumé in #AsciiDoc.

AsciiDoc vs Markdown: 2026년 문서화 포맷 선택 가이드 via Docsio

"일반적인 문서화 프로젝트의 90%에는 Markdown이 적합하다. 반면, 기본 기능으로서 파일 인클루드(Includes), 상호 참조(Cross-references), 조건부 콘텐츠(Conditional content)가 필수적인 도서급(Book-class) 기술 문서를 제작해야 한다면 AsciiDoc을 선택해야 한다."

* https://cb.netspheres.org/p?s=s2snyz9zpcnacugs

#Markdown #AsciiDoc

AsciiDoc vs Markdown: 2026년 문서화 포맷 선택 가이드 via Docsio

"일반적인 문서화 프로젝트의 90%에는 Markdown이 적합하다. 반면, 기본 기능으로서 파일 인클루드(Includes), 상호 참조(Cross-references), 조건부 콘텐츠(Conditional content)가 필수적인 도서급(Book-class) 기술 문서를 제작해야 한다면 AsciiDoc을 선택해야 한다."

* https://cb.netspheres.org/p?s=s2snyz9zpcnacugs

#Markdown #AsciiDoc

AsciiDoc vs Markdown: 2026년 문서화 포맷 선택 가이드 via Docsio

"일반적인 문서화 프로젝트의 90%에는 Markdown이 적합하다. 반면, 기본 기능으로서 파일 인클루드(Includes), 상호 참조(Cross-references), 조건부 콘텐츠(Conditional content)가 필수적인 도서급(Book-class) 기술 문서를 제작해야 한다면 AsciiDoc을 선택해야 한다."

* https://cb.netspheres.org/p?s=s2snyz9zpcnacugs

#Markdown #AsciiDoc

AsciiDoc vs Markdown: 2026년 문서화 포맷 선택 가이드 via Docsio

"일반적인 문서화 프로젝트의 90%에는 Markdown이 적합하다. 반면, 기본 기능으로서 파일 인클루드(Includes), 상호 참조(Cross-references), 조건부 콘텐츠(Conditional content)가 필수적인 도서급(Book-class) 기술 문서를 제작해야 한다면 AsciiDoc을 선택해야 한다."

* https://cb.netspheres.org/p?s=s2snyz9zpcnacugs

#Markdown #AsciiDoc

We've updated our docs website to be based on Antora and is now published here! :cockpit:

This has the added benefit of showing us docs for different versions and allows us to be more flexible.

https://docs.cockpit-project.org/cockpit-guide/latest/guide/index.html

#asciidoc #antora

We've updated our docs website to be based on Antora and is now published here! :cockpit:

This has the added benefit of showing us docs for different versions and allows us to be more flexible.

https://docs.cockpit-project.org/cockpit-guide/latest/guide/index.html

#asciidoc #antora

We've updated our docs website to be based on Antora and is now published here! :cockpit:

This has the added benefit of showing us docs for different versions and allows us to be more flexible.

https://docs.cockpit-project.org/cockpit-guide/latest/guide/index.html

#asciidoc #antora

We've updated our docs website to be based on Antora and is now published here! :cockpit:

This has the added benefit of showing us docs for different versions and allows us to be more flexible.

https://docs.cockpit-project.org/cockpit-guide/latest/guide/index.html

#asciidoc #antora

We've updated our docs website to be based on Antora and is now published here! :cockpit:

This has the added benefit of showing us docs for different versions and allows us to be more flexible.

https://docs.cockpit-project.org/cockpit-guide/latest/guide/index.html

#asciidoc #antora

Hugo Lotus Docs에서 AsciiDoc 사용하기

* https://github.com/fofwisdom/lotusdocs-asciidoc

#AsciiDoc #markup

Hugo Lotus Docs에서 AsciiDoc 사용하기

* https://github.com/fofwisdom/lotusdocs-asciidoc

#AsciiDoc #markup

Hugo Lotus Docs에서 AsciiDoc 사용하기

* https://github.com/fofwisdom/lotusdocs-asciidoc

#AsciiDoc #markup

Hugo Lotus Docs에서 AsciiDoc 사용하기

* https://github.com/fofwisdom/lotusdocs-asciidoc

#AsciiDoc #markup

Writing a lot of content in #ASCIIDOC and discovered #livejs to hot load my edits for preview.

Just add the script to your docinfo file when building on desktop (using fswatch to detect changes and do the rebuild on edit save).

Changes get displayed in the browser a short while later.

https://docs.asciidoctor.org/asciidoc/latest/docinfo/

Putting it here in case it helps others with #DocsLikeCode workflow

Writing a lot of content in #ASCIIDOC and discovered #livejs to hot load my edits for preview.

Just add the script to your docinfo file when building on desktop (using fswatch to detect changes and do the rebuild on edit save).

Changes get displayed in the browser a short while later.

https://docs.asciidoctor.org/asciidoc/latest/docinfo/

Putting it here in case it helps others with #DocsLikeCode workflow

Writing a lot of content in #ASCIIDOC and discovered #livejs to hot load my edits for preview.

Just add the script to your docinfo file when building on desktop (using fswatch to detect changes and do the rebuild on edit save).

Changes get displayed in the browser a short while later.

https://docs.asciidoctor.org/asciidoc/latest/docinfo/

Putting it here in case it helps others with #DocsLikeCode workflow

Writing a lot of content in #ASCIIDOC and discovered #livejs to hot load my edits for preview.

Just add the script to your docinfo file when building on desktop (using fswatch to detect changes and do the rebuild on edit save).

Changes get displayed in the browser a short while later.

https://docs.asciidoctor.org/asciidoc/latest/docinfo/

Putting it here in case it helps others with #DocsLikeCode workflow

Writing a lot of content in #ASCIIDOC and discovered #livejs to hot load my edits for preview.

Just add the script to your docinfo file when building on desktop (using fswatch to detect changes and do the rebuild on edit save).

Changes get displayed in the browser a short while later.

https://docs.asciidoctor.org/asciidoc/latest/docinfo/

Putting it here in case it helps others with #DocsLikeCode workflow

Hey frendos. Does anyone have a good link / summary for how to add a new processor to #asciidoc ?

tl;dr There doesn't seem to be a good way to render #jvm #bytecode and I would like to fix that, if one doesn't already exist. #java #ruby

Hey frendos. Does anyone have a good link / summary for how to add a new processor to #asciidoc ?

tl;dr There doesn't seem to be a good way to render #jvm #bytecode and I would like to fix that, if one doesn't already exist. #java #ruby

Hey frendos. Does anyone have a good link / summary for how to add a new processor to #asciidoc ?

tl;dr There doesn't seem to be a good way to render #jvm #bytecode and I would like to fix that, if one doesn't already exist. #java #ruby

Hey frendos. Does anyone have a good link / summary for how to add a new processor to #asciidoc ?

tl;dr There doesn't seem to be a good way to render #jvm #bytecode and I would like to fix that, if one doesn't already exist. #java #ruby

Hey frendos. Does anyone have a good link / summary for how to add a new processor to #asciidoc ?

tl;dr There doesn't seem to be a good way to render #jvm #bytecode and I would like to fix that, if one doesn't already exist. #java #ruby

@schubisu Es geht mir darum, die Nicht-Fediverse-Bubble über Alternativen zu informieren. Das ist einfach der größte Teil der Bevölkerung. Daher auch die Ideen mit #shareitonlinkedin - also den Alternativen Lösungen auch in anderen Bubbles Reichweite geben.

WriteFreely schaue ich mir mal an. Wenn ich aktuell Blogge nutze ich #Jekyll zur Erstellung statischer Blogs mit #asciidoc und #git auf #gitlab (https://jekyll-theme-endless.gitlab.io/)

Kennt sich hier jemand mit #asciidoc aus? Ich würde gerne ein Sudoku basteln und muss daher in einer Tabelle an bestimmten Stellen dickere Linien zeichnen (jede dritte Spalte und Zeile).

Geht das mit #asciidoctor? Kann mir jemand einen Tipp geben? :BoostOK:

Kennt sich hier jemand mit #asciidoc aus? Ich würde gerne ein Sudoku basteln und muss daher in einer Tabelle an bestimmten Stellen dickere Linien zeichnen (jede dritte Spalte und Zeile).

Geht das mit #asciidoctor? Kann mir jemand einen Tipp geben? :BoostOK:

Kennt sich hier jemand mit #asciidoc aus? Ich würde gerne ein Sudoku basteln und muss daher in einer Tabelle an bestimmten Stellen dickere Linien zeichnen (jede dritte Spalte und Zeile).

Geht das mit #asciidoctor? Kann mir jemand einen Tipp geben? :BoostOK:

Kennt sich hier jemand mit #asciidoc aus? Ich würde gerne ein Sudoku basteln und muss daher in einer Tabelle an bestimmten Stellen dickere Linien zeichnen (jede dritte Spalte und Zeile).

Geht das mit #asciidoctor? Kann mir jemand einen Tipp geben? :BoostOK:

Kennt sich hier jemand mit #asciidoc aus? Ich würde gerne ein Sudoku basteln und muss daher in einer Tabelle an bestimmten Stellen dickere Linien zeichnen (jede dritte Spalte und Zeile).

Geht das mit #asciidoctor? Kann mir jemand einen Tipp geben? :BoostOK:

#Emacs loves #AsciiDoc https://batsov.com/articles/2026/06/11/emacs-loves-asciidoc/

I hope you'll enjoy all the recent improvements in adoc-mode and asciidoc-mode!

#Emacs loves #AsciiDoc https://batsov.com/articles/2026/06/11/emacs-loves-asciidoc/

I hope you'll enjoy all the recent improvements in adoc-mode and asciidoc-mode!

#Emacs loves #AsciiDoc https://batsov.com/articles/2026/06/11/emacs-loves-asciidoc/

I hope you'll enjoy all the recent improvements in adoc-mode and asciidoc-mode!

#Emacs loves #AsciiDoc https://batsov.com/articles/2026/06/11/emacs-loves-asciidoc/

I hope you'll enjoy all the recent improvements in adoc-mode and asciidoc-mode!

#Emacs loves #AsciiDoc https://batsov.com/articles/2026/06/11/emacs-loves-asciidoc/

I hope you'll enjoy all the recent improvements in adoc-mode and asciidoc-mode!

I agree with u/TerribleReason4195 in Reddit: the new site is much better.

@FreeBSDFoundation true: it's a stronger foundation for the future of the FreeBSD Project.

Too few people appreciate the amount of work that's required, collectively and individually, for a milestone such as this.

I believe that this year's transition would have been far more difficult without the migration that Sergio Carlavilla spearheaded five years ago. Before and after: <https://github.com/freebsd/freebsd-doc/tree/0cff342f42461c5081b98bce7581f43df319e4f4> | <https://github.com/freebsd/freebsd-doc/tree/989d921f5d4ac8d8b7c831c13b8954ad1901be24>.

#FreeBSD #website #Hugo #AsciiDoctor #AsciiDoc

I agree with u/TerribleReason4195 in Reddit: the new site is much better.

@FreeBSDFoundation true: it's a stronger foundation for the future of the FreeBSD Project.

Too few people appreciate the amount of work that's required, collectively and individually, for a milestone such as this.

I believe that this year's transition would have been far more difficult without the migration that Sergio Carlavilla spearheaded five years ago. Before and after: <https://github.com/freebsd/freebsd-doc/tree/0cff342f42461c5081b98bce7581f43df319e4f4> | <https://github.com/freebsd/freebsd-doc/tree/989d921f5d4ac8d8b7c831c13b8954ad1901be24>.

#FreeBSD #website #Hugo #AsciiDoctor #AsciiDoc

I agree with u/TerribleReason4195 in Reddit: the new site is much better.

@FreeBSDFoundation true: it's a stronger foundation for the future of the FreeBSD Project.

Too few people appreciate the amount of work that's required, collectively and individually, for a milestone such as this.

I believe that this year's transition would have been far more difficult without the migration that Sergio Carlavilla spearheaded five years ago. Before and after: <https://github.com/freebsd/freebsd-doc/tree/0cff342f42461c5081b98bce7581f43df319e4f4> | <https://github.com/freebsd/freebsd-doc/tree/989d921f5d4ac8d8b7c831c13b8954ad1901be24>.

#FreeBSD #website #Hugo #AsciiDoctor #AsciiDoc

I agree with u/TerribleReason4195 in Reddit: the new site is much better.

@FreeBSDFoundation true: it's a stronger foundation for the future of the FreeBSD Project.

Too few people appreciate the amount of work that's required, collectively and individually, for a milestone such as this.

I believe that this year's transition would have been far more difficult without the migration that Sergio Carlavilla spearheaded five years ago. Before and after: <https://github.com/freebsd/freebsd-doc/tree/0cff342f42461c5081b98bce7581f43df319e4f4> | <https://github.com/freebsd/freebsd-doc/tree/989d921f5d4ac8d8b7c831c13b8954ad1901be24>.

#FreeBSD #website #Hugo #AsciiDoctor #AsciiDoc

I agree with u/TerribleReason4195 in Reddit: the new site is much better.

@FreeBSDFoundation true: it's a stronger foundation for the future of the FreeBSD Project.

Too few people appreciate the amount of work that's required, collectively and individually, for a milestone such as this.

I believe that this year's transition would have been far more difficult without the migration that Sergio Carlavilla spearheaded five years ago. Before and after: <https://github.com/freebsd/freebsd-doc/tree/0cff342f42461c5081b98bce7581f43df319e4f4> | <https://github.com/freebsd/freebsd-doc/tree/989d921f5d4ac8d8b7c831c13b8954ad1901be24>.

#FreeBSD #website #Hugo #AsciiDoctor #AsciiDoc

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: https://docs.freebsd.org/en/books/fdp-primer/overview/

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: https://docs.freebsd.org/en/books/fdp-primer/overview/

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: https://docs.freebsd.org/en/books/fdp-primer/overview/