Merge branch 'master' into restyled/cms/blog/fast-refresh

gatsby-ssr.js

@@ -37,7 +37,8 @@ exports.onRenderBody = function ({ setHeadComponents, setPostBodyComponents }) {
             <script src={withPrefix('js/syntax.js')} />
             <script src={withPrefix('js/toPlainText.js')} />
             <script src={withPrefix('js/ukraine.js')} />
-
+< script src = {
+'https : // cdn.jsdelivr.net/npm/@algolia/algoliasearch-netlify-frontend@1/dist/algoliasearchNetlify.js'} />
             <script src={'https://cdnjs.cloudflare.com/ajax/libs/highlight.js/9.18.5/highlight.min.js'} />
             <script src={withPrefix('js/syntax.js')} />
         </React.Fragment>

src/data/doc_sections.yml

@@ -3,28 +3,31 @@
 root_docs_path: /docs
 sections:
     - about
-    - articles
-    - audio
+    - archive📁
+    - articles🚛
+    - audio🔊
     - career
     - community
-    - content
+    - content📁
     - css
-    - ds-algo
+    - ds-algo🖧
     - docs
     - faq
-    - git
+    - fetch-api
+    - git📁
     - interact
     - javascript
     - js-tips
     - interview
     - leetcode
-    - overflow
-    - projects
-    - python
+    - netlify-cms-jamstack
+    - overflow🌊
+    - projects📽️
+    - python🐍
     - quick-ref
-    - react
-    - reference
-    - tools
+    - react⚛️
+    - reference📚
+    - tools🧰
     - tips
     - tutorials
-    - typescript
+    - typescript<Ty>

src/data/tags/bash.yaml

@@ -0,0 +1,28 @@
+id: "Bash "
+title: Bash
+description: >-
+  <!--StartFragment-->
+
+
+  When a computer boots up, a kernel (whether it's Linux, BSD, Mach, or NT) recognizes all the physical hardware and enables each component to talk with one another and be orchestrated by some basic software. A computer's most basic set of instructions simply keeps it powered on and in a safe state: activating fans periodically to prevent overheating, using subsystems to monitor disk space or "listen" for newly attached devices, and so on. If this was all computers did, they'd be about as interesting as a convection oven.
+
+
+  Computer scientists recognized this early on, so [they developed](https://opensource.com/19/9/command-line-heroes-bash) a *shell* for Unix computers that operates outside of the kernel (or *around* the kernel, like a shell in nature) and allows humans to interact with the computer whenever they want to. It was an exciting development at a time when people were feeding punchcards into computers to tell them what to do. Of all the shells available, Bash is one of the most popular, the most powerful, and the most friendly.
+
+
+  ## Bash is an application
+
+
+  When you start a terminal (such as the [GNOME Terminal](https://gitlab.gnome.org/GNOME/gnome-terminal) or [Konsole](https://konsole.kde.org/) on Linux or [iTerm2](https://iterm2.com/) on macOS) running the Bash shell, you're greeted with a *prompt*. A prompt is a symbol, usually a dollar sign (**$**), indicating that the shell is waiting for your input. Of course, knowing what you're supposed to type is another matter entirely.
+
+
+  This probably comes across as unfriendly, but it's actually a perfectly succinct representation of the many connotations around the term "Bash." To many new users, there's no separation between the concept of Bash and the concept of Linux or Unix: it's the proverbial black-screen-with-green-text into which you're supposed to code what your computer does next. That conflates the Bash shell with the *commands* you type into the shell. It's important to understand that they're two separate things: Bash is just an application, and its primary job is to run *other* applications (in the form of commands) that are installed on the same system.
+
+
+  **[Download our free [Bash cheat sheet](https://opensource.com/downloads/bash-cheat-sheet)]**
+
+
+  You can learn Bash, but only in the context of learning the operating system that it's running on. Without knowing commands, there's not much you can do with Bash.
+
+
+  <!--EndFragment-->

src/data/tags/news.yaml

@@ -0,0 +1,3 @@
+id: News
+title: News
+description: World News

src/data/tags/web-development.yaml

@@ -0,0 +1,10 @@
+id: Web Development
+title: General Web Development
+description: >-
+  <!--StartFragment-->
+
+
+  Web development refers in general to **the tasks associated with developing websites for hosting via intranet or internet**. The web development process includes web design, web content development, client-side/server-side scripting and network security configuration, among other tasks
+
+
+  <!--EndFragment-->

src/pages/blog/eslint-rules.md

@@ -1,5 +1,5 @@
 ---
-title: " ESLint Rules"
+title: ' ESLint Rules'
 template: post
 subtitle: Rules in ESLint are grouped by type to help you understand their purpose
 excerpt: These rules relate to possible logic errors in cod
@@ -9,16 +9,17 @@ thumb_image: https://i.ytimg.com/vi/SydnKbGc7W8/maxresdefault.jpg
 image_position: right
 author: src/data/authors/bgoonz.yaml
 categories:
-  - src/data/categories/js.yaml
-  - src/data/categories/git.yaml
+    - src/data/categories/js.yaml
+    - src/data/categories/git.yaml
 tags:
-  - src/data/tags/cms.yaml
-  - src/data/tags/javascript.yaml
-  - src/data/tags/links.yaml
-  - src/data/tags/resources.yaml
+    - src/data/tags/cms.yaml
+    - src/data/tags/javascript.yaml
+    - src/data/tags/links.yaml
+    - src/data/tags/resources.yaml
 show_author_bio: true
 cmseditable: true
 ---
+
 <!--StartFragment-->
 
 # Rules
@@ -241,7 +242,7 @@ These rules suggest alternate ways of doing things:
 |     | 🔧  |     | [sort-imports](https://eslint.org/docs/rules/sort-imports)                                     | enforce sorted import declarations within modules                                                                      |
 |     |     |     | [sort-keys](https://eslint.org/docs/rules/sort-keys)                                           | require object keys to be sorted                                                                                       |
 |     | 🔧  |     | [sort-vars](https://eslint.org/docs/rules/sort-vars)                                           | require variables within the same declaration block to be sorted                                                       |
-|     | 🔧  |     | [spaced-comment](https://eslint.org/docs/rules/spaced-comment)                                 | enforce consistent spacing after the \`//\` or \`/*\` in a comment                                                     |
+|     | 🔧  |     | [spaced-comment](https://eslint.org/docs/rules/spaced-comment)                                 | enforce consistent spacing after the \`//\` or \`/\*\` in a comment                                                    |
 |     | 🔧  |     | [strict](https://eslint.org/docs/rules/strict)                                                 | require or disallow strict mode directives                                                                             |
 |     |     |     | [symbol-description](https://eslint.org/docs/rules/symbol-description)                         | require symbol descriptions                                                                                            |
 |     |     |     | [vars-on-top](https://eslint.org/docs/rules/vars-on-top)                                       | require \`var\` declarations be placed at the top of their containing scope                                            |
@@ -269,7 +270,7 @@ These rules care about how the code looks rather than how it executes:
 |     | 🔧  |     | [func-call-spacing](https://eslint.org/docs/rules/func-call-spacing)                               | require or disallow spacing between function identifiers and their invocations           |
 |     | 🔧  |     | [function-call-argument-newline](https://eslint.org/docs/rules/function-call-argument-newline)     | enforce line breaks between arguments of a function call                                 |
 |     | 🔧  |     | [function-paren-newline](https://eslint.org/docs/rules/function-paren-newline)                     | enforce consistent line breaks inside function parentheses                               |
-|     | 🔧  |     | [generator-star-spacing](https://eslint.org/docs/rules/generator-star-spacing)                     | enforce consistent spacing around \`*\` operators in generator functions                 |
+|     | 🔧  |     | [generator-star-spacing](https://eslint.org/docs/rules/generator-star-spacing)                     | enforce consistent spacing around \`\*\` operators in generator functions                |
 |     | 🔧  |     | [implicit-arrow-linebreak](https://eslint.org/docs/rules/implicit-arrow-linebreak)                 | enforce the location of arrow function bodies                                            |
 |     | 🔧  |     | [indent](https://eslint.org/docs/rules/indent)                                                     | enforce consistent indentation                                                           |
 |     | 🔧  |     | [jsx-quotes](https://eslint.org/docs/rules/jsx-quotes)                                             | enforce the consistent use of either double or single quotes in JSX attributes           |
@@ -371,4 +372,4 @@ These rules from older versions of ESLint (before the [deprecation policy](http
 | [space-unary-word-ops](https://eslint.org/docs/rules/space-unary-word-ops)                           | [space-unary-ops](https://eslint.org/docs/rules/space-unary-ops)                                                                                        |
 | [spaced-line-comment](https://eslint.org/docs/rules/spaced-line-comment)                             | [spaced-comment](https://eslint.org/docs/rules/spaced-comment)                                                                                          |
 
-<!--EndFragment-->
+<!--EndFragment-->