#markup — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #markup, aggregated by home.social.
-
@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
-
@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
-
@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
-
@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
-
@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
-
#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 -
#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 -
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’
-
YAML s highly-underrated. Just sayin’
-
YAML s highly-underrated. Just sayin’
-
YAML s highly-underrated. Just sayin’
-
YAML s highly-underrated. Just sayin’
-
“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
-
“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
-
“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
-
“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
-
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.
-
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.
-
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;
}
} -
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;
}
} -
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;
}
} -
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;
}
} -
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
-
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
-
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
-
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
-
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:
-
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
-
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
-
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
-
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
-
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
"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 -
"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
