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.

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.

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.

We are pleased to announce the release of CoreUI PRO v5.29.1 for Bootstrap. This patch release fixes how the Time Picker handles an empty value and makes the Calendar open on a month with days to pick when minDate or maxDate exclude today.

We are pleased to announce the release of CoreUI PRO v5.29.0 for Bootstrap. The Multi Select gains external search: the component stops filtering its own list and lets your code fetch matching options from a server or an API, the same way the Autocomplete already does. The release also fixes the Autocomplete external data example.

We are pleased to announce the release of CoreUI PRO v5.28.0 for Bootstrap. The Date Picker and Date Range Picker can now drop minutes and seconds from their time selection. The release also keeps internal fields out of submitted form data, fixes the Calendar, Multi Select, Autocomplete and OTP Input, and includes every fix from CoreUI v5.9.1.

We are pleased to announce the release of CoreUI v5.9.1 for Bootstrap. This maintenance release hardens the sanitizer, makes dispose() leave the page the way it found it across several components, improves accessibility of toggle Buttons and loading animations, and fixes a handful of border-radius details.

“Add a calendar” is one of those requirements that means five different things depending on who says it. A form field for picking a delivery date is a calendar. A month grid showing this sprint’s deadlines is a calendar. A week view where a dispatcher drags jobs between technicians’ columns is also, apparently, a calendar.

These are not sizes of the same feature — they are different features with different costs, and Bootstrap itself ships none of them. Bootstrap 5 has no calendar component at all: no date picker, no month grid, no scheduler. So every “bootstrap calendar” is Bootstrap’s design language plus a component that comes from somewhere else — a library, or your own code.

This article climbs that ladder honestly: what each rung actually requires, what you can reasonably build yourself, and where the cost curve bends hard enough that building stops making sense.

Every Bootstrap data table starts the same way: a <table class="table">, a loop over some rows, done. And for a surprising number of applications, that is genuinely all you need.

Then the requirements arrive one at a time. “Can we sort this by date?” “Can I search it?” “It’s slow with this quarter’s data.” Each one looks small, and each one is answerable with a few lines of JavaScript — until, at a fairly predictable point, it isn’t.

This article walks that ladder honestly. For each threshold we show what you can build yourself with plain Bootstrap (or CoreUI, which shares the same table markup and classes) and vanilla JavaScript, where the hand-rolled version starts to leak, and at which rung it stops being reasonable to keep writing table infrastructure by hand. If your table has 50 rows and never will have more, the code below is all you need — no library, no license, nothing to ship but a few kilobytes of your own JavaScript.

We are pleased to announce the release of CoreUI Free Bootstrap Admin Template v5.6.0. This release adds a search button to the header along with its own demo page, introduces a dedicated Chip Set demo, and brings a set of fixes to icons, internal links, and the build pipeline.