Writing client side applications in your Episerver-solutions, and creating custom localization functionality in the front end? Why not use what Episerver already has?
Missing wildcard hostname mapping might make the inRiver connector fail when importing resources.
If you're using inRiver PIM with the Episerver connector, and upgrading the PIM system from 6.2 to 6.3, there's a breaking change you should be aware of, that could potentially make products on your page invisible.
Having two-way-relationships between content is a common scenario on the web today. Automatically linking from each end of the relationship to the other. We've composed our own, very simple module to do this - and it's now open sourced!
Many companies set up their own, internal package feeds these days, in addition to all the public ones out there. To create awesome packages, there are a few things you should keep in mind.
Simple lists of label-value-pairs on information pages often result in cluttered views. Tidy those up drastically with some simple UIHint-magic.
With the new Episerver.Forms, you get the opportunity to create your own form elements, which vastly extends the use case for them.
In the new Episerver.Forms, you can control data sources for selection form elements through code. Here's how.
After upgrading the build runner to use VS2015, it could no longer find this assembly.
Have you upgraded your Visual Studio solution to VS2015 and started using the new C# 6.0 stuff, and use TeamCity? I hit a few issues on the way that might be worth sharing.
Container pages without a template has been a concept in the EPiServer community for a long time. And I've always hated them. Here's why.
Sharing the QA checklists for EPiServer CMS 7.5 MVC and Commerce that we use at Epinova.