Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is the Dropbox for your rsync.

The hard part in maintaining a website by a team of non-geeks is not a Markdown renderer, but the fact that people have their own preferred tools and workflows, and aren't keen on learning yet another one. All the extra export/import/sync steps are a pain for them, and cause chaos when collaborating. You update the Markdown version, someone else changes the Word version instead, a third person hates Word, and someone else puts notes on GitHub, and now you need to train half a dozen people how to clone a repo and how to fix a detached head.



Markdown though looks like a really constraining medium.


Why would you want there to be a separate upload and file sync step instead of simply editing in the browser?


Versioning? Publishing workflow?

People might like to pass around a draft before publishing an article. Maybe to an editor for feedback. That’s easiest done with a Word document.

Then, when you’re ready to publish, just save the file to the right location. It’s easier than opening an CMS and copying/pasting (marginally).




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: