Revenge of the JavaScript Web Part
According to a recent report, JavaScript is used by 93.6% of all websites. To say that's a large amount is a gigantic understatement. Considering the fact that there are over 1 billion websites in the world, that means there has to be at least 100 million different ways JavaScript is used today (it sure feels like it somedays anyway). Even though many developers strive to use the latest patterns, best practices, and modular implementations, the fact is, we all do our client side scripting a little differently. This trend continues into how we use JavaScript in Kentico CMS web development. There are many different ways to handle it in Kentico, and every site seems to have it done just a little bit differently from the next.
There are great articles out there, from some very smart people, on how to best utilize scripts in Kentico. So I'm not going to cover those scenarios in today's blog post. Instead I am going to focus on a real world scenario that I have dubbed "The Revenge of the JavaScript Web part". Basically it boils down to a Kentico quick tip on one very sneaky gotcha, when dealing with the built-in JavaScript Web Part in Kentico. Keep reading to make sure that you are not bit by the same hard learned lesson that my team and I recently went through.