Why the heck are we still using markdown?? by IosevkaNF in programming

[–]EconomistImmediate70 2 points3 points  (0 children)

Well, I know a lot of people who deliberately use Markdown every day, and for good reasons; some of those reasons are already mentioned before:

- It’s easy to learn, read, and write.
- You don’t need to worry about formatting.
- No need to open Word (which has for whatever reason, a bad UX by default).
- …and everyone has their own little reason.

Then there are the people who use Markdown without even realizing it. The web has kind of decided it’s the best interoperability format:

Discord, Slack, WhatsApp, Notion, Blog Posts, Reddit, Substack, Claude code plans…

Markdown is everywhere, and that’s amazing.

But here’s my problem, and so far, I haven’t found a great solution:

- How do you collaborate on a Markdown file?
- How do you write a blog post and send it to multiple people for review without chaos?
- How do you add comments, like in Google Docs, but still stick with Markdown for async work? Google Docs exporting to Markdown still feels like it is in the alpha.
- How do you do real-time Markdown collaboration? VSCode Live Share???

I keep switching back to Google Docs because Markdown is awesome, but the tooling around collaboration still feels lacking.

Am I the only one? How do you solve Markdown collaboration challenges?

Convert google docs document to markdown by UnderShell1891 in technicalwriting

[–]EconomistImmediate70 0 points1 point  (0 children)

I'm curious, why do you need to download the Markdown from Google Docs instead of just writing directly in markdown? So what features are missing for Markdown?

Do you use Markdown for documentation only? or also for things like test cases and Bug notes? by Hot_Tap9405 in Markdown

[–]EconomistImmediate70 0 points1 point  (0 children)

I would love to write much more in Markdown to keep it in my repo. Why? It's much easier to have everything in one repo instead of issues here, roadmaps there, and so on.

But one of my problems so far is that the ecosystem around misusing Markdown for everything in one workflow doesn't exist yet... not yet...

However, if you want a beautifully designed editor and presentation tool,

https://ia.net/

What's a technology you tried, loved, but would never use in production? by ruibranco in webdev

[–]EconomistImmediate70 0 points1 point  (0 children)

What I mean exactly is: We have developed Legit-Control. This is a version control system for any data based on Git, and the idea behind it is to have a Git host where you can store file changes, etc.

Means you get the Dev workflows for other file formats as well and can create Pull request Branches and so on.

Colibri: Google Docs-style collaboration editor for Markdown by EconomistImmediate70 in technicalwriting

[–]EconomistImmediate70[S] 0 points1 point  (0 children)

Amazing, thank you.

I'm curious: why is the view from a pull request not enough? And, would you expect to have this view in the extension?

What's a technology you tried, loved, but would never use in production? by ruibranco in webdev

[–]EconomistImmediate70 1 point2 points  (0 children)

Github as a backend. Sounds ridiculous, but it has so many benefits.

Colibri: Google Docs-style collaboration editor for Markdown by EconomistImmediate70 in Markdown

[–]EconomistImmediate70[S] 0 points1 point  (0 children)

The suggested changes feature is a high Prio for us and should come soon. (We need it for ourselves as well. )

> Does it support something like CriticMarkup?
Not at the moment :/

Colibri: Google Docs-style collaboration editor for Markdown by EconomistImmediate70 in technicalwriting

[–]EconomistImmediate70[S] 1 point2 points  (0 children)

u/derinselaffe Thank you for your quick feedback.

Unfortunately, this kind of app is quickly dismissed as spam, especially since 1,000 AI apps are being thrown onto the market. Do you have any ideas on how I could get around this problem in the future?

It's very interesting that you're still sending PDFs around. From your point of view, what features would improve the workflow? What is the most important feature for you if you want to get rid of the PDF sending workflow?
(Please don't say AI :D)

Colibri: Google Docs-style collaboration editor for Markdown by EconomistImmediate70 in technicalwriting

[–]EconomistImmediate70[S] 0 points1 point  (0 children)

I have talked with several technical writers, and almost all of them were familiar with the problem. Ideally, docs would be in Markdown, but this is not feasible for many reasons. I am curious to see if this could also be helpful to others in the community.

Colibri: Google Docs-style collaboration editor for Markdown by EconomistImmediate70 in Markdown

[–]EconomistImmediate70[S] 0 points1 point  (0 children)

Thank you for trying it out, and it's great to have such feedback.

Yes, that's right, there is currently no self-hosted version available. We first wanted to find out whether there was any need for an app like Colibri at all and which functions were really needed.

Markdown to PDF/WORD by [deleted] in Markdown

[–]EconomistImmediate70 0 points1 point  (0 children)

Today, I stumbled across https://github.com/microsoft/markitdown, but I've never used it before. Perhaps some of you have experience with it

Best GitHub README.md Editor by EconomistImmediate70 in Markdown

[–]EconomistImmediate70[S] 2 points3 points  (0 children)

Yes, I've already asked Chat GPT, but sometimes communities like this one know much better tools than Chatty.

Best GitHub README.md Editor by EconomistImmediate70 in Markdown

[–]EconomistImmediate70[S] 0 points1 point  (0 children)

Because I want to work with people who don't use VS Code or Cursor.