title: Overview category: builds-guides
CKEditor 5 Builds are a set of ready to use rich-text editors. Every "build" provides a single type of editor with a set of features and a default configuration. Our goal is to provide easy to use solutions that can satisfy a good part of the editing use cases out there.
Classic editor is what most users traditionally learnt to associate with a rich text editor — a toolbar with an editing area placed in a specific position on the page, usually as a part of a form that you use to submit some content to the server.
In CKEditor 5 the concept of the "boxed" editor was reinvented:
<iframe> element) — it is now much easier to style it.{@img assets/img/editor-classic.png 772 Screenshot of a classic editor.}
To try it out, check the {@link examples/builds/classic-editor classic editor example}.
The edited content remains a part of the page, with a floating toolbar attached:
{@img assets/img/editor-inline.png 774 Screenshot of an inline editor.}
To try it out, check the {@link examples/builds/inline-editor inline editor example}.
The edited content remains a part of the page (like in the inline editor). The toolbar appears in a balloon next to the selection (when the selection is not empty):
{@img assets/img/editor-balloon-toolbar.png 779 Screenshot of a baloon toolbar editor.}
To try it out, check the {@link examples/builds/balloon-toolbar-editor balloon toolbar editor example}.
Each build was designed to satisfy as many use cases as possible. They differ in their UI, UX and features, and are based on the following approach:
Features like fonts, colors and alignment will be introduced in the future, when the new types of builds will be introduced with the purpose of satisfying document editing scenarios.
Every build comes with a default set of features and a default configuration of them. Although the builds try to fit many cases, they may still need to be adjusted in some integrations. The following modifications are possible:
Read more in the {@link builds/guides/integration/configuration Configuration guide}.
If a build doesn't provide all the necessary features or you want create a highly optimized build of editor which will contain only the necessary features, then you need to customize the build or create a brand new one. Check {@link builds/guides/development/custom-builds Custom builds} for details on how to change the default builds to match your preferences.
Each of the builds fits several different use cases. Just think about any possible use for writing rich-text in applications.
The following are some common use cases:
The {@link framework/index CKEditor 5 Framework} should be used, instead of builds, in the following cases:
In the following cases CKEditor 4 should be used instead: