CoreUI ONE — 250+ PRO components and 25+ admin templates for React, Angular, Vue, Bootstrap and Next.js, plus Data Grid, Scheduler, 4,300+ PRO icons and the Next.js boilerplate. One license. → See what you get

CoreUI v6 Alpha vs Bootstrap 6 Alpha: What We Took, What We Didn't, and Why

CoreUI v6 Alpha vs Bootstrap 6 Alpha: What We Took, What We Didn't, and Why

Bootstrap published its first v6 alpha on October 8. CoreUI v6 followed with its first alpha two weeks later. CoreUI has been built on Bootstrap from the start, so the obvious question is how close the two v6 lines are.

The short answer: as close as we could make them, with a list of deliberate exceptions. For every file we share with Bootstrap we follow one rule. Class names, CSS custom properties, options, events and public methods stay the same as in Bootstrap wherever we can manage it, so moving from one to the other does not mean rewriting markup. The code behind those names is a separate question. Where we can do better than Bootstrap without changing a name, we do. Where following Bootstrap would cost our users a migration step that buys them nothing, we don’t.

This post goes through all three cases: what we took, what we left out, and where we kept the name but changed what is behind it.

Read More…

CoreUI v6 Alpha: What Changes and Why

CoreUI v6 Alpha: What Changes and Why

The first alpha of CoreUI v6 is on npm. It covers three packages: CoreUI PRO for Bootstrap (@coreui/coreui-pro), for React (@coreui/react-pro) and for Vue (@coreui/vue-pro), each published as 6.0.0-alpha.0 under the next tag. The free editions and Angular follow in later alphas.

Two weeks earlier the Bootstrap team published the first Bootstrap 6 alpha. CoreUI has always been built on Bootstrap, and v6 follows the same architecture: cascade layers, a token map per component, theme classes and colours computed in the browser. Where a class, token, option or event exists in both libraries, it almost always has the same name. What we took from Bootstrap 6, what we did not take and why is the subject of a separate post. This one is about what v6 gives you.

It is an alpha. The API can still change before the release candidate, so pin the exact version and keep it out of production for now.

Read More…

CoreUI PRO for React v6.0.0-alpha.0 - First v6 Alpha

CoreUI PRO for React v6.0.0-alpha.0 - First v6 Alpha

We are pleased to announce CoreUI PRO for React v6.0.0-alpha.0, the first alpha of v6. It is built on CoreUI PRO v6.0.0-alpha.0, and each component now imports the stylesheet it renders into, so an app ships only the CSS it uses. The API can still change before the release candidate, so pin the exact version and do not use it in production yet. The v6 documentation is published next to the v5 docs.

Read More…

CoreUI PRO for Vue v6.0.0-alpha.0 - First v6 Alpha

CoreUI PRO for Vue v6.0.0-alpha.0 - First v6 Alpha

We are pleased to announce CoreUI PRO for Vue v6.0.0-alpha.0, the first alpha of v6. It is built on CoreUI PRO v6.0.0-alpha.0, and each component now imports the stylesheet it renders into, so an app ships only the CSS it uses. The API can still change before the release candidate, so pin the exact version and do not use it in production yet. The v6 documentation is published next to the v5 docs.

Read More…

CoreUI PRO v6.0.0-alpha.0 - First v6 Alpha

CoreUI PRO v6.0.0-alpha.0 - First v6 Alpha

We are pleased to announce CoreUI PRO v6.0.0-alpha.0 for Bootstrap, the first alpha of v6. The JavaScript is now written in TypeScript and ships its own type declarations, positioned components move from Popper to Floating UI, one stylesheet serves both text directions, and dist/css gains a stylesheet per component. The API can still change before the release candidate, so pin the exact version and do not use it in production yet. The v6 documentation is published next to the v5 docs.

Read More…
Subscribe to our newsletter
Get early information about new products, product updates and blog posts.