Show HN: Fiddle.md – a collaborative writing tool by Swipe
1–10 of 71 posts
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#2Nice UX, I really like it!
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#3> Over Quota
> This application is temporarily over its serving quota. Please try again later.
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#4Collaborative editing is great, and I wonder if this project could be adapted as some sort of browser extension that would allow teams to collaboratively edit on pages that don't otherwise support it.
For instance, the project-management software my team currently uses does not allow us to collaboratively edit tickets. Sometimes we've resorted to writing tickets together in Google Docs and then transferring the text back into the project-management tool. It would be awesome if we could use Fiddle.md or a similar tool right there on the page, rather than having to transfer text between tabs.
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#5> Over Quota > This application is temporarily over its serving quota. Please try again later.
We're working on fixing that now. It should be back up very soon!
Edit: It's back. Thanks for the patience.
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#6These types of projects are all really awesome; I just wish they would support RestructuredText.
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#7Looks interesting... Dark theme?
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#8Would be nice if the tab key inserted a tab instead of jumping to the next field (for writing code, etc).
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#9I'm a fan of this - elegant and simple way to make markdown more accessible to those who would otherwise shy away from it's learning curve
Re: Show HN: Fiddle.md – a collaborative writing tool by Swipe
#10Would be nice if the tab key inserted a tab instead of jumping to the next field (for writing code, etc).
Thanks for the feedback. That is something we discussed, and we have it on the list of upcoming improvements.