Thanks for being so helpful. I will try to test what you have suggested and will get back to you in case if there is a difficulty.
Have a good day!
Hello EngincanV,
Thank you for getting back to us. We had also been considering the approach of adding the Basic Theme source code and customizing it, so it’s reassuring to hear your suggestion aligns with our initial direction.
Before we move forward with the refactoring process, I’d appreciate it if you could help clarify a few points to ensure we’re proceeding with confidence. Here are our follow-up questions:
Sidebar Menu and Toolbar Support: Our project is essentially an admin panel with features and menus that vary based on the user type. We’re currently using a layout that includes a sidebar menu and a toolbar, both of which are essential and must remain intact. If we proceed with the Basic Theme, will it support customizing or overriding these elements (SidebarMenu, Toolbar, etc.)? Or would we need to consider using Lepton Lite instead—so we can keep things open-source while also preserving those layout capabilities?
Reusability and Upgrade Compatibility: We plan to develop a custom theme (based on either the Basic Theme or Lepton Lite) by overriding styles and components, and then package it for reuse across multiple projects—much like how LeptonX is structured. Once created, will this custom package remain compatible with future updates to .NET, ABP, or the base theme it’s derived from? Or should we expect to manually modify and update the package each time a new version is released?
We hope your insights on these questions will help us move ahead with a clearer picture and greater confidence in our next steps.
Thanks again for your continuous support and guidance!
Best regards, Mansour
