feat: initial commit

Author: d3lm

.github/ISSUE_TEMPLATE/✨-feature-your-project.md

@@ -0,0 +1,27 @@
+---
+name: "✨ Feature your project"
+about: Are you building with WebContainer API? Tell us about it!
+title: "[✨ Project submission]"
+labels: documentation
+assignees: sylwiavargas
+
+---
+
+Are you building with WebContainer API? Let's celebrate it 🥳
+Let us know and we'll feature it on our website, blog, and/or social media!
+
+---
+## Description
+Tell us a few words about your project.
+
+## Link
+Provide a link or a few links to the project - a website, blog post, a talk, youtube, etc.
+
+## Handles
+Provide a Twitter or GitHub handle of the author of the project.
+
+--- 
+Please note that your submission must:
+- be in accordance with our [Code of Conduct](CODE_OF_CONDUCT.md),
+- relate to WebContainers,
+- feature a project which is still online.

.github/ISSUE_TEMPLATE/🪲-bug-report.md

@@ -0,0 +1,38 @@
+---
+name: "\U0001FAB2 Bug report"
+about: Create a report to help us improve!
+title: "[BUG]"
+labels: bug
+assignees: sylwiavargas
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots or screen recordings to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.gitignore

@@ -0,0 +1,106 @@
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# TypeScript v1 declaration files
+typings/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.test
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+
+# Next.js build output
+.next
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+docs/build
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and *not* Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vitepress/dist
+docs/.vitepress/cache
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port

.prettierrc

@@ -0,0 +1,5 @@
+{
+  "useTabs": false,
+  "singleQuote": true,
+  "printWidth": 100
+}

.stackblitzrc

@@ -0,0 +1,3 @@
+{
+    "startCommand": "npm run dev"
+}

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+	// See https://go.microsoft.com/fwlink/?LinkId=827846
+	// for the documentation about the extensions.json format
+	"recommendations": [
+		"Vue.volar"
+	]
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Code of conduct
+
+## Introduction
+
+We welcome contributions from folks from all skill levels and expertise. We are especially welcoming to new programmers and to folks who have a keen interest in growing as technical writers or DocOps engineers.
+
+We are a community that prioritizes a harassment-free experience for everyone.
+
+## Our Standards
+
+Examples of behavior that contributes to **fostering a positive environment** include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Referring to people by their preferred pronouns and using gender-neutral pronouns when uncertain
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of **unacceptable behavior** by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- 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
+- Dismissing or attacking inclusion-oriented requests
+
+**We prioritize marginalized people's safety over privileged people's comfort.** We will not act on complaints regarding:
+
+- ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’
+- Reasonable communication of boundaries, such as 'leave me alone,' 'go away,' or 'I’m not discussing this with you.'
+- Someone’s refusal to explain or debate social justice concepts
+- Criticisms of racist, sexist, cissexist, or otherwise oppressive behavior or assumptions
+
+In community communication, we do not appreciate any form of aggression (passive aggression included) — please don't post if you can't be kind and empathetic. Be proactive about owning your mistakes and apologizing if you have a feeling or know that you impacted someone in a negative way.
+
+## Attribution
+
+This Code of Conduct is adapted from:
+
+- [Write/Speak/Code](https://www.writespeakcode.com/code-of-conduct/)
+- [Dev.to](https://dev.to/code-of-conduct)

CONTRIBUTING.md

@@ -0,0 +1,62 @@
+
+# Contributor Manual
+
+We welcome contributions from folks from all skill levels and expertise. We are especially welcoming to new programmers and to those with a keen interest in growing as technical writers or DocOps engineers.
+
+---
+
+## Before you begin
+
+We expect contributors to abide by our underlying [Code of Conduct](CODE_OF_CONDUCT.md). All discussions connected to our docs must be kind, respectful, and harassment-free. We will not dignify PRs or other contributions created in the spirit of disregard for the Code of Conduct.
+
+We believe that communication is the lifeblood of any Open Source project. Please use beginner-friendly language. It's very easy to misunderstand one another in asynchronous, text-based conversations. When in doubt, assume everyone has the best intentions but consider helping them do better with clarifying questions and kind feedback. Remember that for many people English is not their first language and in such communication, native English speakers are also expected to flex their "foreigner muscle".
+
+---
+
+## Types of Contributions
+
+There are numerous ways to contribute to docs:
+
+- **Share feedback**
+  - Each docs page features a feedback tool at the bottom - you can use it to let us know what you think!
+  - If you see something broken or think any section could be better or less confusing please [check if there's an issue for that already](https://github.com/stackblitz/webcontainer-docs/issues) and if not, feel free to [create one](https://github.com/stackblitz/webcontainer-docs/issues/new).
+- **Share ideas**
+  - We want our docs to be delightful. If you have an idea on an improvement, reach out to us on [GitHub discussions](https://github.com/stackblitz/webcontainer-docs/discussions).
+- **Fix typos**
+  - Use [Web Publisher](#content-updates-with-web-publisher) for a quick typo fix!
+- **Create demos**
+  - We'd like to help our users see more examples of using WebContainer API. Would you like to create a demo? Before you do, please reach out to us on [GitHub discussions](https://github.com/stackblitz/webcontainer-docs/discussions).
+- **Fix an issue**
+  - You see an issue with the docs platform you'd like to work on? Ask to be assigned to fix it. Before you start your work, please read our [contributing guide](CONTRIBUTING.md).
+- **Reviews**
+  - Please feel free to check existing PRs and issues. Share your loving feedback, help the other contributor approach the task in a better way, spot lurking bugs, errors, and mistakes. You can use pr.new to that end - in the URL of the issue or PR, swap "github.com" with "pr.new" to spin up the environment and the preview.
+
+Thank you for making our docs better!
+
+### What makes good issue
+
+When creating an issue, please include:
+
+- a descriptive title,
+- a link to what this issue refers to (a page, an example, a section),
+- if applicable, a screenshot or screen recording,
+- explanation of why you think it is an issue,
+- if you have an idea, a possible solution,
+- ideally, external links that explain any advanced or lesser-known topics so others can learn from your issue.
+
+Please raise issues in situations like the following:
+
+- confusing, overwhelming, or incorrect explanation,
+- outdated examples,
+- vague or missing content,
+- demo or page request,
+- compromised accessibility,
+- anything broken: demo, page, url, image,
+
+If what you want to say doesn't really fall into actionable "problem" or "improvement", you can **start a new Discussion topic**. For example, feel free to ask:
+
+- Could we split this page into multiple smaller steps?
+- This navigation item doesn't fit where it is - could we move it somewhere else?
+- How could we make the docs site more (adjective)?
+
+---

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 StackBlitz
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.