BlockSlides

BlockSlides is a toolkit for adding a WYSIWYG slide editor straight into your own app. Instead of sending users off to a separate design tool or building an editor from scratch, you drop in a single component and get a full editing surface. Users can build decks, social banners, thumbnails, and printable one-pagers, all from the same underlying slide model. The framing on the site is that one component is all it takes to ship an in-app presentation editor, and everything else layers on top of that. It's squarely a developer product, meant for teams who want authoring inside their own product rather than a standalone app. The site pitches it as the fastest way to add an in-app presentation editor, and it backs that up with a one-line drop-in component you can copy for either framework.

The problem it goes after is a familiar one for product teams. Rich text editors for documents are a solved space, with mature libraries covering paragraphs, marks, and inline formatting. Slides and bounded canvases are a different shape of problem. You need fixed page sizes, layouts, drag positioning, media, and tables, all living inside a frame rather than a flowing document that grows as you type. Rolling that yourself means rebuilding selection, keyboard shortcuts, undo, and export before you write a single feature your users care about. BlockSlides treats that canvas as a first-class model, so you can mix a 16x9 slide, an A4 page, and a LinkedIn banner in one document without fighting the tool.

Under the hood it's ProseMirror-powered. The headless core, published as @blockslides/core, gives you the editor runtime and document model, and framework bindings for React and Vue 3 give you drop-in UI with sensible defaults. Anyone who has worked with Tiptap will recognize the architecture, since content lives as structured JSON and behavior is composed from extensions and node views rather than baked into the editor. There are more than 50 extensions covering text, media, layouts, tables, math, and markdown. On top of that sit prebuilt pieces like a bubble menu that appears when you select text, a template picker, preset templates, drag-and-drop reordering, and image controls, so you can ship a working editor quickly and go deeper only where you need to. The demo on the homepage is a real editor rather than a recording, so you can add a slide from templates, open the bubble menu by selecting text, drag blocks to reorder content, and click an image to explore its controls, which is the same surface you would be embedding.

Because content is JSON-first, you own it. You store the structured document for persistence and versioning, then export to HTML, Markdown, or plain text whenever you need it for publishing, previews, docs, and search indexing. That matters when the editor is one part of a larger product and the output has to feed other systems, drive a static renderer, or get diffed in version control. Nothing is trapped in an opaque binary file, and the same document can render live in the app or statically somewhere else without a separate conversion step.

It's also built with AI workflows in mind. The @blockslides/ai-context package ships prompt bundles, schemas, and templates so that documents generated by a language model stay valid against the editor's structure. If you're building an assistant that drafts a deck from a brief or generates a batch of social graphics, that keeps the output inside the rails of what your editor can actually render, instead of producing JSON the editor then rejects. The starting point for customization is an ExtensionKit that bundles the common extensions, and you extend from there with your own nodes and views when the defaults run out.

Where it stands apart is the focus. Plenty of editor toolkits handle long-form text extremely well. Far fewer take slides and bounded visual canvases seriously as a document type with their own layout rules, and that's the gap BlockSlides is built to fill. It fits teams building presentation or pitch-deck features, social-graphic creators, report and one-pager builders, and any product where users lay out visual assets rather than write essays. The multi-asset angle, one slide model producing many sizes and formats, is the part that would be tedious to assemble from separate tools. The same JSON document can carry mixed sizes, so a deck, a thumbnail, and a banner can sit side by side and be edited with one consistent set of controls.

Access is open source. The packages are published on npm under the MIT license, with the source on GitHub and documentation at blockslides.dev, so you can install it, read the code, and self-host the editor inside your own stack with no vendor lock-in. There's no paid tier or account to sign up for, which makes it easy to evaluate by wiring the demo component into a test app and clicking around. As a young project the community and ecosystem around it are still small, so expect to read source and file issues rather than lean on a large body of tutorials.