3 ms·
For our SaaS [1] we have a plug-in architecture. And each plugin has a concept called install constraints. They consist of app, tier, and the role of the user
by atonse 2y ago
For our SaaS [1] we have a plug-in architecture.
And each plugin has a concept called install constraints. They consist of app, tier, and the role of the user provisioning the account.
Based on the right combination, certain plugins get auto installed and the user can enable/disable optional plugins/features.
Upon installation, the plug-in module has a “lifecycle” module with callbacks for install, uninstall, after_install, etc.
In those, we insert db metadata (pages, folders, menu items, etc) related to that plugin.
All is written in elixir.
1: https://simplyscholar.com https://simplyscholar.com
- mbreese 2y agoI love this concept (and I’m probably in that market segment). But, I didn’t see any examples on your landing page. It would be really nice if you had one or two examples to show off what a resulting site would look like.
- atonse 2y agothanks! We are currently revamping that site because it’s just not converting and we suspect what you said is one of the reasons. We will have samples up in a couple weeks. But stay in touch! ashish@simplyscholar.com