Skip to content

Commit de2c6b7

Browse files
committed
#fix: setting github page
1 parent 151b5c6 commit de2c6b7

File tree

2 files changed

+48
-14
lines changed

2 files changed

+48
-14
lines changed

docs/Technical stack/6-ways-level-up-ci-cd-pipeline.md

+1-14
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,6 @@
11
# 6 strategic ways to level up your CI/CD pipeline
22

3-
> _Source:
4-
> [6 strategic ways to level up your CI/CD pipeline](https://github.blog/2022-07-19-6-strategic-ways-to-level-up-your-ci-cd-pipeline/).
5-
6-
[1. Add performance, device compatibility, and accessibility testing](#1-add-performance-device-compatibility-and-accessibility-testing)
7-
8-
[2. Incorporate more automated security testing](#2-incorporate-more-automated-security-testing)
9-
10-
[3. Build a phased testing strategy](#3-build-a-phased-testing-strategy)
11-
12-
[4. Invest in blue-green deployments for easier rollout](#4-invest-in-blue-green-deployments-for-easier-rollouts)
13-
14-
[5. Adopt infrastructure-as-code for greater flexibility](#5-adopt-infrastructure-as-code-for-greater-flexibility)
15-
16-
[6. Create checkpoints for automated rollbacks](#6-create-checkpoints-for-automated-rollbacks)
3+
> _Source: [6 strategic ways to level up your CI/CD pipeline](https://github.blog/2022-07-19-6-strategic-ways-to-level-up-your-ci-cd-pipeline/).
174
185
## 1. Add performance, device compatibility, and accessibility testing
196

docs/intro.md

+47
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
sidebar_position: 1
3+
---
4+
5+
# Tutorial Intro
6+
7+
Let's discover **Docusaurus in less than 5 minutes**.
8+
9+
## Getting Started
10+
11+
Get started by **creating a new site**.
12+
13+
Or **try Docusaurus immediately** with **[docusaurus.new](https://docusaurus.new)**.
14+
15+
### What you'll need
16+
17+
- [Node.js](https://nodejs.org/en/download/) version 18.0 or above:
18+
- When installing Node.js, you are recommended to check all checkboxes related to dependencies.
19+
20+
## Generate a new site
21+
22+
Generate a new Docusaurus site using the **classic template**.
23+
24+
The classic template will automatically be added to your project after you run the command:
25+
26+
```bash
27+
npm init docusaurus@latest my-website classic
28+
```
29+
30+
You can type this command into Command Prompt, Powershell, Terminal, or any other integrated terminal of your code editor.
31+
32+
The command also installs all necessary dependencies you need to run Docusaurus.
33+
34+
## Start your site
35+
36+
Run the development server:
37+
38+
```bash
39+
cd my-website
40+
npm run start
41+
```
42+
43+
The `cd` command changes the directory you're working with. In order to work with your newly created Docusaurus site, you'll need to navigate the terminal there.
44+
45+
The `npm run start` command builds your website locally and serves it through a development server, ready for you to view at http://localhost:3000/.
46+
47+
Open `docs/intro.md` (this page) and edit some lines: the site **reloads automatically** and displays your changes.

0 commit comments

Comments
 (0)