Commit 0d2090f5 authored by Ernst van Nierop's avatar Ernst van Nierop

remove main uni page and change links to it

parent a64b4cea
......@@ -31,7 +31,7 @@ Please search for similar proposals before posting your own.
* [GitLab Community Forum](https://forum.gitlab.com/): this is the best place to have a discussion.
## Reference
* [GitLab University](https://about.gitlab.com/university/) contains a variety of resources.
* [GitLab University](https://university.gitlab.com/) contains a variety of resources.
* [GitLab CE documentation](http://doc.gitlab.com/ce/): information about the functionality in GitLab for users, administrators and developers.
* [GitLab documentation](https://about.gitlab.com/documentation/) contails links to documentation for all GitLab applications
* [The GitLab Cookbook](https://www.packtpub.com/application-development/gitlab-cookbook): written by core team member Jeroen van Baarsen, it is the most comprehensive book about GitLab.
......
......@@ -23,7 +23,7 @@ Please use <a href="https://gitlab.com/gitlab-com/www-gitlab-com/issues">issues<
* [Security](/handbook/security)
* [Support](/handbook/support)
* [Leadership](/handbook/leadership)
* [GitLab University](/university/)
* [GitLab University](https://university.gitlab.com/)
## This page
......
......@@ -3,7 +3,7 @@ layout: markdown_page
title: "Sales Onboarding"
---
Every salesperson who starts at GitLab will enter an intense 30-day sales bootcamp. The weekly class schedule can be found at [GitLab University](https://about.gitlab.com/university/). In addition, once a new salesperson starts, their manager will create an issue for each of the first 4 weeks, tracking the progress of the new hire.
Every salesperson who starts at GitLab will enter an intense 30-day sales bootcamp. The weekly class schedule can be found at [GitLab University](https://university.gitlab.com/). In addition, once a new salesperson starts, their manager will create an issue for each of the first 4 weeks, tracking the progress of the new hire.
### Week 1 Test
1. [Version Control Systems Test](http://goo.gl/forms/8H8SNcH70T)
......
......@@ -36,7 +36,7 @@ title: "Sales Process"
* [Client Use Cases](https://about.gitlab.com/handbook/use-cases/)
* [Customer Reference Sheet](https://docs.google.com/spreadsheets/d/1Off9pVkc2krT90TyOEevmr4ZtTEmutMj8dLgCnIbhRs/edit#gid=0)
* [GitLab University](https://about.gitlab.com/university/)
* [GitLab University](https://university.gitlab.com/)
* [Our Support Handbook](https://about.gitlab.com/handbook/support/)
### GitLab Version Check <a name="version_check"></a>
......
......@@ -58,7 +58,7 @@ get a better handle on what people are looking for and/or not finding.
**Decrease Demand for Support**
By making training materials for customer trainings available on [GitLab University](/university),
By making training materials for customer trainings available on [GitLab University](https://university.gitlab.com/),
making documentation easy to find and easy to search, and constantly contributing to further documentation
with the trend discovery showing where the need is greatest, we can help the community become
as self sufficient as possible. A seamless interface between the support team and developers closes the
......
......@@ -39,7 +39,7 @@ expected to:
## First steps when you join the team <a name="first-steps"></a>
When you first join the team everything will be new to you. In order to get you started with GitLab quickly
you should take a look at the resources we have available at the [GitLab University](https://about.gitlab.com/university/).
you should take a look at the resources we have available at the [GitLab University](https://university.gitlab.com/).
The [user training](https://gitlab.com/gitlab-org/University/tree/master/training) we use for our customers
is also a great resource to get you started with the basics of Git and GitLab.
......@@ -66,7 +66,7 @@ craft their replies, and to get more insight and knowledge into topics with whic
### Training<a name="training"></a>
Right after joining the team you will go through a [training process](/university/support)
Right after joining the team you will go through a [training process](https://university.gitlab.com/support/)
with the guidance of a fellow Service Engineer. In this training you will learn the ins and
outs of GitLab, how to integrate it with the most used enterprise tools, like LDAP, JIRA,
Jenkins and SAML, how to best talk to our customers, and how to best radiate information you
......@@ -90,12 +90,12 @@ craft a proper answer, you are acknowledging their request.
### Point to documentation, or make it<a name="document-it"></a>
As a general rule, you should always include a link to the applicable documentation as
part of your response to a ticket. If the documentation does not exist yet, then
As a general rule, you should always include a link to the applicable documentation as
part of your response to a ticket. If the documentation does not exist yet, then
_make_ the documentation and send the link in the response. For those situations
where making documentation is a more time consuming exercise:
where making documentation is a more time consuming exercise:
- add the "documentation" tag to the ticket,
- add the "documentation" tag to the ticket,
- respond to the ticket,
- create an issue on the [GitLab CE](https://gitlab.com/gitlab-org/gitlab-ce/) or
[GitLab EE](https://gitlab.com/gitlab-org/gitlab-ee/) repo linking to the ZenDesk
......@@ -215,14 +215,14 @@ When you are viewing a ticket teammates see an eye icon on the left of the ticke
This implies that you're reading or working on the ticket so if your not going
to handle it make sure to close it by closing the tab at the upper section of the
screen that has the ticket's title.
screen that has the ticket's title.
If you see a ticket with this icon that either you feel you can add value to it,
or has been open for too long then please ask your teammate through Slack if he
or she is still working on it. The person's name appears by hovering over the,
ticket's title on the list view or by selecting the ticket and reading the
"Also on this ticket" section on the top left. Notice that if a general account
like GitLab Support is being used there is no name to refer to so you might want
like GitLab Support is being used there is no name to refer to so you might want
to ask on the support and/or general chat channel with the ticket's link.
## Receiving feedback<a name="feedback"></a>
......@@ -231,7 +231,7 @@ After 24 hours of marking the ticket as solved a survey is sent to our customers
the level of support they received. If a customer rates a ticket to which you were assigned as bad, an
email will be sent to you and the ZenDesk manager to notify you of the fact. When this happens, you should
let a Senior know about the problem and follow up with the customer to see if something you did can
be improved.
be improved.
You will also receive a message if the feedback is positive, and it is encouraged to
celebrate those "wins" with the rest of the team through the #support or #thanks
......
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment