# README

![npm bundle size](https://img.shields.io/bundlephobia/minzip/bemtv?style=for-the-badge)[![Coveralls](https://img.shields.io/coverallsCoverage/github/diogoneves07/bemtvjs?label=Test%20coverage\&style=for-the-badge)](https://coveralls.io/github/diogoneves07/bemtvjs)

### Key Features

* Cleaner syntax than other UI libraries and frameworks.
* No “props”. A new way for parent component to pass data to child components.
* Instead of a common routing system or based on files, Bemtv brings a new innovative routing system that is capable of “transforming” a component into a route automatically according to its use in the application.
* Separation of logic related to DOM events from the component template.
* Semi-automatic Code-Splitting.
* CSS-In-JS and CSS-In-Template.
* The design of the components allows the export of all the methods belonging to it, which allows the use of these methods in any part of the application.
* Easy two-way binding between component variables and HTML element properties and attributes.
* Hooks.
* Transform functions that separate data structures like Array, Set, Map and Object from their markup for the template.
* Brackethtml markup language: instead of **`<div>Hey!</div>`** do this: **`div[Hey!]`**.
* Declarative syntactic sugars through the component template.
* It's just Javascript, no JSX or build-time needed, just add it to your *index.html* and have fun!

**“Before you play with Bemtv, do think twice and if you enjoy too much, don't be     surprised! ”**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bemtv.gitbook.io/bemtvjs/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
