Skip to content

proposal: plugin structure #668

@iuioiua

Description

@iuioiua

A valid question I've been asked a few times is, "How can I upgrade SaaSKit once a new version comes out?" Previously, I didn't have a confident answer. Now, a decent solution might be viable with recent functionality added to Deno, Fresh, and the new JSR.

In short, we should make SaaSkit modular with separate plugins that are added, removed and modified with ease. I also propose we convert SaaSKit to a workspaces project to facilitate distribution on JSR.

We must strike a balance between modularity and ease of management. These are the plugins I suggest (subject to changes).

  • core - main components and pages
  • api - REST API
  • auth - sign-in and sign-out
  • dashboard - stats and user page
  • payments - everything payments-related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions