SOP - DXT Shop By Job asset build process (Merch)

Purpose

This document outlines the key processes and policies for creating Shop By Job landing page and banner assets.

Important Notes

• A valid Gmail address is required to access all Google spreadsheets and documents
• JSON process will not begin until all designs are signed off and approved. Changes to the design template after design approval can impact the delivery date for a project.

Policies and Procedures 

DXT File Ownership

• Google spreadsheet initial setup will be done by DXT. Folders and files will be shared with Merchandisers for access.
• A separate spreadsheet is assigned to each of the KOBs .
• Spreadsheet export will be handled by DXT for JSON validation and WCS upload. WCS asset creation will be handled by DXT.
• Slot asset IDs will be sent to Merchandisers for XM set up.

SBJ - Landing Page Process Flow 

1. Google spreadsheet is created by DXT
2. All landing page/banner data is manually inputted into the Google spreadsheet by the Merchandiser
   Note: The pageID (column B) and h1 (column C) data on the spreadsheet is taken from the SEO document that the Web Content Team provides and will be entered by the Merchandiser. The pageID uses the title info found between the opening and closing <title> tags and the h1 uses the h1 info found between the opening and closing <h1> tags. This data must be copied verbatim, without surrounding HTML tags. An example of this document can be viewed here: https://docs.google.com/document/d/1dS_gkTPnOxcfXEhC-bFxTw8tWEzsU8Wd5dWoGWDmqd8/edit?usp=sharing
3. Spreadsheet is exported into valid JSON format by DXT. The exported files can be found in the corresponding KOB's folder in Google Drive: https://drive.google.com/open?id=1pmx1RRkjzzaWN5yJ_LANJHEjdKTqApNT
4. Valid JSON file is entered into WCS by replacing the current data in the KOB's pre-existing JSON asset
   Note: All JSON assets are documented in the Asset Reference Spreadsheet linked below. A new JSON asset should only be created if it does not yet exist for that KOB and should be documented in the Asset Reference Spreadsheet after it has been created in WCS
5. Build landing page assets in WCS
   1. Shop By Job page header - asset (2600004452984) is global and used on all SBJ pages
   2. Title / H1 - a single asset for each KOB is used to generate this content. See Asset Reference Spreadsheet for each KOB's unique asset ID for this page section. If a new H1 asset is needed, use the following HTML:
      <div class="b-container"><div class="section js-content" data-campaign="2600006356248" data-section="Heading">&nbsp;</div></div>
      Note: The data-campaign attribute requires the asset ID for the corresponding KOB's JSON file in WCS. Do not modify the data-section "Heading"
   3. Before Login SEO content - this content is entered manually by DXT into a new asset for each job and is marked up in the WCS HTML block as follows:
      <div class="section">Paste login blurb content from document provided by Web Content Team here. Mark up all text that includes an URL with anchor tags and use links provided within the document</div>
   4. Product Content Section(s) - before creating a new product section asset, check that one has not already been created in WCS for that KOB's section title. Section titles are identified in column D of the JSON Google Spreadsheet. Common and recurring section assets are documented in the Asset Reference Spreadsheet and can be reused across multiple pages in the same KOB. These assets cannot be used across multiple KOBs as the HTML in the asset code references the unique asset ID for each KOB's JSON file in WCS. If a new Product Section Asset is needed, use the following HTML:
      <div class="b-container"><div class="section js-content" data-campaign="2600006356248" data-section="Materials">&nbsp;</div></div>
      Note: The data-campaign attribute requires the asset ID for the corresponding KOB's JSON file in WCS. Enter the section title data from column D in the JSON Google Spreadsheet for the section being built into the data-section attribute
   5. SEO content block - this content is entered manually by DXT into a new asset for each job and is marked up in the WCS HTML block using the same code as the Before Login SEO Content section. 
      Note: This asset must also have the SBJ Global Javascript asset (2600008114549) attached to the JS dropzone on the WCS asset. It is critical that the JS asset be attached and that the SEO Content block appear last in order of assets on the page when set up in XM
6. DXT provides asset IDs to Merchandiser for page setup in XM

SBJ - Home Page Grid Slot Banner Process Flow

SBJ - PLP Grid Slot Banner Process Flow

SBJ - PLP List Slot Banner Process Flow

SBJ - Industry Solutions Content Slot Process Flow

Important Documents

Google Spreadsheet for Each KOB:

Builder
https://docs.google.com/spreadsheets/d/1xtQsX0dBQ6md45PgIAgpCpQQZ9Et6ynkW8aOrn4g8ew/edit?usp=sharing
Commercial
https://docs.google.com/spreadsheets/d/15DWbnX8MWLpE18c6G5Tma3VSxnEDgKxjKG-FrhuA1v4/edit?usp=sharing
FFS
https://docs.google.com/spreadsheets/d/1X7w3_Uog9OmKbMQQ4FCk4wsH3NRRsgsviBrYJ1gf6Oo/edit?usp=sharing
HVAC
https://docs.google.com/spreadsheets/d/1Yv8eVID9jfW-JShKIsqJlpaUVLvEv2sdNneSVQ8FVS4/edit?usp=sharing
ResTrade
https://docs.google.com/spreadsheets/d/1lfrUOIGLJFxmU2jw2S-QVaKTI7vTSeYqwuTc6qBSb0o/edit?usp=sharing
Waterworks
https://docs.google.com/spreadsheets/d/1R0UN2IEMzqswZX-7cxSFXd3VOSjZ0uoC4w5FQTO7W1U/edit?usp=sharing

Asset Reference Spreadsheet:

https://docs.google.com/spreadsheets/d/1cUeH9vNwHlIbJtW35OmeZ3QANNayqPT80vdokAunQnw/edit?usp=sharing

Turnaround Time

Expected Turnaround Time – The turnaround time for a project utilizing JSON can vary, with more custom experiences needing the most time to build and test. Many of the below tasks happen concurrently.

Maintaining JSON Assets after Publish - Once page is in staging and live on the site, any spreadsheet updates/exports will be processed late morning and late afternoon (2x daily). This is to accommodate preview and testing for the next publishing window. To update an existing asset utilizing JSON, please submit a QF ticket to process your changes.