Smartling GDN - POC - Discovery

### Background
We've contracted the GDN with Smartling since the contract began, but we haven't used it. This issue is to track a Proof of Concept for the Smartling GDN prior to contracting it this year.

Note the DRI of the POC will be the Digital Experience team (this issue can be moved if necessary). 

### Proof of Concept Options
1) Full Deployment - This includes a full deployment of the Smartling GDN and will require Smartling Professional Services to implement. Professional Services hours for this type of POC ranges from 25-30 hours, estimated cost is $5,000-$8,000. The reason for the cost is that we would be able to continue to use the GDN once it is set-up and we add it to the contract.
1) Partial Deployment - We would select a few pages (number TBD) and Smartling would connect these to show us how it works. If it is only a few pages, there wouldn't be a cost to this.
1) In depth technical demo - This would be a 90 minute call with Smartling where they would show us (on their site), a step-by-step demo of how the GDN works. This would not be on our site.

### Comments from Smartling
- Prior to any POC, Smartling requested that we define what a successful POC looks like.
- Our next steps on the website evaluation will be to arrange a technical demo of the GDN on the GitLab website highlighting any specific use cases or actions the team would like to validate.
- Similarly, we can schedule a discussion of the pros and cons to use our Repository Connector Vs the GDN to support the website translation initiative both are great options, the deciding factors will be based on your overall strategy/objectives of the website translations project and the team's desired experience/LOE.

### Next Steps
- Determine what we would like to get out of the POC? What questions are we trying to answer / what does success look like?
- Determine which POC option we are most interested in based on the POC goals.
- Technical discussion with Smartling related to using the GDN or the Code Repo for website translation.


### Requests from Smartling
Smartling asked that we answer these questions prior to our GDN discussion.

1- What is the business objective surrounding translations? (Ex: Drive more leads to the website, convert more leads on the website, support an existing international sales team to convert more deals, etc)
 * Answer: Drive more leads, support an existing sales team to convert more deals

2- What success metric will you be tracking against as it relates to translation (Website metrics (traffic, conversion rates, page views, bounce rate, etc), sales team conversation success, new user adoption, decrease in support tickets, etc)
 * Answer: Website metrics, new INQ, trials
 
3- Please list in the order of priority the content you are looking to translate. (Specific websites, Landing Pages, Blogs, Web application)
 * Answer: Ultimately, we will translate about.gitlab.com and all navigation pages. To start with the POC, we will translate the [Homepage](about.gitlab.com), [Why Gitlab](https://about.gitlab.com/why-gitlab/), [Pricing Page] (https://about.gitlab.com/pricing/)

4- What Technology do you use to create and/or serve this content? (CMS, Marketing Automation, E-Comm Platform, Other?)
 * **Need answer**

5.1- What source language is your content in?
 * Answer: English

5.2- Which language(s) are you translating into?
 * Answer: Japanese, French, German

6- What are your annual translation volumes? (best guess of plan is fine)
 * Answer: Currently around 160k processed words for marketing, but this is expected to increase. Web hasn't been started yet.

7- Stakeholders
a. Who needs to be involved in the evaluation?  Answer: Digital Experience team, Marketing Ops, others TBD
b. Who will be using the tool?  Answer: Digital Experience team (technical GDN), project management DRI TBD
c. Who will be vetting the technology and integration path? Answer: Digital Experience team
d. Who is the budget holder for sign-off? Answer: Marketing Operations

8- Describe your ideal translation process.
 * **Answer: Need answer**

9- Describe the challenges you are facing in the current process.
 * Answer: No solution for web translations currently in place.

10- What do you need to see in our solution to move forward with Smartling? 
 * **Answer: Need answer, what does success look like**


@RLeihe268 @mpreuss22 @davidbrown1 @justin.vetter @laurenbarker 


<!-- Please leave the label below on this issue -->

Story points: 4.0