@ebitex/starter-kit-react
Changes to the starter kit and its React renderer. Newest first. How versions work is on Releases and versions.
2026-10-29 — The starter kit and its renderer move to 1.0: presentations, with placement in Template settings
Section titled “2026-10-29 — The starter kit and its renderer move to 1.0: presentations, with placement in Template settings”Starter kit 1.0.0 and @ebitex/starter-kit-react 1.0 are a breaking release.
- The model. An experience’s
heroandsectionsare presentation fields (a Template, its settings and a Component) instead of component fields. Every placement and appearance choice (width, background, appearance, anchor, span, layout, aspect, emphasis, tone, columns, the theme, and an accordion’s behaviour) moved from a contextual field on a Contract to the settings of that Contract’s Template, so the content Contracts hold only editorial content. Tabs and Accordion hold their own items (a label and a list of presentations). Every field id is now kebab-case (primary-action,meta-title). - The renderer.
ebitexRenderers()returns a renderer for every kit Template, and you replace one or add a Template of your own by merging into<ContentProvider renderers>:renderers={{ ...ebitexRenderers(), 'ebitex-card-template': MyCard }}. A renderer is chosen by Template, never by Contract. A custom renderer receives{ template, settings, component }(the Contract’s fields atcomponent.content) in place of{ content }.EbitexProviderkeeps onlylink: itssectionsoption andEbitexSectionPropsare removed. Draw insideFrameto get a Template’s frame and to join the appearance cascade. - Installing. A kit install into an environment that already holds an earlier version is refused, with nothing written, because a new major version is never mixed into an older one. Your existing copy keeps working with the 0.x renderer. To use 1.0, install into a new environment or organization.
If you copied the source with starter-kit-eject, nothing changes for you: the copy is yours.
2026-10-28 — The starter kit renderer’s names now start with Ebitex
Section titled “2026-10-28 — The starter kit renderer’s names now start with Ebitex”@ebitex/starter-kit-react 0.2 renames what it exports and the attributes it writes, so they carry the ebitex prefix the starter kit’s own Contracts already use. The package and the starter-kit-eject command keep their names. Upgrading means changing the names below and nothing else.
| Before | After |
|---|---|
KitProvider |
EbitexProvider |
KitMarkdown |
EbitexMarkdown |
kitRenderers() |
ebitexRenderers() |
KitOptions |
EbitexOptions |
KitSectionProps |
EbitexSectionProps |
KitExperience |
EbitexExperience |
KitLink, KitContext, useKit() |
EbitexLink, EbitexContext, useEbitex() |
--kit-* tokens |
--ebitex-* |
data-kit-theme, data-kit-appearance, data-kit-unknown, data-kit-placeholder |
data-ebitex-theme, data-ebitex-appearance, data-ebitex-unknown, data-ebitex-placeholder |
If you copied the source with starter-kit-eject, nothing changes for you: the copy is yours. If you redefine a token, or select on a data-kit-* attribute in your own CSS or tests, rename those too.
2026-10-27 — A React renderer for the starter kit
Section titled “2026-10-27 — A React renderer for the starter kit”@ebitex/starter-kit-react draws the starter kit’s sections, an experience’s theme, a section’s appearance and Assets media with Tailwind tokens, for use with @ebitex/content-sdk. kitRenderers() gives <ContentProvider> the kit’s one Template, <KitProvider sections={{ ... }}> replaces how one Contract is drawn (or draws a Contract of your own), link replaces how links navigate, and the --kit-* tokens in styles.css carry every colour. The package root has the plain functions that read a delivered category (keyOf, pick) with no React. To take the source instead, npx starter-kit-eject <directory> copies the components, tokens and vocabulary into your project without overwriting a file. See Start a client site from the starter kit.