From #78:
Markdown editor UI appears as plain text editor, doesn't show preview/publish button menu. But doesn't have auto publish behavior as text editor does.
This is part of a larger issue which is that only FileComposer and FileHTML currently have publish functionality. Rather than copy publish functionality across the likes of FileMarkdown, FileCSS, FileJavascript, etc. it might be a better idea to just replace these components with FileComposer.
My only reservation about that is that by default FileComposer is missing code-specific affordances like line numbers, a minimap, etc. The editor configuration can't be changed once the Monaco editor is mounted, but we could mount one of several Monaco editors with their own language-specific configurations based on the MIME type of the content at this endpoint and/or the type inferred from the syntax of the text.
From #78:
This is part of a larger issue which is that only FileComposer and FileHTML currently have publish functionality. Rather than copy publish functionality across the likes of FileMarkdown, FileCSS, FileJavascript, etc. it might be a better idea to just replace these components with FileComposer.
My only reservation about that is that by default FileComposer is missing code-specific affordances like line numbers, a minimap, etc. The editor configuration can't be changed once the Monaco editor is mounted, but we could mount one of several Monaco editors with their own language-specific configurations based on the MIME type of the content at this endpoint and/or the type inferred from the syntax of the text.