Cms kit implemention #10717

4 Answer(s)

• 

  0

  AI-Bot created 3 months ago

  Support Team ABP Agent

  • Yes, you can start using CMS Kit in your Angular-based microservice solution after upgrading to a version where “Angular: CMS Kit Module Features” is delivered (as you saw in 10.2 release notes). That means the Angular UI side exists for the CMS Kit features included in that release, but it does not imply the whole CMS roadmap (SEO meta, media gallery, RSS, versioning, etc.) is already there.

  • Whether you should wait for 10.5 depends on whether you need those not-yet-delivered features on day 1:

    • If your requirement is to use the already-available CMS Kit building blocks (blogs/posts, pages, menus, tags, comments, etc.), upgrade now and start integration.
    • If your requirement is specifically SEO meta management, media gallery, RSS feed, content versioning, social streams, then waiting for the target version (10.5 per your notes) avoids rework because you’ll otherwise implement custom equivalents or placeholders.

  • Microservice + Angular integration documentation: I couldn’t find a verified, dedicated “CMS Kit + Microservice Template + Angular” end-to-end integration guide in the official docs via the available context. What is available (verified) is:

    1. CMS Kit module docs (installation/configuration and feature concepts)
    2. General “add module + enable global features” approach (applies to microservice solutions too)

    Practically, in a microservice architecture you integrate CMS Kit on the backend by adding the module to the relevant service(s) (often the “Public Website” / content-facing service) and then expose endpoints via your gateways; and on the Angular side you consume those endpoints / UI packages that ship with the module (once supported).

  What you should do (safe approach for microservices)

  1. Upgrade your solution to the target ABP version you want (e.g., 10.2+ if that’s when Angular CMS Kit support starts for your case).
  2. Add CMS Kit to the relevant service(s) (the service that will own CMS content), using ABP CLI add-module approach, then:
     • Enable the CMS Kit global features in your Domain.Shared’s GlobalFeatureConfigurator (enable all or selected features).
     • Add EF Core migrations for that service and update DB (or let your migrator handle it).
  3. Regenerate / update gateway configurations if your solution uses gateways to expose service endpoints to Angular.
  4. On the Angular side, after upgrading, you can use the CMS Kit Angular UI capabilities that ship in that ABP version. Missing features (SEO meta, RSS, etc.) simply won’t exist yet; you can still use the delivered subset.

  Links you can rely on

  • https://docs.abp.io/en/abp/latest/Modules/Cms-Kit/Index
  • https://abp.io/community/articles/ciqle4sd
  • https://abp.io/community/articles/tiwvceqd

  ---

  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)

  Save Cancel
• 

  0

  maliming created 3 months ago

  Support Team Fullstack Developer

  Hi,

  The latest stable is 10.4 (2026-05-14). 10.5 is currently in RC and the only CMS Kit change in it is the CodeMirror 6 update. The items you listed (SEO meta, media gallery, RSS, content versioning, social streams) are listed in the road map backlog under "Application Modules / UI Themes" but not assigned to a specific release yet (SEO meta has its own feature request at https://github.com/abpframework/abp/issues/16342). When they land, you'll receive them through a regular version upgrade.

  On the Angular side, CMS Kit support was introduced in 10.2 ("Angular: CMS Kit Module Features" in the release notes) and has been stable since then. Angular support here refers to the admin UI — from 10.2 onwards it covers:

  • Open-source: Blogs, Blog Posts, Pages, Tags, Menus, Comments, Global Resources, CMS Settings
  • Pro: Newsletters, Polls, FAQs, Page Feedbacks, URL Shorting, CMS Settings

  So if you move from 9.3.5 to 10.4 you'll get the full admin set above on Angular. The public-facing pages and widgets (blog list/detail, commenting, ratings, reactions, popular tags, newsletter subscription, etc.) are served by the MVC public-web app that the microservice template already includes — that's the public website you enabled with --public-website, where the CMS Kit MVC views and ViewComponents are wired up.

  A note on the upgrade itself: since you're on 9.3.5 (.NET 9), the main step is the move to .NET 10 in 10.0. Run through the 9.x → 10.x migration guide first, then go to 10.4.

  For the integration steps in a microservice solution, the official guide covers everything you need (CLI command, EF migrations, static proxy, gateway routes, and connection string mapping):

  • https://abp.io/docs/latest/guides/add-module-to-microservice
  • https://abp.io/docs/latest/modules/cms-kit-pro (for enabling features via GlobalFeatureConfigurator)

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  yazilim.ithinka created 3 months ago

  [maliming] said: Hi,

  The latest stable is 10.4 (2026-05-14). 10.5 is currently in RC and the only CMS Kit change in it is the CodeMirror 6 update. The items you listed (SEO meta, media gallery, RSS, content versioning, social streams) are listed in the road map backlog under "Application Modules / UI Themes" but not assigned to a specific release yet (SEO meta has its own feature request at https://github.com/abpframework/abp/issues/16342). When they land, you'll receive them through a regular version upgrade.

  On the Angular side, CMS Kit support was introduced in 10.2 ("Angular: CMS Kit Module Features" in the release notes) and has been stable since then. Angular support here refers to the admin UI — from 10.2 onwards it covers:

  • Open-source: Blogs, Blog Posts, Pages, Tags, Menus, Comments, Global Resources, CMS Settings
  • Pro: Newsletters, Polls, FAQs, Page Feedbacks, URL Shorting, CMS Settings

  So if you move from 9.3.5 to 10.4 you'll get the full admin set above on Angular. The public-facing pages and widgets (blog list/detail, commenting, ratings, reactions, popular tags, newsletter subscription, etc.) are served by the MVC public-web app that the microservice template already includes — that's the public website you enabled with --public-website, where the CMS Kit MVC views and ViewComponents are wired up.

  A note on the upgrade itself: since you're on 9.3.5 (.NET 9), the main step is the move to .NET 10 in 10.0. Run through the 9.x → 10.x migration guide first, then go to 10.4.

  For the integration steps in a microservice solution, the official guide covers everything you need (CLI command, EF migrations, static proxy, gateway routes, and connection string mapping):

  • https://abp.io/docs/latest/guides/add-module-to-microservice
  • https://abp.io/docs/latest/modules/cms-kit-pro (for enabling features via GlobalFeatureConfigurator)

  Thanks

  Thank you, I’ll look into it.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 3 months ago

  Support Team Fullstack Developer

  ok : )

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel