Ramonda

Start here

Two pages, in this order. Together they take about twenty minutes and leave you with a component that holds state and answers a click.

  • Installation — a new project with create-ramonda, or Ramonda added to one you already have. The decorators need a build step, and this is where that is set up.
  • Your first component — a class, a @state field, a handler. The smallest thing that is really a component rather than a snippet.

What to read after those

The order below is the one the site is written in, and each answers a question the one before it raises.

  • Components and JSX — what you are actually writing, and what it puts on the page.
  • State and Props — where a value lives, and how one travels from a parent.
  • Events — the handlers that change it.

By then a page works. Lifecycle, derived values and lists are what it needs to grow.

If you have used a framework before

Two pages are worth reading early, because they explain choices that otherwise look arbitrary: why a class and the reactivity model. Ramonda has no hooks-with-rules and no virtual-DOM diffing of your whole tree, and both pages say what it does instead.

Next