SOP - DXT JSON Projects (Merch)
- Rachael Mink
- Hope Skinner
| STANDARD OPERATING PROCEDURE | |
|---|---|
Title DXT JSON Projects | Effective Date October 2019 |
Department eBusiness | Business Owner Farid Mokraoui |
Purpose
This document outlines the key processes and policies for JSON projects.
Important Notes –
- Decision to use JSON for a project will be determined by the DXT
- JSON is best used for templatized projects such as recurring promotions
- 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.
- For category pages, Merchandisers will receive template pieces they can use to copy/paste into spreadsheets as needed for their pages.
- 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 set to Merchandisers for XM set up.
JSON Process Flow
- Google spreadsheet is created by DXT
- All page/banner data is manually inputted into Google spreadsheet by Merchandiser
- Spreadsheet is exported into valid JSON format by DXT
- HTML/JavaScript/CSS files are uploaded to WCS
- JavaScript parses JSON file data which is then outputted as HTML
- This step happens in the browser on page load
- Data rendered on page comes from the spreadsheet
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.
| WF Task | Turnaround Time | WF Concurrent Task | Turnaround Time |
|---|---|---|---|
| JSON spreadsheet discovery/logic creation (DXT/Merch) | 3 days | JSON spreadsheet shared with Merchandiser (DXT) | 1 day |
| HTML/CSS development (DXT) | 5-10 days | JSON spreadsheet population (Merch) | 5 days |
| JSON/JS development (DXT) | 10-15 days for new template 5 days to reuse or adapt previous template | ||
| JSON spreadsheet review/export (DXT) | 2 days | WCS asset set up / ID delivery (DXT) | 5 days |
| Staging review (DXT/Merch) | 3 days | Spreadsheet edits (Merch) | 2 days |
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.