Adding pre-build to main

Signed-off-by: Eric Gregory <eric@cosmonic.com>

Author: ericgregory

.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

README.md

@@ -0,0 +1,9 @@
+# WASI.dev
+
+WASI.dev is an introduction to [WASI](https://github.com/WebAssembly/WASI/tree/main) for users of all backgrounds. The site is under active development by volunteers coordinated through the Bytecode Alliance's Special Interest Group for Documentation. If you're interested in getting involved, you can find us on the SIG Documentation channel of the [Bytecode Alliance's Zulip server](https://bytecodealliance.zulipchat.com/), or [contribute on the WASI.dev GitHub repo](https://github.com/bytecodealliance/wasi.dev).
+
+### Local development
+
+This website is built using [Docusaurus](https://docusaurus.io/). After forking and checking out the `main` branch of this repository, you can build and start a development server with `npm install` and `npm start`. Most changes are reflected live without having to restart the server. Run `npm run build` to produce the site content, and open a PR to the `gh-pages` branch of the `bytecodealliance/wasi.dev` repo to contribute.
+
+

babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

docs/contribute.md

@@ -0,0 +1,11 @@
+---
+title: "Contribute"
+sidebar_position: 4
+---
+  
+This site is a community effort supported by volunteers through the Bytecode Alliance's Special Interest Group for Documentation. 
+The **[Bytecode Alliance](https://bytecodealliance.org/)** is a community comprised of many individual contributors and 30+ companies involved in the WebAssembly space. 
+
+The Bytecode Alliance is focused on creating a shared implementation of standards produced by the WebAssembly CG, the WASI Subgroup, and other standardization bodies. We believe that standards are best informed by implementation. To enable this, we bring together a wide range of different use cases. Many of our contributors are also active in standardization and use this implementation experience and feedback to inform their work.
+
+If you would like to get involved, you can find us on the SIG Documentation channel of the [Bytecode Alliance's Zulip server](https://bytecodealliance.zulipchat.com/) or [contribute on the WASI.dev GitHub repo](https://github.com/bytecodealliance/wasi.dev).

docs/interfaces.md

@@ -0,0 +1,40 @@
+---
+title: "Interfaces"
+sidebar_position: 2
+---
+
+## Modules and components
+
+WebAssembly binaries may be **components** built according to the [Component Model](https://component-model.bytecodealliance.org/) or **modules** built to the core WebAssembly specification. 
+
+As you begin writing a Wasm application using WASI APIs, one of your first decisions will be which type of binary you want to produce—a decision typically guided by your use-case and the runtime you wish to use. Check to see which WASI releases your runtime supports. 
+
+* **Components** can use WASI 0.2 and the Component Model for composability and interoperability, meaning that a WebAssembly component compiled from one language (Rust, for example) can communicate or be combined with a component compiled from another language (such as Go). WASI 0.2 sets the stage for the future of WASI.
+
+* **Modules** can use APIs from WASI 0.1, an earlier stage of WASI's development. Since WASI 0.2 was released in February 2024, WASI 0.1 support is more widespread among Wasm runtimes, and it is widely used in production today. 
+
+## WASI 0.2
+
+WASI 0.2 is the most recent WASI release. APIs designed for WASI 0.2 and the Component Model are defined with the [**WebAssembly Interface Type (WIT)**](https://github.com/WebAssembly/component-model/blob/main/design/mvp/WIT.md) Interface Description Language (IDL). WIT API definitions are made in `.wit` files which are composed into Wasm component binaries. The following interfaces are included in WASI P2:
+
+| API          | Repository                                     | Version |
+| ------------ | ---------------------------------------------- | ------- |
+| I/O          | https://github.com/WebAssembly/wasi-io         | 0.2.0   |
+| Clocks       | https://github.com/WebAssembly/wasi-clocks     | 0.2.0   |
+| Random       | https://github.com/WebAssembly/wasi-random     | 0.2.0   |
+| Filesystem   | https://github.com/WebAssembly/wasi-filesystem | 0.2.0   |
+| Sockets      | https://github.com/WebAssembly/wasi-sockets    | 0.2.0   |
+| CLI          | https://github.com/WebAssembly/wasi-cli        | 0.2.0   |
+| HTTP         | https://github.com/WebAssembly/wasi-http       | 0.2.0   |
+
+You can explore the types and definitions for a given WASI 0.2 API in its WIT files. When you're ready to start using the API, you will typically generate bindings between the WIT definitions and the language you will be compiling to Wasm. For more information on WIT, see the [WIT section of the Component Model documentation](https://component-model.bytecodealliance.org/design/wit.html). 
+
+## WASI 0.1
+
+WASI P1 APIs were defined with WITX Interface Description Language (IDL), which was an iterative step toward WIT but bears notable differences, including that it was developed as a lower-level derivation of WebAssembly Text Format (a human-readable source format for Wasm modules). Documentation for WASI 0.1 and WITX can be found in the [`legacy` directory of the WASI GitHub repository](https://github.com/WebAssembly/WASI/blob/main/legacy/README.md), along with a [complete list of 0.1 types and modules](https://github.com/WebAssembly/WASI/blob/main/legacy/preview1/docs.md).
+
+## Proposals for the standard
+
+All WASI APIs are **proposals** for standardization by the WASI Subgroup. The API proposals in WASI 0.1 and 0.2 met implementation and portability criteria for inclusion at the time of those releases. 
+
+All active WASI API proposals can be found on the [WASI GitHub repository](https://github.com/WebAssembly/WASI/blob/main/Proposals.md), along with the [process for making a proposal](https://github.com/WebAssembly/WASI/blob/main/Contributing.md#the-phase-process).

docs/introduction.md

@@ -0,0 +1,29 @@
+---
+title: "Introduction"
+slug: /
+sidebar_position: 1
+---
+  
+The **WebAssembly System Interface (WASI)** is a group of standard API specifications for software compiled to the **[W3C WebAssembly (Wasm) standard](https://www.w3.org/TR/wasm-core-2/)**. WASI is designed to provide a secure standard interface for applications that can be compiled to Wasm from any language, and that may run anywhere—from browsers to clouds to embedded devices.  
+
+By standardizing APIs for WebAssembly, WASI provides a way to compose software written in different languages—without costly and clunky interface systems like HTTP-based microservices. We believe that every project with a plugin model should be using WASI, and that WASI is ideally suited for projects with SDKs for multiple languages, e.g. client libraries.
+
+To date, WASI has seen two milestone releases known as **0.1** and **0.2**. (Sometimes you will see these referred to as Preview 1 and Preview 2, or P1 and P2). The concepts and vocabulary of Wasm and WASI can sometimes be opaque to newcomers, so WASI.dev serves as an introduction to WASI for users of all backgrounds. It's very much a work-in-progress, and we welcome contributions on the [GitHub repo](https://github.com/bytecodealliance/wasi.dev). 
+
+## Who are we?
+
+WASI is an open standard under active development by the [**WASI Subgroup**](https://github.com/WebAssembly/WASI/blob/main/Charter.md) in the **W3C WebAssembly Community Group**. Discussions happen in [GitHub issues](https://github.com/WebAssembly/WASI/issues), [pull requests](https://github.com/WebAssembly/WASI/pulls), and [bi-weekly Zoom meetings](https://github.com/WebAssembly/meetings/tree/main/wasi).
+
+## Who are you?
+
+WASI and Wasm are tools for any type of software developer: whether you're writing web apps, plugins, serverless functions, User-Defined Functions (UDFs) in a database, embedded controller components, sidecar networking filters, or something completely different. This site is intended to make WASI understandable regardless of your background, use-case, or familiarity with the WebAssembly ecosystem.
+
+## How to get started
+
+There are many different runtimes that support WASI including [Wasmtime](https://wasmtime.dev/), [WAMR](https://bytecodealliance.github.io/wamr.dev/), [WasmEdge](https://wasmedge.org/), [wazero](https://wazero.io/), [Wasmer](https://wasmer.io/), [wasmi](https://github.com/wasmi-labs/wasmi), and [wasm3](https://github.com/wasm3/wasm3). Many of these runtimes have different areas of focus (i.e., IoT, embedded devices, and edge for WAMR, or server-side and non-web embeddings with components for Wasmtime). The introductory documentation for each is a great place to start.
+
+WASI can be implemented by both core Wasm modules and applications built according to the **Component Model**, a specification for Wasm applications that are interoperable and composable. You can learn more about components in the Bytecode Alliance's **[WebAssembly Component Model](https://component-model.bytecodealliance.org/)** documentation. 
+
+[Continue reading](./interfaces.md) to learn more about WASI interfaces, including available APIs and how they are defined. 
+
+

docs/resources.md

@@ -0,0 +1,27 @@
+---
+title: "Resources"
+sidebar_position: 3
+---
+  
+The following resources are helpful for those wishing to learn more about WASI and the WebAssembly ecosystem:
+
+## WASI
+
+* **[The WASI GitHub repository](https://github.com/WebAssembly/WASI)**
+
+## WASI 0.2 and the Component Model
+
+* **[WASI 0.2 GitHub repository](https://github.com/WebAssembly/WASI/blob/main/preview2/README.md)**
+* **[The Component Model GitHub repository](https://github.com/WebAssembly/component-model/tree/main)**
+* **[The WebAssembly Component Model documentation](https://component-model.bytecodealliance.org/)** 
+* **[The WIT format](https://github.com/WebAssembly/component-model/blob/main/design/mvp/WIT.md)**
+
+## WASI 0.1
+
+* **[WASI 0.1 legacy documentation](https://github.com/WebAssembly/WASI/blob/main/legacy/README.md)**
+* **[WASI 0.1 types and modules](https://github.com/WebAssembly/WASI/blob/main/legacy/preview1/docs.md)**
+
+## WebAssembly
+
+* **[The WebAssembly Core Specification](https://www.w3.org/TR/wasm-core-2/)**
+* **[WebAssembly Text (WAT) format](https://webassembly.github.io/spec/core/text/index.html)**

docusaurus.config.js

@@ -0,0 +1,117 @@
+// @ts-check
+// `@type` JSDoc annotations allow editor autocompletion and type checking
+// (when paired with `@ts-check`).
+// There are various equivalent ways to declare your Docusaurus config.
+// See: https://docusaurus.io/docs/api/docusaurus-config
+
+import {themes as prismThemes} from 'prism-react-renderer';
+
+/** @type {import('@docusaurus/types').Config} */
+const config = {
+  title: 'WASI.dev',
+  favicon: 'img/favicon.ico',
+
+  // Set the production url of your site here
+  url: 'https://bytecodealliance.github.io',
+  // Set the /<baseUrl>/ pathname under which your site is served
+  // For GitHub pages deployment, it is often '/<projectName>/'
+  baseUrl: '/wasi.dev/',
+
+  // GitHub pages deployment config.
+  // If you aren't using GitHub pages, you don't need these.
+  organizationName: 'bytecodealliance', // Usually your GitHub org/user name.
+  projectName: 'wasi.dev', // Usually your repo name.
+  trailingSlash: false,
+
+  onBrokenLinks: 'throw',
+  onBrokenMarkdownLinks: 'warn',
+
+  // Even if you don't use internationalization, you can use this field to set
+  // useful metadata like html lang. For example, if your site is Chinese, you
+  // may want to replace "en" with "zh-Hans".
+  i18n: {
+    defaultLocale: 'en',
+    locales: ['en'],
+  },
+
+  presets: [
+    [
+      'classic',
+      /** @type {import('@docusaurus/preset-classic').Options} */
+      ({
+        docs: {
+          routeBasePath: '/', // Set this value to '/'.
+          
+          sidebarPath: './sidebars.js',
+          // Please change this to your repo.
+          // Remove this to remove the "edit this page" links.
+          editUrl:
+            'https://github.com/facebook/docusaurus/tree/main/packages/create-docusaurus/templates/shared/',
+        },
+        blog: false,
+        theme: {
+          customCss: './src/css/custom.css',
+        },
+      }),
+    ],
+  ],
+
+  themeConfig:
+    /** @type {import('@docusaurus/preset-classic').ThemeConfig} */
+    ({
+      // Replace with your project's social card
+      image: 'img/docusaurus-social-card.jpg',
+      navbar: {
+        title: 'WASI.dev',
+        logo: {
+          alt: 'WASI logo',
+          src: 'img/wasi.png',
+        },
+        items: [
+          {
+            href: 'https://github.com/bytecodealliance/wasi.dev',
+            label: 'GitHub',
+            position: 'right',
+          },
+        ],
+      },
+      footer: {
+        style: 'dark',
+        links: [
+          {
+            title: 'Docs',
+            items: [
+              {
+                label: 'Introduction',
+                to: '/docs/intro',
+              },
+            ],
+          },
+          {
+            title: 'Community',
+            items: [
+              {
+                label: 'Zulip',
+                href: 'https://bytecodealliance.zulipchat.com/',
+              },
+            ],
+          },
+          {
+            title: 'More',
+            items: [
+              {
+                label: 'GitHub',
+                href: 'https://github.com/bytecodealliance/wasi.dev',
+              },
+            ],
+          },
+        ],
+      },
+      prism: {
+        theme: prismThemes.github,
+        darkTheme: prismThemes.dracula,
+      },
+    }),
+};
+
+export default config;