[ ] Create Opensearch index of all available plugins.
[ ] Create public template to search plugins by name and purpose
[ ] Create new module context
The current method of adding a plugin is to add a context, select module, and fill in the required fields. However, this is not a great user experience and prone to error. Instead users will be able to search plugins using an auto complete field querying the opensearch index. The plugins shown will only be those DIRECTLY compatible with the quell/spearhead version. Once a plugin is selected a drop down will be shown to select an exposed module of the plugin.
Index will need to include:
solid name
description
libs[] - libraries relevant to search ie. am charts
library
vendors[] - vendors relevant to search
vendor ie. aws for aws integration
classifications[] - categorize
classification
versions[]
url (remote host)
version ie. 16.0.0-alpha.7
date_released
modules[]
name
compatibility[] - Versions module is compatible.
version ie. 16.0.0-alpha.x
demos[] - links to demonstrations of plugin - In theory should be hosted as pages people build on plugins app.
title
description
url
NOTE: Builders should be able to promote pages without needing to modify urls. For example, local, dev, prod SOLIDS will each have a different URL. When pages using SOLIDS are promoted those URLS require manually modification. This should not be.
We could also design this more like a product
title
vendors
tags (libs)
categories (classifications)
variants (modules)
I think this should be designed as a shop/ecomm system. Knock out two birds with one stone.
Create separate issue for solids website. ie. solids.carbonfreed.app
New Repos:
solids
solids-build
solids-build-prod
solids-objects
solids-objects-prod
This is very much going to be like a shop. Should probably first set-up the shop distro then use that as a template for this.
The current method of adding a plugin is to add a context, select module, and fill in the required fields. However, this is not a great user experience and prone to error. Instead users will be able to search plugins using an auto complete field querying the opensearch index. The plugins shown will only be those DIRECTLY compatible with the quell/spearhead version. Once a plugin is selected a drop down will be shown to select an exposed module of the plugin.
Index will need to include:
NOTE: Builders should be able to promote pages without needing to modify urls. For example, local, dev, prod SOLIDS will each have a different URL. When pages using SOLIDS are promoted those URLS require manually modification. This should not be.
We could also design this more like a product
I think this should be designed as a shop/ecomm system. Knock out two birds with one stone.
Create separate issue for solids website. ie. solids.carbonfreed.app
New Repos:
This is very much going to be like a shop. Should probably first set-up the shop distro then use that as a template for this.