Fully Adaptive / Responsive Singular Codebase

1. What points are we adapting to?

1.1. Action: Research into the ideal breakpoints

1.2. How to handle scaling & performance

1.3. Singular master.css include across both contexts

1.4. Action: What's the ideal tablet experience & breakpoints?

1.5. Action: What's the ideal mobile experience & breakpoint?

1.6. Research & share with team

2. Vendor Integrations

2.1. Tealium: Merge Tealium anthro-us & anthrous-mobile profiles

2.2. BV: How to handle the full content injection approach? Rewrite BV implementation.

2.3. Olapic

2.4. Rich Relevance

2.5. Action: Create a Wiki defining the current vendor implementations and determine which need to be rewritten for a singular context

3. Performance

3.1. Use picture fill or polyfill for images

3.2. Change out development approach to modularly load and inject

3.3. Action: Create a Performance SLA for each important page type: Homepage, Product, Category, etc.

3.4. Images & Media

3.4.1. Action: Investigate Picturefill or new tag types

4. Typography & Font Choices

4.1. Handwritten fonts - how to handle?

4.2. SVG & Font Icons

4.3. Action: Create a best practices guide for feature development to go along with a standardized style guide.

4.4. Web Fonts Usage

4.5. Using %, ems, rems over Pixel specificity

5. Mobile-first Design Paradigm

6. Analytics

6.1. What tagging needs to be updated if we merge mobile & desktop?

7. Current Mobile Specific or Desktop Specific Features

7.1. Action: Document a feature mapping by context: what exists in Mobile and not Desktop, vice versa.

7.2. Example: Quickshop for Desktop

7.3. Example: "Include in Mobile" flag

8. SEO

8.1. How to handle meta tags & canonicals?

8.2. Action: Request a best practices or action plan from our SEO vendor agency & Allie B.

8.3. Redirects: How to handle old mobile pages?

9. QA & Testing

9.1. Action: Define Browser Support Matrix

9.2. How to test across Devices?

9.2.1. Action: Set up L & L on BrowserStack, give access

9.3. Set up VM's for Automated QA testing

10. Internal Training & Education

10.1. Action: L & L on Adaptive, Responsive, etc. for working teams & executives

10.2. Change Verbiage from Mobile to "Small Screen"

10.3. Change Verbiage from Desktop to "Large screen"

11. How to Rollout?

11.1. Action: Begin mapping out plan for Adaptive Header for Mobile/Desktop (all angular

11.2. Action: Map out the Angular Roadmap - what's been rewritten already, what needs action. Prioritize those above other pages.

11.3. Can we A/B test any particular approach before launching?

11.4. Action: Set up a Content Map of Pages between Mobile & Desktop

12. A / B Testing

13. Approvals

13.1. From a UX & Design perspective, how do we showcase a design for approval?

14. Content Workflow

14.1. How do we build out homepages, landings & banners for an adaptive site?