[
  {
    "path": "LICENSE",
    "content": "MIT License\n\nCopyright (c) 2016-2019 Yuki Hattori (yukihattori1116@gmail.com)\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n"
  },
  {
    "path": "README.md",
    "content": "<p align=\"center\">\n  <a href=\"https://marp.app/\">\n    <img alt=\"It's a time to migrate into Marp Next!\" src=\"docs/ogp.png\" height=\"240\" />\n  </a>\n</p>\n\n# It's a time to migrate into [Marp Next]!\n\n**The publication of classic Marp app has ended.**\n\nMarp desktop app, _a simple Markdown presentation writer_, already had stopped maintenance since 2017. Today [Marp team] is focusing into [Marp Next] project, the brand-new presentation ecosystem for the future.\n\n_[See more details in our blog post.](https://marp.app/blog/the-story-of-marp-next)_\n\n## Why?\n\nWe had kept publishing app for stuck users that are thinking Marp Next is too complex.\n\nBut recently, we received [a serious security report for outdated app](https://github.com/yhatt/marp/issues/276). **_By opening a malicious Markdown, an attacker can execute arbitrary code through remote._** We are responsible for saving users from malicious.\n\nIf you are currently using Marp app, **_please stop using as soon as possible_** and migrate into well-maintained Marp Next tools.\n\n## [Marp Next] tools\n\n[Marp Next] is not complex! Simply you can just use either one if you want to create slide deck.\n\n### [Marp for VS Code]&nbsp;(Recommended)\n\n**[Marp for VS Code]**, an extension for [Visual Studio Code], is the best alternative for desktop app users. There are key features inherited from the classic Marp app.\n\n- Live preview\n- Export to PDF, HTML, and PPTX (via [Marp CLI])\n- Support built-in 3 themes and custom theme CSS\n\n### [Marp CLI]\n\n**[Marp CLI]** is simple but powerful CLI converter from Marp Markdown into PDF, HTML, PPTX, and images. You can use it if you don't want GUI editor.\n\nI also have [an example repository](https://github.com/yhatt/marp-cli-example) to automate generating slide deck and serving through [Marp CLI] + [Netlify](https://www.netlify.com/) or [ZEIT Now](https://zeit.co/).\n\n## Migrate Markdown\n\nMarp Next is losing Markdown compatibility with classic app, but your slide would keep appearance as before just by some changes in most cases. Please see [our blog post](https://marp.app/blog/the-story-of-marp-next#migration-plan) for details.\n\n## Thanks\n\nThanks for a lot of users / contributors of desktop app. Marp has changed my life as developer without doubt, and I've learned a lot from many feedbacks.\n\nNow [Marp Next] project is evolving built on them. I hope you like it too.\n\n---\n\n_— Yuki Hattori ([@yhatt](https://github.com/yhatt))_\n\n[marp next]: https://marp.app/\n[marp team]: https://github.com/marp-team/\n[marp for vs code]: https://marketplace.visualstudio.com/items?itemName=marp-team.marp-vscode\n[marp cli]: https://github.com/marp-team/marp-cli\n[visual studio code]: https://code.visualstudio.com\n"
  },
  {
    "path": "docs/index.html",
    "content": "<!DOCTYPE html>\n<html lang=\"en\">\n  <head>\n    <meta charset=\"UTF-8\" />\n    <meta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\" />\n    <meta http-equiv=\"X-UA-Compatible\" content=\"ie=edge\" />\n    <title>Marp - Markdown Presentation Writer</title>\n\n    <link rel=\"icon\" type=\"image/png\" href=\"./marp.png\" />\n\n    <meta name=\"subject\" content=\"Markdown Presentation Writer\" />\n    <meta name=\"description\" content=\"It's a time to migrate into Marp Next!\" />\n    <meta name=\"author\" content=\"Yuki Hattori, yhatt\" />\n\n    <meta property=\"og:type\" content=\"website\" />\n    <meta property=\"og:url\" content=\"https://yhatt.github.io/marp\" />\n    <meta property=\"og:title\" content=\"Marp - Markdown Presentation Writer\" />\n    <meta\n      property=\"og:description\"\n      content=\"It's a time to migrate into Marp Next!\"\n    />\n    <meta property=\"og:image\" content=\"https://yhatt.github.io/marp/ogp.png\" />\n\n    <meta name=\"twitter:card\" content=\"summary\" />\n    <meta name=\"twitter:site\" content=\"@y_hatt\" />\n    <meta\n      name=\"twitter:title\"\n      content=\"Marp - The simplest markdown presentation writer\"\n    />\n    <meta\n      name=\"twitter:description\"\n      content=\"It's a time to migrate into Marp Next!\"\n    />\n    <meta name=\"twitter:image\" content=\"https://yhatt.github.io/marp/ogp.png\" />\n\n    <link rel=\"stylesheet\" type=\"text/css\" href=\"./style.css\" />\n  </head>\n  <body>\n    <nav>\n      <h1 class=\"subject\">\n        <img src=\"marp.png\" alt=\"Marp\" />\n        Marp\n        <small>Markdown Presentation Writer</small>\n      </h1>\n    </nav>\n    <section class=\"jumbotron\">\n      <a href=\"https://marp.app/\">\n        <img src=\"ogp.png\" alt=\"It's a time to migrate into Marp Next!\" />\n      </a>\n    </section>\n    <section>\n      <h1>\n        It's a time to migrate into <a href=\"https://marp.app/\">Marp Next</a>!\n      </h1>\n      <p><strong>The publication of classic Marp app has ended.</strong></p>\n      <p>\n        Marp desktop app, <em>a simple Markdown presentation writer</em>,\n        already had stopped maintenance since 2017. Today\n        <a href=\"https://github.com/marp-team/\">Marp team</a> is focusing into\n        <a href=\"https://marp.app/\">Marp Next</a> project, the brand-new\n        presentation ecosystem for the future.\n      </p>\n      <p>\n        <em\n          ><a href=\"https://marp.app/blog/the-story-of-marp-next\"\n            >See more details in our blog post.</a\n          ></em\n        >\n      </p>\n      <h2>Why?</h2>\n      <p>\n        We had kept publishing app for stuck users that are thinking Marp Next\n        is too complex.\n      </p>\n      <p>\n        But recently, we received\n        <a href=\"https://github.com/yhatt/marp/issues/276\"\n          >a serious security report for outdated app</a\n        >.\n        <strong\n          ><em\n            >By opening a malicious Markdown, an attacker can execute arbitrary\n            code through remote.</em\n          ></strong\n        >\n        We are responsible for saving users from malicious.\n      </p>\n      <p>\n        If you are currently using Marp app,\n        <strong><em>please stop using as soon as possible</em></strong> and\n        migrate into well-maintained Marp Next tools.\n      </p>\n      <h2><a href=\"https://marp.app/\">Marp Next</a> tools</h2>\n      <p>\n        <a href=\"https://marp.app/\">Marp Next</a> is not complex! Simply you can\n        just use either one if you want to create slide deck.\n      </p>\n      <h3>\n        <a\n          href=\"https://marketplace.visualstudio.com/items?itemName=marp-team.marp-vscode\"\n          >Marp for VS Code</a\n        >&nbsp;(Recommended)\n      </h3>\n      <p>\n        <strong\n          ><a\n            href=\"https://marketplace.visualstudio.com/items?itemName=marp-team.marp-vscode\"\n            >Marp for VS Code</a\n          ></strong\n        >, an extension for\n        <a href=\"https://code.visualstudio.com\">Visual Studio Code</a>, is the\n        best alternative for desktop app users. There are key features inherited\n        from the classic Marp app.\n      </p>\n      <ul>\n        <li>Live preview</li>\n        <li>\n          Export to PDF, HTML, and PPTX (via\n          <a href=\"https://github.com/marp-team/marp-cli\">Marp CLI</a>)\n        </li>\n        <li>Support built-in 3 themes and custom theme CSS</li>\n      </ul>\n      <h3><a href=\"https://github.com/marp-team/marp-cli\">Marp CLI</a></h3>\n      <p>\n        <strong\n          ><a href=\"https://github.com/marp-team/marp-cli\">Marp CLI</a></strong\n        >\n        is simple but powerful CLI converter from Marp Markdown into PDF, HTML,\n        PPTX, and images. You can use it if you don't want GUI editor.\n      </p>\n      <p>\n        I also have\n        <a href=\"https://github.com/yhatt/marp-cli-example\"\n          >an example repository</a\n        >\n        to automate generating slide deck and serving through\n        <a href=\"https://github.com/marp-team/marp-cli\">Marp CLI</a> +\n        <a href=\"https://www.netlify.com/\">Netlify</a> or\n        <a href=\"https://zeit.co/\">ZEIT Now</a>.\n      </p>\n      <h2>Migrate Markdown</h2>\n      <p>\n        Marp Next is losing Markdown compatibility with classic app, but your\n        slide would keep appearance as before just by some changes in most\n        cases. Please see\n        <a href=\"https://marp.app/blog/the-story-of-marp-next#migration-plan\"\n          >our blog post</a\n        >\n        for details.\n      </p>\n      <h2>Thanks</h2>\n      <p>\n        Thanks for a lot of users / contributors of desktop app. Marp has\n        changed my life as developer without doubt, and I've learned a lot from\n        many feedbacks.\n      </p>\n      <p>\n        Now <a href=\"https://marp.app/\">Marp Next</a> project is evolving built\n        on them. I hope you like it too.\n      </p>\n      <hr />\n      <p>\n        <em>— Yuki Hattori (<a href=\"https://github.com/yhatt\">@yhatt</a>)</em>\n      </p>\n    </section>\n  </body>\n</html>\n"
  },
  {
    "path": "docs/style.css",
    "content": "body {\n  background: #fff;\n  color: #555;\n  font-size: 18px;\n  line-height: 1.4;\n  font-family: Arial, Helvetica, sans-serif;\n  margin: 0;\n  padding: 0;\n}\n\nnav {\n  border-bottom: 1px solid #eee;\n  height: 60px;\n}\n\nh1.subject {\n  box-sizing: border-box;\n  color: #404050;\n  font-size: 20px;\n  height: 60px;\n  line-height: 40px;\n  margin: 0 auto;\n  max-width: 1000px;\n  padding: 10px;\n}\n\nh1.subject img {\n  display: block;\n  float: left;\n  height: 40px;\n  margin-right: 10px;\n  width: 40px;\n}\n\nh1.subject small {\n  font-size: 0.6em;\n}\n\nsection {\n  box-sizing: border-box;\n  max-width: 1000px;\n  margin: 0 auto 5em auto;\n  padding: 0 20px;\n}\n\nsection.jumbotron {\n  margin: 0 auto;\n}\n\nsection.jumbotron img {\n  display: block;\n  width: 100%;\n  margin: 0;\n}\n\nsection h1 {\n  text-align: center;\n  margin: 0 0 2em 0;\n  padding: 0.25em 0;\n  border-bottom: 3px solid #ccc;\n}\n\nsection h2 {\n  margin: 1.5em 0 1em 0;\n  padding: 0.25em 0;\n  border-bottom: 1px solid #ccc;\n}\n\nsection h3 {\n  margin: 2em 0 1em 0;\n}\n\na {\n  color: #02669d;\n  text-decoration: none;\n}\n\na:hover {\n  color: #003668;\n}\n\nhr {\n  margin: 2.5em 0;\n  height: 0;\n  border: none;\n  border-bottom: 3px solid #ccc;\n}\n"
  }
]