Search
77 results for “MarkDW”
-
-
-
-
-
-
I’m kind of jealous of those of you on a #Mastodon instance with #Markdown support. (https://ilye.ss/notes/202609262230/)
-
I’m kind of jealous of those of you on a #Mastodon instance with #Markdown support. (https://ilye.ss/notes/202609262230/)
-
I’m kind of jealous of those of you on a #Mastodon instance with #Markdown support. (https://ilye.ss/notes/202609262230/)
-
I’m kind of jealous of those of you on a #Mastodon instance with #Markdown support. (https://ilye.ss/notes/202609262230/)
-
I’m kind of jealous of those of you on a #Mastodon instance with #Markdown support. (https://ilye.ss/notes/202609262230/)
-
✨ Trending new AI project on GitHub:
amitshekhariitbhu/ai-system-design — 447★ · Markdown
« AI System Design - Learn how to design AI systems built on LLMs, RAG, and AI Agents step by step. »Discovered in today's radar:
https://olud.ai/latest.html -
✨ Trending new AI project on GitHub:
amitshekhariitbhu/ai-system-design — 447★ · Markdown
« AI System Design - Learn how to design AI systems built on LLMs, RAG, and AI Agents step by step. »Discovered in today's radar:
https://olud.ai/latest.html -
✨ Trending new AI project on GitHub:
amitshekhariitbhu/ai-system-design — 447★ · Markdown
« AI System Design - Learn how to design AI systems built on LLMs, RAG, and AI Agents step by step. »Discovered in today's radar:
https://olud.ai/latest.html -
✨ Trending new AI project on GitHub:
amitshekhariitbhu/ai-system-design — 447★ · Markdown
« AI System Design - Learn how to design AI systems built on LLMs, RAG, and AI Agents step by step. »Discovered in today's radar:
https://olud.ai/latest.html -
✨ Trending new AI project on GitHub:
amitshekhariitbhu/ai-system-design — 447★ · Markdown
« AI System Design - Learn how to design AI systems built on LLMs, RAG, and AI Agents step by step. »Discovered in today's radar:
https://olud.ai/latest.html -
Papier ist so was von ... Aber damit stehe ich schon seit 15 Jahren auf dem Kriegsfuß.
Egal, 1 - 3 x im Jahr muss ich so einen Fensterbriefumschlag verschicken.
Habe jetzt auf die Schnelle keine Writer-Vorlage mit den typischen Falzmarken links entdeckt. Falls es nicht doch schon eine gibt, kann ich meine freigeben.
Haupttext in Markdown und dann einfach reinkopieren passt für mich - mehr Automatisierung lohnt sich nicht :-)
-
Papier ist so was von ... Aber damit stehe ich schon seit 15 Jahren auf dem Kriegsfuß.
Egal, 1 - 3 x im Jahr muss ich so einen Fensterbriefumschlag verschicken.
Habe jetzt auf die Schnelle keine Writer-Vorlage mit den typischen Falzmarken links entdeckt. Falls es nicht doch schon eine gibt, kann ich meine freigeben.
Haupttext in Markdown und dann einfach reinkopieren passt für mich - mehr Automatisierung lohnt sich nicht :-)
-
Papier ist so was von ... Aber damit stehe ich schon seit 15 Jahren auf dem Kriegsfuß.
Egal, 1 - 3 x im Jahr muss ich so einen Fensterbriefumschlag verschicken.
Habe jetzt auf die Schnelle keine Writer-Vorlage mit den typischen Falzmarken links entdeckt. Falls es nicht doch schon eine gibt, kann ich meine freigeben.
Haupttext in Markdown und dann einfach reinkopieren passt für mich - mehr Automatisierung lohnt sich nicht :-)
-
Papier ist so was von ... Aber damit stehe ich schon seit 15 Jahren auf dem Kriegsfuß.
Egal, 1 - 3 x im Jahr muss ich so einen Fensterbriefumschlag verschicken.
Habe jetzt auf die Schnelle keine Writer-Vorlage mit den typischen Falzmarken links entdeckt. Falls es nicht doch schon eine gibt, kann ich meine freigeben.
Haupttext in Markdown und dann einfach reinkopieren passt für mich - mehr Automatisierung lohnt sich nicht :-)
-
Papier ist so was von ... Aber damit stehe ich schon seit 15 Jahren auf dem Kriegsfuß.
Egal, 1 - 3 x im Jahr muss ich so einen Fensterbriefumschlag verschicken.
Habe jetzt auf die Schnelle keine Writer-Vorlage mit den typischen Falzmarken links entdeckt. Falls es nicht doch schon eine gibt, kann ich meine freigeben.
Haupttext in Markdown und dann einfach reinkopieren passt für mich - mehr Automatisierung lohnt sich nicht :-)
-
Check out #tinydot for #publishing your #minimalist #digitalGarden online:
- Ukrainian developer living in the US
- Very responsive to feedback
- Rolls out requested features in days
- Free plan comes w/ 1GB storage
- RSS feed
- New themes soon
- You sign in with #Apple (Web, Mac, iOS app) & your markdown files can be accessed in Finder in a folder called tinydot
- You can keep editing your markdown files in your fav editor & they are published instantly -
@antoinechambertloir @MonniauxD @MatsuBasho Et là dessus, on est là en licence pour essayer d'enseigner la puissance de la ligne de commande (make, script,...) + l'importance de l'approche au #format balise (TeX, LaTeX, Markdown,...) pour séparer contenu et mise en forme + la bibliographie (#format BibLaTeX, Zotero, Jabref) ...mais c'est généré sans connaissance, avec quelques prompts prompts, « et voilà ! ».
(Si je cite groff, c'est autre planète ; quant à refer l'élégant, c'est autre univers). -
@antoinechambertloir @MonniauxD @MatsuBasho Et là dessus, on est là en licence pour essayer d'enseigner la puissance de la ligne de commande (make, script,...) + l'importance de l'approche au #format balise (TeX, LaTeX, Markdown,...) pour séparer contenu et mise en forme + la bibliographie (#format BibLaTeX, Zotero, Jabref) ...mais c'est généré sans connaissance, avec quelques prompts prompts, « et voilà ! ».
(Si je cite groff, c'est autre planète ; quant à refer l'élégant, c'est autre univers). -
@antoinechambertloir @MonniauxD @MatsuBasho Et là dessus, on est là en licence pour essayer d'enseigner la puissance de la ligne de commande (make, script,...) + l'importance de l'approche au #format balise (TeX, LaTeX, Markdown,...) pour séparer contenu et mise en forme + la bibliographie (#format BibLaTeX, Zotero, Jabref) ...mais c'est généré sans connaissance, avec quelques prompts prompts, « et voilà ! ».
(Si je cite groff, c'est autre planète ; quant à refer l'élégant, c'est autre univers). -
@antoinechambertloir @MonniauxD @MatsuBasho Et là dessus, on est là en licence pour essayer d'enseigner la puissance de la ligne de commande (make, script,...) + l'importance de l'approche au #format balise (TeX, LaTeX, Markdown,...) pour séparer contenu et mise en forme + la bibliographie (#format BibLaTeX, Zotero, Jabref) ...mais c'est généré sans connaissance, avec quelques prompts prompts, « et voilà ! ».
(Si je cite groff, c'est autre planète ; quant à refer l'élégant, c'est autre univers). -
@antoinechambertloir @MonniauxD @MatsuBasho Et là dessus, on est là en licence pour essayer d'enseigner la puissance de la ligne de commande (make, script,...) + l'importance de l'approche au #format balise (TeX, LaTeX, Markdown,...) pour séparer contenu et mise en forme + la bibliographie (#format BibLaTeX, Zotero, Jabref) ...mais c'est généré sans connaissance, avec quelques prompts prompts, « et voilà ! ».
(Si je cite groff, c'est autre planète ; quant à refer l'élégant, c'est autre univers). -
Almost two years ago I wrote an #SSG in #go. I rewrote all my course materials in markdown, they used to be #XML/#docbook. I was quite satisfied with myself, except for one thing.
Teaching webdev, programming and databases, I have many code examples in the materials, and I had to copy/paste them into the md files. Code changes, so copy paste is a loop. But it worked.
As you may have noticed recently I was playing with GUI in go. To document my endeavours I habitually make course materials, as if I was going to teach it.
I got fed up with copy pasting, so as a detour in the GUI work, I have written an include mechanism into my SSG so that the build process includes the current content of the code files.
<42>filepath</42> into the md files. Today it was tested, and tomorrow in will be merged into the main branch.
One thing remains as a follow up. The color coding of the syntax depending on language.
All quite useful, almost as if I was still working ;-) -
Almost two years ago I wrote an #SSG in #go. I rewrote all my course materials in markdown, they used to be #XML/#docbook. I was quite satisfied with myself, except for one thing.
Teaching webdev, programming and databases, I have many code examples in the materials, and I had to copy/paste them into the md files. Code changes, so copy paste is a loop. But it worked.
As you may have noticed recently I was playing with GUI in go. To document my endeavours I habitually make course materials, as if I was going to teach it.
I got fed up with copy pasting, so as a detour in the GUI work, I have written an include mechanism into my SSG so that the build process includes the current content of the code files.
<42>filepath</42> into the md files. Today it was tested, and tomorrow in will be merged into the main branch.
One thing remains as a follow up. The color coding of the syntax depending on language.
All quite useful, almost as if I was still working ;-) -
Almost two years ago I wrote an #SSG in #go. I rewrote all my course materials in markdown, they used to be #XML/#docbook. I was quite satisfied with myself, except for one thing.
Teaching webdev, programming and databases, I have many code examples in the materials, and I had to copy/paste them into the md files. Code changes, so copy paste is a loop. But it worked.
As you may have noticed recently I was playing with GUI in go. To document my endeavours I habitually make course materials, as if I was going to teach it.
I got fed up with copy pasting, so as a detour in the GUI work, I have written an include mechanism into my SSG so that the build process includes the current content of the code files.
<42>filepath</42> into the md files. Today it was tested, and tomorrow in will be merged into the main branch.
One thing remains as a follow up. The color coding of the syntax depending on language.
All quite useful, almost as if I was still working ;-) -
Almost two years ago I wrote an #SSG in #go. I rewrote all my course materials in markdown, they used to be #XML/#docbook. I was quite satisfied with myself, except for one thing.
Teaching webdev, programming and databases, I have many code examples in the materials, and I had to copy/paste them into the md files. Code changes, so copy paste is a loop. But it worked.
As you may have noticed recently I was playing with GUI in go. To document my endeavours I habitually make course materials, as if I was going to teach it.
I got fed up with copy pasting, so as a detour in the GUI work, I have written an include mechanism into my SSG so that the build process includes the current content of the code files.
<42>filepath</42> into the md files. Today it was tested, and tomorrow in will be merged into the main branch.
One thing remains as a follow up. The color coding of the syntax depending on language.
All quite useful, almost as if I was still working ;-)