Create tech stack docs (techstack.yml and techstack.md)

[stack-file]

Adding tech stack documentation to allow anyone to easily see what is being used in this repo without digging through config files. Two files are being added: techstack.yml and techstack.md. techstack.yml contains data on all the technologies being used in this repo. techstack.md is a visualization of the YML file and displays the tech stack data in a pretty Markdown file.

💡 Protip: techstack.md contains a comment at the top of the file that the following README snippet (with and without the logos) at the top of the file as a comment:

<--- Readme.md Snippet without images Start --->

Tech Stack

Wladoo/terminal is built on the following main stack:

• ASP.NET – Languages
• C lang – Languages
• C# – Languages
• C++ – Languages
• JavaScript – Languages
• Python – Languages
• .NET – Frameworks (Full Stack)
• .NET Core – Frameworks (Full Stack)
• ASP.NET Core – Frameworks (Full Stack)
• Appium – Mobile Testing Frameworks
• Castle Core – Logging Tools
• GitHub Actions – Continuous Integration
• Selenium – Browser Testing
• Visual Studio – Integrated Development Environment
• Visual Studio Code – Text Editor
• PowerShell – Shells

Full tech stack here

<--- Readme.md Snippet without images End --->

Get the code:

## Tech Stack
Wladoo/terminal is built on the following main stack:

