Is your feature request related to a problem? Please describe.
For Markdown (.md) and OCNote files there is no dedicated code / source view. You cannot paste raw Markdown and reliably edit it as text.
Pasting Markdown into the current editor also does not render correctly. Example:
# Welcome to Markdown
This is a **bold** statement and this is *italicized* text.
## Features
- Easy to read
- Simple to write
- Supports **formatting**
- Works well for documentation
### Example Code
```python
print("Hello, world!")
Headings, lists, emphasis, and fenced code blocks are not handled as expected, so you cannot copy Markdown from elsewhere and drop it in.
It is also hard to:
- Copy the current document as Markdown (e.g. to paste into GitHub, another editor, or chat).
- Paste Markdown and have it automatically render as formatted Markdown.
- Navigate long notes — there is no table of contents from headings.
Describe the solution you'd like
1. Code / Source view
Add a Code / Source view for .md and OCNote files:
- Switch between Preview (rendered) and Code (raw Markdown).
- In Code view, the file is plain text: copy, paste, and edit Markdown as-is.
- Pasting the example above should keep the original Markdown (headings, bold/italic, lists, fenced code blocks).
- Preview should then render that Markdown correctly.
- Optional: split view (source + preview), similar to typical Markdown editors.
Pasting into Code view should insert the clipboard as raw text, without stripping or rewriting syntax.
2. Copy as Markdown / paste Markdown and render
- Copy as Markdown: copy the current document (or selection) as raw Markdown — e.g. a toolbar action, or right-click → Copy as Markdown.
- Paste Markdown and render: when pasting Markdown into the editor, detect it and automatically render it as Markdown (headings, lists, bold/italic, code blocks, etc.), instead of treating it as plain/unformatted text.
Together: copy out clean Markdown, paste in Markdown and see it formatted.
3. Automatically generated table of contents
- Show an auto-generated table of contents on the right side, built from headings (
#, ##, ###, …).
- Clicking an entry should jump to that heading.
- Update the TOC as headings change.
- Optional: collapse/hide the TOC for short notes or on small screens.
Describe alternatives you've considered
- Pasting into the current WYSIWYG/rich editor — Markdown is mangled and does not render correctly.
- Manually copying rendered text — you get rich text or plain text, not Markdown source.
- Editing the file outside OpenCloud, then re-uploading — extra steps and easy to get out of sync.
- Using only the rendered view — no way to fix or paste source when rendering is wrong.
- Scrolling through long notes to find sections — no outline/TOC.
Additional context
A Code view, copy/paste as Markdown, and a heading TOC are standard in Markdown/note apps (GitHub, VS Code, Notion-style outlines, typical Markdown previews). This would make .md and OCNote usable for documentation, moving content in and out of other tools, and navigating longer notes — and would give a fallback when the rich editor mis-handles Markdown.
Is your feature request related to a problem? Please describe.
For Markdown (
.md) and OCNote files there is no dedicated code / source view. You cannot paste raw Markdown and reliably edit it as text.Pasting Markdown into the current editor also does not render correctly. Example:
Headings, lists, emphasis, and fenced code blocks are not handled as expected, so you cannot copy Markdown from elsewhere and drop it in.
It is also hard to:
Describe the solution you'd like
1. Code / Source view
Add a Code / Source view for
.mdand OCNote files:Pasting into Code view should insert the clipboard as raw text, without stripping or rewriting syntax.
2. Copy as Markdown / paste Markdown and render
Together: copy out clean Markdown, paste in Markdown and see it formatted.
3. Automatically generated table of contents
#,##,###, …).Describe alternatives you've considered
Additional context
A Code view, copy/paste as Markdown, and a heading TOC are standard in Markdown/note apps (GitHub, VS Code, Notion-style outlines, typical Markdown previews). This would make
.mdand OCNote usable for documentation, moving content in and out of other tools, and navigating longer notes — and would give a fallback when the rich editor mis-handles Markdown.