init commit, new structure, old content

.github/workflows/hubs-docs.yaml

@@ -0,0 +1,14 @@
+name: hubs-docs
+on:
+  push:
+    branches:
+    paths-ignore: ["README.md"]
+  workflow_dispatch:
+
+jobs:
+  turkeyGitops:
+    uses: mozilla/hubs-ops/.github/workflows/turkeyGitops.yml@master
+    with:
+      registry: mozillareality
+    secrets:
+      DOCKER_HUB_PWD: ${{ secrets.DOCKER_HUB_PWD }}

.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,41 @@
+# Website
+
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
+
+### Installation
+
+```
+$ yarn
+```
+
+### Local Development
+
+```
+$ yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+### Build
+
+```
+$ yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+### Deployment
+
+Using SSH:
+
+```
+$ USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```
+$ GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

babel.config.js

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

blog/2019-05-28-first-blog-post.md

@@ -0,0 +1,12 @@
+---
+slug: first-blog-post
+title: First Blog Post
+authors:
+  name: Gao Wei
+  title: Docusaurus Core Team
+  url: https://github.com/wgao19
+  image_url: https://github.com/wgao19.png
+tags: [hola, docusaurus]
+---
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

blog/2019-05-29-long-blog-post.md

@@ -0,0 +1,44 @@
+---
+slug: long-blog-post
+title: Long Blog Post
+authors: endi
+tags: [hello, docusaurus]
+---
+
+This is the summary of a very long blog post,
+
+Use a `<!--` `truncate` `-->` comment to limit blog post size in the list view.
+
+<!--truncate-->
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
+
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

blog/2021-08-01-mdx-blog-post.mdx

@@ -0,0 +1,20 @@
+---
+slug: mdx-blog-post
+title: MDX Blog Post
+authors: [slorber]
+tags: [docusaurus]
+---
+
+Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
+
+:::tip
+
+Use the power of React to create interactive blog posts.
+
+```js
+<button onClick={() => alert('button clicked!')}>Click me!</button>
+```
+
+<button onClick={() => alert('button clicked!')}>Click me!</button>
+
+:::

blog/2021-08-26-welcome/index.md

@@ -0,0 +1,25 @@
+---
+slug: welcome
+title: Welcome
+authors: [slorber, yangshun]
+tags: [facebook, hello, docusaurus]
+---
+
+[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
+
+Simply add Markdown files (or folders) to the `blog` directory.
+
+Regular blog authors can be added to `authors.yml`.
+
+The blog post date can be extracted from filenames, such as:
+
+- `2019-05-30-welcome.md`
+- `2019-05-30-welcome/index.md`
+
+A blog post folder can be convenient to co-locate blog post images:
+
+![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)
+
+The blog supports tags as well!
+
+**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.

blog/authors.yml

@@ -0,0 +1,17 @@
+endi:
+  name: Endilie Yacop Sucipto
+  title: Maintainer of Docusaurus
+  url: https://github.com/endiliey
+  image_url: https://github.com/endiliey.png
+
+yangshun:
+  name: Yangshun Tay
+  title: Front End Engineer @ Facebook
+  url: https://github.com/yangshun
+  image_url: https://github.com/yangshun.png
+
+slorber:
+  name: Sébastien Lorber
+  title: Docusaurus maintainer
+  url: https://sebastienlorber.com
+  image_url: https://github.com/slorber.png

docs/archive/_category_.json

@@ -0,0 +1,7 @@
+{
+  "label": "Archive",
+  "position": 6,
+  "link": {
+    "type": "generated-index"
+  }
+}

docs/archive/discord-bot.md

@@ -0,0 +1,74 @@
+---
+sidebar_position: 1
+---
+
+# Discord Bot (Deprecated)
+
+## About
+
+The [Hubs Discord Bot](https://hubs.mozilla.com/discord) makes it easy to connect Hubs rooms to your Discord chat server. When a Hubs room is associated with a Discord channel, users will be assigned abilities in the Hubs room based on their Discord roles. For example, Discord owners and moderators will be able to change settings on a Hubs room and be able to moderate users in the room.
+
+![Hubs Discord bot](/img/discord-bot.jpeg)
+
+## Features
+
+- Allows you to authenticate users joining your Hubs room.
+- Saves a record of text chat and photos created in the Hubs room.
+- Posts in the Discord channel when someone joins or leaves the Hubs room.
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/5HtRJolThZ8" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
+
+## Set Up
+
+If your room is hosted on hubs.mozilla.com:
+
+1. [Click here](https://discordapp.com/oauth2/authorize?client_id=509129921826914304&permissions=536890368&scope=bot) to invite the Hubs Discord bot to your Discord server.
+2. Choose the channel(s) you want Hubs to run in or create new one(s).
+3. Give the bot appropriate permissions (see below) on these channels.
+4. Create a webhook named "Hubs" in the channels you want it to run in. (Go to the channel's Settings-->Integrations) It will use this
+   webhook to bridge chat and send Hubs status updates.
+5. Try out the bot! Type !hubs in a channel the bot is in to see some things you can do.
+
+Using Hubs Cloud? You can [add the bot to your Hubs Cloud server](./hubs-cloud-discord-bot.md).
+
+### User Permissions
+
+Your room's user permissions will inherit the permissions that their Discord role has in the channel that the bot is bound to. Specifically
+
+- To enter the room they must have "View Channel" permission
+- To be a moderator they must have "Kick Members" permission (and "View Channel").
+  - Moderators can kick and mute members in the hubs room.
+  - Moderators can also create and manipulate objects, draw and share video even if these are turned off in the room settings.
+  - Note: only discord users with verified emails can become moderators
+- To be a room owner they must have "Manage Channels" (and "Kick Members and "View Channel")
+  - Room owners are able to change the name and scene in the room, modify other room settings, and close the room.
+  - Note: only discord users with verified emails can become room owners
+- The discord permissions can set either via their discord role globally, or permissions given on the specific channel to that user/role
+
+### Bot Permissions
+
+The bot requires several permissions in order to work.
+
+- "Send messages," "Read messages," and "Embed links" are necessary in order to bridge between the Hubs room that is linked to a channel and the messages that are sent within the channel on Discord.
+- "Manage webhooks" is necessary in order for the bot to find and use a webhook for bridging chat.
+- "Manage channels" is necessary in order for the bot to set the channel topic and bridge chat. Note: We do not ask for this permission globally when you add the bot to your server, instead we recommend you grant this permission to the bot in specific groups or channels.
+
+### Commands
+
+The following features outline the current bot commands and how they can be accessed by users in the Discord server:
+
+🦆`!hubs` - Lists information about the currently linked room.
+
+🦆`!hubs create` - Creates a default Hubs room and puts its URL into the channel topic. Rooms created with `!hubs create` will inherit moderation permissions from this Discord channel and only allow Discord users in this channel to join the room.
+
+🦆`!hubs create [environment URL] [name]` - Creates a new room with the given environment and name, and puts its URL into the channel topic. Valid environment URLs include glTFs, GLBs, and Spoke scene pages.
+
+🦆`!hubs help` - Get information about how to use the Hubs bot.
+
+🦆`!hubs stats` - Shows some summary statistics about room usage.
+
+🦆`!hubs remove` - Removes the room URL from the topic and stops bridging the Discord channel with Hubs.
+
+🦆`!hubs notify set [datetime]` - Sets a one-time notification to notify @​here to join the room at some future time.
+
+🦆`!hubs notify clear` - Removes all pending notifications.

docs/archive/hubs-cloud/_category_.json

@@ -0,0 +1,7 @@
+{
+  "label": "Hubs Cloud (Deprecated)",
+  "position": 2,
+  "link": {
+    "type": "generated-index"
+  }
+}

docs/archive/hubs-cloud/adding-admins.md

@@ -0,0 +1,37 @@
+---
+sidebar_position: 9
+---
+
+# Adding Administrators
+
+Administrators for your hub have full access rights. They can:
+
+- Have access to the [Admin Console](./hubs-cloud-getting-started.md) to update system settings and app configuration.
+- [Manage the content library](./hubs-cloud-managing-content.md) and [import content](./hubs-cloud-importing-content.md).
+- Have access to the [Scene Editor](./spoke-creating-projects.md) to create and publish new scenes, regardless of settings.
+
+To assign other accounts administrative access, you need to get their account id and then assign administrator rights in the Admin Console.
+
+### Account ID Lookup
+
+Hubs Cloud does not store any personally identifying information in the database. To get another user's account ID to make them an administrator, you will need to have them follow these steps:
+
+- Log in to their account via the "Sign In" link on the homepage.
+- Navigate to a room page, or create a new room.
+- Open the developer tools for their browser. How-to for [Chrome](https://developers.google.com/web/tools/chrome-devtools) or [Firefox](https://developer.mozilla.org/en-US/docs/Tools).
+- In the Console log, near the beginning, they'll need to look for a line that looks like `Logged into account XXXXXXXXXXXXXXX` where `XXXXXXXXXXXXXXX` is a series of numbers. This their account ID.
+- It is safe for them to share their account ID, others who have their account ID will not gain access or visibility into their activity if they share it.
+
+### Granting Admin Access
+
+Once you have an account ID you'd like to grant access to, navigate to the **Accounts** section in the Admin Console:
+
+![Hubs Cloud Accounts](/img/hubs-cloud-accounts.jpeg)
+
+From there, enter the Account ID you would like to change to administrator under **Search ID** and then click Edit:
+
+![Hubs Cloud Find Account](/img/hubs-cloud-find-account.jpeg)
+
+Then set the account to **Is admin** and click **Save**:
+
+![Hubs Cloud Select Admin](/img/hubs-cloud-select-admin.jpeg)