From 1842fa82e35d444208f402b0f3713f2f768095d6 Mon Sep 17 00:00:00 2001 From: Demis Bellot Date: Sun, 25 Feb 2024 16:17:31 +0800 Subject: [PATCH] update --- src/_includes/component-links.md | 4 ++++ src/_posts/2024-03-01_vite-press-plugin.md | 13 +++++++------ 2 files changed, 11 insertions(+), 6 deletions(-) create mode 100644 src/_includes/component-links.md diff --git a/src/_includes/component-links.md b/src/_includes/component-links.md new file mode 100644 index 0000000..6a87dd9 --- /dev/null +++ b/src/_includes/component-links.md @@ -0,0 +1,4 @@ +- [React Components in Markdown](/posts/markdown-components-in-react) +- [Vue Components in Markdown](https://press-vue.servicestack.net/posts/markdown-components-in-vue) +- [.NET Razor SSG Vue Components in Markdown](https://razor-ssg.web-templates.io/posts/javascript) +- [.NET Blazor Vue Components in Markdown](https://blazor-vue.web-templates.io/posts/javascript) diff --git a/src/_posts/2024-03-01_vite-press-plugin.md b/src/_posts/2024-03-01_vite-press-plugin.md index bfdf8b0..9379af3 100644 --- a/src/_posts/2024-03-01_vite-press-plugin.md +++ b/src/_posts/2024-03-01_vite-press-plugin.md @@ -486,13 +486,14 @@ of the code-block to convert the structured ascii layout into a more familiar GU nextjs.md ``` -This nice thing about this approach of marking up documentation is that the markdown content still remains in optimal -human-readable form even without any custom components to render rich UI components. +The benefit of this approach of marking up documentation is that the markdown content still remains in an optimal +human-readable form even when the markdown renderer lacks the custom fenced components to render the richer UI. ## Components In Markdown -Ideally most of your Markdown content are able to just make use of the above features, but when even more interactivity -and richer functionality is required you're able to embed components directly in Markdown, but comes at the cost of -reduced portability. +Up till now all above features will let you render the same markdown content in all available Vue, React, Razor or Blazor +templates. At the cost of reduced portability, you're also able to embed rich Interactive Vue or React components directly in +markdown. + +:::include component-links.md::: -#### [React Components in Markdown](/posts/markdown-components-in-react) \ No newline at end of file