marp-team/marp

The entrance repository of Markdown presentation ecosystem

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 4th, 2026
Created on March 25th, 2018
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 296
Total Stargazers: 12,464 (+0)
Total Subscribers: 80 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Marp is a Markdown presentation ecosystem that enables developers to write slide decks using plain Markdown syntax.

The project addresses the friction of creating presentations through traditional GUI tools by providing a text-based workflow. Rather than a monolithic application, Marp is structured as a modular ecosystem where different components handle specific concerns: Marpit serves as a lightweight framework for converting Markdown to slide decks, Marp Core adds practical features and built-in themes on top of that foundation, and Marp CLI provides command-line tooling to export presentations into HTML, PDF, PPTX, and image formats. A VS Code extension integrates preview functionality directly into the editor.

Developers should choose this tool if they prefer writing presentations in Markdown and version-controlling them alongside code. The modular architecture means you can adopt just the pieces you need—use Marpit if you want a minimal framework, Marp Core for a feature-complete converter with themes, or the CLI for batch conversion workflows. The VS Code extension makes it practical for those working within that editor. The project explicitly acknowledges that older components like Marp Web and framework-specific renderers for React and Vue are inactive, so adoption decisions should focus on the actively maintained core and CLI tools.

Development activity shows consistent engagement across the ecosystem. The project maintains clear separation of concerns by distributing functionality across multiple repositories, each with a focused scope. The team actively manages the project through a discussion forum and maintains an awesome list curating community contributions and extensions. Contributing guidelines are documented and enforced across all sub-projects.