Building an Episerver Component with Dojo including Localization and Context

I'm rather torn about whether or not to break this up into multiple, topical posts as it threatens to be a bit long. We'll see how it goes... (ended up being one very long post)

I recently released a new "Page Preview" package for Episerver 10+ that adds a (somewhat large and obvious) Page Preview button to the author components / gadgets. The add-on is documented in the Git repo linked. This article (or series) is more about creating such a gadget - I'm going to keep it as high-level and logical as I can.

My add-on uses a Partial Router to function, which is merely utilized by the functionality the add-on is meant to provide, not core to the fact that it is a component. So though that is in my code, it's not covered here. I do cover building a partial router in the docs I wrote for my Episerver Ascend 2017 presentation and the topic is definitely worth a Google if you've a mind to check it out.

Quick Tip: Localized Strings in Episerver Attributes

I have a few blog posts I want to get done, but for now I'm starting with a quick tip I wanted to put out there for any newbie developers working in Episerver or working with translations in the authoring environment. I'm rather new to it at the moment, so every little bit helps.

This post is a quick solution to providing translated (or translatable) text that's being set within one of Episerver's class or property attributes - where only constants are expected.