Hello Team,
In our previous tickets, we raised concerns regarding CMS functionality not working properly in Angular-based ABP projects.
We recently noticed that in the 10.1 final milestone (https://github.com/abpframework/abp/milestone/131?closed=1 ), the following items have been implemented:
- Angular – Implementing the CMS Kit module features
- Angular – Dynamic Form Component
- Dynamic form component
However, the official documentation does not yet appear to reflect these updates, particularly regarding installation steps, configuration, and integration guidance for Angular projects. We are planning to implement CMS Kit in our Angular-based solution before March, and clear documentation is critical for us to proceed confidently.
Could you please guide us on:
- The correct installation steps for CMS Kit in Angular projects
- Required module dependencies and configurations
- Any breaking changes or migration notes
- Expected timeline for documentation updates
Looking forward to your guidance.
Thank you.
4 Answer(s)
-
0
As of what I can verify from the available sources/tools right now, there is no published/verified “CMS Kit for Angular” installation & integration documentation, and I also couldn’t locate any
@abp/ng.*cms-kit*(or similar) Angular package/module implementation in the indexedabpframework/abprepository via code search.Because of that, I can’t provide definitive step-by-step Angular installation/configuration instructions for CMS Kit (packages to install, Angular modules to import, routes/menu contributions, proxy generation modules, etc.) without guessing.
Milestone link you referenced is reachable and confirms you’re looking at ABP 10.1 milestone items, but it doesn’t itself provide consumable installation steps for Angular:
- https://github.com/abpframework/abp/milestone/131?closed=1
For general Angular setup verification (not CMS Kit specific), these official quick-start pages are reachable:
- https://abp.io/docs/10.1/framework/ui/angular/quick-start
- https://abp.io/docs/latest/framework/ui/angular/quick-start
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hello,
The CMS Kit Admin feature has been postponed and will be available with the 10.2 preview release. You can follow the release notes here: https://github.com/abpframework/abp/releases
Below are the steps to configure the frontend for an existing project.
- Install the required packages
yarn add @volo/abp.ng.cms-kit-pro yarn add @abp/ng.cms-kit yarn add codemirror yarn add @toast-ui/editor- Update
app.config.tsAdd the CMS Kit providers to your providers array:
import { provideCmsKitProAdminConfig } from '@volo/abp.ng.cms-kit-pro/admin/config'; import { provideCmsKitAdminConfig } from '@abp/ng.cms-kit/admin/config'; export const appConfig: ApplicationConfig = { providers: [ // ... provideCmsKitProAdminConfig(), provideCmsKitAdminConfig(), ] };- Update
app.routes.tsRegister the CMS routes:
export const APP_ROUTES: Routes = [ { path: 'cms', loadChildren: () => Promise.all([ import('@volo/abp.ng.cms-kit-pro/admin').then(c => c.createRoutes()), import('@abp/ng.cms-kit/admin').then(c => c.createRoutes()), ]).then(([proRoutes, cmsKitRoutes]) => [ ...proRoutes, ...cmsKitRoutes, ]), }, ];- Update
angular.json
"styles": [ "node_modules/@toast-ui/editor/dist/toastui-editor.css", "node_modules/@toast-ui/editor/dist/toastui-editor-only.css", "node_modules/@toast-ui/editor/dist/toastui-editor-viewer.css", "node_modules/@toast-ui/editor/dist/theme/toastui-editor-dark.css", ]
Dynamic Forms are now available in the latest stable release. The documentation will be updated shortly. In the meantime, you can access the related document here:
https://github.com/abpframework/abp/blob/37bec2f8abc03a8747024497f4839ad0449018d4/docs/en/framework/ui/angular/dynamic-form-module.md
Please let us know if you need any further assistance. Thank you for your cooperation.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi, Thanks for the follow-up. At the moment, this depends on the ABP version you are targeting:
- If you are staying on
10.1.x, then yes, CMS Kit admin features are not available in Angular out of the box. In that case, admins cannot manage pages, menus, blogs, and similar CMS Kit admin screens from the Angular UI. - If you move to
10.2.xpreview/RC, Angular CMS Kit packages have started to become available. The published Angular package@abp/ng.cms-kitincludes admin routes for comments, tags, pages, blogs, blog posts, menus, and global resources, so page and menu management can be done from Angular in that version line. - There is also a published commercial package named
@volo/abp.ng.cms-kit-prostarting with10.2.0-rc.1. So, to answer your question directly: - For
10.1.x: your understanding is correct. You should not plan on using CMS Kit admin features from Angular. - For
10.2.xpreview/RC: Angular support has started to exist, and page/menu-related admin functionality is no longer limited to MVC/Blazor only. The confusing part here is that the public CMS Kit documentation is still behind the current package state. The current10.1and10.2CMS Kit module pages still mention MVC/Blazor-oriented support, so the documentation has not fully caught up with the Angular package publication yet. If you need a stable production plan today on10.1.x, we recommend using the MVC / Razor Pages or Blazor admin UI for CMS Kit, or building custom Angular screens on top of the CMS Kit admin APIs. If you want, please share your exact target version (10.1.xor10.2.x) and we can provide the corresponding Angular installation guidance for that version. Best regards, ABP Support Team
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) - If you are staying on