@astlide/core
The core of Astlide, with no framework in it. It holds what every Astlide package shares, so a deck of MDX, Markdown, HTML and PowerPoint slides looks and behaves the same wherever it runs.
Building a site? Install the package for your framework. Each one depends on this core:
| Framework | Package |
|---|---|
| Astro | @astlide/astro |
| React | @astlide/react |
| Next.js | @astlide/next |
| Vue | @astlide/vue |
| Nuxt | @astlide/nuxt |
What's in it
@astlide/core/deckreads a deck folder:_config.json, then numbered.mdx,.md,.htmland.pptxslides. MDX compiles for any JSX runtime with the same pipeline Astro uses.@astlide/core/renderrenders a deck to HTML, PDF, PNG or PPTX without building a site.@astlide/core/runtimeis the deck runtime that every framework drives: navigation, fragments, the presenter window, overview, drawing, notes. It comes with the chrome markup and the stylesheets in@astlide/core/styles/*.@astlide/core/pptxand@astlide/core/templatescover PowerPoint import and PowerPoint templates as themes, kept in a folder, S3, GCS or Azure.@astlide/core/schemahas the frontmatter and_config.jsonschemas.@astlide/core/pluginhas the plugin API.- The
astlideCLI exports, imports and renders decks, and runs the MCP server for coding agents.
📖 Docs: https://astlide.dev/ (日本語: https://astlide.dev/ja/)
Coming from Astlide 2
The Astro integration that used to be @astlide/core is now @astlide/astro. Install it in place of @astlide/core, then import astlide, astlideDeckLoader and slideSchema from @astlide/astro. Component paths move too: @astlide/core/components/* becomes @astlide/astro/components/*.
License
MIT