Ondrej Vasil Technical Leader at Kentico Software

There are a lot of ways how you can insert your JavaScript into a page. Only a few of them are actually a good practice and leave your site more manageable and in a better state performance-wise. In this article, I will show you the best practices for working with JavaScript in Kentico.

This article describes best practices of how you can work with CSS in Kentico. It is divided into two sections. The first section describes a simple scenario, in which a front-end developer wants to write raw CSS without using any advanced tools such as CSS preprocessors or file. The second, more advanced scenario is intended for developers that make use of the more advanced tools and need the CSS files to be stored in filesystem so that they can apply their usual workflow when writing CSS in Kentico.

In this article, we’ll show you the current best practices for implementing a website menu when building a site in Kentico.

Working with transformations in Kentico can seem like a rather complex task. It’s reasonable to follow best practices to avoid any issues in the future.

Let’s assume the following main scenario: You, as a developer, want to add a new article list on your web site’s home page. Content editor has already created the Articles, the design and styling were done by another one of your colleagues and now it’s your turn to make the content shine.

In this post, we’ll focus on the best practices related to transformations used in listing web parts.

You’ve already seen many tweets and posts about the new fancy Kentico 8. Among other features, it brings a new admin experience through the updated user interface, which has been completely redesigned and is light and fresh. From a web development point of view, it was really tough to make it consistent, but at the same time, it was definitely full of web development excitement. Working without a system in place would get us into huge trouble. With this in mind, I'd like to briefly describe what concepts, tools and blocks we used so that you have an overview of "what´s inside".  This will give you a better starting point for your customizations and module development.

Though Google is phasing out its Google Reader service, we still believe that RSS feeds are alive and kicking in our DevNet community.

Hooray! Kentico’s websites have finally been upgraded to Kentico EMS 7, so that we too can leverage all its great features! We managed to keep website outage down to 45 minutes. The automatic upgrade procedure was really helpful, but of course we had to prepare the upgrade of our custom code in advance. What are we looking forward to using the most? Read on.

I’m back with another set of DevNet features we’ve prepared for your better user experience.

You have probably noticed a tiny little window popping up all over the DevNet portal recently, asking you to give us a feedback. This research has highlighted a bunch of key things that we should focus on in order to make your development life a little bit easier. There are a couple of things that have been affected in terms of usability of the DevNet portal.

There have been a lot of changes done in controls and web parts and the Dialogs.css stylesheet reference in new version 6.0. Therefore, it may happen that you'll experience issues connected with CSS styles on some parts of our sample sites. In order to overcome this incorrect behavior, we've prepared a special CSS stylesheet which fixes all those issues. To get complete instructions, please read on.

In this article you’ll see how to integrate a Mega Menu. There are plenty of solutions for complex looking menus with images, link descriptions etc. all over the internet. They are using Javascript, CSS or combination of those two. In this example, we’ll integrate the following Mega Menu solution which is completely CSS driven (which is great from the Accessibility and a bit the SEO point of view): How to Build a Kick-Butt CSS3 Mega Drop-Down Menu