Component state and API
If you are writing your own web components, there are three pieces of terminology it's important to understand:
If you are writing your own web components, there are three pieces of terminology it's important to understand:
This page guides you through setting up a simple example of two components that communicate via a store shared value.
This page guides you through installing the foundation-store in your legacy project. This isn't recommended - all new applications created via Genesis Create or genx will install the store for you, and then you can just follow the example tutorial. However, if you're adding Genesis into an existing project (or you're using an old Genesis project from before the store was a default component) you can follow this guide.
The foundation-store provides a decoupled and testable way to manage application state, which adheres to our best practices. Using foundation-store is completely optional; you might decide that your application doesn't warrant a store, or that you would prefer to use a store that you are more familiar with.
Store bindings