feat: Publish Seedling to NPM without content

[toshify]

Maybe we could make Seedling a NPM package without content, that serves as a package we require in our content project, that then picks up the content in the content project. Then each content project can have its own repository, and update the content delivery system, i.e. the Seedling app, whenever new app-changes are published to NPM.

[toshify]

Adding Seedling would look something like this:

yarn add nodepa/seedling # or npm install nodepa/seedling

Then we could mandate a index.js/.ts file that require Seedling and direct to content, e.g.:

// index.ts
import Seedling from 'nodepa/seedling';

const seedling = new Seedling({
  variousLessonConfig: "goes here"',
  mainContentPackFile: "Lessons.json";
});

// Lessons.json
{
  "langauge": "plutonic",
  "numberOfLessons": "2",
  "lessons": ["Lesson1.json", "Lesson2.json"],
  "instructions": {
    "homeButton": "assets/instructions/home_button.mp3",
    "instructionsButton": "assets/instructions/instructions_button.mp3"
  }
}

[toshify]

I expect issues with building both Seedling without content for NPM as well as building the content pack.

[toshify]

The biggest benefit is that content and app will be decoupled, allowing content developers to choose what license to release their content under, if any.

[toshify]

This would require versioning (semver) and releases, as well as versioning of content formats to ensure the particular Seedling version can eat the content files.