# Web Languages ## Long Live the Web We are huge fans of the Web and Javascript community and regularly follow thought leaders, specially from the React team, to keep up to date with the latest best practices. However, we engineer for users, not other engineers, so we try to remain as pragmatic as possible. That said, I think we still do pretty well with staying up to date, although I'm not sure for how long after this last ReactConf :). ## Our Approach There is no point in listing out a bunch of frameworks and linters here. In general, we follow the **"pick the best tool for the job philosophy"**. Check out [Kathari](https://github.com/kleros/kleros-docs/blob/master/contribution-guidelines/code-style-and-guidelines/broken-reference/README.md) and [one of our dapps](https://github.com/kleros/doges-on-trial) to get a sense of what we think that is at the moment. --- # 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://docs.kleros.io/contribution-guidelines/code-style-and-guidelines/web-languages.md?ask= ``` 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.