Liam Bigelow
Liam Bigelow
This was mentioned in #896 but declined at that point. Since then, however, the winds of change have blown in favor of `graphql-ws`. The [graphql-ws protocol](https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md) differs from Apollo's original...
Error: ``` Failed to load component-lib/bookshop/bookshop.config.js Error [ERR_REQUIRE_ESM]: require() of ES Module /.../component-lib/bookshop/bookshop.config.js from /.../.npm/_npx/26f890b013d3948d/node_modules/@bookshop/init/main.js not supported. bookshop.config.js is treated as an ES module file as it is a .js...
Currently Bookshop Browser renders its menus and components within the tagged element. We should expose another attribute that can be used to render these two concerns in separate locations: ```...
Bookshop generate is too fragile in some build scenarios when passed bad input, for example: ``` blueprint: - ``` Processing these files should provide much better error handling and reporting...
Envisioning the components: ```yaml # hero.bookshop.yml blueprint: title: Hello World alignment: Left _inputs: alignment: type: select options: values: - Left - Center - Right ``` ```yaml # paragraph.bookshop.yml blueprint: text:...
Workshopping flexible components, picturing a component definition like the following: ```yaml # hero.bookshop.yml spec: structures: - content_blocks blueprint: title: Hello World alignment: Left ``` Available as a nested component: ```yaml...
Currently, the only component shorthand available is: ```yaml button: "bookshop:button" #or: buttons: ["bookshop:button"] ``` In both of these instances, the object or array will be initialized in the CMS empty....
The engine's `eval` calls should be memoized where possible to reduce computation on subsequent renders. Ideally this could be performed at the `live` package level rather than being left up...
The data is plumbed and the other SSGs support this — the Hugo WASM now needs to re-implement the `site.AllPages` & co group of functions, mapping CloudCannon's `info.json` back into...
Often page builders have to make a choice between exposing "fine" components to the editor (`title`, `button`) or exposing "coarse" components to the editor (`landing-page-hero`, `two-column-product-info`). A useful Bookshop feature...