Commit 74c0f837 authored by Jarek Ostrowski's avatar Jarek Ostrowski

Search and replace for old font awesome classes

parent 4e68662e
Pipeline #24547562 passed with stages
in 17 minutes and 49 seconds
......@@ -187,7 +187,7 @@ def tier_bullet(issue)
end
def product_vision_bullet(issue)
output = "<i class=\"vision-item fa fa-#{'check-' if issue['state'] == 'closed'}square-o\" aria-hidden=\"true\"></i> [#{issue['title']}](#{issue['web_url']})"
output = "<i class=\"vision-item far fa-#{'check-' if issue['state'] == 'closed'}square\" aria-hidden=\"true\"></i> [#{issue['title']}](#{issue['web_url']})"
output << ' <kbd>Starter</kbd>' if issue['labels'].include? 'GitLab Starter'
output << ' <kbd>Premium</kbd>' if issue['labels'].include? 'GitLab Premium'
output << ' <kbd>Ultimate</kbd>' if issue['labels'].include? 'GitLab Ultimate'
......@@ -200,7 +200,7 @@ def epic_web_url(group, epic)
end
def product_vision_bullet_from_epic(group, epic)
output = "<i class=\"vision-item fa fa-minus-square-o\" aria-hidden=\"true\"></i> [#{epic['title']}](#{epic_web_url(group, epic)})"
output = "<i class=\"vision-item far fa-minus-square\" aria-hidden=\"true\"></i> [#{epic['title']}](#{epic_web_url(group, epic)})"
output << ' <kbd>Starter</kbd>' if epic['labels'].include? 'GitLab Starter'
output << ' <kbd>Premium</kbd>' if epic['labels'].include? 'GitLab Premium'
output << ' <kbd>Ultimate</kbd>' if epic['labels'].include? 'GitLab Ultimate'
......
......@@ -37,7 +37,7 @@ Counting down to August 23rd, 2018!
<i class="fab fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i>
<br/><br/>
<span class="h3" id="nextSummitCountdown">
<i class="fa fa-spinner fa-spin fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>
<i class="fas fa-spinner fa-spin fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>
</span>
</p>
......
......@@ -36,7 +36,7 @@ be applied to an iOS app, Ruby gem, static website, or other type of project.
Grouping is based on stages in the [DevOps
Toolchain](https://en.wikipedia.org/wiki/DevOps_toolchain) and our [product
categories](/handbook/product/categories/), including several new ones for 2018.
categories](/handbook/product/categories/), including several new ones for 2018.
Also see our [blog post](/2017/10/11/from-dev-to-devops) on the complete
DevOps vision. Or see the [open issues for `Product Vision
2018`](https://gitlab.com/groups/gitlab-org/-/issues?label_name%5B%5D=Product+Vision+2018).
......@@ -48,8 +48,8 @@ DevOps vision. Or see the [open issues for `Product Vision
## Manage
### Reporting & Analytics
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Cycle Analytics](https://docs.gitlab.com/ee/user/project/cycle_analytics.html)<br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Conversational Development Index](https://docs.gitlab.com/ee/user/admin_area/monitoring/convdev.html)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Cycle Analytics](https://docs.gitlab.com/ee/user/project/cycle_analytics.html)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Conversational Development Index](https://docs.gitlab.com/ee/user/admin_area/monitoring/convdev.html)<br>
## Plan
......@@ -62,19 +62,19 @@ scheduling work, and communicating plans.
### Chat integration
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Mattermost](https://docs.gitlab.com/omnibus/gitlab-mattermost/)<br/>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Slack](https://docs.gitlab.com/ee/user/project/integrations/slack.html)
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Mattermost](https://docs.gitlab.com/omnibus/gitlab-mattermost/)<br/>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Slack](https://docs.gitlab.com/ee/user/project/integrations/slack.html)
### Project management
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Issue tracker](https://docs.gitlab.com/ee/user/project/issues/)<br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Issue board](https://docs.gitlab.com/ee/user/project/issue_board.html)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Issue tracker](https://docs.gitlab.com/ee/user/project/issues/)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Issue board](https://docs.gitlab.com/ee/user/project/issue_board.html)<br>
<%= product_vision["project management"] %>
### Portfolio Management
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Epics](https://docs.gitlab.com/ee/user/group/epics/)<br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Roadmap](https://docs.gitlab.com/ee/user/group/roadmap/)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Epics](https://docs.gitlab.com/ee/user/group/epics/)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Roadmap](https://docs.gitlab.com/ee/user/group/roadmap/)<br>
<%= product_vision["portfolio management"] %>
## Create
......@@ -91,8 +91,8 @@ source code, but increasingly other content such as design files.
<%= product_vision["repository"] %>
#### Code Review
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Merge request](https://docs.gitlab.com/ee/user/project/merge_requests/)<br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Image discussion in merge request diff](https://docs.gitlab.com/ee/user/discussions/#image-discussions)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Merge request](https://docs.gitlab.com/ee/user/project/merge_requests/)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Image discussion in merge request diff](https://docs.gitlab.com/ee/user/discussions/#image-discussions)<br>
<%= product_vision["code review"] %>
### Web IDE
......@@ -117,12 +117,12 @@ sent to production. Creation of an explicit build aligns well with Docker where
the result of the build stage is a Docker image which is stored in a registry
and later pulled for testing and deployment.
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Code Quality](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality_diff.html) <kbd>Premium</kbd><br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Code Quality](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality_diff.html) <kbd>Premium</kbd><br>
<%= product_vision["ci"] %>
## Package
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Container Registry](https://docs.gitlab.com/ee/user/project/container_registry.html)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Container Registry](https://docs.gitlab.com/ee/user/project/container_registry.html)<br>
<%= product_vision['devops:package'] %>
## Release
......@@ -132,17 +132,17 @@ and later pulled for testing and deployment.
A key part of CD is being able to deploy. We currently have the ability via
scripts in the `deploy` stage in `.gitlab-ci.yml`. We will go further.
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Environments](https://docs.gitlab.com/ee/ci/environments.html)<br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Deployment history](https://docs.gitlab.com/ee/ci/environments.html#viewing-the-deployment-history-of-an-environment)<br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Deploy boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html) <kbd>Premium</kbd><br>
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Canary deployments](https://docs.gitlab.com/ee/user/project/canary_deployments.html) <kbd>Premium</kbd><br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Environments](https://docs.gitlab.com/ee/ci/environments.html)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Deployment history](https://docs.gitlab.com/ee/ci/environments.html#viewing-the-deployment-history-of-an-environment)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Deploy boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html) <kbd>Premium</kbd><br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Canary deployments](https://docs.gitlab.com/ee/user/project/canary_deployments.html) <kbd>Premium</kbd><br>
<%= product_vision['devops:release'] %>
## Configure
### Application Control Panel
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Variables](https://docs.gitlab.com/ee/ci/variables/#variables)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Variables](https://docs.gitlab.com/ee/ci/variables/#variables)<br>
<%= product_vision['application control panel'] %>
### Infrastructure Configuration
......@@ -180,7 +180,7 @@ easily manage their deployments.
### Application Performance Monitoring (APM)
<i class="vision-item fa fa-check-square-o" aria-hidden="true"></i> [Prometheus monitoring](https://docs.gitlab.com/ee/ci/environments.html#monitoring-environments)<br>
<i class="vision-item far fa-check-square" aria-hidden="true"></i> [Prometheus monitoring](https://docs.gitlab.com/ee/ci/environments.html#monitoring-environments)<br>
<%= product_vision['application performance monitoring'] %>
### Infrastructure Monitoring
......@@ -213,9 +213,9 @@ easily manage their deployments.
*Not a lifecycle stage, but part of our 2018 plan*
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> Push to Geo secondary (proxied to primary) <kbd>Premium</kbd><br>
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> Automatic DR <kbd>Premium</kbd><br>
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> [Improve speed index](/handbook/engineering/performance/#speed-index)<br>
<i class="vision-item far fa-square" aria-hidden="true"></i> Push to Geo secondary (proxied to primary) <kbd>Premium</kbd><br>
<i class="vision-item far fa-square" aria-hidden="true"></i> Automatic DR <kbd>Premium</kbd><br>
<i class="vision-item far fa-square" aria-hidden="true"></i> [Improve speed index](/handbook/engineering/performance/#speed-index)<br>
<%= product_vision["performance"] %>
## Distribution
......@@ -244,5 +244,5 @@ enterprise grade Helm Charts.
### Cloud Native Installation
<i class="vision-item fa fa-square-o" aria-hidden="true"></i> [Cloud native GitLab Helm Chart (GA)](https://gitlab.com/groups/charts/-/epics/15)<br>
<i class="vision-item far fa-square" aria-hidden="true"></i> [Cloud native GitLab Helm Chart (GA)](https://gitlab.com/groups/charts/-/epics/15)<br>
<%= product_vision["Cloud Native"] %>
......@@ -221,7 +221,7 @@ extra_js:
Create multiple Issue Boards for each of your projects.
It's simple: navigate to your Issue Board, click <i class="fa fa-caret-down" style="color: rgb(49,163,92)" aria-hidden="true"></i> to open a dropdown menu that will give you the
It's simple: navigate to your Issue Board, click <i class="fas fa-caret-down" style="color: rgb(49,163,92)" aria-hidden="true"></i> to open a dropdown menu that will give you the
option to create new boards, edit the existing ones, or delete the boards you
don't need anymore. Use the same dropdown menu to navigate between your boards.
......
......@@ -17,7 +17,7 @@ title: "Blog Handbook"
Our blog is managed by the Content Marketing team. Other team members are encouraged to contribute blog posts, but please see the [publishing processes](#publishing-processes) section and follow the steps there to get started.
<div class="alert alert-purple center"><h3 class="purple"><i class="fa fa-gitlab" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> &nbsp;&nbsp;<strong>EVERYONE CAN CONTRIBUTE</strong>&nbsp;&nbsp; <i class="fa fa-gitlab" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i></h3></div>
<div class="alert alert-purple center"><h3 class="purple"><i class="fab fa-gitlab" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> &nbsp;&nbsp;<strong>EVERYONE CAN CONTRIBUTE</strong>&nbsp;&nbsp; <i class="fab fa-gitlab" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i></h3></div>
### Blog endboss
......@@ -162,7 +162,7 @@ Do you have a better idea? Don't hesitate, [create an issue][blog-tracker] with
{::options parse_block_html="true" /}
<div class="panel panel-gitlab-orange">
#### <i class="fa fa-globe fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Release posts
#### <i class="fas fa-globe fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Release posts
{: .panel-heading #release-posts}
<div class="panel-body">
......@@ -173,7 +173,7 @@ Examples: [release] posts, [security release] posts.
</div>
<div class="panel panel-gitlab-purple">
#### <i class="fa fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Team members' posts
#### <i class="fab fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Team members' posts
{: .panel-heading #team-members-posts}
<div class="panel-body">
Whenever we have something interesting to talk about, we encourage our own team
......@@ -185,7 +185,7 @@ please take a look at the [publishing processes].
</div>
<div class="panel panel-warning">
#### <i class="fa fa-rocket fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Guest posts
#### <i class="fas fa-rocket fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Guest posts
{: .panel-heading #guest-posts}
<div class="panel-body">
These posts are specific for community members that want to write about their own tools, features, and software integrations with GitLab. They can be written by the owners, executives or any team members of those companies, and will be reviewed by the GitLab [blog editorial team].
......@@ -280,7 +280,7 @@ tags: tag1, tag2, tag3 # added June, 2018
---
```
<i class="fa fa-exclamation-triangle" aria-hidden="true"></i> New frontmatter! Social Media information: `twitter_image`, `description`, CTA buttons, `author_gitlab`, and `guest`!
<i class="fas fa-exclamation-triangle" aria-hidden="true"></i> New frontmatter! Social Media information: `twitter_image`, `description`, CTA buttons, `author_gitlab`, and `guest`!
{: .alert .alert-warning .ambar}
```yaml
......
......@@ -170,7 +170,7 @@ make sure that:
Write the description of every feature as you do to regular blog posts. Please write according to
the [markdown guide](/handbook/product/technical-writing/markdown-guide/).
<i class="fa fa-exclamation-triangle" aria-hidden="true" style="color: red"></i>
<i class="fas fa-exclamation-triangle" aria-hidden="true" style="color: red"></i>
**Important!** Make sure to merge `master` into the release post branch **before
pushing changes** to any existing file to avoid merge conflicts. Do not rebase,
do `git pull origin master` then `:wq`.
......
......@@ -16,7 +16,7 @@ title: "Community Advocacy"
----
## <i class="fa fa-book fa-fw icon-color font-awesome" aria-hidden="true"></i> Community Advocate Resources
## <i class="fas fa-book fa-fw icon-color font-awesome" aria-hidden="true"></i> Community Advocate Resources
- Community Advocate Onboarding
- [Onboarding](/handbook/marketing/developer-relations/community-advocacy/onboarding/checklist/)
......
......@@ -21,7 +21,7 @@ The GitLab Marketing team includes four functional groups: Marketing & Sales Dev
----
## <i class="fa fa-book fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Handbooks
## <i class="fas fa-book fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Handbooks
{: #marketing-handbooks}
- [Blog]
......@@ -50,11 +50,11 @@ The GitLab Marketing team includes four functional groups: Marketing & Sales Dev
----
## <i class="fa fa-gitlab fa-fw icon-color font-awesome" aria-hidden="true"></i> GitLab Marketing Purpose
## <i class="fab fa-gitlab fa-fw icon-color font-awesome" aria-hidden="true"></i> GitLab Marketing Purpose
<br />
<div class="alert alert-purple center"><h3 class="purple"><strong>We <i class="fa fa-heart orange font-awesome" aria-hidden="true"></i> GitLab</strong></h3></div>
<div class="alert alert-purple center"><h3 class="purple"><strong>We <i class="fas fa-heart orange font-awesome" aria-hidden="true"></i> GitLab</strong></h3></div>
We think GitLab (.com, CE, and EE) is the fastest way for developers, designers, and IT practitioners to turn their ideas into production software. The GitLab Marketing team is here to do the following:
......@@ -81,7 +81,7 @@ We track Integrated Campaign results in salesforce.com, and costs associated wit
Different marketing teams handle different aspects of Integrated Campaigns. Which team are you looking for? Here's what each does.
## <i class="fa fa-users fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Team Functional Groups
## <i class="fas fa-users fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Team Functional Groups
{: #groups}
......@@ -262,7 +262,7 @@ Partner Marketing is responsbile for joint GTM strategy for partnerships. They c
[Position Description coming soon](#){:.btn .btn-purple-inv}
[Handbook][Partner Marketing]{:.btn .btn-purple}
## <i class="fa fa-suitcase fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Production
## <i class="fas fa-suitcase fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Production
{: #marketing-products}
<!-- The following HTML blocks are the Marketing Products boxes -->
......@@ -370,7 +370,7 @@ Partner Marketing is responsbile for joint GTM strategy for partnerships. They c
</div>
<!-- END OF MARKETING PRODUCTS -->
## <i class="fa fa-clock-o fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing OKR Overview
## <i class="far fa-clock fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing OKR Overview
{: #okrs}
Our team and the demands on marketing are growing quickly. In order to align our goals with company goals as well as prioritize what we are working on, OKRs help us to maintain structure.
......@@ -388,7 +388,7 @@ Each member of the marketing team is responsible for 3 Objectives and 3 Key Resu
- [Quick overview of OKRs](http://www.slideshare.net/HenrikJanVanderPol/how-to-outperform-anyone-else-introduction-to-okr)
## <i class="fa fa-cogs fa-fw icon-color font-awesome" aria-hidden="true"></i> Meetings and structure
## <i class="fas fa-cogs fa-fw icon-color font-awesome" aria-hidden="true"></i> Meetings and structure
{: #meetings}
These are just the required meetings for team members and managers. Of course, meetings are encouraged when it expedites a project or problem solving among members, so the team and company. Don't be afraid to say "Hey, can we hangout?" if you need help with something.
......@@ -505,7 +505,7 @@ The meeting should run as follows:
- Team agrees on what key takeaways are from the last quarter.
- Team agrees on what Marketing OKRs should be for the upcoming quarter.
## <i class="fa fa-thumbs-o-up fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing team SLAs (Service Level Agreements)
## <i class="far fa-thumbs-up fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing team SLAs (Service Level Agreements)
{: #sla}
When working remotely in a fast-paced organization, it is important for a team to agree on a few basic service level agreements on how we would like to work together. With any of these, things can come up that make it not possible to meet the SLAs, but we all agree to use best effort when possible.
......@@ -517,7 +517,7 @@ When working remotely in a fast-paced organization, it is important for a team t
- Try not to email co-workers on weekends. Try out [Boomerang](http://www.boomeranggmail.com/) and set all your emails to send Monday morning at 6 AM. People will think you're up and working early! Time off is important. We all have stressful weeks so please unplug on the weekends where possible.
- Do not ping someone in a public channel on chat on the weekends. This is rude.
## <i class="fa fa-file-code-o fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Handbook Updates
## <i class="far fa-file-code fa-fw icon-color font-awesome" aria-hidden="true"></i> Marketing Handbook Updates
{: #handbook}
Anything that is a process in marketing should be documented in the Marketing Handbook.
......@@ -532,7 +532,7 @@ Anything that is a process in marketing should be documented in the Marketing Ha
- If more than one person are performing a role, the task should be shared to update the handbook with all processes or guidelines.
- Follow the [Markdown Style Guide] for about.GitLab.com.
## <i class="fa fa-rocket fa-fw icon-color font-awesome" aria-hidden="true"></i> How to contact marketing
## <i class="fas fa-rocket fa-fw icon-color font-awesome" aria-hidden="true"></i> How to contact marketing
{: #contact-marketing}
- [**GitLab Marketing public issue tracker**](https://gitlab.com/gitlab-com/marketing/issues/); please use confidential issues for topics that should only be visible to team members at GitLab
......
......@@ -1092,7 +1092,7 @@ Yes, we can use fancy [Font Awesome] icons too.
_Regular_
```
### <i class="fa fa-puzzle-piece" aria-hidden="true"></i> Puzzle Icon
### <i class="fas fa-puzzle-piece" aria-hidden="true"></i> Puzzle Icon
{: #puzzle}
```
......@@ -1101,10 +1101,10 @@ And you can go further, such as the following.
_Styled_
```
### <i class="fa fa-puzzle-piece fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Purple Puzzle Icon
### <i class="fas fa-puzzle-piece fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Purple Puzzle Icon
{: #puzzle-purple}
### <i class="fa fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Orange GitLab Tanuki
### <i class="fab fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Orange GitLab Tanuki
{: #tanuki-orange}
```
......@@ -1117,17 +1117,17 @@ _Styled_
_Regular_
### <i class="fa fa-puzzle-piece" aria-hidden="true"></i> Puzzle Icon
### <i class="fas fa-puzzle-piece" aria-hidden="true"></i> Puzzle Icon
{: #puzzle}
----
_Styled_
### <i class="fa fa-gitlab fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Purple GitLab Tanuki
### <i class="fab fa-gitlab fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Purple GitLab Tanuki
{: #tanuki-purple}
### <i class="fa fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Orange GitLab Tanuki
### <i class="fab fa-gitlab fa-fw" style="color:rgb(252,109,38); font-size:.85em" aria-hidden="true"></i> Orange GitLab Tanuki
{: #tanuki-orange}
</div>
......@@ -1735,9 +1735,9 @@ My text in an purple box.
To be used in a CTA for webcast announcement in blog posts.
You can use it for other purposes as well. Use it together with the [HMTL parser](#html-parser):
<i class="fa fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>&nbsp;&nbsp;
<i class="fab fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>&nbsp;&nbsp;
The webcast I want to announce - [Register here][webcast-link]!
&nbsp;&nbsp;<i class="fa fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>
&nbsp;&nbsp;<i class="fab fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>
{: .alert .alert-webcast}
[webcast-link]: #
......@@ -1745,9 +1745,9 @@ The webcast I want to announce - [Register here][webcast-link]!
```md
{::options parse_block_html="true" /}
<i class="fa fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>&nbsp;&nbsp;
<i class="fab fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>&nbsp;&nbsp;
The webcast I want to announce - [Register here][webcast-link]!
&nbsp;&nbsp;<i class="fa fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>
&nbsp;&nbsp;<i class="fab fa-gitlab" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i>
{: .alert .alert-webcast}
```
......@@ -1893,7 +1893,7 @@ To embed from SlideShare, go to the document you want to embed and hit the **Sha
button located below the slides. Copy the code under **Embed** and place it
inside the `figure` tag.
<i class="fa fa-exclamation-triangle" aria-hidden="true" style="color: rgb(138, 109, 59)
<i class="fas fa-exclamation-triangle" aria-hidden="true" style="color: rgb(138, 109, 59)
;"></i> Be careful to only include the iframe content and strip anything else.
SlideShare will also add some other information in the embed code which you
will have to remove, otherwise the markdown page will be broken.
......@@ -1909,7 +1909,7 @@ else except from the iframe, would result in this:
</figure>
```
<i class="fa fa-info-circle" aria-hidden="true" style="color: rgb(49, 112, 143)
<i class="fas fa-info-circle" aria-hidden="true" style="color: rgb(49, 112, 143)
;"></i> You can safely omit the `<figure>` tag since SlideShare's widget is
already responsive, but we are showing this that way in order to be consistent
with the rest of the handbook.
......
......@@ -19,7 +19,7 @@ title: Support Handbook
----
## <i class="fa fa-question-circle fa-fw icon-color font-awesome" aria-hidden="true"></i> Support Direction
## <i class="fas fa-question-circle fa-fw icon-color font-awesome" aria-hidden="true"></i> Support Direction
The overall direction for Support in 2018 is set by our overall [strategic objectives](/strategy), with a particular emphasis on continued improvement of (Premium) Customer satisfaction. As can also be inferred from our [publicly visible OKR page](/okrs/), the effort focuses on the following elements.
......@@ -117,7 +117,7 @@ In order to attract support team's attention in Slack, you can use the team hand
- `@servicesteam` - Services support team members.
## <i class="fa fa-book fa-fw icon-color font-awesome" aria-hidden="true"></i> Support Resources
## <i class="fas fa-book fa-fw icon-color font-awesome" aria-hidden="true"></i> Support Resources
- [Support Onboarding](/handbook/support/onboarding)
- [Support Engineer Onboarding Checklist](https://gitlab.com/gitlab-com/support/support-team-meta/blob/master/.gitlab/issue_templates/Support%20Engineering%20Bootcamp.md)
......
......@@ -2,7 +2,7 @@
%button.navbar-toggle{type: "button", data: {target: "#blog-category-nav", toggle: "collapse"}}
%span
All Topics
<i class="fa fa-chevron-down"></i>
<i class="fas fa-chevron-down"></i>
.collapse.navbar-collapse#blog-category-nav
%ul.nav.navbar-nav.animated
%li{class: ("active" if current_page.url == "/blog/")}
......
......@@ -17,7 +17,7 @@
wrapper.insertBefore(tocs, container);
[].slice.call(titles).forEach(function(el) {
el.innerHTML += '<a href="#' + el.id + '" class="handbook-md-anchor"><i class="fa fa-link"></i></a>';
el.innerHTML += '<a href="#' + el.id + '" class="handbook-md-anchor"><i class="fas fa-link"></i></a>';
el.classList.add('handbook-md-title');
});
......
......@@ -11,59 +11,59 @@ We think there's always room for improvement, and everything is a draft. As alwa
<!-- more -->
<i class="fa fa-code-fork" aria-hidden="true"></i> **1. Use feature branches, no direct commits on master.**
<i class="fas fa-code-branch" aria-hidden="true"></i> **1. Use feature branches, no direct commits on master.**
{: .alert .alert-success .green}
If you're coming over from [SVN], for example, you'll be used to a trunk-based workflow. When using Git you should create a **branch** for whatever you’re working on, so that you end up doing a code review before you merge.
<i class="fa fa-check-square-o" aria-hidden="true"></i> **2. Test all commits, not only ones on master.**
<i class="fas fa-check-square-o" aria-hidden="true"></i> **2. Test all commits, not only ones on master.**
{: .alert .alert-success .green}
Some people set up their CI to only test what has been merged into **master**. This is too late; people should feel confident that **master** always has green tests. It doesn't make sense for people to have to test **master** before they start developing new features, for example. CI isn’t expensive, so it makes the best sense to do it this way.
<i class="fa fa-flask" aria-hidden="true"></i> **3. Run all the tests on all commits (if your tests run longer than 5 minutes have them run in parallel).**
<i class="fas fa-flask" aria-hidden="true"></i> **3. Run all the tests on all commits (if your tests run longer than 5 minutes have them run in parallel).**
{: .alert .alert-success .green}
If you're working on a feature branch and you add new commits, run tests then and there. If the tests are taking a long time, try running them in parallel. Do this server-side in merge requests, running the complete test suite. If you have a test suite for development and another that you only run for new versions; it’s worthwhile to set up [parallel] tests and run them all.
<i class="fa fa-code" aria-hidden="true"></i> **4. Perform code reviews before merges into master, not afterwards.**
<i class="fas fa-code" aria-hidden="true"></i> **4. Perform code reviews before merges into master, not afterwards.**
{: .alert .alert-success .green}
Don't test everything at the end of your week. Do it on the spot, because you'll be more likely to catch things that could cause problems and others will also be working to come up with solutions.
<i class="fa fa-terminal" aria-hidden="true"></i> **5. Deployments are automatic, based on branches or tags.**
<i class="fas fa-terminal" aria-hidden="true"></i> **5. Deployments are automatic, based on branches or tags.**
{: .alert .alert-success .green}
If you don't want to deploy **master** every time, you can create a **production branch**; but there’s no reason why you should use a script or log in somewhere to do it manually. Have everything automated, or a specific branch that triggers a [production deploy][environment].
<i class="fa fa-tags" aria-hidden="true"></i> **6. Tags are set by the user, not by CI.**
<i class="fas fa-tags" aria-hidden="true"></i> **6. Tags are set by the user, not by CI.**
{: .alert .alert-success .green}
A user sets a **tag** and, based on that, the CI will perform an action. You shouldn’t have the CI change the repository. If you need very detailed metrics, you should have a server report detailing new versions.
<i class="fa fa-cloud-upload" aria-hidden="true"></i> **7. Releases are based on tags.**
<i class="fas fa-cloud-upload-alt" aria-hidden="true"></i> **7. Releases are based on tags.**
{: .alert .alert-success .green}
If you tag something, that creates a new release.
<i class="fa fa-eye-slash" aria-hidden="true"></i> **8. Pushed commits are never rebased.**
<i class="fas fa-eye-slash" aria-hidden="true"></i> **8. Pushed commits are never rebased.**
{: .alert .alert-success .green}
If you push to a public branch you shouldn't rebase it since that makes it hard to follow what you're improving, what the test results were, and it breaks cherrypicking.
We sometimes sin against this rule ourselves when we ask a contributor to squash and rebase at the end of a review process to make something easier to revert.
But in general the guideline is: code should be clean, history should be realistic.
<i class="fa fa-folder-open-o" aria-hidden="true"></i> **9. Everyone starts from master, and targets master.**
<i class="far fa-folder-open" aria-hidden="true"></i> **9. Everyone starts from master, and targets master.**
{: .alert .alert-success .green}
This means you don’t have any long branches. You check out **master**, build your feature, create your merge request, and target **master** again. You should do your complete review **before** you merge, and not have any intermediate stages.
<i class="fa fa-bug" aria-hidden="true"></i> **10. Fix bugs in master first and release branches second.**
<i class="fas fa-bug" aria-hidden="true"></i> **10. Fix bugs in master first and release branches second.**
{: .alert .alert-success .green}
If you find a bug, the **worst** thing you can do is fix it in the just-released version, and not fix it in **master**. To avoid it, you always fix forward. Fix it in **master**, then **cherry-pick** it into another patch-release branch.
<i class="fa fa-pencil-square-o" aria-hidden="true"></i> **11. Commit messages reflect intent.**
<i class="far fa-edit" aria-hidden="true"></i> **11. Commit messages reflect intent.**
{: .alert .alert-success .green}
You should not only say what you did, but also why you did it. It’s even more useful if you explain why you did this over any other options.
......
......@@ -9,9 +9,9 @@ author_gitlab: sytses
categories: company
---
<i class="fa fa-exclamation-triangle gitlab-orange" aria-hidden="true"></i>
<i class="fas fa-exclamation-triangle gitlab-orange" aria-hidden="true"></i>
<span class="red">**WARNING**</span>
<i class="fa fa-exclamation-triangle gitlab-orange" aria-hidden="true"></i>
<i class="fas fa-exclamation-triangle gitlab-orange" aria-hidden="true"></i>
**git-annex** support on GitLab EE was **deprecated** in
[GitLab 8.17](/2017/02/22/gitlab-8-17-released/#git-annex-support) (2017/02/22),
and was [**permanently removed**](https://gitlab.com/gitlab-org/gitlab-ee/issues/1648) in
......
......@@ -9,9 +9,9 @@ image_title: /images/unsplash/trees-raysoflight.jpg
{::options parse_block_html="true" /}
<i class="fa fa-exclamation-triangle" style="font-size:.85em" aria-hidden="true"></i>&nbsp;&nbsp;
<i class="fas fa-exclamation-triangle" style="font-size:.85em" aria-hidden="true"></i>&nbsp;&nbsp;
Please read the [up-to-date version of this article](/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/)!
&nbsp;&nbsp;<i class="fa fa-exclamation-triangle" style="font-size:.85em" aria-hidden="true"></i>
&nbsp;&nbsp;<i class="fas fa-exclamation-triangle" style="font-size:.85em" aria-hidden="true"></i>
{: .alert .alert-webcast}
{::options parse_block_html="false" /}
......
......@@ -301,7 +301,7 @@ certificate to **each** custom domain or subdomain you've added to your projects
_Steps to set up a custom domain_
- From your project's dashboard, go to **Settings** (<i class="fa fa-cog" aria-hidden="true"></i>) **> Pages > New Domain**
- From your project's dashboard, go to **Settings** (<i class="fas fa-cog" aria-hidden="true"></i>) **> Pages > New Domain**
- Add your domain to the first field: `mydomain.com`
- If you have an SSL/TLS digital certificate and its key, add them to their respective fields.
If you don't, just leave the fields blank.
......
......@@ -66,7 +66,7 @@ and less repetitive. Let's take a quick look at the list below, then describe th
- Preprocessors
- Directory structure
### <i class="fa fa-terminal fa-fw" style="color:rgb(226,67,41); font-size:.85em"></i> Environment
### <i class="fas fa-terminal fa-fw" style="color:rgb(226,67,41); font-size:.85em"></i> Environment
{: #environment}
The **environment**, also called **platform**, consists essentially on the [programming language]
......@@ -75,7 +75,7 @@ of the SSG. Examples: [Ruby], [Python], [Node JS][node].
<a name="template-engine"></a>
### <i class="fa fa-cogs fa-flip-horizontal fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Template engine
### <i class="fas fa-cogs fa-flip-horizontal fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Template engine
{: #template_engine}
The **template engine** is very important we understand, since all the dynamic structure of our sites
......@@ -113,7 +113,7 @@ _Advantages over flat HTML_
- Avoid repetition: every block repeated sitewide would be included to every page, equivalently
- Update faster: if we change something in the file `footer.html`, it will affect the entire site
### <i class="fa fa-pencil fa-flip-horizontal fa-fw" style="color:rgb(226,67,41); font-size:.85em"></i> Markup language
### <i class="fas fa-pencil-alt fa-flip-horizontal fa-fw" style="color:rgb(226,67,41); font-size:.85em"></i> Markup language
{: #markup-language}
**[Markup language]** is a system to write documents making them somehow syntactically distinguishable
......@@ -170,7 +170,7 @@ The content for our example would output simply:
<p>Some text.</p>
```
### <i class="fa fa-puzzle-piece fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Preprocessors
### <i class="fas fa-puzzle-piece fa-fw" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Preprocessors
{: #preprocessors}
The **preprocessors** are made to speed up our development process too. They simplify
......@@ -211,7 +211,7 @@ preprocessors, but that's not in focus on this post.
By the way, the given Sass example will be compiled exactly to the CSS code above it.
### <i class="fa fa-folder-open-o fa-fw" style="color:rgb(226,67,41); font-size:.85em"></i> Directory structure
### <i class="far fa-folder-open fa-fw" style="color:rgb(226,67,41); font-size:.85em"></i> Directory structure
{: #directory-structure}
The **directory structure** is different for each SSG. It's important to study the file
......
......@@ -128,7 +128,7 @@ other improvements to fix these problems, but we expect to be able to quickly an
concurrently build our packages when it is all done. Feel free to
[track our progress](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1232).
## We <i class="fa fa-heart" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Docker
## We <i class="fas fa-heart" style="color:rgb(107,79,187); font-size:.85em" aria-hidden="true"></i> Docker
{: #we-love-docker}
As you can see, providing a GitLab Docker image was just the beginning of our
......
......@@ -9,9 +9,9 @@ author_twitter: virtuacreative
image_title: '/images/blogimages/startssl-gitlab-pages/startssl-gitlab-pages-cover.jpg'
---
<i class="fa fa-exclamation-triangle red" aria-hidden="true"></i>
<i class="fas fa-exclamation-triangle red" aria-hidden="true"></i>
<span class="red">**WARNING**</span>
<i class="fa fa-exclamation-triangle red" aria-hidden="true"></i>
<i class="fas fa-exclamation-triangle red" aria-hidden="true"></i>
**StartCom** certificates have recently been **distrusted** by [Mozilla Firefox](https://blog.mozilla.org/security/2016/10/24/distrusting-new-wosign-and-startcom-certificates/) and [Google Chrome](https://security.googleblog.com/2016/10/distrusting-wosign-and-startcom.html). Certs issued prior to October 21st, 2016 don't seem to have been affected and are therefore still trusted.<br>
In response to my contact, StartCom affirmed they're working hard to revert this situation and hope to have a resolution by the end of January, 2017.<br>
<span class="note">Update by Marcia Ramos, on 2016/12/20.</span>
......@@ -161,21 +161,21 @@ let's take a look at the table below.
| Feature | StartSSL Class 1 | Let's Encrypt |
| ---- | :---- | :---- |
| **Cost** | Free | Free |
| **Expiration** | <i class="fa fa-check" style="color: green;"></i> [In 1 year][startssl-class-1-features] (365 days) | [In 3 months][lets-renewal] (90 days) |
| **Client Install / CSR** | <i class="fa fa-check" style="color: green;"></i> All OSs | Complicated on [Windows][lets-win] |
| **CSR method** | <i class="fa fa-check" style="color: green;"></i> Desktop App or command line | Command line only |
| **Browser Support** | <i class="fa fa-check" style="color: green;"></i> [All][startssl-about] | [Most of them][lets-browser-support] |
| **Expiration** | <i class="fas fa-check" style="color: green;"></i> [In 1 year][startssl-class-1-features] (365 days) | [In 3 months][lets-renewal] (90 days) |
| **Client Install / CSR** | <i class="fas fa-check" style="color: green;"></i> All OSs | Complicated on [Windows][lets-win] |
| **CSR method** | <i class="fas fa-check" style="color: green;"></i> Desktop App or command line | Command line only |
| **Browser Support** | <i class="fas fa-check" style="color: green;"></i> [All][startssl-about] | [Most of them][lets-browser-support] |
| **Server Support** | [All][startssl-about] | All, with [plugins][lets-plugins] |
| **Revocation** | [Paid][startssl-revocation] | <i class="fa fa-check" style="color: green;"></i> [Free][lets-features] |
| **S/MIME Client Auth** | <i class="fa fa-check" style="color: green;"></i> [Supported][startssl-class-1-features] | [Not supported][lets-smime] |
| **Insurance** | <i class="fa fa-check" style="color: green;"></i> [$ 10,000 USD][startssl-class-1-features] | [None][lets-features] |
| **Customer support** | <i class="fa fa-check" style="color: green;"></i> [Live Chat, Phone][startssl-support], Ticket | [Forum][lets-forum] |
| **Hash Algorithm** | <i class="fa fa-check" style="color: green;"></i> SHA-256, SHA-384, SHA-512 | [SHA-256][lets-sha-256] |
| **Domain validation** | <i class="fa fa-check" style="color: green;"></i> Email or Code file Validation | [Code file validation][lets-domain-validation] |
| **Domains limit** | [5 domains][startssl-class-1-features] | <i class="fa fa-check" style="color: green;"></i> [Limited][lets-limits] |
| **Revocation** | [Paid][startssl-revocation] | <i class="fas fa-check" style="color: green;"></i> [Free][lets-features] |
| **S/MIME Client Auth** | <i class="fas fa-check" style="color: green;"></i> [Supported][startssl-class-1-features] | [Not supported][lets-smime] |
| **Insurance** | <i class="fas fa-check" style="color: green;"></i> [$ 10,000 USD][startssl-class-1-features] | [None][lets-features] |
| **Customer support** | <i class="fas fa-check" style="color: green;"></i> [Live Chat, Phone][startssl-support], Ticket | [Forum][lets-forum] |
| **Hash Algorithm** | <i class="fas fa-check" style="color: green;"></i> SHA-256, SHA-384, SHA-512 | [SHA-256][lets-sha-256] |
| **Domain validation** | <i class="fas fa-check" style="color: green;"></i> Email or Code file Validation | [Code file validation][lets-domain-validation] |
| **Domains limit** | [5 domains][startssl-class-1-features] | <i class="fas fa-check" style="color: green;"></i> [Limited][lets-limits] |
| **Subdomains** | Supported | Supported |
| **Free domains** | Supported | Supported |
| **Domain name** | Non-commercial names | <i class="fa fa-check" style="color: green;"></i> Unrestricted |
| **Domain name** | Non-commercial names | <i class="fas fa-check" style="color: green;"></i> Unrestricted |
| **Wildcard support** | No | No |
| **Support EV certificates** | [Upgrading (paid)][start-ssl-ev] | No |
......@@ -401,7 +401,7 @@ The image below illustrates the result of the steps above.
Finally, let's add the key and the certificate to our project:
- On your GitLab UI, open your **Project's Settings** (<i class="fa fa-cog" aria-hidden="true"></i>) and navigate to **Pages**
- On your GitLab UI, open your **Project's Settings** (<i class="fas fa-cog" aria-hidden="true"></i>) and navigate to **Pages**
- If your domain (the one you just issued the certificate for) is already added to that project,
**remove** it. Don't worry, we'll add it back
- Click **+ New Domain**
......@@ -423,7 +423,7 @@ with [Site 24x7][site-24-7], if you want.
Do you want to see a working example of a GitLab Pages Project secure with StartSSL Class 1?
Visit <https://gitlab.virtuacreative.com.br> and click on the green lock
(<i class="fa fa-lock" style="color:rgb(0,192,29)" aria-hidden="true"></i>) to check the certificate.
(<i class="fas fa-lock" style="color:rgb(0,192,29)" aria-hidden="true"></i>) to check the certificate.
This URL is an alias for <https://virtuacreative.gitlab.io>.
## Getting Help
......
......@@ -107,7 +107,7 @@ The next screen reviews the Pricing Tiers, which are the VM sizes. I
chose a "**D1 Standard**" VM, which meets the minimum system requirements to
run a small GitLab environment. When ready click 'Select'.
<i class="fa fa-info-circle" aria-hidden="true" style="color: rgb(49, 112, 143);"></i>
<i class="fas fa-info-circle" aria-hidden="true" style="color: rgb(49, 112, 143);"></i>
By default, only the recommended tiers are shown. To choose a larger one click
on 'View all'.
{: .alert .alert-info}
......@@ -164,7 +164,7 @@ In the screenshot above I have set my DNS name to
`gitlab-ce-test.xxx.cloudapp.azure.com`. Hit **Save** for the changes to take
effect.