bookshop VS vite

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.

As of this writing, initializing a Hattip project requires some manual commands. However, keep in mind that a zero-config development environment based on Vite is in the works.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 4200, } })

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/