# Extensibility > The ways to extend Cloud Management Platform (CMP), from importing ready-made content to writing your own --- Site [llms.txt](/llms.txt) --- This page is a map of the extension points, ordered by effort: import content someone has already written, assemble blueprints, attach actions, and then extend the interface. ## Content Library The [Content Library](/docs/cmp/use/catalog/content-library/) is CloudBolt's catalog of ready-made content you can download into your instance, including blueprints, actions, rules, recurring jobs, and UI extensions. Much of it is a complete solution you can use as-is, and the rest serves as a worked example. Start here before building anything from scratch. ## Blueprints [Blueprints](/docs/cmp/use/blueprints/) define the services CMP offers and how it creates and manages them, making them the primary way to extend what users can order. A blueprint is composed of items that deploy infrastructure and actions that run your own logic at each stage of the resource's lifecycle. To offer a service that CMP has no built-in support for, build an [XaaS blueprint](/docs/cmp/developer-resources/guide/blueprints/xaas/). For guidance on writing them, see [Develop blueprints](/docs/cmp/developer-resources/guide/blueprints/). ## Actions [Actions](/docs/cmp/use/orchestration/actions/) are a mechanism for running code inside CMP. Several types are supported, including plugins, remote scripts, and webhooks. What makes actions useful is where they run from: - On demand, when a user selects it: [server actions](/docs/cmp/use/orchestration/actions/server-actions/) and [resource actions](/docs/cmp/use/orchestration/actions/resource-actions/). - On a schedule: [recurring jobs](/docs/cmp/use/orchestration/recurring-jobs/). - When something happens: [rules](/docs/cmp/use/orchestration/rules/). - At a point in a resource's life: [blueprint actions](/docs/cmp/use/blueprints/build/blueprint-actions/) and [orchestration actions](/docs/cmp/use/orchestration/actions/orchestration-actions/). Actions can also replace CMP behavior. For example: - [Generated parameter options](/docs/cmp/configure/order-forms-and-pricing/parameters/generated-options/): determine a parameter's options in code. - [Compute Server Rate](/docs/cmp/configure/order-forms-and-pricing/rates/#compute-server-rate-orchestration-action): substitute your own rate calculation. - [SSO orchestration actions](/docs/cmp/configure/access-and-security/users/sso-saml/orchestration-actions/): configure an SSO user automatically upon login. For how trigger points work and how to write an action, see [Orchestration actions](/docs/cmp/use/orchestration/actions/orchestration-actions/). ## UI customization ### Branding [Branded portals](/docs/cmp/configure/administration/system/branded-portals/) cover the domains, logos, images, and login pages users see. The colors and layout a portal displays come from its [theme configuration](/docs/cmp/configure/administration/system/theme-configurations/), which several portals can share. Neither involves code. For customization beyond them, see [How to white-label CloudBolt](https://support.cloudbolt.io/cloudbolt/s/article/how-to-white-label-cloudbolt--718143776--1) in the support knowledge base. ### Extensions [UI extensions](/docs/cmp/developer-resources/ui-extensions/), or XUIs, add to the interface: new screens, forms, and components; extra tabs on existing pages; and entire workflows. Download them from the Content Library or write your own. ## CloudBolt Forge [CloudBolt Forge](https://github.com/CloudBoltSoftware/cloudbolt-forge) is an open-source GitHub repository where CloudBolt developers share blueprints, actions, and other content. It is a useful reference when you are planning a solution.