Which is to say that streams resolve to physical locations, expanded upon in the Multisite-setup part of the docs. So the context
-property works as a prefix in the case above;
import@:
type: partials/sidebar
context: blueprints://
Will try to import /user/plugins/admin/blueprints/partials/sidebar.yaml
, since blueprints://
by defaults resolves to Admin’s /blueprints
-folder.
But context: user://themes/mytheme
will resolve to /user/themes/mytheme
, and in conjunction with import@: type: partials/sidebar
this means it tries to import /user/themes/mytheme/partials/sidebar.yaml
.
There is a distinct lack of documentation about how blueprints work under the hood, it’s all in code in Rockettheme/Toolbox, and since almost all failures are silenced debugging them is difficult.