<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Nenad Nicevski</title><link href="http://world.optimizely.com" /><updated>2025-03-05T22:06:56.0000000Z</updated><id>https://world.optimizely.com/blogs/nenad-nicevski/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Optimizing Experiences with Optimizely: Custom Audience Criteria for Mobile Visitors</title><link href="https://blogs.perficient.com/?p=378170" /><id>In today&amp;#8217;s mobile-first world, delivering personalized experiences to visitors using mobile devices is crucial for maximizing engagement and conversions. Optimizely’s powerful experimentation and personalization platform allows you to define custom audience criteria to target mobile users effectively. By leveraging Optimizely’s audience segmentation, you can create tailored experiences based on factors such as device type, operating [&amp;#8230;]</id><updated>2025-03-05T22:06:56.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Anchor/Jump Links – simple example, but useful</title><link href="https://blogs.perficient.com/?p=332476" /><id>Having additional navigation for your content is a must-have in any modern website. One example of that kind of navigation is Anchor/Jump links navigation. Simple, but very effective. We are simply using anchor links to jump to a specific part of the page. But since we are using the Optimizely CMS we are gonna make [&amp;#8230;]</id><updated>2023-04-26T20:04:25.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Custom XhtmlString Render Service – Force Absolute URL for Images</title><link href="https://blogs.perficient.com/?p=317609" /><id>Working with a headless website setup sometimes can be challenging. For example, if you insert an image directly into the TinyMCE text editor sometimes (it depends on a lot of factors) you can see the relative path to the server storage where the image is saved. But because it&amp;#8217;s a headless setup, the front end [&amp;#8230;]</id><updated>2022-10-07T15:12:55.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Content Delivery – Removing necessary fields and how to add new fields to the API response</title><link href="https://blogs.perficient.com/?p=316570" /><id>What is a headless CMS? A&#160;headless CMS&#160;is a back-end only content management system (CMS) built from the ground up as a content repository that makes content accessible via a RESTful API or GraphQL API for display on any device. The term “headless” comes from the concept of chopping the “head” (the front end, i.e. the [&amp;#8230;]</id><updated>2022-08-24T10:46:57.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>How to enable Webpack on your Episerver Project</title><link href="https://blogs.perficient.com/?p=284258" /><id>If you&amp;#8217;re building modern web applications, you need to carefully consider the front-end technology stack you use. Webpack, a static module bundler, combined with NPM for package management is a great starting point. Here&amp;#8217;s how you can incorporate these technologies into your Asp.net MVC application built upon Episerver. Alongside Node.js we need to have node-sass [&amp;#8230;]</id><updated>2020-12-01T14:21:46.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Page Restrictions in an Initialization Module</title><link href="https://blogs.perficient.com/?p=284189" /><id>Managing your AllowedTypes (insert options) in Episerver can become overwhelming, depending on the strategy you take. You can read about different options here: https://world.episerver.com/blogs/Henrik-Fransas/Dates/2015/10/the-known-and-unknown-of-include-includeon-exclude-and-excludeon/ https://world.episerver.com/documentation/Items/Developers-Guide/Episerver-CMS/75/Content/Attributes/ but there is a strategy you can take for a very developer-friendly approach. As highlighted on Epi World forum thread (Dylan McCurry and I worked together on the project where [&amp;#8230;]</id><updated>2020-11-24T16:28:32.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Episerver YouTube Video Block</title><link href="https://epijocks.com/?p=218" /><id>Video for Content Editors These days, every website has some video content. We wanted to make editing video easier for Epi content editors, so we created the YouTube Video block. This block is a feature of our new SCORE for Episerver platform, which launched in 2019. To create the best editor experience with on-page editing [&amp;#8230;]</id><updated>2020-03-05T16:47:17.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>