distributing and publishing apps made with Greenwood

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Following in the theme of #570 , an underlying theme is that others could create apps built on top of Greenwood. But what would that look like and what would best practices / options look like?

1. Should everything just be a plugin?
2. Or can projects depend on @greenwood/cli directly?
3. And what are the options, using a GitHub or actually publishing to npm?

Details

So this may not even require anything of Greenwood specifically, but instead maybe just experimentation and documentation?

For something simple, degit may be an option. Or maybe Greenwood can / should create a community "installer?

[thescientist13]

As a potential POC / example of doing something like this, I'm creating a Greenwood bases presentation repo here for an upcoming conference I am giving in August.
https://github.com/thescientist13/greenwood-starter-presentation

My plan is to build the styles / slides from the perspective of creating it as something to share as a "theme pack" ( #570 ).

[thescientist13]

Some interim thoughts on handling pages from a theme pack - #681 (comment)

[thescientist13]

An observation on how vite does it
https://github.com/vitejs/vite/tree/main/packages/create-vite