I had a sudden "what if…?" intuition for a potential #productivity speedup in my #opensource bug reporting workflow when tables of data are involved, and… it turns out that it is actually possible.
As you can see in this short demonstration I recorded below, you can paste #LibreOffice#spreadsheet cells into a #GitLab ticket, and it automatically converts it to a proper #MarkDown table. It just works! What is this sorcery!? 🤯 What a time to be alive.
You have to realize that this is a Trojan horse strategy. Like, you want the docs to be the product, fine. This is what all tech writers want eventually. But be very careful about the product not being, for example, the pipelines or the site you’re gonna render. I mean, that might be part of the product. The product is the docs, right? But you have to enter a software company with Markdown with that mindset. Otherwise it will just turn into something that’s not even a feature, and lose importance.
The value of Markdown is that it allow us to enter with very low friction into worlds that maybe haven’t even thought about docs.”" https://passo.uno/pros-cons-markdown/
Is there interest in a #foss static #forum software? Yes, you heard that right.
Thinking about creating a system for basically periodically scanning the inbox of a mail account, creating a #markdown draft which then can get approved or rejected by simply moving it to the appropiate folder. A #cronjob is then picking it up and compiling the forum page again.
This would work with mailto links, so any email editor is already the writing tool.
I just discovered that @MonaApp will save the Alt Text in the captions when saving a photo. It makes sense, since it also copies the caption into Alt Text. This should be more common. Are there other Mastodon apps with this feature?
Not posted on here in a while - What's everyone's thoughts on @tana vs @logseq - online vs offline etc. etc. Kind of flipflopping between one and the other at the moment
@ednico I’m looking forward to trying #Logseq again for my tasks and short-term notes after the database version comes out, which I’m hoping will fix the syncing issues.
(I just hope it doesn’t take as long as Bear 2 did…)
For my long term/permanent notes, I expect to remain completely committed to #Obsidian and its local, interoperable plaintext #markdown files.
Check your #Hugo#Markdown postings for a number of common problems and issues before publishing a post.
Each part is configurable. Probably works with tools like #Jekyll too. Works standalone, or as #git pre-commit check. And comes with a suite of tests if you want to add new checks.
This is a pain in the butt to read (before: hard-wrapped, after: unbroken). Yes, this applies to #Markdown files especially. Burn me at the stake if you want, but Markdown embedded in source files is not an exception.
VitePress is a Static Site Generator (SSG) that takes #Markdown, applies a theme to it, and generates static HTML pages. Built on #Vue. #JavaScript#VueJS
Using Markdown to create slides? Why not? With presenter notes and a presenter view with preview of the next slide? Sure! https://marp.app has you covered.
Dis Internet tu utilises quoi comme éditeur #markdown sous Windows ? J'utilisais Ghostwriter mais il semble ne plus fonctionner. J'ai bien trouvé Atom mais je cherche mieux.
Vous avez ça ?
VERY disappointed in GitHub refusing to support the LaTeX \colorbox (outright banned) or \textcolor macros (seemingly only very limited support) or any CSS solution to allow one to create colored text in Markdown files... I was hoping to create color swatches as shown in the attached preview (in VSCode), but just none of this works on GitHub...
(And yes, I understand there're some potential accessibility issues, but there're more social solutions to address these than an outright technical ban of colored text! It's 2024!)
Now, all users can get is a boring list of color names with their hex values sans pre-visualization... 😤😭
Nach einem Windows-Update heute Morgen funktioniert mein @obsidian nicht mehr. Meeehh. Ich habe noch keine Idee, wie das zu fixen wäre.
Was bin ich froh, dass ich mich für ein System entschieden habe, das mit #Markdown-Dateien arbeitet. So kann ich - leicht eingeschränkt - weiterarbeiten, bis das #Obsidian-Problem gelöst ist.
You can now write your Markdown in separate .fragment.md files and import() them as if they were JavaScript modules, just like you can with HTML and CSS fragments.
And while they don’t support props, they do support slots (including named slots, which you can use as poor man’s props.)
Quick heads up: I’ve just deployed a fix that escapes backticks in Markdown fragments and generally makes the Markdown fragment support more robust in Kitten.
(Remember that updating Kitten is as easy as running kitten update from the command-line. Or just run the one-line installation command again from the Install section of the site, whichever you find easiest. Either way, it literally only takes a couple of seconds.)