Hieu Doan
Optimizely
Dec 4, 2009
visibility 8358
star star star star star
(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

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026