Frequently Asked Questions

Why use a SPA instead of full page reloads?

SPAs provide smoother navigation, persistent UI elements, and faster transitions.

Does the SPA replace AdminLTE?

No — it enhances AdminLTE by loading content dynamically.

Why are modules separated?

To keep the system maintainable, testable, and extendable.

Why expose a global SPA API?

So admin tools, debugger panels, and inline buttons can trigger SPA actions.

Can breadcrumbs be customized?

Yes — use `$breadcrumbOverrides` to rename segments.

Does the SPA support nested directories?

Yes — breadcrumbs and loader work with any depth.

Can I add icons to breadcrumbs?

Yes — modify `breadcrumbs.php` to include `<i>` tags.

Does SPA work with PHP pages?

Yes — it loads any HTML fragment returned by the server.

Can SPA load JSON?

Not by default — but loader.js can be extended.

Can SPA be extended with components?

Yes — the architecture is designed for future component systems.