Rendering Markdown in Enhance #202
Conversation
Signed-off-by: macdonst <simon.macdonald@gmail.com>
Signed-off-by: macdonst <simon.macdonald@gmail.com>
|
related: an old entry I wrote about using custom elements in Markdown. maybe it can be repurposed as an aside here or a sub-document |
|
@tbeseda Yes, I think an aside letting folks know they can use custom-elements in their markdown is a good idea. |
Signed-off-by: macdonst <simon.macdonald@gmail.com>
Signed-off-by: macdonst <simon.macdonald@gmail.com>
Co-authored-by: Cole Peters <cole@colepeters.com>
Signed-off-by: macdonst <simon.macdonald@gmail.com>
| ### Render order matters | ||
|
|
||
| When rendering HTML from Markdown that includes custom elements the rendering order matters. First, render the markdown to HTML with Arcdown then "enhance" that HTML by running it through Enhance SSR before sending it to the browser. | ||
|
|
There was a problem hiding this comment.
I feel it would be good to add a few words as to why.
Something like:
since Enhance expands custom elements that would not be present in the markup until after markdown converts the source into HTML.
There was a problem hiding this comment.
I think the main worry is when the custom element is expanded it creates valid html which cannot be parsed by the markdown parser.
There was a problem hiding this comment.
Yes that is true as well
There was a problem hiding this comment.
Maybe we should just say that Enhance produces a full HTML page and not a HTML snippet like Arcdown does.
There was a problem hiding this comment.
Removed this section after chatting about it in Enhance sync
Co-authored-by: Cole Peters <cole@colepeters.com>
We've seen folks searching for Markdown and Enhance so I'm trying to surface our solution on enhance.dev.