RFC: Migrate to Nuxt

[antfu]

Migrating Nuxt would allow us to share the Nuxt ecosystem, like installing integrations with Nuxt Modules or so. With the upcoming WebSocket support, it will make it easier to deploy a server-aware slides that are able to sync the presentation with a production build.

Meanwhile, Nuxt's templating, plugins, and module system would help us to organize the code in a better way.

This is a long-term plan that might require quite some effort. We plan to take it in a progressive approach, that we refactor our code base to a Nuxt-friendly way first so later we could migrate with fewer steps.

[rightaway]

Nuxt should enable a production build that doesn't need a running web server because it has SSG. Opening index.html from a browser on the same device should be enough to run the presentation which will be possible from devices when they are offline and can't install their own web servers such as phones and tablets.

[cnguyen-de]

thanks for creating this RFC, especially as soon as after our talk at Amsterdam ❤️

looking forward to use Nuxt superpowers

[shinGangan]

I look forward to this issue.

OG image can't be implemented in the current slidev.
( I hope that it would be nice to be able to set OG images when publishing slides on SNS... )

I'm happy to be able to implement it using the Nuxt OG Image module and Nuxt Devtools.

[mirismaili]

My ideal choice for export is an SSG (Static Site Generation) export that can be easily presented using a simple static web server while also being optimized for SEO.

[arkhaiel]

Hi there !
As a teacher I write lessons for my students in markdown files, and build a website using a Nuxt + Nuxt Content website. Recently I thought it would be a lot nicer to create slideshows to present things during the class, and keep the full length lessons in the website.

I heard about slidev months ago, so it was an evidence to go and try using this project, and I love it ! But I didn't understand why/how it was not possible to include it in my website codebase, to share components I use in the full length lessons for example.

So, I looked into the issues and found this RFC.
I scratched my head on this because I'm not even sure how integrating slidev in the nuxt ecosystem could be done, but I think it's a very good idea ! Maybe a "slidev" folder next to a "content" folder, generating URLs based on a prefix, could be handy.
Or a deeper integration with nuxt content, which would trigger a slidev build for md files with something like "slidev: true" in the frontmatter ?

[edimitchel]

cc @antfu THIS 👆

[arkhaiel]

cc @antfu THIS 👆

haha thanks. Few days after my comment, I've used slidev by diving deeper and I must say the DX is amazing. If I put the "components sharing" question aside, I'm pretty happy with my workflow :

• I put a /slides folder in the root of my Nuxt project
• This folder contains its own packages.json and is a full slidev project
• I create slideshows from this slidev project, with the amazing DX (it would be quite hard to integrate in the dev flow of a Nuxt project)
• I export the slideshow with the options --out ../public/slides --base /slides
• I link the slide or simply access it from its raw URL

I think my workflow can be greatly improved, but for now it's all good.

I want to give a bug shout-out to @antfu and the slidev team for this amazing work, I've smiled A LOT, like each time I thought "that would be so cool if ..., oh wait it's actually a thing ?! and it's way better than I hoped !". The UX/DX of this project is one of the best I've encountered so far.