diff --git a/.circleci/config.yml b/.circleci/config.yml
index aefe926..6ff995b 100644
--- a/.circleci/config.yml
+++ b/.circleci/config.yml
@@ -1,15 +1,11 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
# Configuration for Circle CI.
#
# References:
-# - https://circleci.com/docs/2.0
-# - https://circleci.com/docs/2.0/circleci-images
+# 1. https://circleci.com/docs/2.0
+# 2. https://circleci.com/docs/2.0/circleci-images
version: 2.1
diff --git a/.editorconfig b/.editorconfig
index 3348add..f160665 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -1,9 +1,8 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Configurations for EditorConfig.
+# See https://editorconfig.org/#file-format-details for more details.
# +--------------------+
# + Base Configuration +
@@ -16,7 +15,7 @@ end_of_line = lf
indent_size = 2
indent_style = space
insert_final_newline = true
-max_line_length = 120
+max_line_length = 160
trim_trailing_whitespace = true
# +-----------+
diff --git a/.eslintignore b/.eslintignore
index b8735c0..1581030 100644
--- a/.eslintignore
+++ b/.eslintignore
@@ -1,9 +1,8 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Path match pattern to ignore specific files and directories.
+# See https://eslint.org/docs/user-guide/configuring/ignoring-code for more details.
.circleci/*
.github/*
diff --git a/.eslintrc.js b/.eslintrc.js
index ac18885..da427de 100644
--- a/.eslintrc.js
+++ b/.eslintrc.js
@@ -1,15 +1,10 @@
/*
- * Copyright (C) 2017-present Arctic Ice Studio
- * Copyright (C) 2017-present Sven Greb
- *
- * Project: Nord Visual Studio Code
- * Repository: https://github.com/arcticicestudio/nord-visual-studio-code
- * License: MIT
+ * Copyright (c) 2016-present Sven Greb
+ * This source code is licensed under the MIT license found in the license file.
*/
/**
* Configurations for ESLint.
- *
* @see https://eslint.org/docs/user-guide/configuring
*/
module.exports = {
diff --git a/.gitattributes b/.gitattributes
index 105159c..5a605c6 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,21 +1,17 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Configuration to define attributes per path.
# References:
-# https://git-scm.com/docs/gitattributes
-# https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#Keyword-Expansion
+# 1. https://git-scm.com/docs/gitattributes
+# 2. https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes#Keyword-Expansion
-# Automatically perform line feed (LF) normalization for files detected as text and leave all files detected as binary
-# untouched.
+# Automatically perform line feed (LF) normalization for files detected as text and leave all files detected as binary untouched.
* text=auto eol=lf
# +--------+
# + Assets +
# +--------+
-*.ai binary
*.png binary
# +-----------------+
diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 273e7e9..84b72ae 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -1,19 +1,14 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
-# Configuration for the GitHub feature to automatically request reviews from the code owners when a pull request
-# changes any owned files.
+# Configuration for the GitHub feature to automatically request reviews from the code owners
+# when a pull request changes any owned files.
#
# References:
-# https://github.com/blog/2392-introducing-code-owners
-# https://help.github.com/articles/about-codeowners
+# 1. https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-file-location
+# 2. https://github.com/blog/2392-introducing-code-owners
# +----------------------+
# + Core Team Code Owner +
# +----------------------+
-* @arcticicestudio
* @svengreb
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index 719e6e8..0000000
--- a/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
-
-## [Please follow one of the issue templates](https://github.com/arcticicestudio/nord-visual-studio-code/issues/new/choose)
-
-To keep the backlog clean and actionable, issues should be opened using [one the provided issue templates](https://github.com/arcticicestudio/nord-visual-studio-code/issues/new/choose) to help maintainers and the community to understand it, find related reports and to resolve tickets faster.
-
-### Support
-
-If you got a question or need help with any aspect of the project feel free to [join the community](https://www.nordtheme.com/community) and ensure to read the [extensive project documentations](https://www.nordtheme.com/docs).
-
-You can also search for already opened and related issue using the search for the [“question“](https://github.com/arcticicestudio/nord-visual-studio-code/labels/type-question) issue label.
diff --git a/.github/ISSUE_TEMPLATE/bugs.md b/.github/ISSUE_TEMPLATE/bugs.md
deleted file mode 100644
index ef77fcc..0000000
--- a/.github/ISSUE_TEMPLATE/bugs.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-name: Bug Report
-about: Report a bug that is caused by the code in this repository
----
-
-
-
-> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
-
-## Prerequisites
-
-This section and the instructions in the sections below are only part of this issue template. Please ensure to **delete this whole section, all pre-filled instructions of the sections below and sections you have not filled out before submitting** to ensure a clear structure and overview.
-
-Please do your best to provide as much information as possible and use a clear and descriptive title for your bug report to help maintainers and the community understand and reproduce the behavior, find related reports and to resolve the ticket faster.
-
-- **Ensure the bug has not already been reported by using the [GitHub Issues search](https://github.com/arcticicestudio/nord-visual-studio-code/issues)** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one. If you find a closed issue that seems to be similar to this one, include a link to the original issue in the [metadata head](#metadata-head) section of this issue.
-- **Ensure your contribution belongs to the correct [main or port project repository](https://github.com/arcticicestudio?&tab=repositories&q=nord).**
-- **Ensure the bug is reproducible and has not already been fixed** — use the [latest version](https://github.com/arcticicestudio/nord-visual-studio-code/releases/latest) and [`develop`](https://github.com/arcticicestudio/nord-visual-studio-code/tree/develop) branch.
-
-## Metadata Head
-
-The metadata head can be added to the top of the issue as [Markdown text quote](https://help.github.com/articles/basic-writing-and-formatting-syntax) containing the the ID of other related issues.
-
-> Related issues:
-
-## Description
-
-Describe the bug as in many relevant details as possible with a clear and concise description. Ensure to fill in the [steps to reproduce](#steps-to-reproduce) it.
-
-### Steps to Reproduce
-
-1. Step One
-2. Step Two
-3. ...
-
-### Expected Behavior
-
-What you expect to happen?
-
-### Actual Behavior
-
-What actually happens?
-
-## Example
-
-Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md#mcve)
-
-**This is a optional section, but it can drastically increase the speed at which this issue can be processed since it takes away the time-consuming reconstruction to reproduce the bug.**
-The recommended way is to upload it as [Gist](https://gist.github.com) or new repository to GitHub, but of course you can [attach it to this issue](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests), use any free file hosting service or paste the code in [Markdown code blocks](https://help.github.com/articles/basic-writing-and-formatting-syntax) into this issue.
-
-## Environment and Versions
-
-- What is the version of _Nord Visual Studio Code_ you are running?
-- What is the name and the version of your OS?
- - Have you tried to reproduce it on different OS environments and if yes is the behavior the same for all?
-- If the problem is related to the runtime of the project (e.g. [Node.js](https://nodejs.org), [Go](https://golang.org) or [Java](https://java.com)) please provide the version you're running.
- - Are you using any additional CLI arguments to run the project?
-- What is the version of the build tool (e.g. [npm](https://www.npmjs.com), [dep](https://golang.github.io/dep) or [Gradle](https://gradle.org)) you are running?
- - Are you using any additional CLI arguments to start the build tool task/script other than defined by the project?
-
-If you've installed [Node.js](https://nodejs.org) on your system you can run [envinfo](https://www.npmjs.com/package/envinfo) via [npx](https://blog.npmjs.org/post/162869356040/introducing-npx-an-npm-package-runner) which will print environment information that help the the community to better reproduce the bug.
-
-Run the following command **from within the project root** and paste the output in the code block below: `npx envinfo --system --system --IDEs --languages --binaries --markdown --clipboard`
-
-```md
-Paste output of the command here.
-```
-
-## Stack Trace and Error Messages
-
-```raw
-Paste the full stack trace, error messages or the logfile here.
-```
-
-... or [attach them as files](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests) to this issue.
-
-## Additional Context
-
-Add any other context, screenshots or screencasts which are relevant for this issue.
-
-## References
-
-Add any other references and links which are relevant for this issue.
-
-## Potential Solution
-
-Maybe include the lines of code that you have identified as causing the bug or references to other projects where this bug has already been reported.
diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md
deleted file mode 100644
index f4ec584..0000000
--- a/.github/ISSUE_TEMPLATE/enhancement.md
+++ /dev/null
@@ -1,59 +0,0 @@
----
-name: Enhancement Suggestions
-about: Submit an enhancement suggestion for new features or minor improvements to existing functionality
----
-
-
-
-> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
-
-## Prerequisites
-
-This section and the instructions in the sections below are only part of this issue template. Please ensure to **delete this whole section, all pre-filled instructions of the sections below and sections you have not filled out before submitting** to ensure a clear structure and overview.
-
-Please do your best to provide as much information as possible and use a clear and descriptive title for your enhancement suggestion to help maintainers and the community understand and reproduce the behavior, find related reports and to resolve the ticket faster.
-
-- **Ensure the enhancement has not already been reported by using the [GitHub Issues search](https://github.com/arcticicestudio/nord-visual-studio-code/issues)** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one. If you find a closed issue that seems to be similar to this one, include a link to the original issue in the [metadata head](#metadata-head) section of this issue.
-- **Ensure your contribution belongs to the correct [main or port project repository](https://github.com/arcticicestudio?&tab=repositories&q=nord).**
-- **Check if the enhancement has already been implemented** — use the [latest version](https://github.com/arcticicestudio/nord-visual-studio-code/releases/latest) and [`develop`](https://github.com/arcticicestudio/nord-visual-studio-code/tree/develop) branch to ensure that the feature or improvement has not already been added.
-
-## Metadata Head
-
-The metadata head can be added to the top of the issue as [Markdown text quote](https://help.github.com/articles/basic-writing-and-formatting-syntax) containing the ID of other related issues.
-
-> Related issues:
-
-## Description
-
-Describe the enhancement in many relevant details as possible.
-
-### Benefits
-
-Add specific use-cases and explain why this feature or improvement would be useful and maybe include references to related known problems or bug reports.
-
-### Possible Drawbacks
-
-Describe possible negative impacts regarding e.g. functionality or usability.
-
-### Alternative Solutions
-
-If you've considered alternative features or solutions please describe it clearly and concise.
-
-## Example
-
-Provide a [MCVE - The Minimal, Complete, and Verifiable Example](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md#mcve)
-
-**This is a optional section, but it can drastically increase the speed at which this issue can be processed since it takes away the time-consuming reconstruction to reproduce the enhancement.**
-The recommended way is to upload it as [Gist](https://gist.github.com) or new repository to GitHub, but of course you can [attach it to this issue](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests), use any free file hosting service or paste the code in [Markdown code blocks](https://help.github.com/articles/basic-writing-and-formatting-syntax) into this issue.
-
-## Additional Context
-
-Add any other context, screenshots or screencasts which are relevant for this issue.
-
-## References
-
-Add any other references and links which are relevant for this issue.
-
-## Potential Solution
-
-Maybe include references to other projects where this enhancement already exists.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 84b8c56..0000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-> **Please read the [contribution guidelines](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md) before filling out this issue template**.
-
-## Prerequisites
-
-This section and the instructions in the sections below are only part of this pull request template. Please ensure to **delete this whole section, all pre-filled instructions of the sections below and sections you have not filled out before submitting** to ensure a clear structure and overview.
-
-Please do your best to provide as much information as possible and use a clear and descriptive title for your enhancement suggestion or bug fix to help maintainers and the community understand and reproduce the behavior, find related pull requests and to merge it faster.
-
-- **Ensure the pull request has not already been submitted by using the [GitHub Issue search](https://github.com/arcticicestudio/nord-visual-studio-code/issues)** — check if this enhancement or bug fix has already been suggested. If it has **and the pull request is still open**, add your additions as comment or [suggest a change](https://help.github.com/articles/incorporating-feedback-in-your-pull-request/#applying-a-suggested-change) to the existing pull request instead of opening a new one. If you find a closed pull request that seems to be similar to this one, include a link to the original pull request in the [metadata head](#metadata-head) section of this new pull request.
-- **Ensure your contribution belongs to the correct [main or port project repository](https://github.com/arcticicestudio?&tab=repositories&q=nord).**
-- **Ensure to adhere to the [pull request contribution guidelines](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CONTRIBUTING.md#pull-requests)**, especially the one for tests and documentations.
-- **Check if the enhancement has already been implemented or bug already fixed** — use the [latest version](https://github.com/arcticicestudio/nord-visual-studio-code/releases/latest) and [`develop`](https://github.com/arcticicestudio/nord-visual-studio-code/tree/develop) branch to ensure that the enhancement or bug fix has not already been added.
-
-## Metadata Head
-
-The metadata head should be added to the top of the pull request as [Markdown text quote](https://help.github.com/articles/basic-writing-and-formatting-syntax) containing the [GitHub issue keyword(s)](https://help.github.com/articles/closing-issues-using-keywords) to link to the related enhancements suggestions (`Closes`) or bug reports (`Fixes`). You can add additional details like dependencies to other pull requests and the order it needs to be merged.
-
-> Closes ISSUE_ID
-> Must be merged **after**/**before** ISSUE_ID
-
-## Description
-
-Describe the changes as in many relevant details as possible. If this is a enhancement suggestion add specific use-cases and explain why this feature or improvement would be useful. If this is a bug fix ensure to provide a _before/after_ comparison by describing the current behavior and the new behavior.
-
-## References
-
-Add any other references and links which are relevant for this pull request.
diff --git a/.gitignore b/.gitignore
index f0af994..201ee3c 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,9 +1,8 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Path match pattern to intentionally ignore untracked files and directories.
+# See https://git-scm.com/docs/gitignore for more details.
# +---------+
# + Node.js +
diff --git a/.husky/pre-commit b/.husky/pre-commit
index 8eb0919..e50a607 100755
--- a/.husky/pre-commit
+++ b/.husky/pre-commit
@@ -1,17 +1,7 @@
#!/bin/sh
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
-
-# Git "pre-commit" hook for husky.
-#
-# References:
-# 1. https://github.com/typicode/husky
-# 2. https://git-scm.com/docs/githooks#_pre_commit
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
. "$(dirname "$0")/_/husky.sh"
diff --git a/.mailmap b/.mailmap
index 2f3c921..df88d05 100644
--- a/.mailmap
+++ b/.mailmap
@@ -1,13 +1,8 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Docs
-# Repository: https://github.com/arcticicestudio/nord-docs
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
-# Configuration for Git mail mapping feature to coalesce together commits by the same person in the shortlog, where their name and/or email address was spelled differently.
-#
-# References:
-# https://git-scm.com/docs/git-shortlog#_mapping_authors
-Arctic Ice Studio
+# Configuration for the Git mail mapping feature to coalesce together commits by the same person in the shortlog,
+# where their name and/or email address was spelled differently or has been changed.
+# See https://git-scm.com/docs/git-shortlog#_mapping_authors for more details.
Sven Greb
+Sven Greb
diff --git a/.npmrc b/.npmrc
index 403b673..a717f65 100644
--- a/.npmrc
+++ b/.npmrc
@@ -1,9 +1,18 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+# Configurations for npm.
+# See https://docs.npmjs.com/cli/v7/configuring-npm/npmrc for more details.
+
+# Only use a lockfile for single-consumer projects, like applications, but not for multi-consumer projects like
+# libraries.
+# It helps to pin dependency versions, improves the security through integrity checksums, prevents possible errors
+# caused by updated transitive dependencies and allows to get deterministic build results, but it can hide problems in
+# multi-consumer projects when any later versions of a used dependency, or its transitive dependencies, is not
+# compatible with the own project anymore.
package-lock=true
-save-exact=false
+
+# Do not resolve to the latest minor and patch updates.
+# Automatically pin dependencies to exact versions instead of resolving to latest minor and patch updates.
+# This prevents possible errors caused by updated transitive dependencies.
+save-exact=true
diff --git a/.prettierignore b/.prettierignore
index 4f0d3d3..9f48cc7 100644
--- a/.prettierignore
+++ b/.prettierignore
@@ -1,10 +1,9 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Path match pattern to ignore (i.e. not reformat) certain files and folders.
+# See https://prettier.io/docs/en/ignore for more details.
assets/*
-node_modules/*
+**/node_modules/*
*.vsix
diff --git a/.remarkignore b/.remarkignore
index 3f1bfc6..611ff8e 100644
--- a/.remarkignore
+++ b/.remarkignore
@@ -1,13 +1,12 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Path match pattern to ignore when searching for files.
+# See https://github.com/unifiedjs/unified-engine/blob/HEAD/doc/ignore.md for more details.
.circleci/*
.vscode/*
assets/*
-node_modules/*
+**/node_modules/*
themes/*
*.vsix
diff --git a/.remarkrc.js b/.remarkrc.js
index 87c0c3d..b50faf0 100644
--- a/.remarkrc.js
+++ b/.remarkrc.js
@@ -1,16 +1,12 @@
/*
- * Copyright (C) 2017-present Arctic Ice Studio
- * Copyright (C) 2017-present Sven Greb
- *
- * Project: Nord Visual Studio Code
- * Repository: https://github.com/arcticicestudio/nord-visual-studio-code
- * License: MIT
+ * Copyright (c) 2016-present Sven Greb
+ * This source code is licensed under the MIT license found in the license file.
*/
/**
* Configurations for remark-lint.
- *
* @see https://github.com/remarkjs/remark-lint
+ * @see https://remark.js.org
*/
module.exports = {
plugins: ["@arcticicestudio/remark-preset-lint"],
diff --git a/.vscodeignore b/.vscodeignore
index 7e4a368..99fa8ca 100644
--- a/.vscodeignore
+++ b/.vscodeignore
@@ -1,9 +1,8 @@
-# Copyright (C) 2017-present Arctic Ice Studio
-# Copyright (C) 2017-present Sven Greb
-#
-# Project: Nord Visual Studio Code
-# Repository: https://github.com/arcticicestudio/nord-visual-studio-code
-# License: MIT
+# Copyright (c) 2016-present Sven Greb
+# This source code is licensed under the MIT license found in the license file.
+
+# Path match pattern to ignore when searching for files.
+# See https://code.visualstudio.com/api/working-with-extensions/publishing-extension#using-.vscodeignore for more details.
!assets/extension-marketplace-icon.png
!assets/extension-marketplace-icon-2x.png
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 93760bc..6db4a74 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,16 +1,31 @@
-
# 0.19.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/30) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/26)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/26)
⇅ [Show all commits][137]
@@ -48,7 +63,7 @@ This release version includes features introduced in [VS Code version 1.59][140]
-Color tokens for status bar warning items — #225 ⇄ #231 (⊶ b3f2b83a) by @roosephu
+Color tokens for bracket pair colorization — #225 ⇄ #231 (⊶ b3f2b83a) by @roosephu
↠ [VS Code 1.60][143] (August 2021) introduced [native, high performance bracket pair colorization][144] (opt-in via `editor.bracketPairColorization.enabled` setting) to address performance issues of popular extensions. The color tokens have been added and adjusted to match Nord's theme style:
@@ -65,7 +80,7 @@ Note that bracket pair colorization is a feature that does not go well with the
-Color tokens for status bar warning items — #224 ⇄ #232 (⊶ 2ea762e7) by @wenmin92
+Color tokens for TypeScript and JavaScript inlay hints — #224 ⇄ #232 (⊶ 2ea762e7) by @wenmin92
↠ [VS Code 1.60][143] (August 2021) introduced [inlay hints for JavaScript and TypeScript][145] (opt-in via `editor.inlayHints.enabled`), including new color tokens to customize their appereance. They have been added and adjusted to match Nord's theme style:
@@ -93,7 +108,7 @@ Note that bracket pair colorization is a feature that does not go well with the
At the same time outdated dependencies have been upgraded to their latest, compatible version. This also changed the versions by using [the `^` caret range selector][139] to reduce the overhead of updating dependencies.
-- [`@arcticicestudio/eslint-config-base`][135] — the minimum versions will be bumped from `0.5.0` to [`0.11.0`][134].
+- [`@svengreb/eslint-config-base`][135] — the minimum versions will be bumped from `0.5.0` to [`0.11.0`][134].
- [`babel-eslint`][146] → [`@babel/eslint-parser`][152] — the `babel-eslint` package is deprecated and is now available as `@babel/eslint-parser`.
- [`eslint-plugin-json`][163] → [`eslint-plugin-jsonc`][166] — since Visual Studio Code uses [JSONC][170] the `eslint-plugin-jsonc` matches better to the scope of this repository. It also utilizes the ESLint engine by passing the AST to it.
- [`del-cli`][171] — updated from version [`1.1.0`][172] to [`^4.0.1`][173].
@@ -102,14 +117,14 @@ At the same time outdated dependencies have been upgraded to their latest, compa
- [`eslint-plugin-prettier`][154] — updated from version [`3.1.0`][155] to [`^4.0.0`][156].
- [`prettier`][35] — updated from version [`1.17.1`][158] to [`^2.4.1`][159].
- [`remark-cli`][160] — updated from version [`6.0.1`][161] to [`^9.0.0`][162].
-- [`remark-preset-lint-arcticicestudio`][32] → [`@arcticicestudio/remark-preset-lint`][164] — the `remark-preset-lint-arcticicestudio` package is deprecated and is now available as `@arcticicestudio/remark-preset-lint`. This also includes the linting and adjusting for matches that are found after running with the new rules.
+- [`remark-preset-lint-arcticicestudio`][32] → [`@svengreb/remark-preset-lint`][164] — the `remark-preset-lint-arcticicestudio` package is deprecated and is now available as `@svengreb/remark-preset-lint`. This also includes the linting and adjusting for matches that are found after running with the new rules.
- [`vsce`][40] — updated from version [`6.0.1`][168] to [`^1.100.0`][169].
# 0.18.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/29) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/25)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/25)
⇅ [Show all commits][130]
@@ -141,7 +156,7 @@ This release version includes features introduced in [VS Code version 1.58][131]
# 0.17.1
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/28) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/24)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/24)
⇅ [Show all commits][129]
@@ -168,7 +183,7 @@ This release version includes a small bug fix, introduced [version 0.17.0](#0170
# 0.17.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/27) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/23)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/23)
⇅ [Show all commits][116]
@@ -349,7 +364,7 @@ They have been added to make them conform with Nord's theme style:
# 0.16.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/26) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/22)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/22)
⇅ [Show all commits][113]
@@ -420,7 +435,7 @@ These changes broke the current style of Nord and made the theme har to use. The
# 0.15.1
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/25) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/21)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/21)
⇅ [Show all commits][111]
@@ -432,13 +447,13 @@ This release version mainly migrates a NPM package dependency that has been depr
Switch to new ESLint configuration preset package — #190 (⊶ 13ef97ec) by @kremalicious
↠ Before the [`eslint-config-arcticicestudio-base` NPM package][31] was used which has been deprecated and also deleted from the registry.
-Because the goal of the deprecation was to move to the new [`@arcticicestudio/eslint-config-base` package][112] anyway it has now been switched.
+Because the goal of the deprecation was to move to the new [`@svengreb/eslint-config-base` package][112] anyway it has now been switched.
# 0.15.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/24) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/20)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/20)
## Features
@@ -482,7 +497,7 @@ Because the goal of the deprecation was to move to the new [`@arcticicestudio/es
# 0.14.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/23) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/19)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/19)
## Features
@@ -495,7 +510,7 @@ See the [semantic highlighting guide for themes][100] and [Github wiki][98] for
# 0.13.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/22) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/18)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/18)
## Features
@@ -552,7 +567,7 @@ It now uses `nord4` with a opacity of 90% as color value (`#d8dee9e6`).
# 0.12.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/21) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/17)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/17)
## Features
@@ -587,7 +602,7 @@ By renaming the theme file, Nord aligns to the [official bundled and default the
# 0.11.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/20) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/16)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/16)
## Features
@@ -612,7 +627,7 @@ By renaming the theme file, Nord aligns to the [official bundled and default the
# 0.10.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/19) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/15)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/15)
## Features
@@ -642,7 +657,7 @@ Please see the [corresponding issue in the Nord Docs repository][82] to get an o
# 0.9.1
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/18) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/14)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/14)
# Bug Fixes
@@ -651,7 +666,7 @@ Please see the [corresponding issue in the Nord Docs repository][82] to get an o
# 0.9.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/16) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/13)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/13)
# Features
@@ -766,7 +781,7 @@ New and refactored NPM script commands are
# 0.8.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/15) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/12)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/12)
## Features
@@ -815,7 +830,7 @@ It has been set to `nord2` with a opacity of 80% to match the style of inactive
**Comment Color Brightness** — #117/#14/#72 ⇄ #118 (⊶ 7e3881b6)
↠ Implemented the frequently requested and long-time outstanding increase of the comment color (`nord3`) brightness by 10% from a lightness level of ~35% to ~45%.
-➜ **Please see [arcticicestudio/nord#94][67] for all details about this design change decision**!
+➜ **Please see [nordtheme/nord#94][67] for all details about this design change decision**!
For users who would like to use the previously used coloring VS Code allows to [customize and override styles of a specific theme][43] through the user settings. To override the highlighting color of comments **only for Nord** the following snippet can be added to the settings (JSON) file:
@@ -850,9 +865,9 @@ Please see the official documentation about [user and workspace settings][45] fo
↠
Previously the Git diff view used `nord14` with a opacity of 30% to highlight added/modified elements causing some syntax elements like comments to be bad readable. This has now been changed to use `nord9` with a opacity of 20% instead to ensure a better readability and general clearer visual appearance. Also the previously used theme keys `diffEditor.insertedTextBorder` and `diffEditor.removedTextBorder` have been removed for a more clutter-free style.
-
Before
+
Before
-
+
After
@@ -867,7 +882,7 @@ There is still a lot of potential to improve the highlighting for Git diff views
# 0.7.1
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/14) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/11)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/11)
## Bug Fixes
@@ -878,7 +893,7 @@ There is still a lot of potential to improve the highlighting for Git diff views
# 0.7.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/12) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/10)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/10)
## Features
@@ -1005,23 +1020,23 @@ All currently implemented Gulp tasks have therefore been migrated to npm scripts
### Documentation
**Migration to MIT license** — #63 ⇄ #64 (⊶ b26446a5)
-↠ Adapted to the MIT license migration of [29][]. Details can be found in the main task ticket [arcticicestudio/nord#55][30].
+↠ Adapted to the MIT license migration of [29][]. Details can be found in the main task ticket [nordtheme/nord#55][30].
# 0.6.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/11) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/9)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/9)
## Features
### UI
-❯ Added new [new theming color keys][51] for highlighting the [overview ruler][42] introduced in Visual Studio Code version 1.16. (#45 in PR #48, @arcticicestudio, 0459527b)
+❯ Added new [new theming color keys][51] for highlighting the [overview ruler][42] introduced in Visual Studio Code version 1.16. (#45 in PR #48, @svengreb, 0459527b)
Status Highlighting Word Highlighting
-❯ Added new [new theming color key for title bar border][50] for macOS introduced in Visual Studio Code version 1.15. (#46 in PR #49, @arcticicestudio, ad564a4d)
+❯ Added new [new theming color key for title bar border][50] for macOS introduced in Visual Studio Code version 1.15. (#46 in PR #49, @svengreb, ad564a4d)
-❯ Added new [new theming color keys][51] to determine the activity of tabs via a bottom-border introduced in Visual Studio Code version 1.16. (#47 in PR #50, @arcticicestudio, aaf7447f)
+❯ Added new [new theming color keys][51] to determine the activity of tabs via a bottom-border introduced in Visual Studio Code version 1.16. (#47 in PR #50, @svengreb, aaf7447f)
## Improvements
@@ -1061,17 +1076,17 @@ Nord Visual Studio Code adapted to the following contraints:
- Images in `README.md` and `CHANGELOG.md` may not be SVGs unless they are from [approved badge providers][41].
- Images in `README.md` and `CHANGELOG.md` may not use data URIs.
-Additionally, the [footer mountain banner](https://github.com/arcticicestudio/nord/blob/develop/src/assets/banner-footer-mountains.svg) has been changed to PNG format (arcticicestudio/nord#49) and removed the non-HTTPS Arctic Ice Studio logo favicon from the copyright footer line.
+Additionally, the [footer mountain banner](https://github.com/nordtheme/nord/blob/main/src/assets/banner-footer-mountains.svg) has been changed to PNG format (nordtheme/nord#49) and removed the non-HTTPS Arctic Ice Studio logo favicon from the copyright footer line.

-❯ A [`.vscodeignore`][48] file has been added to reduce the size of the distributed `vsix` extension package. (#57 in PR #58, @arcticicestudio @kevinah95, 4660525b)
+❯ A [`.vscodeignore`][48] file has been added to reduce the size of the distributed `vsix` extension package. (#57 in PR #58, @svengreb @kevinah95, 4660525b)
This results in a reduced `vsix` extension package size of **almost 99%** from **~4.7 MB to ~41 kB**!
# 0.5.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/8) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/6)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/6)
## Features
@@ -1095,7 +1110,7 @@ This results in a reduced `vsix` extension package size of **almost 99%** from *
# 0.4.2
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/10) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/8)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/8)
## Bug Fixes
@@ -1107,7 +1122,7 @@ This results in a reduced `vsix` extension package size of **almost 99%** from *
# 0.4.1
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/9) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/7)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/7)
## Bug Fixes
@@ -1117,9 +1132,9 @@ This results in a reduced `vsix` extension package size of **almost 99%** from *
# 0.4.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/7) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/1)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/1)
-[VS Code 1.13](https://code.visualstudio.com/updates/v1_13) has been released including a bunch of [new workbench theme features](https://code.visualstudio.com/updates/v1_13#_new-theming-colors) documented in the official [Theme Color Reference](https://code.visualstudio.com/docs/getstarted/theme-color-reference#_editor-colors). (@arcticicestudio, #25, PR #27, 6aff96bb)
+[VS Code 1.13](https://code.visualstudio.com/updates/v1_13) has been released including a bunch of [new workbench theme features](https://code.visualstudio.com/updates/v1_13#_new-theming-colors) documented in the official [Theme Color Reference](https://code.visualstudio.com/docs/getstarted/theme-color-reference#_editor-colors). (@svengreb, #25, PR #27, 6aff96bb)
(@ajitid, #24, PR #28, 6840124e)
## Features
@@ -1222,7 +1237,7 @@ Next to the changes above the following new workbench theme settings have been a
# 0.3.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/6) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/5)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/5)
## Improvements
@@ -1242,7 +1257,7 @@ Next to the changes above the following new workbench theme settings have been a
# 0.2.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/5) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/6)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/6)
**Please note that the minimal version for this theme is now >=1.12.0 due to the new VS Code theme- and workbench API!**
@@ -1252,39 +1267,39 @@ Next to the changes above the following new workbench theme settings have been a
❯ Implemented full support for the new VS Code theme- and [workbench](https://code.visualstudio.com/docs/getstarted/theme-color-reference) API introduced in version [1.12.0](https://code.visualstudio.com/updates/v1_12#_workbench-theming). (@skbolton, #8 PR #11, e25f748b)
-
-A complete list of all implemented workbench UI styles can be found in the [README](https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/README.md#features).
+A complete list of all implemented workbench UI styles can be found in the [README](https://github.com/nordtheme/visual-studio-code/blob/develop/readme.md#features).
Thanks to @octref and @Tyriar for testing and providing improvement suggestions!
-
Activity Bar Badges
+
Activity Bar Badges
-
Tabs
+
Tabs
-
Status Bar
+
Status Bar
-
Panels and terminal colors
+
Panels and terminal colors
-
Editor Widgets (Search)
+
Editor Widgets (Search)
-
Notifications
+
Notifications
-
Side Bar Views (Debug)
+
Side Bar Views (Debug)
-
Peek View
+
Peek View
-
Diff Editor
+
Diff Editor
-
Peek View
+
Peek View
-
Validations
+
Validations
-
Validations Active selection Inactive selection Active selection with keyboard navigation marker Active- and inactive selection with hover marker
+
Validations Active selection Inactive selection Active selection with keyboard navigation marker Active- and inactive selection with hover marker
❯ Implemented support for terminal ANSI colors. (@threeve, PR #4, 4e5815be)
-
+
## Improvement
@@ -1300,17 +1315,17 @@ Thanks to @octref and @Tyriar for testing and providing improvement suggestions!
❯ Updated the _Quick Open_ keymapping for OSX. (@uonick, PR #9, e93694da)
-❯ Changed the shields (badges) style to `flat-square`. (@arcticicestudio, caafb9d5)
+❯ Changed the shields (badges) style to `flat-square`. (@svengreb, caafb9d5)
## Bug Fixes
### Documentation
-❯ Fixed a typo in the project description. (@arcticicestudio, #6, 8744b392)
+❯ Fixed a typo in the project description. (@svengreb, #6, 8744b392)
# 0.1.1
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/4) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/3)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/3)
## Bug Fixes
@@ -1320,7 +1335,7 @@ Thanks to @octref and @Tyriar for testing and providing improvement suggestions!
# 0.1.0
- [](https://github.com/arcticicestudio/nord-visual-studio-code/projects/3) [](https://github.com/arcticicestudio/nord-visual-studio-code/milestone/2)
+ [](https://github.com/orgs/nordtheme/projects/1/views/10) [](https://github.com/nordtheme/visual-studio-code/milestone/2)
**Initial VS Code Marketplace extension release version!**
@@ -1328,11 +1343,11 @@ Thanks to @octref and @Tyriar for testing and providing improvement suggestions!
A complete list of all implemented features can be found in the [README][174] section.
-❯ Implemented the main color theme file [`Nord.tmTheme`][175]. (@arcticicestudio, #1, 63b16747)
+❯ Implemented the main color theme file [`Nord.tmTheme`][175]. (@svengreb, #1, 63b16747)
-
+
-Detailed information about features, supported languages and install instructions can be found in the [README][176] and in the [project wiki][177].
+Detailed information about features, supported languages and install instructions can be found in the [repository documentation][176].
# 0.0.0
@@ -1340,6 +1355,27 @@ Detailed information about features, supported languages and install instruction
**Project Initialization**
+
+
-[174]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/README.md#features
-[175]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/themes/Nord.tmTheme
-[176]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/README.md#installation
-[177]: https://github.com/arcticicestudio/nord-visual-studio-code/wiki
+[174]: https://github.com/nordtheme/visual-studio-code/blob/develop/readme.md#features
+[175]: https://github.com/nordtheme/visual-studio-code/blob/develop/themes/Nord.tmTheme
+[176]: https://github.com/nordtheme/visual-studio-code/blob/develop/readme.md#installation
[178]: https://img.shields.io/badge/Release_Date-2017--02--18-88C0D0.svg?style=flat-square
-[52]: https://github.com/arcticicestudio/nord-visual-studio-code/issues/100#issuecomment-426005938
+[52]: https://github.com/nordtheme/visual-studio-code/issues/100#issuecomment-426005938
[53]: https://code.visualstudio.com/updates/v1_18#_git-status-in-file-explorer
[54]: https://code.visualstudio.com/updates/v1_18
[55]: https://code.visualstudio.com/updates/v1_20#_more-themable-colors-for-editor-tabs
@@ -1442,7 +1477,7 @@ otherwise Markdown elements are not parsed and rendered!
[66]: https://github.com/Microsoft/vscode/issues/71663
-[67]: https://github.com/arcticicestudio/nord/issues/94
+[67]: https://github.com/nordtheme/nord/issues/94
[68]: https://github.com/al2Me6
[69]: https://github.com/danfo
[70]: https://github.com/marcusramberg
@@ -1454,7 +1489,7 @@ otherwise Markdown elements are not parsed and rendered!
[75]: https://circleci.com/docs/2.0/configuration-reference
-[76]: https://github.com/arcticicestudio/nord-visual-studio-code/issues/133
+[76]: https://github.com/nordtheme/visual-studio-code/issues/133
[77]: https://github.com/blog/2392-introducing-code-owners
[78]: https://github.com/blog/2380-new-community-tools
[79]: https://github.com/blog/1184-contributing-guidelines
@@ -1510,18 +1545,18 @@ otherwise Markdown elements are not parsed and rendered!
-[111]: https://github.com/arcticicestudio/nord-visual-studio-code/compare/v0.15.0...v0.15.1
-[112]: https://www.npmjs.com/package/@arcticicestudio/eslint-config-base
+[111]: https://github.com/nordtheme/visual-studio-code/compare/v0.15.0...v0.15.1
+[112]: https://www.npmjs.com/package/@svengreb/eslint-config-base
-[113]: https://github.com/arcticicestudio/nord-visual-studio-code/compare/v0.15.1...v0.16.0
+[113]: https://github.com/nordtheme/visual-studio-code/compare/v0.15.1...v0.16.0
[114]: https://code.visualstudio.com/updates/v1_46#_new-debug-console-theme-colors
[115]: https://code.visualstudio.com/updates/v1_57#_updated-quick-pick-suggest-widget-color
-[116]: https://github.com/arcticicestudio/nord-visual-studio-code/compare/v0.16.0...v0.17.0
+[116]: https://github.com/nordtheme/visual-studio-code/compare/v0.16.0...v0.17.0
[117]: https://code.visualstudio.com/updates/v1_46#_new-input-theme-colors
[118]: https://code.visualstudio.com/updates/v1_50
[119]: https://code.visualstudio.com/updates/v1_50#_new-theme-colors
@@ -1537,11 +1572,11 @@ otherwise Markdown elements are not parsed and rendered!
-[129]: https://github.com/arcticicestudio/nord-visual-studio-code/compare/v0.17.0...v0.17.1
+[129]: https://github.com/nordtheme/visual-studio-code/compare/v0.17.0...v0.17.1
-[130]: https://github.com/arcticicestudio/nord-visual-studio-code/compare/v0.17.1...v0.18.0
+[130]: https://github.com/nordtheme/visual-studio-code/compare/v0.17.1...v0.18.0
[131]: https://code.visualstudio.com/updates/v1_58
[132]: https://code.visualstudio.com/updates/v1_58#_markdown-math-formula-syntax-highlighting
@@ -1551,7 +1586,7 @@ otherwise Markdown elements are not parsed and rendered!
[134]: https://github.com/arcticicestudio/styleguide-javascript/releases/tag/v0.11.0
[135]: https://github.com/arcticicestudio/styleguide-javascript/tree/main/packages/%40arcticicestudio/eslint-config-base
[136]: https://github.blog/2020-10-13-presenting-v7-0-0-of-the-npm-cli
-[137]: https://github.com/arcticicestudio/nord-visual-studio-code/compare/v0.18.0...v0.19.0
+[137]: https://github.com/nordtheme/visual-studio-code/compare/v0.18.0...v0.19.0
[138]: https://blog.npmjs.org/post/621733939456933888/npm-v7-series-why-keep-package-lockjson
[139]: https://semver.npmjs.com
[140]: https://code.visualstudio.com/updates/v1_59
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
deleted file mode 100644
index ee3839d..0000000
--- a/CODE_OF_CONDUCT.md
+++ /dev/null
@@ -1,61 +0,0 @@
-# Code of Conduct
-
-All (core) team members, contributors/committers and volunteers in this project are required to act according to the following Code of Conduct. We ask you to follow these guidelines which help steer our interactions and strive to keep Visual Studio Code a positive and growing project and help us provide and ensure a safe environment for everyone.
-
-If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact us at support@nordtheme.com or directly to one of the core team members via [email][mailmap]. Your reports will be taken seriously and not dismissed or argued with.
-
-## What we believe in and how we act
-
-- In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. We welcome people regardless of these or other attributes.
-- Our community is based on mutual respect, tolerance, and encouragement.
-- We believe that a diverse community where people treat each other with respect is stronger, more vibrant and has more potential contributors and more sources for ideas. We aim for more diversity.
-- We are kind, welcoming and courteous to everyone.
-- We are focusing on what is best for the community.
-- We are respectful of others, their positions, their skills, their commitments and their efforts.
-- We are attentive in our communications, whether in person or online, and we are tactful and respectful when approaching differing views and experiences.
-- We are aware that language shapes reality. Thus, we use inclusive, gender-neutral language in the documents we provide and when we talk to people. When referring to a group of people, we aim to use gender-neutral terms like “team”, “folks” or “everyone”. [1][ref-gender-neutral-docs]
-- We respect that people have differences of opinion and criticize constructively.
-
-## Unacceptable Behavior
-
-- Do not be mean or rude.
-- Do not discriminate against anyone.
-- Sexism and racism of any kind (including sexist and racist "jokes"), demeaning or insulting behavior and harassment are seen as direct violations to this Code of Conduct. Harassment includes offensive verbal comments related to age, body size, culture, ethnicity, gender expression, gender identity, level of experience, nationality, personal ability or disability, physical appearance, physical or mental difference, race, religion, set of skills, sexual orientation, socio-economic status, and subculture. Harassment also includes sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, inappropriate physical contact, and unwelcome sexual attention.
-- Respect that some individuals and cultures consider the casual use of profanity offensive and off-putting.
-- Derailing, tone arguments and otherwise playing on people's desires to be nice are not welcome, especially in discussions about violations to this Code of Conduct.
-- Please avoid unstructured critique.
-- Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
-
-## Responsibilities
-
-The members of the core team and project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting us via support@nordtheme.com or directly to one of the project core team members or owner via [email][mailmap]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
-
-## Consequences for Violations
-
-If a participant engages in any behavior violating this Code of Conduct, the core team members and project owner of this project may take any action they deem appropriate, including warning the offender or expulsion from the project, exclusion from any interaction and loss of all rights in this project.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
-
-Decisions about consequences of violations of this Code of Conduct are made by this projects core team members and project owner as named above and will not be discussed with the person responsible for the violation.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
-
----
-
-Thanks for the inspirations and attributions to GitHub's [Open Source Guides][oss-guides], [Hoodie's Code of Conduct][hoodie-coc] and the [Contributor Covenant Version 1.4][contrib-cov-1.4].
-
-[contrib-cov-1.4]: https://contributor-covenant.org/version/1/4/code-of-conduct
-[hoodie-coc]: http://hood.ie/code-of-conduct
-[mailmap]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/.mailmap
-[oss-guides]: https://opensource.guide
-[ref-gender-neutral-docs]: https://modelviewculture.com/pieces/gendered-language-feature-or-bug-in-software-documentation
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
deleted file mode 100644
index 0e2f906..0000000
--- a/CONTRIBUTING.md
+++ /dev/null
@@ -1,231 +0,0 @@
-# Contributing to Nord Visual Studio Code
-
-Thanks for contributing to Nord Visual Studio Code!
-
-This is a set of guidelines for contributing to Nord Visual Studio Code. Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
-
-Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalize your pull requests.
-
-As for everything else in the project, the contributions to Nord Visual Studio Code are governed by our [Code of Conduct][gh-coc]. By participating, you are expected to uphold this code. Please report unacceptable behavior at support@nordtheme.com or directly to one of the core team members via [email][gh-mailmap].
-
-## Getting Started
-
-Nord Visual Studio Code is an open source project and we love to receive contributions from the community! There are many ways to contribute, from [writing- and improving documentation and tutorials](#documentations), [reporting bugs](#bug-reports), [submitting enhancement suggestions](#enhancement-suggestions) which can be incorporated into this project and Nord Visual Studio Code itself by [submitting a pull request](#pull-requests).
-
-The project development workflow and process uses [GitHub Issues][gh-issues]- and [Pull Requests][gh-pr] management to track issues and pull requests including multiple [issue templates][gh-issues-templates].
-
-Before you continue with these contribution guidelines we highly recommend to read the awesome GitHub [Open Source Guides][os-guide] on how to [making open source contributions][os-guide-contrib].
-
-### Repository Assignment
-
-Nord is a large open source project which is [split up into multiple repositories][gh-profile-repo-search] with [support for many port projects][nt-ports] and is intentionally very modular. Each port project lives in its own repository.
-
-**Please make sure to determine the correct repository before you continue!**
-Contributions related to Nord belong to [Nord's repository][gh-nord] while contributions related to [this project][gh-nord-visual-studio-code] are welcome in the main repositories. This helps all core team members, committers and maintainer to process every contribution faster without organization overhead.
-
-### Bug Reports
-
-A bug is a _demonstrable problem_ that is caused by the code in the repository. This section guides you through submitting a bug report for Nord Visual Studio Code. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior and find related reports.
-
-**Do NOT report security vulnerabilities in public issues!** Please only contact one of the core team members or project owner in a responsible manner by [email][gh-mailmap] or via support@nordtheme.com. We will assess the issue as soon as possible on a best-effort basis and will give you an estimate for when we have a fix and release available for an eventual public disclosure.
-
-- **Use the [GitHub Issue search][gh-issues]** — check if the issue has already been reported. If it has **and the issue is still open**, add a comment to the existing issue instead of opening a new one. If you find a closed issue that seems like it is the same thing that you are experiencing, open a new issue and include a link to the original issue in the body of your new one.
-- **Determine [which repository the contribution belongs to](#repository-assignment).**
-- **Check if the issue has been fixed** — try to reproduce it using the [latest version][gh-releases-latest] and [`develop`][gh-branch-develop] branch in the repository.
-- **Isolate the problem** — ideally create a [MCVE](#mcve).
-
-When you are creating a bug report, please provide as much detail and context as possible. Fill out on of [the required templates][gh-issues-template-bug], the information it asks helps maintainers to reproduce the problem and resolve issues faster.
-
-- **Use a clear and descriptive title** for the issue to identify the problem.
-- **Describe the exact steps which reproduce the problem** in as many details as possible.
-- **Include screenshots and animated GIFs** if appropriate which show you following the described steps and clearly demonstrate the problem.
-- **Provide specific examples to demonstrate the steps**. Include links to files or GitHub projects, or copy/pasteable snippets. If you are providing snippets in the issue, use [Markdown code blocks][ghh-markdown-code-blocks] or [attach files to the issue][ghh-attach-file].
-
-If possible please provide more context by answering these questions:
-
-- **Did the problem start happening recently** e.g. after updating to a new version of Nord Visual Studio Code or was this always a problem?
- - If the problem started happening recently, **can you reproduce the problem in an older version of Nord Visual Studio Code?**
- - What is the most recent version in which the problem does not happen?
-- **Can you reliably reproduce the issue?** If not, please provide details about how often the problem happens and under which conditions it normally happens.
-
-Please include details about your configuration and environment based on the [issue template][gh-issues-template-bug].
-
-### Enhancement Suggestions
-
-This section guides you through submitting an enhancement suggestion, including completely new features and minor improvements to existing functionality or any new [port project][nt-ports]. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
-
-- **Use the [GitHub Issues search][gh-issues]** — check if this enhancement has already been suggested. If it has **and the issue is still open**, add your additions as comment to the existing issue instead of opening a new one.
-- **Determine [which repository the contribution belongs to](#repository-assignment).**
-- **Check if the enhancement has already been implemented** — use the [latest version][gh-releases-latest] and [`develop`][gh-branch-develop] branch to ensure that the feature or improvement has not already been added.
-- **Provide a reduced show case** — ideally create a [MCVE](#mcve).
-
-Before creating enhancement suggestions, please check if your idea fits with the scope and provide as much detail and context as possible using a structured layout like the [the issue template][gh-issues-template-enhancement].
-
-- **Use a clear and descriptive title** for the issue to identify the suggestion.
-- **Provide a step-by-step description of the suggested enhancement** in as many details as possible and provide use-cases.
-- **Provide examples to demonstrate the need of an enhancement**. Include copy/pasteable snippets which you use in those examples, use [Markdown code blocks][ghh-markdown-code-blocks] or [attach files to the issue][ghh-attach-file].
-- **Describe the current behavior** and **explain which behavior you expected to see instead** and why.
-- **Explain why this enhancement would be useful** to most Nord Visual Studio Code users.
-- **Maybe list some other projects where this enhancement exists.**
-
-### Pull Requests
-
-This section guides you through submitting an pull request. Following these guidelines helps maintainers and the community to better understand your code.
-
-**Please [suggest an enhancement](#enhancement-suggestions) or [report a bug](#bug-reports) first before embarking on any significant pull request** (e.g. implementing features, refactoring code, fixing a bug), otherwise you risk spending a lot of time working on something that the core team members and project owner might not want to merge into the project.
-
-When you are submitting an pull request, please provide as much detail and context as possible. Fill out [the required template][gh-issues-template-pr] to help maintainers to understand your submitted code.
-
-- **Use a clear and descriptive title for the pull request**
-- **Do not include issue numbers in the pull request title** but fill in the metadata section at the top of the [required pull request template][gh-issues-template-pr] making use of the [GitHub issue keywords][ghh-issue-keywords] to link to specific [enhancement suggestions](#enhancement-suggestions) or [bug reports](#bug-reports).
-- **Include screenshots and animated GIFs** if appropriate which show you following the described steps and clearly demonstrate the change.
-- **Make sure to follow the [JavaScript](#javascript-style-guide), [Markdown](#markdown-style-guide) and [Git](#git-style-guide) style guides**.
-- **Remain focused in scope and avoid to include unrelated commits**.
-- **Features and improvements should always be accompanied with tests and documentation**. If the pull request improves the performance consider to include a benchmark test, optimally including a chart.
-- **Lint and test before submitting the pull request**.
-- **Make sure to create the pull request from a [topic branch][git-docs-branching-workflows]**.
-
-**All pull requests must be send against the [`develop`][gh-branch-develop] branch** - Please read the [branch organization](#branch-organization) section below for details about the branching model.
-
-### Documentations
-
-Nord Visual Studio Code's documentation consists of guides, which helps users to learn about the project, and the project docs, which serves as a reference.
-
-You can help improve the docs and guides by making them more coherent, consistent or readable, adding missing information, correcting factual errors, fixing typos, bringing them up to date when there are differences to the latest version. This can be done by submitting a [enhancement suggestion](#enhancement-suggestions) and then opening a [pull request](#pull-requests) for it.
-
-## Branch Organization
-
-Nord Visual Studio Code uses the [gitflow][] branching model. The repository consists of two core branches with an infinite development lifecycle:
-
-- `master` - The source code of `HEAD` always reflects a tagged release version.
-- `develop` - The default branch where the source code of `HEAD` always reflects a state with the latest development state.
-
-**All [pull requests](#pull-requests) for the limited development lifecycle _story_/_topic_ branches must be send against the `develop` branch**.
-
-
-
-## How else can I help?
-
-
-
-### Improve Issues
-
-Some issues are created with missing information, not reproducible, or plain invalid. You can help to make it easier for maintainer to understand and resolve them faster. since handling issues takes a lot of time that could rather spend on writing code.
-
-### Give Feedback On Issues and Pull Requests
-
-We're always looking for more opinions on discussions in issues and pull request reviews which is a good opportunity to influence the future direction of Nord Visual Studio Code.
-
-The [question][gh-issues-label-question] issue label is a good place to find ongoing discussions and questions.
-
-## Style Guides
-
-Every major open source project has its own style guide, a set of standards and conventions for the writing and design of code, documentations and Git commit messages. It is much easier to understand a large code base when all the code in it is in a consistent style.
-
-A style guide establishes and enforces style to improve the intelligibility and communication within the project community. It ensures consistency and enforces best practice in usage and language composition.
-
-### JavaScript Style Guide
-
-Nord Visual Studio Code adheres to the [Arctic Ice Studio JavaScript Style Guide][gh-styleguide-javascript].
-
-[![][gh-styleguide-javascript-badge]][gh-styleguide-javascript]
-
-### Markdown Style Guide
-
-Nord Visual Studio Code adheres to the [Arctic Ice Studio Markdown Style Guide][gh-styleguide-markdown].
-
-[![][gh-styleguide-markdown-badge]][gh-styleguide-markdown]
-
-### Git Commit Messages
-
-A well-crafted Git commit message is the best way to communicate _context_ about a change to the maintainers. The code will tell what changed, but only the commit message can properly tell why. Re-establishing the context of a piece of code is wasteful. We can't avoid it completely, so our efforts should go to reducing it as much as possible.
-
-Nord Visual Studio Code adheres to the [Arctic Ice Studio Git Style Guide][gh-styleguide-git].
-
-[![][gh-styleguide-git-badge]][gh-styleguide-git]
-
-The style guide assumes that you are familiar with the [gitflow][] branching model.
-
-## MCVE
-
-A Minimal, Complete, and Verifiable Example.
-
-When [reporting a bug](#bug-reports), sometimes even when [suggesting enhancements](#enhancement-suggestions), the issue can be processed faster if you provide code for reproduction. That code should be…
-
-- …Minimal – Use as little code as possible that still produces the same behavior
-- …Complete – Provide all parts needed to reproduce the behavior
-- …Verifiable – Test the code you're about to provide to make sure it reproduces the behavior
-
-A MCVE is a common practice like on [Stack Overflow][stackoverflow-mcve] and sometimes it is also called [SSCCE][], a _Short, Self Contained, Correct (Compilable), Example_.
-
-The recommended way for GitHub based projects is to create it as [Gist][gh-gist] or new repository, but of course you can [attach it to issues and pull requests as files][ghh-attach-file], use any free code paste- or file hosting service or paste the code in [Markdown code blocks][ghh-markdown-code-blocks] into the issue.
-
-### Minimal
-
-The more code there is to go through, the less likely developers can understand your enhancement or find the bug. Streamline your example in one of two ways:
-
-- **Restart from scratch**. Create new code, adding in only what is needed to demonstrate the behavior and is also useful if you can't post the original code publicly for legal or ethical reasons.
-- **Divide and conquer**. When you have a small amount of code, but the source of the bug is entirely unclear, start removing code a bit at a time until the problem disappears – then add the last part back and document this behavior to help developers to trace- and debug faster.
-
-#### Minimal and readable
-
-Minimal does not mean terse – don't sacrifice communication to brevity. Use consistent naming and indentation following the [style guides](#style-guides), and include comments if needed to explain portions of the code.
-
-### Complete
-
-Make sure all resources and code necessary to reproduce the behavior is included. The problem might not be in the part you suspect it is, but another part entirely.
-
-### Verifiable
-
-To entirely understand your enhancement or bug report, developers will need to verify that it _exists_:
-
-- **Follow the contribution guidelines regarding the description and details**. Without information developers won't be able to understand and reproduce the behavior.
-- **Eliminate any issues that aren't relevant**. Ensure that there are no compile-time errors.
-- **Make sure that the example actually reproduces the problem**. Sometimes the bug gets fixed inadvertently or unconsciously while composing the example or does not occur when running on fresh machine environment.
-
-## Versioning
-
-Nord Visual Studio Code follows the [Semantic Versioning Specification][semver] (SemVer). We release patch versions for bug fixes, minor versions for enhancements like new features and improvements, and major versions for any backwards incompatible changes. Deprecation warnings are introduced for breaking changes in a minor version so that users learn about the upcoming changes and migrate their code in advance.
-
-Every significant change is documented in the [changelog][gh-changelog].
-
-## Credits
-
-Thanks for the inspirations and attributions to GitHub's [Open Source Guides][os-guide] and various contribution guides of large open source projects like [Atom][gh-atom-contrib], [React][react-contrib] and [Ruby on Rails][ruby-on-rails-contrib].
-
-[gh-atom-contrib]: https://github.com/atom/atom/blob/master/CONTRIBUTING.md
-[gh-branch-develop]: https://github.com/arcticicestudio/nord-visual-studio-code/tree/develop
-[gh-changelog]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CHANGELOG.md
-[gh-coc]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/CODE_OF_CONDUCT.md
-[gh-gist]: https://gist.github.com
-[gh-issues]: https://github.com/arcticicestudio/nord-visual-studio-code/issues
-[gh-issues-label-question]: https://github.com/arcticicestudio/nord-visual-studio-code/labels/type-question
-[gh-issues-template-bug]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/.github/ISSUE_TEMPLATE/bugs.md
-[gh-issues-template-enhancement]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/.github/ISSUE_TEMPLATE/enhancement.md
-[gh-issues-template-pr]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/.github/PULL_REQUEST_TEMPLATE.md
-[gh-issues-templates]: https://github.com/arcticicestudio/nord-visual-studio-code/issues/new/choose
-[gh-mailmap]: https://github.com/arcticicestudio/nord-visual-studio-code/blob/develop/.mailmap
-[gh-nord]: https://github.com/arcticicestudio/nord
-[gh-nord-visual-studio-code]: https://github.com/arcticicestudio/nord-visual-studio-code
-[gh-pr]: https://github.com/arcticicestudio/nord-visual-studio-code/pulls
-[gh-profile-repo-search]: https://github.com/arcticicestudio?&tab=repositories&q=nord
-[gh-releases-latest]: https://github.com/arcticicestudio/nord-visual-studio-code/releases/latest
-[gh-styleguide-git]: https://github.com/arcticicestudio/styleguide-git
-[gh-styleguide-git-badge]: https://raw.githubusercontent.com/arcticicestudio/styleguide-git/develop/assets/styleguide-git-banner-typography-badge.svg?sanitize=true
-[gh-styleguide-javascript]: https://github.com/arcticicestudio/styleguide-javascript
-[gh-styleguide-javascript-badge]: https://raw.githubusercontent.com/arcticicestudio/styleguide-javascript/develop/assets/styleguide-javascript-banner-typography-badge.svg?sanitize=true
-[gh-styleguide-markdown]: https://github.com/arcticicestudio/styleguide-markdown
-[gh-styleguide-markdown-badge]: https://raw.githubusercontent.com/arcticicestudio/styleguide-markdown/develop/assets/styleguide-markdown-banner-typography-badge.svg?sanitize=true
-[ghh-attach-file]: https://help.github.com/articles/file-attachments-on-issues-and-pull-requests
-[ghh-issue-keywords]: https://help.github.com/articles/closing-issues-using-keywords
-[ghh-markdown-code-blocks]: https://help.github.com/articles/basic-writing-and-formatting-syntax
-[git-docs-branching-workflows]: https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows
-[gitflow]: http://nvie.com/posts/a-successful-git-branching-model
-[nt-ports]: https://nordtheme.com/ports
-[os-guide]: https://opensource.guide
-[os-guide-contrib]: https://opensource.guide/how-to-contribute
-[react-contrib]: https://facebook.github.io/react/contributing/how-to-contribute.html
-[ruby-on-rails-contrib]: http://guides.rubyonrails.org/contributing_to_ruby_on_rails.html
-[semver]: https://semver.org
-[sscce]: http://sscce.org
-[stackoverflow-mcve]: https://stackoverflow.com/help/mcve
diff --git a/LICENSE b/LICENSE
index cd0b7b1..996f8fb 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,7 +1,6 @@
MIT License (MIT)
-Copyright (C) 2017-present Arctic Ice Studio (https://www.arcticicestudio.com)
-Copyright (C) 2017-present Sven Greb (https://www.svengreb.de)
+Copyright (c) 2016-present Sven Greb (https://www.svengreb.de)
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
diff --git a/README.md b/README.md
index 7d10967..b1e7bae 100644
--- a/README.md
+++ b/README.md
@@ -1,18 +1,66 @@
-
## Getting Started
@@ -26,7 +74,11 @@ Thanks to the official [VS Code Extension Marketplace][vscode-extmarket-home], _
Open the [extension marketplace][vscode-docs-extmarket] by clicking on the _Extensions_ icon in the [_Activity Bar_][vscode-docs-ui-actbar]. Search for `Nord` and click on the Install button.
-
+
+
+
+
+
See Nord Visual Studio Code's documentation for details about more installation options like a [manual import through a local VSIX extension file][nord-docs-home-install#local].
@@ -34,23 +86,45 @@ See Nord Visual Studio Code's documentation for details about more installation
To activate the theme click on the gear icon in the _Activity Bar_ and select _Color Theme_. Search for `Nord` and confirm the color theme change with Enter.
-
+
+
+
+
+
See Nord Visual Studio Code's documentation for details about [more activation options][nord-docs-home-install#activation].
## Features
-
Your IDE. Your style.
A unified UI and editor syntax element design provides a clutter-free and fluidly merging appearance.
+
+
Your IDE. Your style.
+
A unified UI and editor syntax element design provides a clutter-free and fluidly merging appearance.
+
-
+
+
+
+
+
-
Beautiful code to keep focused.
The editor color scheme supports a wide range of programming languages — From bundled definitions up to many popular third-party syntax extensions.
+
+
Beautiful code to keep focused.
+
The editor color scheme supports a wide range of programming languages — From bundled definitions up to many popular third-party syntax extensions.
+
-
+
+
+
+
+
Small details with unobtrusive styles.
Popular and common code editor features like search result marker and brace matching are designed to get out of your way with a visually attractive appearance.
-
+
+
+
+
+
## Contributing
@@ -62,24 +136,39 @@ Please take a moment to read Nord's full [contributing guide][nord-contrib-guide
The guide also includes information about [minimal, complete, and verifiable examples][nord-contrib-guide-mcve] and other ways to contribute to the project like [improving existing issues][nord-contrib-guide-impr-issues] and [giving feedback on issues and pull requests][nord-contrib-guide-feedback].
-