Add Your Own Component to Bombie in 5 Edits
This is the third post in the Bombie series. The first post was an intro, the second covered the architecture. This one is a hands-on walkthrough: take a Material-UI component that isn’t already in Bombie, and wire it up so it appears in the palette, drags onto the canvas, opens a property editor, and renders in the live preview.
The whole change is five small edits across the same five files for every new component. Once you’ve done one, the next one takes about ten minutes.
I’ll use Rating as the running example. It’s a single-leaf component (no children), it has a small but meaningful prop surface (value, max, precision, size, readOnly, disabled), and it’s not already in the catalog.
Prerequisites
Clone and run Bombie locally:
git clone https://github.com/amith-moorkoth/bombie.git
cd bombie
cp .env.example .env
npm install
npm start
You’ll get the builder at http://localhost:8080/generate-component. Open src/Lib/ComponentGenerator/ — every file you’re going to touch lives under there.
Edit 1: register the component in the catalog
The catalog is the source of truth for what Bombie knows about. It lives in two files:
-
Data/element-base.js— display name + tag -
Data/elements.js— drag-and-drop type info
Add Rating to element-base.js:
// src/Lib/ComponentGenerator/Data/element-base.js
export const ELEMENT_BASE = {
// …existing entries
Rating: { tag: "Rating", displayName: "Rating" },
};
And to elements.js:
// src/Lib/ComponentGenerator/Data/elements.js
export const ELEMENTS = {
// …existing entries
Rating: {
type: "leaf", // it's a leaf, no children
accept: [], // it doesn't accept any drops
},
};
type controls where this component can be dropped (most things accept "leaf"). accept is what this component allows as a child — empty for leaves like Rating, populated for containers like Box / Grid / Stack.
Edit 2: write the builder UI file
This is the only new file you’ll create. It defines two things: the schema (what the property editor shows) and the render (what the canvas draws).
Create src/Lib/ComponentGenerator/Container/UI/Rating.js:
// src/Lib/ComponentGenerator/Container/UI/Rating.js
import Rating from "@mui/material/Rating";
import { makeLeafComponent } from "./Common/make-component";
export default makeLeafComponent({
tag: "Rating",
schema: {
Appearance: {
size: {
type: "select",
options: ["small", "medium", "large"],
default: "medium",
},
max: {
type: "number",
default: 5,
min: 1,
max: 10,
},
precision: {
type: "select",
options: [0.5, 1],
default: 1,
},
},
State: {
value: {
type: "number",
default: 3,
min: 0,
},
readOnly: { type: "boolean", default: false },
disabled: { type: "boolean", default: false },
},
},
render: ({ props }) => <Rating {...props} />,
// Optional defaults applied when the component is dropped on the canvas
defaultProps: { value: 3, max: 5, precision: 1, size: "medium" },
});
A few notes on what’s happening here:
-
makeLeafComponentis a factory fromUI/Common/make-component.js. It wraps the renderer with the builder chrome (selection outline, wrench button, delete button) and registers the schema so the property editor knows what controls to show. - Schema groups become sections in the property dialog. “Appearance” gets one card, “State” gets another. This is what makes the editor scannable instead of a wall of inputs.
-
Field types the editor knows about:
string,number,boolean,select,color. Anything else falls through to a text input. -
renderreceives the node’sprops(already merged with defaults) and returns plain JSX. No builder logic in this function — that’s what the wrapper handles.
For container components (Box, Grid, Stack, Card, etc.) you’d use makeContainerComponent instead. It accepts the same schema / render shape but also wires up a <DropBox> around the children so things can be dropped inside.
Edit 3: register it in the renderer switch
The canvas uses a central registry to know which builder UI file handles which tag. Add Rating to it:
// src/Lib/ComponentGenerator/Container/element-render.js
import Rating from "./UI/Rating";
// …other imports
export const REGISTRY = {
// …existing entries
Rating,
};
This is the registry the recursive renderer (element-recursion.js) consults for every node it walks. node.info.tag looks up its renderer here.
Edit 4: add an icon + put it in a palette category
The palette in the left sidebar groups components by category. Two small additions:
// src/Lib/ComponentGenerator/Elements/icon-map.js
import StarIcon from "@mui/icons-material/Star";
// …
export const ICON_MAP = {
// …existing entries
Rating: StarIcon,
};
// src/Lib/ComponentGenerator/Elements/index.js
export const CATEGORIES = {
Layout: [/* … */],
"Form Elements": ["TextField", "Select", /* …, */ "Rating"], // add here
"Data Display": [/* … */],
Feedback: [/* … */],
Navigation: [/* … */],
};
Categories are just arrays of tags. Pick the one that makes sense — Rating is technically a form input but it’s also a display element. I put it under “Form Elements” because it has a value and a readOnly mode, but “Data Display” is a defensible choice too.
Edit 5: teach the preview about it
The live preview has its own renderer (render-preview.js) that emits clean MUI JSX without builder chrome. It uses a switch keyed by tag — add a branch:
// src/Lib/ComponentGenerator/Preview/render-preview.js
import Rating from "@mui/material/Rating";
// …
const RENDERERS = {
// …existing entries
Rating: ({ node }) => <Rating {...node.props} />,
};
That’s it. The preview will now render Rating the same way the canvas does, minus the outline and wrench.
Testing your change
Hot-reload should pick everything up. Open the builder, find “Rating” in the Form Elements category, drag it onto the canvas. You should see five stars with the third one filled in (your defaultProps.value: 3).
Click the wrench. You should see the property dialog with two sections — “Appearance” with size / max / precision, and “State” with value / readOnly / disabled. Flip “readOnly” to true, change value to 4.5 (oh wait — precision is 1; set precision to 0.5 first, then 4.5 works).
Click Preview. The iframe shows your component without any builder chrome. Toggle Mobile / Tablet / Desktop — Rating doesn’t have responsive breakpoints itself, but if you’d dropped it inside a Grid it would reflow correctly.
If something doesn’t render: the most common culprit is forgetting Edit 3 (register in element-render.js) or Edit 5 (register in render-preview.js). One controls the canvas, the other controls the preview, and the symptoms are different — canvas-only failures mean a missing entry in element-render.js, preview-only failures mean a missing entry in render-preview.js.
What about container components?
For containers, two things change:
- Use
makeContainerComponentinstead ofmakeLeafComponent. It wraps a<DropBox>around the rendered children. - In
elements.js, settype: "container"and populateacceptwith the tags this container will receive (usually["leaf", "container"]to allow nesting).
The render function for a container gets children it should render the canvas-rendered subtree into. Example skeleton:
makeContainerComponent({
tag: "MyContainer",
schema: { /* … */ },
render: ({ props, children }) => (
<MyContainer {...props}>{children}</MyContainer>
),
});
children here is the already-rendered subtree (with builder chrome on the canvas, plain JSX in the preview).
A note on prop validation
Bombie doesn’t enforce prop validation beyond what MUI itself does at runtime. If you put value: 99 on a Rating with max: 5, MUI will clamp it. The schema’s min/max hints are advisory — the editor uses them for its number input UI, but the property dialog won’t refuse to let you save an out-of-range value.
In practice this hasn’t been a problem because the editor’s controls (select dropdowns, numeric inputs with min/max) make it hard to enter nonsense in the first place. But if you’re adding a component with strict prop constraints, document them in the schema using a description field — the property dialog will surface it as helper text.
Recap
For any new component, the five edits are:
-
Catalog —
Data/element-base.js+Data/elements.js -
Builder UI — one new file under
Container/UI/ -
Renderer registry — add to
REGISTRYinelement-render.js -
Palette — add icon to
icon-map.jsand tag toElements/index.js -
Preview renderer — add a branch in
render-preview.js
There’s no central manifest file that needs to be regenerated, no build step that needs to run, no test that needs to pass before the new component shows up. Hot-reload picks everything up in seconds.
The whole architecture is built around making this addition cheap, because the practical value of Bombie scales with how many MUI components it knows about. PRs that add components are exactly the kind of contribution I want.
In the next post — last in this series — I’ll cover the operational lessons: GitHub Pages SPA deep links, the CSP-per-mode setup, and why bombie-three.vercel.app ended up on Vercel even though the repo has a GitHub Pages workflow.
Links
- Repo: https://github.com/amith-moorkoth/bombie
- Live demo: https://bombie-three.vercel.app/
- Previous post: How I Built a Visual UI Builder for React with a JSON-Driven Tree
- Next post: Lessons from Building Bombie: SPA Deep Links, CSP, and an Iframe Preview
Çevrimiçi müzik alanının lideri Spotify bugün ilk olarak “Studio by Spotify Labs” ile dikkat çekti. Önümüzdeki haftalarda ayrı bir masaüstü uygulaması olarak çıkacak sürüm, kullanıcıların yazılı komutlarla kişiselleştirilmiş günlük özetler, podcast’ler ve çalma listeleri oluşturmasına imkan tanıtacak. Yapay zeka içerikleri, Spotify dinleme geçmişinin yanı sıra bağlanan uygulamalardan alınan bilgilerden yararlanılarak oluşturulacak ve kişisel kütüphaneye kaydedilecek. Bugün buna ek olarak yapay zeka destekli “remiks” altyapısı da duyuruldu. Bunun için Universal Music Group (UMG) ile iş birliği gerçekleştiren şirket, kullanıcıların yalnızca yazılı komutlarla yeni parçalar oluşturmasına imkan tanıyacak. Sanatçılar isterlerse şarkılarının yapay zeka ile remiks’lenmesine izin vermeyecek, izin veren sanatçılara ise ekstra ödeme yapılacak. Bugün, podcast içerikleri hakkında entegre yapay zeka sistemine soru sorulmasına imkan tanıyan bir altyapıyı kullanıma sunmaya başlayan şirket, önümüzdeki aylarda müzik, sesli kitap ve podcast’ler için yapay zeka destekli çalma listesi (Prompted Playlist) özelliğinin kullanıma sunulacağını da aktarıyor.
Honor, resmi olarak Türkiye’de satılan 600 serisine odaklanan ilginç bir aksesuar hazırladı. 25 Mayıs’ta detaylandırılacak ürün, temel olarak yuvarlak formda bir dokunmatik ekran ve telefonların arkasına özel bir kılıf aracılığıyla tutturulabiliyor. Aynı zamanda tek başına kullanıma özel bir kılıfı da bulunan ürün, arka kamera ile selfie çekilmesini kolaylaştırıyor (canlı vizör), bir dolgu ışığı olarak kullanılabiliyor veya uzaktan kumanda olarak görev yapabiliyor. Honor 600 serisi ortak olarak 6,57 inç boyutunda 120 Hz AMOLED ekranla geliyor. 600 modeline Snapdragon 7 Gen 4, 600 Pro modeline ise Snapdragon 8 Elite işlemciyle güç veren şirket, her iki telefonda da silikon temelli 7.000 mAh batarya (Avrupa’da 6.400 mAh) kullanıyor. 600 Pro’ya 50W kablosuz şarj desteği ekleyen şirket, ortak kablolu şarj hızını ise 80W olarak açıklıyor. Kamera tarafına geçildiğinde 600 ve 600 Pro’nun arkasında 200 megapiksellik 1/1.4 inç geniş açı ve 12 megapiksellik ultra geniş açı kameralar bir araya getiriliyor. 600 Pro’da bunlara ek olarak CIPA […]
Xiaomi Clip-On kablosuz kulaklık modeli, Smart Band 10 Pro akıllı bileklik ve bataryasıyla dikkat çeken 17 Max bugün resmi olarak tanıtıldı. Yeni ürünlerden “Clip-On”, “açık yapılı” ses deneyimi sunuyor, yani ürün müzik dinlerken çevrenin duyulmasına da imkan tanıyor ve doğrudan kulağın yanına takılarak kullanılıyor. 11 mm dinamik sürücülere ve IP67 sertifikasına sahip olan kulaklık, LHDC 5.0 desteğiyle geliyor. Yapay zeka destekli çeviri özelliğinin de bulunduğu 124 dolarlık model, şarj kutusuyla birlikte 38 saatlik batarya ömrü vadediyor. İlk olarak Çin’de satılacak 630 dolarlık Xiaomi 17 Max ise 100W kablolu / 50W kablosuz şarj destekli 8.000 mAh silikon bataryasıyla dikkat çekiyor. 6,9 inç boyutunda 1-120 Hz OLED ekran taşıyan cihaz, gücünü Snapdragon 8 Elite Gen 5 işlemciden alıyor ve arkasında 200 megapiksellik geniş açı (HP9), 50 megapiksellik ultra geniş açı ile 50 megapiksellik 3x periskop telefoto kameraları bir araya getiriyor. Bugün tanıtılan bir diğer ürün olan Smart Band 10 Pro ise 2024’te […]