| title | layout | description |
|---|---|---|
Riot FAQ |
detail |
Questions and Answers about Riot, User Interface (UI) Micro-Libary |
Riot is against the current trend of boilerplate and unneeded complexity. We think that a small, powerful API and concise syntax are extremely important things on a client-side library. Riot also provides an unopinionated stack that gives developers the freedom to work with the best technology they like.
Riot is free, open source and licensed under the MIT License.
Absolutely. The project is mature enough.
Riot.js 4 supports all of the major modern browsers. Browsers like IE11 are not supported: if you need to support older browsers you might consider using an [older Riot version]({{ site.data.globals.legacy }})
W3C specification demands you use a dash in the tag name. Instead of <person> you must write <my-person>. Obey this rule if you care about W3C. Both work fine. More info
Leaving out semicolons makes the code less crowded. This is aligned with our general minimalistic approach. We use single quotes for the same reason. If you contribute to Riot, please leave out semicolons and double quotes.
Yes. You can use CSS normally inside a Riot tag file. The web component standard also has a mechanism for CSS encapsulation. However, it's unlikely that this improves the overall manageability of your CSS.
It's not evil, it just looks "old". To have JS and HTML under the same module is more important than aesthetics. The minimal Riot syntax makes event handlers look decent.
Sure. The Riot core doesn't provide much out of the box but the riot.install method allows us to plug in new features. A bunch of Riot plugins to enhance the default components API is on my TODO list.