MVP Scope and UACs

[mkotsollaris]

hypothesis: Engineers would like to be using a low-code/low-effort solution for managing their feature lifecycles rather than maintaining error-prone codebases.

MVP Scope:

1. Facet-extension: Responsible for CRUDing facets.

UAC:

• As a facet customer, I am able to install the plugin, create an account or log in, and create facets. My progress should be saved as I go, in case I want to re-load my facets at some point later.

Depends on: facet-api

2. facet-api: Responsible for storing and processing facet-extension information.

UAC:

• As an API consumer (ie facet-extension), I want the ability to have a performant API, so that I can depend on it as I store my preferred facet configuration per workspace and user.

Depends on: -

3. mutation-observer-injectable-script: Responsible for hiding the actual elements on the client-side.

UAC:

• As a facet customer, I want the ability to copy-paste a snippet of code in my codebase, so that I am able to rollout my preselected facets.

Depends on: facet-api
Explanation: If facet-api goes down, clients are incapable of retrieving the script