#markup — Public Fediverse posts

I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

I am thinking things like …

• Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
• Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
• More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
• Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
• More obligatory metadata like authorship, tags, publishing/modification date etc.
• Integration of non-search engine discoverability features like webrings, directly on a site level
• Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
• Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

… and so on.

I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

#web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

I am thinking things like …

• Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
• Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
• More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
• Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
• More obligatory metadata like authorship, tags, publishing/modification date etc.
• Integration of non-search engine discoverability features like webrings, directly on a site level
• Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
• Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

… and so on.

I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

#web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

I am thinking things like …

• Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
• Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
• More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
• Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
• More obligatory metadata like authorship, tags, publishing/modification date etc.
• Integration of non-search engine discoverability features like webrings, directly on a site level
• Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
• Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

… and so on.

I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

#web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

I should at some point get around to writing the specifications for the alternative web document markup language I've had in my head forever.

HTML isn't bad, but it is definitely constrained by its position as the default markup language for the whole modern web. They need to cater to everyone, from super fancy corporate websites, massive web applications, social media, video sites, encyclopedias, personal homepages, art projects, hobbyists, to professional webdev engineers ...

I really want something purpose-built for a more semantic, personal hypertext web aimed at enthusiasts.

Perhaps it wouldn't be as versatile as HTML, but it doesn't need to fit all use cases of every possible target audience or be viable for businesses.

I am thinking things like …

• Styling should be handled exclusively by the browser based on semantic elements and application-level user preferences (perhaps minimal style recommendations/hints at best).
• Differentiating types of hyperlinks; internal navigation links, important main links, optional context/rabbithole links etc.
• More granular and specific semantic elements, like the uncoupling of times and dates, splitting address/contact elements into specific fields like e-mail and name, quotations with attributions, definitions etc.
• Integration of other semantic data projects such as MusicBrainz, Wikidata or Wikipedia (holy link rot, but we'll see).
• More obligatory metadata like authorship, tags, publishing/modification date etc.
• Integration of non-search engine discoverability features like webrings, directly on a site level
• Easier cross-document reusable elements, i. e. integrating the same header or footer on each site
• Extensive entity-oriented data support with URIs, e. g. in-line fetching of things like names, pronouns or contact data from a central 'person' entity URL to automatically propagate things like name changes through the web.

… and so on.

I could even experiment with the markup tech itself; it doesn't need to be XML after all. It could even be something like a stand-off annotation document allowing the division of content writing from mark-up. Or something with a similarly simple syntax as Markdown, but with semantic instead of styling information.

And then comes the arduous task of implementing a parser. :popcorn: I'm so excited.

#web #webDev #markup #markupLanguages #html #hypertext #www #worldWideWeb #programming #tech

Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

Jim Hall (Apress)

“From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

You Will Learn to:

- Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
- Understand how the technologies and tools have evolved over time
- Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

This Book is For:
- Technical writers, technology history enthusiasts and researchers.”

https://books.google.pt/books?id=2XsAEgAAQBAJ

#TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

Jim Hall (Apress)

“From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

You Will Learn to:

- Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
- Understand how the technologies and tools have evolved over time
- Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

This Book is For:
- Technical writers, technology history enthusiasts and researchers.”

https://books.google.pt/books?id=2XsAEgAAQBAJ

#TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

Jim Hall (Apress)

“From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

You Will Learn to:

- Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
- Understand how the technologies and tools have evolved over time
- Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

This Book is For:
- Technical writers, technology history enthusiasts and researchers.”

https://books.google.pt/books?id=2XsAEgAAQBAJ

#TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

Jim Hall (Apress)

“From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

You Will Learn to:

- Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
- Understand how the technologies and tools have evolved over time
- Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

This Book is For:
- Technical writers, technology history enthusiasts and researchers.”

https://books.google.pt/books?id=2XsAEgAAQBAJ

#TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

Just released. Judging from its Table of Contents, it promises to be very interesting in mere historical and technical terms. My suspiction is that it runs the danger of being too much enciclopedic.

From Markup to Markdown: The Evolution of Technical Writing, Typesetting Tools and Frameworks

Jim Hall (Apress)

“From Markup to Markdown is a history of how writers have used computers to write, and a look ahead to see what the future looks like for technical writing. This book explores both “technology history” and “how it works” about how we write with computers, with code examples so readers can explore and fully understand how each writing tool and framework works behind the scenes.

Starting with an overview of the major milestones of writing with digital technologies since the 1960s, you will learn about RUNOFF and how this inspired roff on Unix (and the more familiar versions, nroff and troff). You will also explore word processing milestones like WordStar, and printing technologies like the phototypesetter and the dot matrix printer, before moving onto modern markup and writing systems like HTML, Markdown and DITA and how they play a role in how we write today.

From Markup to Markdown is ideal for writers, technical communication professionals, history of computing researchers as well as “retro-computing” enthusiasts.

You Will Learn to:

- Explore the history of technical writing in the age of the personal computer, from the 1960s to the present day
- Understand how the technologies and tools have evolved over time
- Learn how each tool works with simple and clear code samples and exercises, giving you an under-the-hood understanding of how each system works, from RUNOFF markup to modern Markdown

This Book is For:
- Technical writers, technology history enthusiasts and researchers.”

https://books.google.pt/books?id=2XsAEgAAQBAJ

#TechnicalWriting #Markup #HTML #Markdown #DITA #TechnicalCommunication #HistoryOfTechnology

Update! DOT-Export aus dWb+ http://elbosso.codeberg.page/dot_export_aus_dwb_.html#content

Bereits seit längerem war ein Feature in
dWb+
in der Beta-Phase, das es unkompliziert erlaubt, Workspaces in
beliebige andere Formate zu exportieren. Während dieser Tests wurden verschiedene
Formate als Testsubjekt herangezogen - unter anderem DOT.
#Komponenten #August_2026 #KW_33_2026 #Markup #Java #dWb_

Update! DOT-Export aus dWb+ http://elbosso.codeberg.page/dot_export_aus_dwb_.html#content

Bereits seit längerem war ein Feature in
dWb+
in der Beta-Phase, das es unkompliziert erlaubt, Workspaces in
beliebige andere Formate zu exportieren. Während dieser Tests wurden verschiedene
Formate als Testsubjekt herangezogen - unter anderem DOT.
#Komponenten #August_2026 #KW_33_2026 #Markup #Java #dWb_

Update! DOT-Export aus dWb+ http://elbosso.codeberg.page/dot_export_aus_dwb_.html#content

Bereits seit längerem war ein Feature in
dWb+
in der Beta-Phase, das es unkompliziert erlaubt, Workspaces in
beliebige andere Formate zu exportieren. Während dieser Tests wurden verschiedene
Formate als Testsubjekt herangezogen - unter anderem DOT.
#Komponenten #August_2026 #KW_33_2026 #Markup #Java #dWb_

Update! DOT-Export aus dWb+ http://elbosso.codeberg.page/dot_export_aus_dwb_.html#content

Bereits seit längerem war ein Feature in
dWb+
in der Beta-Phase, das es unkompliziert erlaubt, Workspaces in
beliebige andere Formate zu exportieren. Während dieser Tests wurden verschiedene
Formate als Testsubjekt herangezogen - unter anderem DOT.
#Komponenten #August_2026 #KW_33_2026 #Markup #Java #dWb_

Gitlab Act 2 und meine Konsequenzen daraus http://elbosso.codeberg.page/gitlab_act_2_meine_konsequenzen_daraus.html#content

Ich habe kurz nach dem 11. Mai 2026 von den Änderungen erfahren, die bei Gitlab als Organisation
geplant sind.
Diese Informationen lassen mir keine andere Wahl, als gänzlich auf das Produkt zu verzichten.
#August_2026 #OpenSource #KW_33_2026 #AI_und_ML #Markup #Linux #Rants

Gitlab Act 2 und meine Konsequenzen daraus http://elbosso.codeberg.page/gitlab_act_2_meine_konsequenzen_daraus.html#content

Ich habe kurz nach dem 11. Mai 2026 von den Änderungen erfahren, die bei Gitlab als Organisation
geplant sind.
Diese Informationen lassen mir keine andere Wahl, als gänzlich auf das Produkt zu verzichten.
#August_2026 #OpenSource #KW_33_2026 #AI_und_ML #Markup #Linux #Rants

Gitlab Act 2 und meine Konsequenzen daraus http://elbosso.codeberg.page/gitlab_act_2_meine_konsequenzen_daraus.html#content

Ich habe kurz nach dem 11. Mai 2026 von den Änderungen erfahren, die bei Gitlab als Organisation
geplant sind.
Diese Informationen lassen mir keine andere Wahl, als gänzlich auf das Produkt zu verzichten.
#August_2026 #OpenSource #KW_33_2026 #AI_und_ML #Markup #Linux #Rants

Gitlab Act 2 und meine Konsequenzen daraus http://elbosso.codeberg.page/gitlab_act_2_meine_konsequenzen_daraus.html#content

Ich habe kurz nach dem 11. Mai 2026 von den Änderungen erfahren, die bei Gitlab als Organisation
geplant sind.
Diese Informationen lassen mir keine andere Wahl, als gänzlich auf das Produkt zu verzichten.
#August_2026 #OpenSource #KW_33_2026 #AI_und_ML #Markup #Linux #Rants

Gitlab Act 2 und meine Konsequenzen daraus http://elbosso.codeberg.page/gitlab_act_2_meine_konsequenzen_daraus.html#content

Ich habe kurz nach dem 11. Mai 2026 von den Änderungen erfahren, die bei Gitlab als Organisation
geplant sind.
Diese Informationen lassen mir keine andere Wahl, als gänzlich auf das Produkt zu verzichten.
#August_2026 #OpenSource #KW_33_2026 #AI_und_ML #Markup #Linux #Rants

This week is the #Balisage2026 conference - #XMLisNotDead #markup #declarativeMarkup #XML #MarkupMonday

With XML, the marked-up document is (usually) primary, not the application. You can have multiple applications processing the same documents.

This week is the #Balisage2026 conference - #XMLisNotDead #markup #declarativeMarkup #XML #MarkupMonday

With XML, the marked-up document is (usually) primary, not the application. You can have multiple applications processing the same documents.

This week is the #Balisage2026 conference - #XMLisNotDead #markup #declarativeMarkup #XML #MarkupMonday

With XML, the marked-up document is (usually) primary, not the application. You can have multiple applications processing the same documents.

This week is the #Balisage2026 conference - #XMLisNotDead #markup #declarativeMarkup #XML #MarkupMonday

With XML, the marked-up document is (usually) primary, not the application. You can have multiple applications processing the same documents.

This week is the #Balisage2026 conference - #XMLisNotDead #markup #declarativeMarkup #XML #MarkupMonday

With XML, the marked-up document is (usually) primary, not the application. You can have multiple applications processing the same documents.

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

A survey of little known text markup and templating languages. It omits mainstream ones such as HTML, TeX, and Markdown.

https://brett.coulstock.id.au/markup-language-zoo.html

#MarkupLanguages #markup #text

Other than org-mode – is there another interactivity and productivity focused plain-text markup language that allows me to magically enrich my marked-up notes with interactive elements, automation and such for the CLI/TUI?

Like, most simple markup languages for text (e. g. Markdown) concern themselves with structuring and styling, which is great. Headlines, bold, italics, lists, all that.

And then of course there are myriads of more complex markup languages (e. g. HTML) that are meant to be parsed by a program to provide functionality to the elements you marked up in the text.

The latter is pretty much what I'm looking for; but HTML specifically isn't it, because it's focused on online hypertext documents, and has surprisingly little interactive elements without scripting, much less in the command line/TUI.

I am basically looking for a markup language that is suitable for all kinds of text files I might write on my computer – to-do lists, idea collections, quick notes, structured articles, fiction stories etc. – that comes with a parser/reader/interpreter of sorts that not only adds visible style and structure, but actually makes my marked up elements as interactive, semantic and 'smart' as possible.

Like selectable datetimes, automatic time zone conversion, parsing URLs, interactive checkboxes, to-do entries that can be ticked off and/or archived, proper tables, metadata like title and author, and so on.

I want a semantic-as-fuck markup language.

I feel like org-mode is nearly alone in that niche. It would be almost perfect but I don't use emacs, I don't like how it controls, and outside of the emacs community, there is therefore little support for org-mode, interpreter application-wise.

[Not looking for advice on how to use org-mode or why I should totally give it a chance with tool neofoobar or whatnot, I'm only looking for alternatives. :P]

#MarkupLanguages #Markup #Linux #AskFedi #OrgMode #CommandLine #Tui #Cli

Other than org-mode – is there another interactivity and productivity focused plain-text markup language that allows me to magically enrich my marked-up notes with interactive elements, automation and such for the CLI/TUI?

Like, most simple markup languages for text (e. g. Markdown) concern themselves with structuring and styling, which is great. Headlines, bold, italics, lists, all that.

And then of course there are myriads of more complex markup languages (e. g. HTML) that are meant to be parsed by a program to provide functionality to the elements you marked up in the text.

The latter is pretty much what I'm looking for; but HTML specifically isn't it, because it's focused on online hypertext documents, and has surprisingly little interactive elements without scripting, much less in the command line/TUI.

I am basically looking for a markup language that is suitable for all kinds of text files I might write on my computer – to-do lists, idea collections, quick notes, structured articles, fiction stories etc. – that comes with a parser/reader/interpreter of sorts that not only adds visible style and structure, but actually makes my marked up elements as interactive, semantic and 'smart' as possible.

Like selectable datetimes, automatic time zone conversion, parsing URLs, interactive checkboxes, to-do entries that can be ticked off and/or archived, proper tables, metadata like title and author, and so on.

I want a semantic-as-fuck markup language.

I feel like org-mode is nearly alone in that niche. It would be almost perfect but I don't use emacs, I don't like how it controls, and outside of the emacs community, there is therefore little support for org-mode, interpreter application-wise.

[Not looking for advice on how to use org-mode or why I should totally give it a chance with tool neofoobar or whatnot, I'm only looking for alternatives. :P]

#MarkupLanguages #Markup #Linux #AskFedi #OrgMode #CommandLine #Tui #Cli

Other than org-mode – is there another interactivity and productivity focused plain-text markup language that allows me to magically enrich my marked-up notes with interactive elements, automation and such for the CLI/TUI?

Like, most simple markup languages for text (e. g. Markdown) concern themselves with structuring and styling, which is great. Headlines, bold, italics, lists, all that.

And then of course there are myriads of more complex markup languages (e. g. HTML) that are meant to be parsed by a program to provide functionality to the elements you marked up in the text.

The latter is pretty much what I'm looking for; but HTML specifically isn't it, because it's focused on online hypertext documents, and has surprisingly little interactive elements without scripting, much less in the command line/TUI.

I am basically looking for a markup language that is suitable for all kinds of text files I might write on my computer – to-do lists, idea collections, quick notes, structured articles, fiction stories etc. – that comes with a parser/reader/interpreter of sorts that not only adds visible style and structure, but actually makes my marked up elements as interactive, semantic and 'smart' as possible.

Like selectable datetimes, automatic time zone conversion, parsing URLs, interactive checkboxes, to-do entries that can be ticked off and/or archived, proper tables, metadata like title and author, and so on.

I want a semantic-as-fuck markup language.

I feel like org-mode is nearly alone in that niche. It would be almost perfect but I don't use emacs, I don't like how it controls, and outside of the emacs community, there is therefore little support for org-mode, interpreter application-wise.

[Not looking for advice on how to use org-mode or why I should totally give it a chance with tool neofoobar or whatnot, I'm only looking for alternatives. :P]

#MarkupLanguages #Markup #Linux #AskFedi #OrgMode #CommandLine #Tui #Cli

Other than org-mode – is there another interactivity and productivity focused plain-text markup language that allows me to magically enrich my marked-up notes with interactive elements, automation and such for the CLI/TUI?

Like, most simple markup languages for text (e. g. Markdown) concern themselves with structuring and styling, which is great. Headlines, bold, italics, lists, all that.

And then of course there are myriads of more complex markup languages (e. g. HTML) that are meant to be parsed by a program to provide functionality to the elements you marked up in the text.

The latter is pretty much what I'm looking for; but HTML specifically isn't it, because it's focused on online hypertext documents, and has surprisingly little interactive elements without scripting, much less in the command line/TUI.

I am basically looking for a markup language that is suitable for all kinds of text files I might write on my computer – to-do lists, idea collections, quick notes, structured articles, fiction stories etc. – that comes with a parser/reader/interpreter of sorts that not only adds visible style and structure, but actually makes my marked up elements as interactive, semantic and 'smart' as possible.

Like selectable datetimes, automatic time zone conversion, parsing URLs, interactive checkboxes, to-do entries that can be ticked off and/or archived, proper tables, metadata like title and author, and so on.

I want a semantic-as-fuck markup language.

I feel like org-mode is nearly alone in that niche. It would be almost perfect but I don't use emacs, I don't like how it controls, and outside of the emacs community, there is therefore little support for org-mode, interpreter application-wise.

[Not looking for advice on how to use org-mode or why I should totally give it a chance with tool neofoobar or whatnot, I'm only looking for alternatives. :P]

#MarkupLanguages #Markup #Linux #AskFedi #OrgMode #CommandLine #Tui #Cli

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

Twenty years of #Markdown hindsight, in one markup language: #Carve.

What a "post-Markdown" standard could look like: strictly specified, secure by design, lightweight source for complex HTML/PDF targets.

https://www.dereuromark.de/2026/07/13/twenty-years-of-markdown-hindsight-in-one-markup-language-carve/

#markup #documentation #opensource #php #js #rust

Twenty years of #Markdown hindsight, in one markup language: #Carve.

What a "post-Markdown" standard could look like: strictly specified, secure by design, lightweight source for complex HTML/PDF targets.

https://www.dereuromark.de/2026/07/13/twenty-years-of-markdown-hindsight-in-one-markup-language-carve/

#markup #documentation #opensource #php #js #rust

Twenty years of #Markdown hindsight, in one markup language: #Carve.

What a "post-Markdown" standard could look like: strictly specified, secure by design, lightweight source for complex HTML/PDF targets.

https://www.dereuromark.de/2026/07/13/twenty-years-of-markdown-hindsight-in-one-markup-language-carve/

#markup #documentation #opensource #php #js #rust

Twenty years of #Markdown hindsight, in one markup language: #Carve.

What a "post-Markdown" standard could look like: strictly specified, secure by design, lightweight source for complex HTML/PDF targets.

https://www.dereuromark.de/2026/07/13/twenty-years-of-markdown-hindsight-in-one-markup-language-carve/

#markup #documentation #opensource #php #js #rust

Twenty years of #Markdown hindsight, in one markup language: #Carve.

What a "post-Markdown" standard could look like: strictly specified, secure by design, lightweight source for complex HTML/PDF targets.

https://www.dereuromark.de/2026/07/13/twenty-years-of-markdown-hindsight-in-one-markup-language-carve/

#markup #documentation #opensource #php #js #rust

Mini-QR und Silverbullet neu im Docker-Zoo http://elbosso.codeberg.page/mini_qr_silverbullet_neu_docker_zoo.html#content

Ich habe eine weitere Alternative zum Aufnehmen von
Notizen
in meinen Docker-Zoo aufgenommen
#Virtualisierung #KW_28_2026 #Juli_2026 #Docker #Markup #Linux

Mini-QR und Silverbullet neu im Docker-Zoo http://elbosso.codeberg.page/mini_qr_silverbullet_neu_docker_zoo.html#content

Ich habe eine weitere Alternative zum Aufnehmen von
Notizen
in meinen Docker-Zoo aufgenommen
#Virtualisierung #KW_28_2026 #Juli_2026 #Docker #Markup #Linux

Mini-QR und Silverbullet neu im Docker-Zoo http://elbosso.codeberg.page/mini_qr_silverbullet_neu_docker_zoo.html#content

Ich habe eine weitere Alternative zum Aufnehmen von
Notizen
in meinen Docker-Zoo aufgenommen
#Virtualisierung #KW_28_2026 #Juli_2026 #Docker #Markup #Linux

Mini-QR und Silverbullet neu im Docker-Zoo http://elbosso.codeberg.page/mini_qr_silverbullet_neu_docker_zoo.html#content

Ich habe eine weitere Alternative zum Aufnehmen von
Notizen
in meinen Docker-Zoo aufgenommen
#Virtualisierung #KW_28_2026 #Juli_2026 #Docker #Markup #Linux

Mini-QR und Silverbullet neu im Docker-Zoo http://elbosso.codeberg.page/mini_qr_silverbullet_neu_docker_zoo.html#content

Ich habe eine weitere Alternative zum Aufnehmen von
Notizen
in meinen Docker-Zoo aufgenommen
#Virtualisierung #KW_28_2026 #Juli_2026 #Docker #Markup #Linux

Typesetter è un editor Rust/GTK per Typst con anteprima live, click-to-jump, supporto font variabili e gestione pacchetti integrata #Typesetter #Typst #Markup #Editor #GTK #Rust #Documenti #OpenSource #Software

https://www.linuxeasy.org/typesetter-editor-minimalista-per-documenti-con-typst/?utm_source=mastodon&utm_medium=jetpack_social

Typesetter è un editor Rust/GTK per Typst con anteprima live, click-to-jump, supporto font variabili e gestione pacchetti integrata #Typesetter #Typst #Markup #Editor #GTK #Rust #Documenti #OpenSource #Software

https://www.linuxeasy.org/typesetter-editor-minimalista-per-documenti-con-typst/?utm_source=mastodon&utm_medium=jetpack_social

Typesetter è un editor Rust/GTK per Typst con anteprima live, click-to-jump, supporto font variabili e gestione pacchetti integrata #Typesetter #Typst #Markup #Editor #GTK #Rust #Documenti #OpenSource #Software

https://www.linuxeasy.org/typesetter-editor-minimalista-per-documenti-con-typst/?utm_source=mastodon&utm_medium=jetpack_social

Typesetter è un editor Rust/GTK per Typst con anteprima live, click-to-jump, supporto font variabili e gestione pacchetti integrata #Typesetter #Typst #Markup #Editor #GTK #Rust #Documenti #OpenSource #Software

https://www.linuxeasy.org/typesetter-editor-minimalista-per-documenti-con-typst/?utm_source=mastodon&utm_medium=jetpack_social

Typesetter è un editor Rust/GTK per Typst con anteprima live, click-to-jump, supporto font variabili e gestione pacchetti integrata #Typesetter #Typst #Markup #Editor #GTK #Rust #Documenti #OpenSource #Software

https://www.linuxeasy.org/typesetter-editor-minimalista-per-documenti-con-typst/?utm_source=mastodon&utm_medium=jetpack_social

Experiment der Erzeugung von PlantUML-Diagrammen aus Quelltext http://elbosso.codeberg.page/experiment_erzeugung_plantuml_diagrammen_aus_quelltext.html#content

Heute will ich von einem letztlich gescheiterten Experiment erzählen. Um mal ein Zitat aus einem Song zu benutzen: "Ja, auch das muss ab und zu mal sein!"
#Komponenten #KW_28_2026 #Juli_2026 #Markup #Java

Experiment der Erzeugung von PlantUML-Diagrammen aus Quelltext http://elbosso.codeberg.page/experiment_erzeugung_plantuml_diagrammen_aus_quelltext.html#content

Heute will ich von einem letztlich gescheiterten Experiment erzählen. Um mal ein Zitat aus einem Song zu benutzen: "Ja, auch das muss ab und zu mal sein!"
#Komponenten #KW_28_2026 #Juli_2026 #Markup #Java

Experiment der Erzeugung von PlantUML-Diagrammen aus Quelltext http://elbosso.codeberg.page/experiment_erzeugung_plantuml_diagrammen_aus_quelltext.html#content

Heute will ich von einem letztlich gescheiterten Experiment erzählen. Um mal ein Zitat aus einem Song zu benutzen: "Ja, auch das muss ab und zu mal sein!"
#Komponenten #KW_28_2026 #Juli_2026 #Markup #Java

Experiment der Erzeugung von PlantUML-Diagrammen aus Quelltext http://elbosso.codeberg.page/experiment_erzeugung_plantuml_diagrammen_aus_quelltext.html#content

Heute will ich von einem letztlich gescheiterten Experiment erzählen. Um mal ein Zitat aus einem Song zu benutzen: "Ja, auch das muss ab und zu mal sein!"
#Komponenten #KW_28_2026 #Juli_2026 #Markup #Java

Seen on an image processing development channel:

“binary formats have a lot of advantages. Don't get me wrong. But for stuff which are fundamentally text or some kind of tree or structural (like the structure of an image), a good old XML is just a completely different level of usable.”

#markup #XML

Seen on an image processing development channel:

“binary formats have a lot of advantages. Don't get me wrong. But for stuff which are fundamentally text or some kind of tree or structural (like the structure of an image), a good old XML is just a completely different level of usable.”

#markup #XML

Seen on an image processing development channel:

“binary formats have a lot of advantages. Don't get me wrong. But for stuff which are fundamentally text or some kind of tree or structural (like the structure of an image), a good old XML is just a completely different level of usable.”

#markup #XML

Seen on an image processing development channel:

“binary formats have a lot of advantages. Don't get me wrong. But for stuff which are fundamentally text or some kind of tree or structural (like the structure of an image), a good old XML is just a completely different level of usable.”

#markup #XML

Seen on an image processing development channel:

“binary formats have a lot of advantages. Don't get me wrong. But for stuff which are fundamentally text or some kind of tree or structural (like the structure of an image), a good old XML is just a completely different level of usable.”

#markup #XML