1. Phase 2, International
1.1. Development
1.1.1. Phase 2 components
1.1.1.1. Flip cards (Prabhu)
1.1.1.2. Social Media ??
1.1.1.3. Resource cards ??
1.1.1.4. Resource article templates ??
1.1.1.5. Columned lists ??
1.1.2. Deferred bugs/issues/enhancements
1.1.2.1. Bug scrub to set priority
1.2. Move Try/Buy flows into Brightspot
1.2.1. identify options to meet INTL / TLD strategy requirments
1.2.1.1. Request time from Hansel to walk through how we could achieve what we want (RICK/MICHAEL)
1.2.1.1.1. Need to define next steps with Rick
1.2.1.2. Define the work tasks that need to be done to achieve this
1.2.1.3. Check out eCom emails: what is triggering the language of the emails that are going out today?
1.2.1.3.1. locale=en_US --> the first part of this parameter defines language of emails
1.3. Country specific elements
1.3.1. Add modules on country level
2. SEO
2.1. https://docs.google.com/spreadsheets/d/1q8wY-JuZ1ChC2ihBa8E9vQtoKGd5f8ghZM_dx4SFZoQ/edit#gid=0
2.2. Meeting to define tasks
2.3. Set up meeting with Charmaine to see if we want to do anymore from the list.
3. INTL Migration
3.1. Migration order
3.1.1. engb
3.1.2. de
3.1.3. es
3.1.4. fr
3.1.5. it
3.1.6. nl
3.1.7. se
3.1.8. pt
3.1.8.1. not needed
3.1.9. no
3.1.9.1. not needed
3.1.10. fi
3.1.10.1. not needed
3.1.11. dk
3.1.11.1. not needed
3.2. GEO IP redirect
3.2.1. need a GEO IP DB partner if Demandbase DB is not been used anymore --> research spke
3.2.1.1. https://www.maxmind.com/en/geoip2-country-database
3.2.1.2. https://github.com/fiorix/freegeoip
3.3. product comparison site
3.3.1. potentially use pricing ocmponent
3.4. Migrate eCom flows to BS
3.4.1. try flows
3.4.2. buy flows
3.4.3. general
3.4.3.1. Form processing/validating missing (deprecated) in Brightspot/Dari. Need to develop on our own?
3.4.3.2. new eCom API Client/Catalog Import in Brightspot (already done in Prototype)
3.4.3.3. SSL, at least for payment
3.4.3.4. Need to find out all parameters for configuration
3.4.3.4.1. catalog
3.4.3.4.2. plankey
3.4.3.4.3. region
3.4.3.4.4. promotion
3.4.3.4.5. locale
3.4.3.4.6. validpromo
3.4.3.4.7. nocc
3.4.3.4.8. ipaddress
3.4.3.4.9. defaultPromoCode
3.4.3.4.10. marketo hidden fields
3.4.3.4.11. sfdc
3.4.3.5. automated testing framework
3.4.3.6. Serverside or Javascript Wizard (using angular)?
3.5. PDF handling
3.5.1. lead gen PDFs are today in CQ. Need to find a ways to deal with that.
3.6. Videos
3.6.1. INTL Videos on YT as well?
3.6.1.1. Yes, clarified with Becky / Lindsay. They'll take care. EMEA team to provide list of videos.
3.7. Motionpoint
3.7.1. Discussion needed if we still need to host sites / landingpages still with MP or if we can move away from them
3.7.1.1. All clarified. There'll likely be no more LPs anymore.
3.8. Marketo Forms
3.8.1. Research: how do we make marketo forms INTL in terms of languages dynamically presented
3.9. Chat for INTL
3.9.1. Research - What does need to be changed to integrate moxie on INTL sites
3.9.1.1. Include Alysha prior to launch in order to let her know about the domain changes.
3.9.1.1.1. done, will include here before launch
3.10. EU cookie functionality
3.10.1. Design: https://jira.ops.expertcity.com/browse/WPLTFM-565
3.10.2. Develop: https://jira.ops.expertcity.com/browse/WPLTFM-471
3.11. Opt In rules
3.11.1. Design: https://jira.ops.expertcity.com/browse/WPLTFM-566
3.11.2. Develop: https://jira.ops.expertcity.com/browse/WPLTFM-695
3.12. Impressum
4. Fast Follow Issues (end July deadline)
4.1. Need to add # of seats to square form
4.2. Integration: Tracking Cookies
4.3. Design: Review of all subpages
5. communication to the team (Newsletter)
5.1. Newsletter 1
5.1.1. Domain strategy
5.1.2. Timeline
5.1.3. Rollout plan (which product first, sequence)
5.1.4. Program forge update (Rob to send to Thomas)
5.2. Newsletter 2
5.2.1. Kalender view of June - visual
5.2.2. transparency of components we're working on
5.2.2.1. speak about them being used across all products
5.2.2.2. Provide visual of all components
5.2.3. benefits of the new architecture
5.3. Newsletter 3
5.3.1. Thomas to add
6. Domain Strategy
6.1. Get approval on one-domain strategy (Thomas)
6.2. How do we treat G2W, G2T
6.2.1. Will not change. To remain under GoToMeeting.com/...
6.3. How do we treat G2A
6.3.1. .../remote-support still needs to remain
6.3.1.1. .../remote-support/en-uk
6.3.2. get.gotoassist.com or getgo.gotoassist.com???
6.3.2.1. Matt and Rouven to present to David K to make final decision
6.4. Clarify options with OPS (DEFERRED UNTIL AFTER PHASE 1)
6.4.1. Resource Center (UberFlip)
6.4.1.1. Rob to check with Matt
6.5. GEO IP browser redirect rules- need to be define
6.5.1. https://www.draw.io/#G0B_UERAAOODsFSWZ1RVdwT1VVdzQ
6.5.2. Review with Rick, Steven and Nav (Anh to schedule meeting)
6.5.2.1. Jira Ticket for research spike: https://jira.ops.expertcity.com/browse/WPLTFM-170
6.5.3. Communicate outcome to POs
6.6. Domains Audit (from OPS)
6.6.1. Clean up domains/redirects
6.6.1.1. Reviewed the domains that pointed to CQ but am sure if those are all domains (Thomas)
6.6.1.2. Merge Rob's and Thomas' list and audit
6.6.1.2.1. Provide list of all domains that need to be moved to Brightspot
6.6.2. gotomeeting.com
6.6.3. gotoassist.com
6.6.3.1. meeting to clarify options with Stephen (German Ops team)
6.6.4. gotomypc.com
6.6.4.1. options for subdomian: get.gotomypc.com or others?
6.7. Page URLs Audit (With PO)
6.7.1. Anh check with Annah and SMs to see where we're at.
7. Environments
7.1. Get understanding of general setup
7.2. Meet OPS team to get understanding of time line and to dos
7.2.1. Review docker image/prep work/vanilla instance
7.2.2. Install Github on Stash
7.2.2.1. Define branches, tags, etc.
7.2.3. Build the environment
7.2.4. Deploy Stash on our evironment
7.2.5. Migrate PS Github to our environment
7.2.6. DNS name and resolution
7.2.6.1. Buy and install SSL certs
7.2.6.2. Netscaler config in ED1, stage, production
7.2.7. Build production environment
7.2.8. Define deployment process
7.2.8.1. CI on dev/ED1
7.2.8.2. Research Spike: Jenkins build system overview
7.3. Implementation
7.3.1. Dev environment - No longer needed internally. Going with PSD hosting.
7.3.2. Production: mid May - Going with PSD hosting
7.3.3. PSD guys troubleshooting issues
7.3.4. Jenkins built process
7.3.4.1. BEAM Training
8. Backend-Architecture
8.1. Agree on high level setup of system
8.2. Meeting with Hyoo / Steven and internal Dev Team in order to kick off the architectural setup
8.3. Locale POC
8.3.1. How to set up configuration for country to currency mappings and sites to languages (in BS)
8.4. Implementation
9. MVP
9.1. Agree on what MVP is
9.2. Define needed components
9.2.1. See Jira tickets
9.2.2. Should we allow user selection of language and currency for MVP or just have the pages.?? (Thomas)
9.2.2.1. Language and Country will be selectable in non-US sites if POs do not approve for US sites.
9.3. URL decision
9.3.1. Decide on what subfolder path from gotomeeting.com
9.3.1.1. Rob/Anh to talk with Sara
9.3.1.2. Create GetGo Dev ops Jira for URL change
9.3.1.2.1. Pass over to Kevin when we decide on URL subfolder
9.4. Assessment from PO (Al)
9.5. Implementation
9.6. Go Live Date: 5/26
10. Care pages
10.1. Get requirements in for component development
10.1.1. define needed components
10.1.1.1. Get Satisfaction component
10.1.1.1.1. imports list of topics
10.1.1.1.2. define # of entries
10.1.1.2. Sendgrid
10.1.1.3. Salesforce: to pull self help articles
10.1.1.4. SurveyGizmo
10.2. Define URL/Domain structure
10.2.1. Meet with Thomas for guidence
10.3. Walk care team through INTL setup w.r.t. localizing content and domain structure
10.3.1. Schedule meeting with care team: TLD structure + system architecture
10.4. Implementation
10.4.1. Nav training with Steven
10.4.2. Work on simple component to get experience in developing with Brightspot development
10.4.3. Meet with Rob to talk about architecture
10.5. Migration planning
10.5.1. Page inventory
10.5.2. G2M homepage (MVP)
10.5.3. Setting up Jira board
11. Create slides for high level - high priority items for Phase 2.
12. Integrations
12.1. MVP integrations
12.1.1. define needed integrations for MVP
12.1.2. Integratoin
12.1.2.1. FEC/Commerce Handoff (Trial flow)
12.1.2.2. channeltracking
12.1.2.3. Tealium/AA
12.1.2.3.1. Rob communicating with Sara on domain strategy
12.2. Post MVP
12.2.1. Moxie
12.2.1.1. Integrated via Tealium
12.2.1.1.1. Testing to verify
12.2.2. Optimizely
12.2.3. FEC/Commerce Handoff (Buy flow) [Will do with pricing component]
12.2.4. Demandbase for contact sales form
12.2.4.1. decision: will not be used any longer
12.2.5. YouTube
12.2.5.1. Marketing account for YouTube
12.2.5.1.1. Need requirements define and sent to Lindsay and Becky
12.2.5.1.2. Do inventory of all videos for all products
12.2.6. Cookies: tracked people who clicked on Login for webinar and training
12.2.7. Cookies: track people who have tried other products
13. Migration
13.1. Editors
13.1.1. Who
13.1.1.1. Scrum masters
13.1.1.2. Designers
13.1.2. How long
13.2. Redirects
13.2.1. Can we handle redirects through BS?
13.3. Define plan with Annah
13.3.1. https://docs.google.com/document/d/1IuLK5q4Moia_qp7uTwc250avDSIWfkRvD2fUMDwah7Y/edit
13.4. Add canonical tags to section pages in Jira
13.4.1. <link rel="canonical" href="http://example.com/blog" />
13.4.2. Michael has this task. Might not need to add them manually. https://jira.ops.expertcity.com/browse/WPLTFM-120
13.5. G2A/P Migration
13.5.1. LPs
13.5.2. Resource Articles
13.5.3. Redirect set ups
13.5.4. URL assignments
13.5.5. Internal links checks
14. Frontend-Architecture
14.1. Define Frontend Architecture
14.1.1. Implementation of the FE JS framework
14.1.2. Training: Non platform devs, care devs, Michael
14.1.3. Documentation: confluence page (on-going)
14.1.3.1. Javascript
14.1.3.2. Localization
14.1.3.3. Build system (grunt)
14.2. Implementation
15. Phase3 and Beyond
15.1. Future Integration points
15.1.1. CloudSearch (Care: would replace SF search)
15.1.2. Concierge chat
15.1.3. AWS/ElasticCache or CloudFront (Care: would replace SF article service)
15.1.4. Marketo (post to)
15.1.5. Salesforce (post to)
15.2. Translation
15.2.1. Motionpoint translation API (ROB)
15.2.2. Thomas to follow up with Dmitri
15.2.2.1. Support site
15.2.2.2. Salesforce articles
15.2.3. Meet with Maren about overall strategy
15.2.4. Define localization requirements for CMS