Helen Hopkinson
Mar 31, 2008
visibility 6000
star star star star star
(0 votes)

Working with EPiServer CMS every day....

...has its good points, its great points and its not-so-great points! I've recently been very involved in the migration of content from the "old" EPiServer Knowledge Center to the "new" EPiServer World. And I'd be lying if I said that working with EPiServer CMS 5 as an editor every day doesn't make me want to swear out loud sometimes, something I'm sure my colleagues would confirm.

EPiServer CMS is an easy-to-use, intuitive application that makes it easy as pie for Web editors (and anybody else involved with updating a Web site) to add, edit, delete and update information on a Web site. I'm the first one to agree that it really couldn't be easier than it is with EPiServer CMS, and I'm honestly not just saying that because I work at EPiServer.

However....there are also some not-so-great points about the application and I'd like to take just a few moments to dwell on one of these to let my fellow editors know that they are not alone in their occasional editing frustration.

What can possibly have irritated me enough to warrant an entire blog post? Well, it's the "small" things that have got to me over the past few months. I say "small", because they are not a life-or-death bug or feature and do not therefore receive the highest attention from Product Management, and rightly so. One of these "small" things is the bookmark functionality in EPiServer CMS.

To add a bookmark to a page in EPiServer CMS, you place the cursor where you want the bookmark to be entered and either click the Insert Bookmark icon or right-click and select Insert -> Bookmark. Either way opens the Insert Bookmark dialog, where you enter the text that you want to make up your bookmark. But when the Insert Bookmark dialog opens, the cursor isn't automatically placed in the text field where you enter your bookmark. You have to move the cursor with the mouse and click in the Bookmark name field.

Yes, it may seem like a petty thing to all you hard-core developers, but when you have the task of creating at least 10 bookmarks on several hundred Web pages, after the first hundred unnecessary clicks, you get to the stage of wanting to swear out loud, believe me.

So, what am I trying to say with this blog post? To all you EPiServer CMS editors all over the world, whether you're a beginner or advanced EPi user, you're not alone when it comes to occasionally getting irritated by some of the "smaller" issues. Even us editors at EPiServer suffer occasionally, but believe me when I say that I'm fighting for your cause from the inside! Please also feel free to air your frustration about your "small" irritations on the EPiServer User Forum.

Mar 31, 2008

Comments

error Please login to comment.
Latest blogs
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |

Optimizely Content APIs: the Setup the Docs Don't Walk You Through

CMS 13 is pushing things firmly in the direction of Optimizely Graph, but plenty of teams are still running on older CMS versions, or have good...

Andre | Jun 22, 2026