Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

proposal: plugin structure #668

Open
iuioiua opened this issue Feb 8, 2024 · 0 comments
Open

proposal: plugin structure #668

iuioiua opened this issue Feb 8, 2024 · 0 comments

Comments

@iuioiua
Copy link
Contributor

iuioiua commented Feb 8, 2024

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant