# Guides - [Frequent questions](https://atomico.gitbook.io/doc/guides/frequent-questions.md) - [Is it advisable to declare events using the props API?](https://atomico.gitbook.io/doc/guides/frequent-questions/is-it-advisable-to-declare-events-using-the-props-api.md): It is not recommended to use the props API to create an event, as this callback associated as props will have the following limitations: - [How to declare events for your component at the type level for TSX?](https://atomico.gitbook.io/doc/guides/frequent-questions/how-to-declare-events-for-your-component-at-the-type-level-for-tsx.md) - [When and why to use shadowDom?](https://atomico.gitbook.io/doc/guides/frequent-questions/when-and-why-to-use-shadowdom.md) - [Can I use Atomico in browsers without ESM support?](https://atomico.gitbook.io/doc/guides/frequent-questions/page.md) - [Component](https://atomico.gitbook.io/doc/guides/component.md): Working on this documentation... - [Naming](https://atomico.gitbook.io/doc/guides/component/naming.md): Simple but useful - [CSS Styles with Shadow DOM](https://atomico.gitbook.io/doc/guides/component/css-styles-with-shadow-dom.md): Working on this documentation... - [Atomico with Typescript](https://atomico.gitbook.io/doc/guides/atomico-with-typescript.md): Atomico with Typescript will improve the scalability of your project thanks to a really productive type system when creating, distributing and maintaining webcomponents - [Props](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/props.md) - [Component](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/typescript.md): Type to structure a component from its creation - [Meta-types](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/meta-types.md) - [Type](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/meta-types/type.md) - [Event declaration](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/meta-types/declare-meta-types-to-the-component.md) - [Method declaration](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/meta-types/method-declaration.md) - [Check the correct use of hooks](https://atomico.gitbook.io/doc/guides/atomico-with-typescript/check-the-correct-use-of-hooks.md): By default most hooks infer types automatically, however here are some typing tips: - [Atomico and React](https://atomico.gitbook.io/doc/guides/atomico-and-react.md) - [Integrating Atomico in React](https://atomico.gitbook.io/doc/guides/atomico-and-react/integrating-atomico-in-react.md) - [From React to Atomico](https://atomico.gitbook.io/doc/guides/atomico-and-react/from-react-to-atomico.md): Atomico inherits part of the React syntax and applies it to webcomponents, with a closer to standard approach. - [Rendering Differences](https://atomico.gitbook.io/doc/guides/atomico-and-react/from-react-to-atomico/rendering-differences.md) - [VirtualDOM api differences](https://atomico.gitbook.io/doc/guides/atomico-and-react/from-react-to-atomico/virtualdom-api-differences.md): Guide that defines some differences that exist between Atomico and React when working with the DOM. - [Atomico and Asynchrony](https://atomico.gitbook.io/doc/guides/atomico-and-asynchrony.md): With Atomico, asynchrony is really easy thanks to the fact that they will allow you to know the status of the process or suspend the rendering of the component. - [Atomico design patterns](https://atomico.gitbook.io/doc/guides/atomico-design-patterns.md): Atomico has been designed to be simple even in complex situations, in this guide you will know some patterns that Atomico offers to create webcomponents at an advanced level. - [Webcomponents with hybrid rendering](https://atomico.gitbook.io/doc/guides/atomico-design-patterns/webcomponents-with-hybrid-rendering.md): Improve the interaction of your inputs with forms using hybrid rendering (LightDOM and ShadowDOM) - [Slot as templates](https://atomico.gitbook.io/doc/guides/atomico-design-patterns/slot-as-templates.md) - [Slot](https://atomico.gitbook.io/doc/guides/atomico-design-patterns/slot.md) - [Atomico and Storybook](https://atomico.gitbook.io/doc/guides/atomico-and-storybook.md) - [Frequent questions](https://atomico.gitbook.io/doc/guides/atomico-and-storybook/frequent-questions.md) - [SSR / SSG](https://atomico.gitbook.io/doc/guides/ssr-ssg.md): Implement SSR and SST without friction - [Archives](https://atomico.gitbook.io/doc/guides/archives.md) - [Class inheritance](https://atomico.gitbook.io/doc/guides/archives/class-inheritance.md) - [Forms and shadowDOM](https://atomico.gitbook.io/doc/guides/archives/forms-and-shadowdom.md): Improve the interaction with the forms and accessibility of your components. - [Tips](https://atomico.gitbook.io/doc/guides/archives/tips.md): Here are some tips you can take into account when creating webcomponents with Atomico - [Design systems](https://atomico.gitbook.io/doc/guides/archives/design-systems.md): I will show you a series of useful techniques to start programming your design systems with Atomico, analyzing the recommended structure and its files. - [Atomico style guide](https://atomico.gitbook.io/doc/guides/archives/atomico-style-guide.md): First thanks for using Atomico 😉, in this guide you will find some useful tips when developing with Atomico, all with the aim that your webcomponents are sustainable and scalable over time. - [File structure](https://atomico.gitbook.io/doc/guides/archives/atomico-style-guide/file-structure.md) - [Monorepo](https://atomico.gitbook.io/doc/guides/archives/atomico-style-guide/file-structure/monorepo.md) - [Design systems](https://atomico.gitbook.io/doc/guides/archives/atomico-style-guide/file-structure/design-systems.md) --- # 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://atomico.gitbook.io/doc/guides.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.