Skip to main content

Concepts

Strategy​

We designed Plexus to take the business logic away from the components; this essentially turns your components into puppets for Plexus to orchestrate. Keeping business log seprate has many benifits, including versitility.

Structure​

Plexus was designed to be completely unopinionated on how to structure your app. You can technically place our functions anywhere, but we have several style guides you can follow if you don't know where to start. We are also working on an NPX script to set up and edit a Plexus core, update to newer versionsof Plexus, and get lists of files/components using a core module!

Internal Terms​

  • Constructor Function (CF): The functions you import from our package. You use these to create Instances.
  • Stateful: A reactive variable that can be subscribed to and updated.
  • Instance: Something that is connected to the plexus "network".
  • Module: The optional objects where you merge all your instances together, structured however you want!
  • Core: The optional object where you merge all your instances and/or modules together, structured however you want!