4 ms·
No, this isn't always true. I have hated every WYSIWYG intranet my employer has used. I just want to write Markdown. Luckily, we also had access to a file ser
by suprjami 2y ago
No, this isn't always true.
I have hated every WYSIWYG intranet my employer has used. I just want to write Markdown.
Luckily, we also had access to a file server with ~/public_html and httpd with PHP.
So I just threw PHP Markdown Extra and a htaccess file up, now I can write in Markdown and it magically works. If that was done with Python I wouldn't care either.
(that old webserver has since been retired and the new one doesn't have PHP, so now I render locally with Pandoc and rsync my HTML files directly, sigh)
- emj 2y agoI agree, there are two things I miss with markdown: import/export of text + media, multi user editing. This is always an extra step when you do not have and editing builtin in the Wiki that handles that. The "paste" image into document feature is one of the most useful features of a wiki if you want to write a fast bare bones tutorial.