#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

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_

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.

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

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

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

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

TIL about Cooklang – Recipe Markup Language https://cooklang.org/ 'Cooklang is a simple, human-readable text format for writing recipes that can be understood by both cooks and computers.'
#markup #cooking

TIL about Cooklang – Recipe Markup Language https://cooklang.org/ 'Cooklang is a simple, human-readable text format for writing recipes that can be understood by both cooks and computers.'
#markup #cooking

Neue Plugins in meiner neovim-Konfiguration http://elbosso.codeberg.page/neue_plugins_meiner_neovim_konfiguration.html#content

Nachdem ich das letzte Mal darüber
berichtet habe,
dass einige Plugins aus meiner
neovim-Konfiguration
rausgeflogen sind, habe ich nun mal wieder zwei neue darin aufgenommen
#OpenSource #KW_27_2026 #Juni_2026 #Markup #Linux

Neue Plugins in meiner neovim-Konfiguration http://elbosso.codeberg.page/neue_plugins_meiner_neovim_konfiguration.html#content

Nachdem ich das letzte Mal darüber
berichtet habe,
dass einige Plugins aus meiner
neovim-Konfiguration
rausgeflogen sind, habe ich nun mal wieder zwei neue darin aufgenommen
#OpenSource #KW_27_2026 #Juni_2026 #Markup #Linux

🚨🚀 BREAKING: "HTML is a native image format" says a brave soul who clearly never met #SVG or heard of "efficiency." 🤦‍♂️ Because when life gives you pixels, you should definitely turn them into an incomprehensible soup of #markup and JS. 🍜🔍
https://hmml.eddocu.com #HTMLImageFormat #Efficiency #DevHumor #HackerNews #ngated

🚨🚀 BREAKING: "HTML is a native image format" says a brave soul who clearly never met #SVG or heard of "efficiency." 🤦‍♂️ Because when life gives you pixels, you should definitely turn them into an incomprehensible soup of #markup and JS. 🍜🔍
https://hmml.eddocu.com #HTMLImageFormat #Efficiency #DevHumor #HackerNews #ngated

HASC NDAA markup challenges Space Force on satellite programs
https://atlas.whatip.xyz/post.php?slug=hasc-ndaa-markup-challenges-space-force-on-satellite-programs
<p>House Armed Services Committee seeks to preserve a missile-warning satellite program the Pentagon wants
#challenges #satellite #programs #markup

I’ve been trying to post (not always in the same place) about the usefulness of text #markup for documents - #XML especially - using the tag #MarkupMonday each time.

The goal is to spread awareness that XML, and declarative markup, labelling of parts, is in active use, and yes is worth doing, in the right place.

There was some push-back on the xml-dev (reborn) mailing list against XML being useful in a world with LLMs in it, which was discouraging.

But i stick by it: XML is not dead! 😉

I’ve been trying to post (not always in the same place) about the usefulness of text #markup for documents - #XML especially - using the tag #MarkupMonday each time.

The goal is to spread awareness that XML, and declarative markup, labelling of parts, is in active use, and yes is worth doing, in the right place.

There was some push-back on the xml-dev (reborn) mailing list against XML being useful in a world with LLMs in it, which was discouraging.

But i stick by it: XML is not dead! 😉

@yantar92 @screwlisp I know.

However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.

That's totally different perspective and the way non Org people stumble over information.

After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.

https://karl-voit.at/2021/11/27/orgdown/

I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.

YMMV

#LML #publicvoit

@yantar92 @screwlisp I know.

However, I think you've got the Org point of view perspective and I want to promote Orgdown to people who will never hear of Emacs or are even opposing the use of Emacs. Totally different turf and hosting information at org or worg doesn't help here.

That's totally different perspective and the way non Org people stumble over information.

After all, the #Emacs community never differentiated the tool #Orgmode from the much more general lightweight #markup language #Orgdown. The focus of #OD is the latter and I want to promote that by mostly neglecting any connection to Emacs, Elisp and the communities involved. Not directing people to the mixup of information on Orgmode.org was a very deliberate decision of mine.

https://karl-voit.at/2021/11/27/orgdown/

I know that some org community people disagree with my approach for various reasons. Some of the arguments do have real substance, most rather not.

YMMV

#LML #publicvoit

#Business #Findings
What SEOs get wrong about AI search · “SEOs agree on what to do, but not what to call it.” https://ilo.im/16c7ig

_____
#AI #SearchEngine #SEO #FAQs #Content #Citations #Communities #Authority #Schema #Markup

#Business #Findings
What SEOs get wrong about AI search · “SEOs agree on what to do, but not what to call it.” https://ilo.im/16c7ig

_____
#AI #SearchEngine #SEO #FAQs #Content #Citations #Communities #Authority #Schema #Markup

Markup l’app per iOS per evidenziare il testo e fare riassunti, ecco un abbonamento a vita #markup #appstore

https://www.melamorsicata.it/2021/02/02/markup-lapp-per-ios-per-evidenziare-il-testo-e-fare-riassunti-ecco-un-abbonamento-a-vita/

Markup l’app per iOS per evidenziare il testo e fare riassunti, ecco un abbonamento a vita #markup #appstore

https://www.melamorsicata.it/2021/02/02/markup-lapp-per-ios-per-evidenziare-il-testo-e-fare-riassunti-ecco-un-abbonamento-a-vita/

Marbella gardener stunned by €10k hidden markup on second-hand car from Sevilla dealership https://www.allforgardening.com/1700265/marbella-gardener-stunned-by-e10k-hidden-markup-on-second-hand-car-from-sevilla-dealership/ #Car #ConsumerFinancing #garden #gardener #gardening #MarkUp #NewsSpain #newspaper #Santander #TheOlivePress

Marbella gardener stunned by €10k hidden markup on second-hand car from Sevilla dealership https://www.allforgardening.com/1700265/marbella-gardener-stunned-by-e10k-hidden-markup-on-second-hand-car-from-sevilla-dealership/ #Car #ConsumerFinancing #garden #gardener #gardening #MarkUp #NewsSpain #newspaper #Santander #TheOlivePress

YAML s highly-underrated. Just sayin’

#programming #markup

YAML s highly-underrated. Just sayin’

#programming #markup

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

“Why The Heck Are We Still Using Markdown?”, Burak Güngör (https://bgslabs.org/blog/why-are-we-using-markdown/).

Via HN: https://news.ycombinator.com/item?id=47629903

On Lobsters: https://lobste.rs/s/nn403y/why_heck_are_we_still_using_markdown

#Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

New hVmark Release: v1.6.0

I added two new markers: code and centered text. And the latter accomplishes the task in the most deprecated way possible.

https://github.com/HisVirusness/hvmark

hVmark is my tiny, opinionated markup language: MIT-licensed, intentionally strict, and built to power HisVirusness.com.

#markup #webdev #indieweb #smallweb #esolang #markdown

@pepelsbey

1. Open "about:support"
2. Find "Profile Folder"
3. Open this and create there folder "chrome" (yes, chrome) with file "userContent.css"
4. Write specific CSS:

@-moz-document url-prefix("chrome://devtools/content/") {
.devtools-monospace {
font-family: "JetBrainsMono-Regular", "JetBrains Mono", monospace !important;
}

.inspector-panel #markup-view {
font-family: "JetBrainsMono-Regular", "JetBrains Mono", monospace !important;
}
}

@pepelsbey

1. Open "about:support"
2. Find "Profile Folder"
3. Open this and create there folder "chrome" (yes, chrome) with file "userContent.css"
4. Write specific CSS:

@-moz-document url-prefix("chrome://devtools/content/") {
.devtools-monospace {
font-family: "JetBrainsMono-Regular", "JetBrains Mono", monospace !important;
}

.inspector-panel #markup-view {
font-family: "JetBrainsMono-Regular", "JetBrains Mono", monospace !important;
}
}

Ik werk steeds vaker met Markup (md) files in plaats van doc of odf.

Dat levert kleinere bestanden op die ook zonder speciale software (Word, Libreoffice) nog te lezen (en bewerken) zijn.

Die omvang voor dat ene bestand maakt niet zo veel uit, maar als je er honderden of meer hebt, dan scheelt dat enorm.

Tevens voor de toekomst minder afhankelijk van de dan beschikbare software.

Geïnspireerd door dit artikel van @martijnaslander

https://world.hey.com/martijnaslander/de-meedogenloze-consequenties-van-digitaliseren-in-plaats-van-informatiseren-08eef934

#markup #archivering #digitale

Ik ga steeds vaker over op Markup (MD) files in plaats van doc(x) of odf.

Het levert n.l. vele malen kleinere bestanden op die zonder speciale software (Word, Libreoffice) te lezen (en bewerken) is.

Die omvang voor dat ene bestand maakt niet zo veel uit, maar als je er honderden, duizenden of nog meer hebt, dan scheelt dat enorm.

En je maakt je er voor de toekomst minder afhankelijk van de dan beschikbare software.

Meer hierover:

https://world.hey.com/martijnaslander/de-meedogenloze-consequenties-van-digitaliseren-in-plaats-van-informatiseren-08eef934

#markup #archivering #digitale

You can use this site to refresh your markdown skills
On this Server we can write with the beautiful markdown attributes in our toots. I also use markdown when I make my descriptions on GitHub.

#Markdown #syntax #language #markup #programming #GitHub #technology

https://www.markdownguide.org/basic-syntax/

You can use this site to refresh your markdown skills
On this Server we can write with the beautiful markdown attributes in our toots. I also use markdown when I make my descriptions on GitHub.

#Markdown #syntax #language #markup #programming #GitHub #technology

https://www.markdownguide.org/basic-syntax/

Call for papers: https://balisage.net/index.html

Information representation is about more than HTML and JSON...

