| 1 | --- |
| 2 | title: Re-creation of Marp website for the unified docs |
| 3 | date: 2020-08-22 |
| 4 | description: We are announcing that Marp team is working to the re-creation of marp.app website for hosting the unified documentation. |
| 5 | author: Yuki Hattori |
| 6 | github: yhatt |
| 7 | --- |
| 8 | |
| 9 | [marpit framework]: https://marpit.marp.app/ |
| 10 | [marp core]: https://github.com/marp-team/marp-core |
| 11 | [marp cli]: https://github.com/marp-team/marp-cli |
| 12 | [marp for vs code]: https://marketplace.visualstudio.com/items?itemName=marp-team.marp-vscode |
| 13 | |
| 14 | I could not have imagined that now we are living in a unique pandemic era when I wrote [the last article](/blog/the-story-of-marp-next). Even under those severe circumstances, I'm still making progress of Marp. |
| 15 | |
| 16 | Marp gives some tools for making a convincing slide deck with fewer efforts, and they get loved by a lot of users. In early this year, [Marp Core] has reached the stable v1 release, and our tools around the core are keeping steps with it. Needless to mention here, we will keep going to enhance our tools. |
| 17 | |
| 18 | Today we are announcing that **Marp team is working to the re-creation of [marp.app](/) website for hosting the unified documentation**. If you are reading this article, you should have already seen the re-created website! Currently the unified docs is not yet ready but we are going to announce here as soon as getting ready. |
| 19 | |
| 20 | <!-- more --> |
| 21 | |
| 22 | # For the unified documentation |
| 23 | |
| 24 | As Marp ecosystem spreads out, Marp team has become to regard the lack of unified documentation as an important issue. Our docs are scattered to many repos per tool, and it would make confusion when learning overall of Marp. In addition, we often have been asked basics of Marp in the issue tracker and sometimes even prevent our works for evolving Marp. |
| 25 | |
| 26 | For making users take advantage of Marp easier, I'm going to work improving the documentation together with evolving Marp tools. |
| 27 | |
| 28 | ## Re-created [marp.app](/) |
| 29 | |
| 30 | The re-created web page is the first step for building the unified docs. I had tried various tools to build the website and found a place to rest in [Next.js](https://nextjs.org/) and [Tailwind CSS](https://tailwindcss.com/). I believe we will be able to build more useful documentation pages by these. |
| 31 | |
| 32 | It is managed in our entrance repository [marp-team/marp](https://github.com/marp-team/marp) as same as before. If shipped new documentation, we would accept some improvements in the documentation from the community. |
| 33 | |
| 34 | --- |
| 35 | |
| 36 | ## Mid-term plans for Marp tools |
| 37 | |
| 38 | Might as well, finally let me share some mid-term plans for each tools I'll work shortly. |
| 39 | |
| 40 | - [Marpit framework]: Enhance directives |
| 41 | - [Marp Core]: Add new built-in theme and simplify auto-scaling feature |
| 42 | - [Marp CLI]: Handout template |
| 43 | - [Marp for VS Code]: Better auto-completion for Marp directives |
| 44 | |
| 45 | We also had announced [long-term plans earlier](/blog/the-story-of-marp-next): [Marp Web](https://web.marp.app/), Marp integration modules with [React](https://github.com/marp-team/marp-react) and [Vue](https://github.com/marp-team/marp-react), and [Marpit v2](https://github.com/marp-team/marpit/issues/194). However, _they are not yet in active and may need to reconsider plans because we have not enough positive feedbacks from community._ |
| 46 |