Hieu Doan
Dec 4, 2009
  8049
(1 votes)

Organize your Composer functions in the Toolbox

I got a question from a customer that they wanted to organize theirs 30+ Composer functions in the toolbox somehow to make the life easier for the editors when they creating Composer content. This article will give you an instruction on how you can do that.

Define category root for Composer

Composer uses the standard categories in EPiServer CMS for categorizing theirs functions. By default, Composer add a category in the first level with name “Extension Category” and define this as the root category for Composer.  Of course you can change the root by going to the Composer admin, under the tab “Settings” and select another category as root in the list “Category root for Composer”.

clip_image002

 

Creating Composer categories

Go to the tab “Categories” and add some categories. You can also doing this by using the EPiServer standard category manager (Admin  -> System Administration –> Edit categories) but only the first child level under the category, which was defined as root for Composer in previous step, will be used.

clip_image002[5]

 

Categorizing Composer function

Now you can organize your functions by editing the Composer function definition under the tab “Function types” and select the category/categories.

clip_image002[7]

 

And the result…

clip_image002[9]

 

That’s all. Now it’s easier to find the functions you want to work with. All functions that not been grouped by any category are placed under the “Uncategorized” group.

Dec 04, 2009

Comments

Please login to comment.
Latest blogs
Creating an admin tool - unused assets

Let's make an admin tool to clean unused assets and see how to extend your favorite CMS with custom tools and menues! We will build a tool step by...

Daniel Ovaska | Apr 15, 2026

Running Optimizely CMS on .NET 11 Preview

Learn how to run Optimizely CMS on the .NET 11 preview with a single-line change. Explore performance gains, PGO improvements, and future-proofing...

Stuart | Apr 15, 2026 |

Your Optimizely Opal Is Probably Burning Carbon It Doesn't Need To

Four patterns Optimizely practitioners could be getting wrong with Opal agents: inference levels, oversized tool responses, missing output...

Andy Blyth | Apr 15, 2026 |

Optimizely CMS 13: A Strategic Reset for Content, AI, and Composable Marketing

Optimizely CMS 13 is not just another version upgrade—it represents a deliberate shift toward a connected, AI-enabled, and API-driven content...

Augusto Davalos | Apr 14, 2026

The 74% Problem: Why Most Companies Are Getting AI Wrong

I’ve seen this before… The pattern. The rush, the excitement, the scramble to adopt something new before anyone has stopped to ask what problem it...

Mark Welland | Apr 14, 2026

Scheduled jobs with parameters

Scheduled jobs is an integral part of most Optimizely solution but the UI has, in my opinon, always been lacking in usability and features. Earlier...

Per Nergård (MVP) | Apr 14, 2026