Hello weekend 😊

Typst Documentation
https://typst.app/docs/reference/html/

#markup #typst

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/

It occurs to Us that just how horrible the #markup situation for #Matrix is isn't very common or accessible knowledge, so here's a summary from a nerd who loves tinkering with markup.

For background, unlike the common asmuption, Matrix doesn't actually work with #MarkDown (#CommonMark), but defines a narrow set of HTML tags and attributes to be supported and it's the client's job to convert markdown to HTML before sending. And, before We say anything bad about it, We absolutely love the idea, if it were executed properly, it would completely blow every other chat platform out of the water with how powerful the markup is while remaining just as accessible to the average user.

Of course, this is #mtarix we're talking about, so what actually happens is that
1. "Implement any of these tags at your convenience. We do not care how many or which." ( https://spec.matrix.org/latest/client-server-api/#mroommessage-msgtypes )and
2. even if you follow the """strongly advised""" set to a tee, there's still so much behavior left undefined that even when things are "supported", there is no guarantee that anything but the most basic of markup will result in messages that look anything alike.

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

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

Спустя несколько лет использования #neorg я незаметно для себя перешёл от идеи формата разметки с [развитой системой ссылок](https://mastodon.ml/@mintbug/114072074832481412) (привет, #norg) к идее формата, которому можно скормить что угодно и назвать это ссылкой (#markdown, иди нахуй), ибо все проблемы решаются [кастомными](https://mastodon.ml/@mintbug/115833182576699583) uri-[схемами](https://mastodon.ml/@mintbug/114015148511221715). Впрочем, когда мы имеем дело с полноценным языком программирования (привет, #typst), мы можем не только без боли использовать строки с возможностью экранирования, но и расширить его собственные возможности.

#uri #pkm #markup

New hVmark Release: v1.5.0

I added something that probably should’ve been deployed with subheadings:
horizontal rules (---, ***, ___)
Better late than never.

GitHub: https://github.com/HisVirusness/hvmark
Docs: https://hisvirusness.com/hvmark#2025-12-29-v1-5-0

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

#markup #webdev #indieweb #smallweb #esolang

hVmark, the custom markup language behind HisVirusness.com, is officially FOSS.

https://hisvirusness.com/now#hvmark-is-officially-foss

#markup #markdown #marksideways #github #foss #webdev #indieweb #smallweb