You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Optional Rich Markdown Editor: advanced viewer + source-respecting editor in a sandboxed iframe
#38353
Agents write a lot of Markdown (plans, specs, docs), and we review it in T3 all day. The file preview renders GFM, Mermaid and math, but richer documents (richer that GFM, like Pandoc or MyST syntax) cannot render these:
inline vega charts
grids, list tables, admonitions.
radio button (very useful for desin choices directly in MD)
The other option is to generate HTML artifacts, which are great for prototypes, but horrible for collaborative surface: you need a backend, a way to route to your remote phone for instance. MD is simple, text, and allows all kind of really useful and elegant extensions.
Proposal
An optional Rich Markdown Editor for .md files:
Advanced viewer: Vega-Lite charts, MyST grids and cards, {list-table}, admonitions, figures, PlantUML (no jar dependencies), structured frontmatter.
Source-respecting editor: click a block or a table cell to edit it in place. Only that block's source changes; the rest of the file is never reformatted, so diffs stay clean.
Optional, installed beside T3: nothing new in the core bundle. It could be a small plugin or "viewer" extension point: a viewer registered for some file extensions shows up in Open in / Open With, next to the default view.
Runs in a sandboxed iframe: isolated from the app's DOM, CSS and session. It talks to T3 through a small postMessage protocol (read/write file, file changed, open link, theme). It works remotely, since file access goes through T3's existing RPCs.
opt-in use of the markdown extension: by default, write GFM, and optionally enable your agent to write to the full extend (gris, vega graph,...)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Problem
Agents write a lot of Markdown (plans, specs, docs), and we review it in T3 all day. The file preview renders GFM, Mermaid and math, but richer documents (richer that GFM, like Pandoc or MyST syntax) cannot render these:
The other option is to generate HTML artifacts, which are great for prototypes, but horrible for collaborative surface: you need a backend, a way to route to your remote phone for instance. MD is simple, text, and allows all kind of really useful and elegant extensions.
Proposal
An optional Rich Markdown Editor for
.mdfiles:{list-table}, admonitions, figures, PlantUML (no jar dependencies), structured frontmatter.An implementation already exists as a VS Code extension: Markdown OKF-Schema Studio.
A browser build for iframe embedding is tracked in gsemet/markdown-okf-schema-studio#413. T3 would only need the extension point.
Related
All reactions