World is now on Opti ID! Learn more

Hieu Doan
Dec 4, 2009
  5055
(0 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
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |