Malibu is the culmination of Quintype’s experiences of taking hundreds of content websites into production. The goal is for malibu and the underlying tools to do all the heavy lifting for you, so that you can build an immersive applications quickly.
Malibu ships with PWA support. By default, Malibu will render a shell when a returning user opens your site, which drastically improves percieved performance. Malibu can also be configured to work in offline mode.
Malibu can be integrated with Project Lancelot, a curated collection of components to help you quickly build stunning content pages.
Malibu starts with a sub second First Contentful Paint and First Meaningful Paint by default. Even when multiple rich components are added, most malibu based sites load sub 2 seconds. Multiple components are available for performance tuning, like LazyLoadImages
Malibu does not enforce any constraints on the design of your site. You can build any kind of UI on top of malibu.
Malibu includes @quintype/components, a set of viewless components to handle common patterns like logins, paywalls, lazy loading images, and infinite scroll.
Most Quintype features are supported by default in Malibu, and often simply involves enabling features in the configuration
Malibu’s pages are already configured with the correct Cache-Control and Cache-Tag headers, so that our CDN keeps your pages in cache, but still expires pages as soon as you update your content.
Malibu is built and maintained by a dedicated team at Quintype, and receives weekly updates. Getting the latest features is as simple as
All of Quintype’s SEO features are already implemented via the @quintype/seo package.
Malibu handles a lot of the heavy lifting that developers typically have to do to set up a project. We have easy deployments with black knight, and we handle best practices like asset fingerprinting and zero downtime deploys for you. We can even set up as many environments as you want.
Head over to the tutorial to get started.