bookshop VS msw

It seems like CloudCannon has this with their open-source Bookshop component editor which can integrate with their hosted CMS.

https://github.com/CloudCannon/bookshop

The small user base, however, means there probably aren't other CMSs that use the same component representations or CMS live data bindings. This means while Bookshop components are portable between CMSs on paper, it's not in practice (e.g. you can't easily hook it up to another CMS with a visual editor like Wordpress's Gutenberg, Storyblok, etc.).

You can use a script to import your Hugo theme but this will only give you text editing functionality (markdown). For the visual editing experience you will need to convert your current theme to a cloudcannon theme using bookshop https://github.com/CloudCannon/bookshop

What's everybody using to make their javascript smaller nowadays? I used Grunt to minify my JS, CSS, and images many moons ago but I want to update my template to actually use bundle to deliver my assets since I'm creating a visual editor with CloudCannon.

Bookshop is a component development workflow for static websites. Bookshop defines a convention for building self-contained components in the templating languages supported by common SSGs. Using these conventions, Bookshop provides developer tooling that empowers you to integrate these components with your stack, build and browse UI components locally, and provide rich live editing experiences for your editors.

Sendit is a multipurpose Eleventy theme made with the Bootstrap CSS framework. The components have been converted to Bookshop. It’s the perfect starting point to see how CloudCannon works.

Sendit is a multipurpose Eleventy theme with a built-in blog, made with the Bootstrap CSS framework. The components have been converted to Bookshop. It’s the perfect starting point to see how CloudCannon’s Visual Editing and component-based page-building works, and how they can really speed up your blogging flow.

For users of our open-source component development workflow Bookshop, we’ve created a full reference guide for Bookshop on Eleventy and a Bookshop starter template. (The Sendit theme comes with Bookshop and a wide range of components already configured, too!)

The last place our improvements touch on is visual page building. You can now create new pages in the Visual Editor and edit the page’s default data right away — with no build needed. We also added an option to preview your new page without a build. To get a preview, you’ll need pages configured to render from your front matter using Data Bindings and Previews (we also recommend Bookshop here). Then you can use the new option new_preview_url to set your preview to another page’s output URL. The Visual Editor will load that set preview URL and use the Data Bindings and Previews to render your new page without saving. You can try this with our Megakit template.

Our SSGs through the ages series delves into the history of this space, and one of the trends that we’re seeing is larger and larger projects migrating to static websites, helped in part by the efficiency of static site generators like Hugo. We build many such sites for ourselves — the CloudCannon documentation is nothing to sneeze at — as well as for our Enterprise partners, and our customers build yet more on our platform every day. As this scale continues to increase, we find ourselves encountering new and interesting challenges. In the past we have released open-source tools for component-driven development, internationalization, pagination and portability. Now, we have our sights set on search.

Bookshop, one of our own open-source tools, allows the kind of component-based editing in SSGs such as Hugo, Jekyll, and Eleventy that — to put it bluntly — no one thought was possible. It’s an inflection point that will affect how these SSGs will be used in the coming years; think Elementor’s block-based builder for WordPress, with increasing support for additional platforms that don’t have rigid security and maintenance constraints. With Bookshop, developers can work with custom components on the SSG they choose, without being locked into a single platform.

However, I discovered a great combination that transformed my API call testing in TypeScript: Vitest and Mock Service Worker (MSW). Their well-crafted design makes them incredibly easy to use, enhancing the overall testing experience.

While mocks are effective, they require modifying the component's internal logic or mocking global functions like fetch. This can become cumbersome for complex components with numerous API interactions. Here's where MSW shines.

> For those wondering what the use case is, you must not have tried it. It does take work to set up (with each version that's less), but it can be very nice to test in isolation esp in cases where a component is under a login, the 4th page of a 10 page form, etc. Also obviously if you're working on a component library that ships without an app, Storybook can be your development and/or demo app.

I have worked with storybook extensively over the past couple of years and my team is moving away from it in favour of MSW (https://mswjs.io).

For "4th page of a 10 page form" during the development there's hot reloading which is really stable nowadays and haven't failed me, although I understand that some setups are old and it might be easier to configure Storybook than good hot reloading.

I'm not entirely sure about the testing part of it and I'd be grateful if you could elaborate. I haven't felt the need for some special setup with SB because for unit tests, I can test a deeply nested component separately. For E2E tests, I usually test the whole form.

I agree on the component library part, this is probably the only use case where Storybook is 100% justified, but I'm unconvinced about the

Additionally, thank you to all our community launch partners across the frontend ecosystem for helping us bring Storybook 8 to the world! Thanks to Chromatic, Figma, ViteConf, Omlet, DivRiots, story.to.design, StackBlitz, UXpin, Nx, Mock Service Worker, Anima, Zeplin, zeroheight, kickstartDS, and Kendo UI.

similar with msw.js, but fully automated

they could be network mocks (use msw)

With orval, we can also integrate the API client in our unit tests. Orval provides first class support for mocking through the (Mock Service Worker)[https://mswjs.io/] library, and it can automatically generate the MSW handlers for testing server.

Consider a hypothetical scenario where data from a list of companies within an ERP needs to be retrieved. As a personal recommendation, leverage tools like MSW for top-level mocks, which can significantly enhance the testing process.