- [ASP.NET](https://www.asp.net/) – Languages
- [C lang](http://en.wikipedia.org/wiki/C_(programming_language)) – Languages
- [C#](http://csharp.net) – Languages
- [C++](http://www.cplusplus.com/) – Languages
- [JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript) – Languages
- [Python](https://www.python.org) – Languages
- [.NET](http://www.microsoft.com/net/) – Frameworks (Full Stack)
- [.NET Core](https://docs.microsoft.com/en-us/dotnet/core/) – Frameworks (Full Stack)
- [ASP.NET Core](docs.microsoft.com/en-us/aspnet/core/) – Frameworks (Full Stack)
- [Appium](http://appium.io/) – Mobile Testing Frameworks
- [Castle Core](https://github.com/castleproject/Core) – Logging Tools
- [GitHub Actions](https://github.com/features/actions) – Continuous Integration
- [Selenium](http://www.seleniumhq.org/) – Browser Testing
- [Visual Studio](http://msdn.microsoft.com/en-us/vstudio/aa718325.aspx) – Integrated Development Environment
- [Visual Studio Code](https://code.visualstudio.com/) – Text Editor
- [PowerShell](https://docs.microsoft.com/en-us/powershell/) – Shells

Full tech stack [here](/techstack.md)

---

<--- Readme.md Snippet with images Start --->

Tech Stack

Wladoo/terminal is built on the following main stack:

• ASP.NET – Languages
• C lang – Languages
• C# – Languages
• C++ – Languages
• JavaScript – Languages
• Python – Languages
• .NET – Frameworks (Full Stack)
• .NET Core – Frameworks (Full Stack)
• ASP.NET Core – Frameworks (Full Stack)
• Appium – Mobile Testing Frameworks
• Castle Core – Logging Tools
• GitHub Actions – Continuous Integration
• Selenium – Browser Testing
• Visual Studio – Integrated Development Environment
• Visual Studio Code – Text Editor
• PowerShell – Shells

Full tech stack here

<--- Readme.md Snippet with images End --->

Get the code:

## Tech Stack
Wladoo/terminal is built on the following main stack:

- <img width='25' height='25' src='https://img.stackshare.io/service/6755/2c45151a4a11d3a3c8e71bb34dd069d6_400x400.png' alt='ASP.NET'/> [ASP.NET](https://www.asp.net/) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/no-img-open-source.png' alt='C lang'/> [C lang](http://en.wikipedia.org/wiki/C_(programming_language)) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/1015/1200px-C_Sharp_wordmark.svg.png' alt='C#'/> [C#](http://csharp.net) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/1049/cplusplus.png' alt='C++'/> [C++](http://www.cplusplus.com/) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/1209/javascript.jpeg' alt='JavaScript'/> [JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/993/pUBY5pVj.png' alt='Python'/> [Python](https://www.python.org) – Languages
- <img width='25' height='25' src='https://img.stackshare.io/service/1014/IoPy1dce_400x400.png' alt='.NET'/> [.NET](http://www.microsoft.com/net/) – Frameworks (Full Stack)
- <img width='25' height='25' src='https://img.stackshare.io/service/6403/default_91fc1f0ee315262794273aa1387eaf8fed8436e6.png' alt='.NET Core'/> [.NET Core](https://docs.microsoft.com/en-us/dotnet/core/) – Frameworks (Full Stack)
- <img width='25' height='25' src='https://img.stackshare.io/service/11331/asp.net-core.png' alt='ASP.NET Core'/> [ASP.NET Core](docs.microsoft.com/en-us/aspnet/core/) – Frameworks (Full Stack)
- <img width='25' height='25' src='https://img.stackshare.io/service/2855/0KVJyYNC_400x400.jpg' alt='Appium'/> [Appium](http://appium.io/) – Mobile Testing Frameworks
- <img width='25' height='25' src='https://img.stackshare.io/service/20916/default_6d17162c9963bc83521ee29cf394f349c95173f3.png' alt='Castle Core'/> [Castle Core](https://github.com/castleproject/Core) – Logging Tools
- <img width='25' height='25' src='https://img.stackshare.io/service/11563/actions.png' alt='GitHub Actions'/> [GitHub Actions](https://github.com/features/actions) – Continuous Integration
- <img width='25' height='25' src='https://img.stackshare.io/service/1517/sbUizSli_400x400.jpg' alt='Selenium'/> [Selenium](http://www.seleniumhq.org/) – Browser Testing
- <img width='25' height='25' src='https://img.stackshare.io/service/1451/SR2hUhQN.png' alt='Visual Studio'/> [Visual Studio](http://msdn.microsoft.com/en-us/vstudio/aa718325.aspx) – Integrated Development Environment
- <img width='25' height='25' src='https://img.stackshare.io/service/4202/Visual_Studio_Code_logo.png' alt='Visual Studio Code'/> [Visual Studio Code](https://code.visualstudio.com/) – Text Editor
- <img width='25' height='25' src='https://img.stackshare.io/service/3681/powershell-logo.png' alt='PowerShell'/> [PowerShell](https://docs.microsoft.com/en-us/powershell/) – Shells

Full tech stack [here](/techstack.md)

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view or the 📜action log for details.

Unrecognized words (4)

aspnet
Machaj
techstack
Wladoo

Previously acknowledged words that are now absent

CLA demoable DUMMYUNIONNAME everytime Hirots inthread ntsubauth NTWIN OPENIF OPENLINK PCLIENT PCOBJECT PCUNICODE PNTSTATUS PPROCESS PUNICODE reingest unmark :arrow_right:

To accept ✔️ these unrecognized words as correct and remove the previously acknowledged and now absent words, run the following commands

... in a clone of the [email protected]:Wladoo/terminal.git repository
on the tech-stack-file branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/v0.0.21/apply.pl' |
perl - 'https://github.com/Wladoo/terminal/actions/runs/8102323837/attempts/1'

Pattern suggestions ✂️ (1)

You could add these patterns to .github/actions/spelling/patterns/5053797ca6ab2b95517d0fd4bcb3da0b48acb188.txt:

# Automatically suggested patterns
# hit-count: 3 file-count: 1
# microsoft
\b(?:https?://|)(?:(?:download\.visualstudio|docs|msdn2?|research)\.microsoft|blogs\.msdn)\.com/[-_a-zA-Z0-9()=./%]*

Warnings (1)

See the 📂 files view or the 📜action log for details.

ℹ️ Warnings	Count
ℹ️ candidate-pattern	1

See ℹ️ Event descriptions for more information.

✏️ Contributor please read this

By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.

⚠️ The command is written for posix shells. If it doesn't work for you, you can manually add (one word per line) / remove items to expect.txt and the excludes.txt files.

If the listed items are:

• ... misspelled, then please correct them instead of using the command.
• ... names, please add them to .github/actions/spelling/allow/names.txt.
• ... APIs, you can add them to a file in .github/actions/spelling/allow/.
• ... just things you're using, please add them to an appropriate file in .github/actions/spelling/expect/.
• ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in .github/actions/spelling/patterns/.

See the README.md in each directory for more information.

🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.