Search
1000 results for “markd”
-
Anyone have a recommendation for a bike computer / web service that lets you easily download data from your rides (in an automated fashion, with some kind of script or CLI tool)?
I have a Garmin one now, which syncs with my phone through their app, and uplaods data to their site ... which, until recently, I was able to pull down data from with some Python. But Garmin seems intent on breaking any third party tools that let its users do that. I searched for other tools that might work with Garmin, but they each had a message at the top of the repo saying, essentially, "This tool no longer works, Garmin broke it."
So I turn to the #BikeTooter / #LazyWeb oracle -- are there any bike computer manufacturers who aren't actively trying to stop their own users from downloading their data? OR any third party sites that allow automated exporting? Strava does have an API, but the only way I could reliably get all the data I wanted was to do a full export, which is a very manual process.
I should explain my use case: I want to keep track of my bike rides, on my own computers.
Current workflow is:
go for a ride,
when I finish, Garmin device syncs (through the phone app) to Garmin's site,
then later I run a script that pulls down any recent rides from Garmin's site,
and wraps them in Markdown and other stuff,
so I can post them over here https://arewehaving.fun/on-a-bike/ (only some rides, most just get archived on a site only I can see)Other requirements: I'd rather not have to plug bike computer into something to get data off of it -- I can barely remember to keep it charged ;-)
-
Via @axelklinger, #GitLab as #OER tool, using #Markdown and producing multiple formats (through @pandoc ?).
https://www.youtube.com/watch?v=0wQKqRXwaWo&t=703sSimilarly, @pascaliensis had mentioned MS-owned GitHub's affordances during this webinar (in French) about OER #repositories and #metadata.
https://www.youtube.com/watch?v=Hc5maU3x368&t=2903sInterestingly enough, #Quebec has its own GitLab instance:
https://forge.gouv.qc.ca/Context: discussion on #OEG Connect @cogdog
https://connect.oeglobal.org/t/input-sought-choosing-using-an-institutional-oer-repository/4317/
-
GPT-5.5 in Codex, after working for over 10 minutes, applied a *robust* markdown separator and a regression test 🤣 I'm going to start calling \n a robust white-space only line separator.
-
GPT-5.5 in Codex, after working for over 10 minutes, applied a *robust* markdown separator and a regression test 🤣 I'm going to start calling \n a robust white-space only line separator.
-
GPT-5.5 in Codex, after working for over 10 minutes, applied a *robust* markdown separator and a regression test 🤣 I'm going to start calling \n a robust white-space only line separator.
-
GPT-5.5 in Codex, after working for over 10 minutes, applied a *robust* markdown separator and a regression test 🤣 I'm going to start calling \n a robust white-space only line separator.
-
GPT-5.5 in Codex, after working for over 10 minutes, applied a *robust* markdown separator and a regression test 🤣 I'm going to start calling \n a robust white-space only line separator.
-
Es ist ein Kaninchenloch.
Heute Teil 1 einer Schulung zu #Lia'Script - ebenfalls #markdown basiert, aber optimiert für die Lehre. Mega.
Und mein Arbeitgeber hat gerade für teuer Geld ein Moodle-System bestellt. Von dem Geld hätte man Software-Lizenzen für Video-Schnitt etc kaufen können und statt des LMS dann LiaScript verwenden. Nuja. Nächstes Mal.
Vielleicht kann man ja auch schon was kombinieren.
-
I went ahead with this and
- switched my blog to djot
- plan to maintain cdjot and gemtext.lua
- marked my smu fork as unmaintained and added a short retro to the readme
- marked my md2gemini fork as unmaintained
- wrote a blog post about it -
Charts in Markdown? Jetzt isser bekloppt geworden ;-) Viel Spaß beim Lesen wie ich in Markdown deterministische Piecharts in meinem ISMS Dokumenten-Workflow baue.
https://blog.jakobs.systems/blog/20260414-charts-in-markdown/
#Markdown #ISMS #pandoc #LaTeX #Charts #Dashboards #Workflow #bash #awk
-
Charts in Markdown? Jetzt isser bekloppt geworden ;-) Viel Spaß beim Lesen wie ich in Markdown deterministische Piecharts in meinem ISMS Dokumenten-Workflow baue.
https://blog.jakobs.systems/blog/20260414-charts-in-markdown/
#Markdown #ISMS #pandoc #LaTeX #Charts #Dashboards #Workflow #bash #awk
-
#LibreOffice #Writer ora supporta #Markdown : conversione diretta tra #docx #odt e #md
-
#LibreOffice #Writer ora supporta #Markdown : conversione diretta tra #docx #odt e #md
-
#LibreOffice #Writer ora supporta #Markdown : conversione diretta tra #docx #odt e #md
-
#LibreOffice #Writer ora supporta #Markdown : conversione diretta tra #docx #odt e #md
-
#LibreOffice #Writer ora supporta #Markdown : conversione diretta tra #docx #odt e #md
-
#Jimmy - Pour exporter toutes vos notes en #Markdown
Des dizaines d'applications supportées ainsi que les principaux formats : #DOCX, #ODT, #HTML, #EPUB, #CSV et même les #Jupyter #Notebooks
https://korben.info/jimmy-convertisseur-notes-markdown-universel.html
-
#Jimmy - Pour exporter toutes vos notes en #Markdown
Des dizaines d'applications supportées ainsi que les principaux formats : #DOCX, #ODT, #HTML, #EPUB, #CSV et même les #Jupyter #Notebooks
https://korben.info/jimmy-convertisseur-notes-markdown-universel.html
-
#Jimmy - Pour exporter toutes vos notes en #Markdown
Des dizaines d'applications supportées ainsi que les principaux formats : #DOCX, #ODT, #HTML, #EPUB, #CSV et même les #Jupyter #Notebooks
https://korben.info/jimmy-convertisseur-notes-markdown-universel.html
-
Looking to migrate an existing website to 11ty. It's predominantly blog content, and the blog posts themselves will be in Markdown. But I'm at a bit of a loss around which template language to use.
I'm very familiar with TSX, so maybe I should stick with that? Is there a reason to use something like Nunjucks instead?
-
@t3dotgg
Everything needs to change.
https://youtu.be/QwShVo0zfuk?si=4bzYwKiMK8shTWpZ
( Ed : In the world of coding and radically so markdown is the new king 👑 )
3/21/2026
-
today on #CreativeCode (ex #kinetic): I redesigned page credits in a way I like best. It's the little "🛎️" bottom -right of https://nonlinear.nyc/dudes/
Next steps are:
- stress test credits
- test markdown on frontmatter description (for longer copy)
- mobile version
- redesign actual credits column
- tags as pills, better popover -
"Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.
The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.
Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."
https://apichangelog.substack.com/p/making-api-documentation-dynamic
#API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience
-
"Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.
The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.
Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."
https://apichangelog.substack.com/p/making-api-documentation-dynamic
#API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience
-
"Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.
The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.
Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."
https://apichangelog.substack.com/p/making-api-documentation-dynamic
#API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience
-
"Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.
The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.
Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."
https://apichangelog.substack.com/p/making-api-documentation-dynamic
#API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience
-
"Consumers want to be able to try an API operation and access concrete example information, or configuration data, such as credentials. Markdown alone isn’t going to provide these elements for you. Fortunately, there’s something else that will, as we’ll see next.
The solution you need is called MDX. It’s a superset of Markdown that lets you embed components within your content. Or just render dynamic information obtained from executing JavaScript. You get to keep the simplicity and versatility of Markdown. But now, you can also use dynamic elements and data. This completely changes the game for API documentation. You can, for instance, embed a component to show the consumer’s API key, or one to make an API request and show its response. This hands-on interactivity helps users test the API faster. And, because of that, it significantly reduces the Time to First Call, or TTFC. Since a low TTFC means the API onboarding experience is excellent, it translates directly into a higher perception of quality. Which is exactly what you’re looking for.
Moving from pure Markdown to MDX doesn’t have to be complicated. However, and especially if you have little coding experience, putting an MDX system together from scratch can be challenging. Luckily, there are many systems that already support MDX. Docusaurus, for instance, supports it by default. Astro is another example of a content system where you can use MDX. There are more options, including commercial ones. What I’d recommend, though, is to check out the official documentation and have a go at the MDX playground."
https://apichangelog.substack.com/p/making-api-documentation-dynamic
#API #APIDocumentation #TechnicalWriting #Markdown #MDX #APIDesign #DX #DeveloperExperience
-
Tác giả AymericZip xây dựng parser Markdown/MDX đa khung (React, Vue, Svelte...) đáp ứng: lightweight, SSR/CSR, hỗ trợ MDX HTML, i18n, type-safe, config linh hoạt. Xử lý front-matter bằng Zod, tích hợp Intlayer cho nội dung đa ngôn ngữ. Demo: renderMarkdown("### Tiêu đề", {h3: (props) => <h3 className="text-xl" {...props}/>}). Ưu điểm: không chain plugin, tải nội dung ngay lập tức (build time). Dùng cho blog, docs, policy, CMS headless. #Markdown #MDX #Intlayer #PhầnMềm #KháiNiệm #Markdown #Chia
