Hello Eduardo Avila,

Thank you for your interest in the Fasto Angular Admin Dashboard Template and for taking the time to review the demo.

Regarding your technical questions:

1. Standalone Components

   The template currently follows the standard Angular module-based architecture and uses **AppModule along with feature modules**. It is not fully migrated to Angular Standalone Components yet. However, the structure is clean and modular, so migrating to standalone components in the future would be straightforward if needed.

2. Style Encapsulation

   Each component includes its **own SCSS file for component-specific styling**, which keeps styles scoped and maintainable. In addition to this, there is a **global `styles.scss` file** used for shared styles, variables, layout utilities, and theme-level styling.

3. Third-Party Plugins

   Plugins such as FullCalendar, ApexCharts, and other libraries are integrated in a modular way through npm packages and imported only where required. They are not tightly coupled with the core layout, which makes it easier to replace or integrate other libraries like Syncfusion if needed.

Overall, the template is designed to be **developer-friendly, modular, and extendable**, so integrating additional UI libraries or components should work without major conflicts.

If you have any other technical questions before purchasing, feel free to ask. We'll be happy to help.

Best regards

Lakhan G

DexignZone Team

I am interested in purchasing your template for a project, but I have a few technical questions regarding the architecture and styling to ensure compatibility with other libraries I plan to integrate (like Syncfusion).

1.-Standalone Components: Is the template fully migrated to Standalone Components, or does it still rely on AppModule and shared modules?

2.-Style Encapsulation: Does each component come with its own scoped SCSS file, or are the styles mostly defined in a global styles.scss file?

3.-Third-Party Plugins: Are the included plugins (like FullCalendar, ApexCharts, etc.) integrated as independent peer dependencies, or are they tightly coupled with the core layout?