Editing a microsite requires access to every asset used to create the microsite and every source file used to edit the assets in the microsite.

A list of example assets are below. This is not a comprehensive list. This list will change depending on what assets were used to create the microsite and what software those assets were developed or altered in. 

Source Code

When delivering a code package, any developer or source files used to generate the package should also be provided. The expectation is that the Global WCMS team will localize this microsite for other markets, and may have to customize the code. Example: JavaScript libraries that generate JS files or front-end automation tools like Node, Gulp, or Grunt, etc. Include a README if you are using any of these kind of tools to generate a build of the code to be delivered to us.

Example

Here are two pieces of code to compare (they do not do the same thing, just an example of formatting):

$.ajax({
  type: "POST",
  url: "/url",
  data: formData,
  success: function(result) {
    //show thank you message
    if (result == "TRUE") {
      submission_message = "Thanks for your submission!";
      showFeedback("success", submission_message);
    }
});

function r(e, t, n, r, o) {
        var s = e.charAt(0).toUpperCase() + e.slice(1),
            i = (e + " " + x.join(s + " ") + s).split(" ");
        return p(t, "string") || p(t, "undefined")

In the left column, you'll notice there are useful variable names like formData, submissionMessage, showFeedback; we can infer and understand what is going on here. On the right, you'll notice all the variable names are just letters. This was generated and compressed from a different file where the developer has names for the variables that make sense. It is really hard to understand or even guess what the code in the right column is doing. We need the code on the left.

Design Assets

Include any and all design files and assets. We need to be able to export out new versions of images. We prefer Photoshop files as that is what our team has access to. Design web-apps like Sketch or Figma make it hard for us to localize anything. Sketch can export to Adobe XD, but our team does not have access to this software.

Example

When we only get the final asset, it's impossible to localize something like this. It's only one layer. There are words in white that we can't change to a different language. We can maybe paste a different screen on the meter, but that's about all we can do.	In this PSD, it has layers where can easily add different products to create any combination we want. We can also swap phone screens. These are the kind of assets we need.