+
+ {author}
+
+ ) : (
+ author
+ )}
+
+ {reserved && (
+ <>
+ Reserved
+
+ )}
+ 
][marp web]
+
+### Use via any devices
+
+By migrating to the web-based app, Marp will be able using in mobile device: Android and iOS. That's sure it's well suited to the tablet device like iPad.
+
+
+
+Marp Web would work also in Chrome OS well. Marp especially has many users in the field of education, and supporting Chrome OS that has large share in its field is meaningful.
+
+### Blazing-fast live preview ⚡️
+
+We think Marp's important feature is a blazing-fast live preview. In the web-based app, realizing the same feature had many difficulties.
+
+In currently published tech-demo, you can try Marp's really fast preview on the web. The preview applies as soon as typing, and it would not block your typing even if you have a large Markdown slides over than 100 pages.
+
+# Integrations
+
+The modulized Marp Core brought Marp integrations for some tools.
+
+## [Marp for VS Code][marp vscode]
+
+Honestly, I don't think to want to make a new editor because there are many great Markdown editors in the world. I had been thinking it would be awesome if Marp could integrate with a something else powerful Markdown editor. And now, Marp can use in [Visual Studio Code](https://code.visualstudio.com/)!
+
+[
][marp vscode]
+
+It was realized because VS Code is using the same Markdown engine (markdown-it) as Marpit framework. Of course you can export slides as PDF and HTML easily, powered by [Marp CLI].
+
+[marp vscode]: https://marketplace.visualstudio.com/items?itemName=marp-team.marp-vscode
+
+## [Marp React] & [Marp Vue] (In development)
+
+[marp react]: https://github.com/marp-team/marp-react
+[marp vue]: https://github.com/marp-team/marp-vue
+
+Marp's blazing fast live-preview is not only for ours! We provide Marp renderer component into [React][marp react] and [Vue][marp vue]. Both Marp React and Marp Vue have supported the incremental update using framework's virtual DOM, and they are been easy to build your app.
+
+Especially, Marp React would become to the base of the future of [Marp Web].
+
+# Migration plan
+
+## Desktop app ([yhatt/marp](https://github.com/yhatt/marp))
+
+If you are using an old Marp application, **you should migrate to use Marp Next tools.** I NEVER recommend continue to use the old Marp, because _its maintainance has stopped 2 years ago and there is concern about security issues._
+
+In future, the main interface would become to Marp Web. We have bet to PWA technology that has a lot of advantages. The desktop app is planned as "Marp Desktop" but it just may become a wrapper of Web interface.
+
+I would stop publishing the old Marp and archive its repository if Marp Web has grown to become replacable the old Marp.
+
+## Your slide deck
+
+Your Markdown slides written in the old Marp syntax should rewrite to suit to the brand-new Marp ecosystem.
+
+In a new Marp, we have reconsidered Markdown syntax based on feedback to the old Marp app. So, some syntaxs are losing compatibillity.
+
+### Syntax
+
+- In Marp Core, non-whitelisted HTML elements are disabled by default because of security reason. Currently our whitelist includes only `
+
+ {author}
+
+ ) : (
+ author
+ )}
+
+ {reserved && (
+ <>
+ Reserved
+
+ )}
+
+)
+
+const BlogBase: React.FC+ +
+ {children} ++ +
+