Balisage is the most theoretical of the markup conferences (Nothing is more practical than a good theory). And this is the last.

No! While that tree stands, our scholar-gypsy is not gone! as Vaughan Williams quoted Matthew Arnold.

Don’t miss your last chance! to speak, to listen, to learn, to teach, to be.

#XML #MarkupMonday #Balisage2026 #Balisage #markup

Call for papers: https://balisage.net/index.html

Information representation is about more than HTML and JSON...

Balisage is the most theoretical of the markup conferences (Nothing is more practical than a good theory). And this is the last.

No! While that tree stands, our scholar-gypsy is not gone! as Vaughan Williams quoted Matthew Arnold.

Don’t miss your last chance! to speak, to listen, to learn, to teach, to be.

#XML #MarkupMonday #Balisage2026 #Balisage #markup

"If mark_up_ is complicated, then the opposite of that complexity must be… markd_own_. This kind of solution, where it’s so smart it seems obvious in hindsight, is key to Markdown’s success. John worked to make a format that was so simple that anybody could pick it up in a few minutes, and powerful enough that it could help people express pretty much anything that they wanted to include while writing on the internet. At a technical level, it was also easy enough to implement that John could write the code himself to make it work with Movable Type, his publishing tool of choice. (Within days, people had implemented the same feature for most of the other blogging tools of the era; these days, virtually every app that you can type text into ships with Markdown support as a feature on day one.)

Prior to launch, John had enlisted our mutual friend, the late, dearly missed Aaron Swartz, as a beta tester. In addition to being extremely fluent in every detail of the blogging technologies of the time, Aaron was, most notably, seventeen years old. And though Aaron’s activism and untimely passing have resulted in him having been turned into something of a mythological figure, one of the greatest things about Aaron was that he could be a total pain in the ass, which made him terrific at reporting bugs in your software. (One of the last email conversations I ever had with Aaron was him pointing out some obscure bugs in an open source app I was working on at the time.) No surprise, Aaron instantly understood both the potential and the power of Markdown, and was a top-tier beta tester for the technology as it was created. His astute feedback helped finely hone the final product so it was ready for the world, and when Markdown quietly debuted in March of 2004, it was clear that text files around the web were about to get a permanent upgrade."
https://www.anildash.com/2026/01/09/how-markdown-took-over-the-world/
#Markdown #AI #GenerativeAI #SoftwareDevelopment #HTML #WebDevelopment #MarkUp #Documentation #SoftwareDocumentation

"If mark_up_ is complicated, then the opposite of that complexity must be… markd_own_. This kind of solution, where it’s so smart it seems obvious in hindsight, is key to Markdown’s success. John worked to make a format that was so simple that anybody could pick it up in a few minutes, and powerful enough that it could help people express pretty much anything that they wanted to include while writing on the internet. At a technical level, it was also easy enough to implement that John could write the code himself to make it work with Movable Type, his publishing tool of choice. (Within days, people had implemented the same feature for most of the other blogging tools of the era; these days, virtually every app that you can type text into ships with Markdown support as a feature on day one.)

Prior to launch, John had enlisted our mutual friend, the late, dearly missed Aaron Swartz, as a beta tester. In addition to being extremely fluent in every detail of the blogging technologies of the time, Aaron was, most notably, seventeen years old. And though Aaron’s activism and untimely passing have resulted in him having been turned into something of a mythological figure, one of the greatest things about Aaron was that he could be a total pain in the ass, which made him terrific at reporting bugs in your software. (One of the last email conversations I ever had with Aaron was him pointing out some obscure bugs in an open source app I was working on at the time.) No surprise, Aaron instantly understood both the potential and the power of Markdown, and was a top-tier beta tester for the technology as it was created. His astute feedback helped finely hone the final product so it was ready for the world, and when Markdown quietly debuted in March of 2004, it was clear that text files around the web were about to get a permanent upgrade."
https://www.anildash.com/2026/01/09/how-markdown-took-over-the-world/
#Markdown #AI #GenerativeAI #SoftwareDevelopment #HTML #WebDevelopment #MarkUp #Documentation #SoftwareDocumentation

Two markup/XML conferences announced today

XML Prague - https://www.xmlprague.cz/ in... er... Prague... and

26th annual meeting of the Text Encoding Initiative (TEI) https://tei2026.tei-c.org/ in Vancouver.

Don’t forget also Balisage - https://www.balisage.net/

#MarkupMonday #TEI #tei2026 #XML #XMLPrague #XML_Prague #conference #balisage #markup #digitalHumanities #techDoc

John Macfarlane, professeur en philosophie à l'Université de Californie (Berkeley) et créateur de Pandoc sera à l'Université de Rouen Normandie demain jeudi 29 janvier 2026, pour parler de Pandoc.
(Ce n'est pas moi qui organise mais je serai le modérateur pour la conférence l'après-midi.)
Informations :
https://ceen.hypotheses.org/2472
#pandoc #markup