How customization works
You change how Kaizendex looks in four ways, easiest first: settings, CSS, HTML and scripts.
Most people only need the first one. The others are there when settings are not enough.
The four ways
| Way | Think of it as | What it changes | Example | Runs code? |
|---|---|---|---|---|
| Settings (JSON) | filling in a form | colours, fonts, sizes, spacing, shapes, animations, which fields a card shows and where | “checkbox shape: circle” | no |
| CSS | paint and position | any look of any named part of the screen | a glowing card, a hand-drawn border | no |
| HTML | the furniture inside a box | what is inside a part, and in what order | a card with a GIF in the middle and the checkbox in a corner | no |
| Scripts (TypeScript) | instructions for a helper | logic: a card’s own look, or an Automation | “glow when the streak passes 30” | yes, in a sealed engine |
| HTML blocks | a small website in a glass box | anything inside its box | a 3D globe of your runs on a dashboard | yes, in a sealed frame |
JSON is a plain text format for settings. TypeScript is a programming language.
An HTML block is not the same as the HTML way. It is a block you add to a Block page or a Dashboard (for example on a dashboard). It can hold JavaScript, so it runs in a sealed frame. The HTML of a design cannot run code.
Settings and HTML are two ways to write the same card. You can switch between them at any time.
The AI uses the easiest way that works. Ask it for “a star checkbox on my Habits cards”, and it changes a setting, not a script.
Settings and CSS use the same names. The theme value color.accent is the CSS variable
--color-accent. The name tag checkbox is the same in both.
Looks belong to designs, data changes belong to Automations
A design decides how things look and where a click takes you. It never changes your data beyond the one control you clicked.
Example: you tick “Done” on a habit card. The design plays confetti. If ticking should also add the tag Finished, that is an Automation on the Habits collection. The Automation runs however the box gets ticked: on the card, in a table, by the AI or from a phone notification.
What you can and cannot change
| You can change | You cannot change |
|---|---|
| every colour, font, size, spacing, roundness, shadow and animation | the hidden insides of the app that have no name tag (unless you switch on Free CSS) |
| the look and the inside of every named part | protected screens: sign-in, payment, “Delete for good” and the rest |
| what a click opens and plays, and the one value a clicked control changes | deleting, moving to the Trash, sharing, privacy, plans and settings |
| how things look on every screen size | the few rules each view needs to work (a table row stays a row) |
| anything inside an HTML block | an HTML block reaching the rest of the app |
Free CSS is an opt-in for your own account. It lets your CSS aim at anything except protected screens. After every update the app asks you to check it. See Safe designs.