[Shock] - Load pages, assets, layouts, and components from the network.
For example, I'm publishing a bunch of documentation websites for FBH packages. Every such website includes an identical section about FBH. I'd like to avoid maintaining duplicate versions of that description across all those webpages. Instead, I'd like to publish a repo that contains a component that each documentation website can load over the network. This creates a single source of truth that can be updated at any time.
[Shock] - Load pages, assets, layouts, and components from the network.
For example, I'm publishing a bunch of documentation websites for FBH packages. Every such website includes an identical section about FBH. I'd like to avoid maintaining duplicate versions of that description across all those webpages. Instead, I'd like to publish a repo that contains a component that each documentation website can load over the network. This creates a single source of truth that can be updated at any time.