We are using CMS Kit Pro in our application. https://abp.io/docs/commercial/8.1/modules/cms-kit
Right now, the host admin (host) configures CMS Kit Pro and our users can use the features that the host admin has created (pages, blogs, etc.). Now we want to enable multi‑tenancy for CMS Kit Pro. https://abp.io/docs/2.1/Multi-Tenancy
The requirement is: Each tenant should be able to use CMS Kit Pro to create blogs, pages, newsletters, etc.
The end users of that tenant should be able to access this content without login (public website), similar to a WordPress site.
Questions:
1.What is the recommended way to implement this scenario with CMS Kit Pro in a multi‑tenant application?
2.Is there any built‑in feature or recommended pattern for exposing tenant‑specific CMS content (pages newsletter subscription, FAQ, etc.)
3.Publicly without requiring authentication?
Do we need a separate public web site host per tenant, or can we have a single public site that serves different content based on the current tenant?
Any guidance or example configuration (especially for the public website + multi‑tenancy setup) would be very helpful.
We are following this articles to customise the sidebars - https://abp.io/docs/latest/framework/ui/angular/component-replacement?_redirected=B8ABF606AA1BDF5C629883DF1061649A#how-to-replace-a-layout https://github.com/abpio/abp-commercial-docs/blob/dev/en/themes/lepton-x/how-to-use-lepton-x-components-with-angular-custom-layout.md
Initially we used to do it in our previous projects and it was working completely fine. We were using app.module.ts (Traditional Module-Based Configuration).
With ABP studio new update -
we were using app.config.ts (Standalone API-Based Configuration)
we are following the appraoch that we used to follow and the imports
import { LpxSideMenuLayoutModule } from '@volosoft/ngx-lepton-x/layouts'; import { LpxResponsiveModule } from '@volo/ngx-lepton-x.core';// optional. Only, if you are using lpxResponsive directive
these imports I am doing in app.config.ts ,
We are able to see the Customised Sidebars in the UI, but none of the leptonX components are visible in the UI.
like <lpx-navbar></lpx-navbar>, <lpx-footer></lpx-footer> and all.