Create monorepo with main project, remark plugin and gatsby remark plugin.

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/beige-balloons-protect.md

@@ -0,0 +1,8 @@
+---
+'@nmbl/code-snippets': major
+'@nmbl/code-snippets-gatsby-remark-plugin': major
+'@nmbl/code-snippets-remark-plugin': major
+'@nmbl/code-snippets-website': major
+---
+
+Switch to default exports since they just work in Remark world.

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@1.7.0/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

.changeset/new-bugs-buy.md

@@ -0,0 +1,8 @@
+---
+'@nmbl/code-snippets': major
+'@nmbl/code-snippets-gatsby-remark-plugin': major
+'@nmbl/code-snippets-remark-plugin': major
+'@nmbl/code-snippets-website': major
+---
+
+First iteration of code snippets along with docs website and remark / gatsby plugins.

.changeset/pre.json

@@ -0,0 +1,14 @@
+{
+  "mode": "pre",
+  "tag": "beta",
+  "initialVersions": {
+    "@nmbl/code-snippets": "0.0.1",
+    "@nmbl/code-snippets-gatsby-remark-plugin": "0.0.1",
+    "@nmbl/code-snippets-remark-plugin": "0.0.1",
+    "@nmbl/code-snippets-website": "0.0.1"
+  },
+  "changesets": [
+    "beige-balloons-protect",
+    "new-bugs-buy"
+  ]
+}

.gitignore

@@ -1,2 +1,3 @@
 node_modules/
-dist/
+dist/
+.generated/

.prettierignore

@@ -0,0 +1 @@
+fixtures/

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+  "recommendations": [
+    "csstools.postcss",
+    "bradlc.vscode-tailwindcss",
+    "Orta.vscode-jest"
+  ]
+}

.vscode/launch.json

@@ -0,0 +1,48 @@
+{
+  "configurations": [
+    {
+      "name": "Attach by Process ID",
+      "processId": "${command:PickProcess}",
+      "request": "attach",
+      "skipFiles": ["<node_internals>/**"],
+      "type": "pwa-node"
+    },
+    {
+      "command": "npm run build",
+      "name": "Build All Packages",
+      "request": "launch",
+      "type": "node-terminal",
+      "autoAttachChildProcesses": false
+    },
+    {
+      "command": "npm run start:website",
+      "name": "Develop Website",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "command": "npm run serve",
+      "name": "Serve Built Website",
+      "request": "launch",
+      "type": "node-terminal"
+    },
+    {
+      "type": "node",
+      "name": "vscode-jest-tests",
+      "request": "launch",
+      "console": "integratedTerminal",
+      "internalConsoleOptions": "neverOpen",
+      "disableOptimisticBPs": true,
+      "cwd": "${workspaceFolder}",
+      "runtimeExecutable": "yarn",
+      "args": [
+        "run",
+        "test",
+        "--runInBand",
+        // when filtering, every package not matching will have no tests
+        "--passWithNoTests",
+        "--testTimeout=9999"
+      ]
+    }
+  ]
+}

.vscode/settings.json

@@ -1,3 +1,4 @@
 {
-  "editor.formatOnSave": true
+  "editor.formatOnSave": true,
+  "jest.jestCommandLine": "yarn run test:vscode"
 }

.vscode/tasks.json

@@ -3,11 +3,28 @@
   "tasks": [
     {
       "type": "typescript",
-      "tsconfig": "./test/fixtures/tsconfig.json",
+      "tsconfig": "./helpers/tsconfig.watch.json",
       "option": "watch",
       "problemMatcher": ["$tsc-watch"],
       "group": "none",
-      "label": "tsc: watch - test/fixtures/tsconfig.json",
+      "label": "tsc: watch - helpers",
+      "options": {
+        "shell": {
+          "executable": "cmd.exe",
+          "args": ["/d", "/c"]
+        }
+      },
+      "runOptions": {
+        "runOn": "folderOpen"
+      }
+    },
+    {
+      "type": "typescript",
+      "tsconfig": "./fixtures/tsconfig.watch.json",
+      "option": "watch",
+      "problemMatcher": ["$tsc-watch"],
+      "group": "none",
+      "label": "tsc: watch - fixtures",
       "options": {
         "shell": {
           "executable": "cmd.exe",

README.md

@@ -0,0 +1,10 @@
+---
+slug: '/'
+title: 'Nmbl Code Snippets - Home'
+---
+
+# Nmbl Code Snippets
+
+## Metadocumenting voraciously
+
+Try reading the [docs](docs).

docs/index.md

@@ -0,0 +1,71 @@
+---
+slug: '/docs'
+---
+
+# Welcome to Nmbl Code Snippets
+
+What is a code snippet? Well, it's a snippet of code, but that's not all.
+
+> Code snippets should be testable, tested and maintained.
+
+Shots fired. That's right, code snippets should be living, breathing... code. Real code. Library owners, contributors, and evangelists write hundreds of examples, deploy them to the docs sites, chat rooms, sandboxes and issue trackers of the world, and forget about them. Then, a developer like me comes along, tries out 100 examples, and they are all broken. WHY!
+
+Because code snippets aren't testable, tested, or maintained. *But they should be! HOW?!*
+
+This project is how. I'm writing in a markdown document right now, and I'm about to write a code snippet. Not just any code snippet, but a code snippet which is integrated into the build process of this very project. If the code doesn't compile, these snippets never make it to production, and you *don't read this documentation*. Sound too good to be true? If you're reading this, think again!
+
+## The Header snippet
+
+I've created a snippet surrounding the header of the docs website for this project. The documentation of this snippet can't be wrong, because if it is, the build will fail, and the documentation will never be deployed. If I ever remove the header of the website, `@nmbl/code-snippets` will throw an error, and again the documentation will never be deployed.
+
+### The Source ([with snippets preserved](preserving-snippets)):
+
+[comment]: # "@snippet:start preserve-snippets"
+
+```tsx file=./src/header/header.tsx preserve-snippets
+import * as React from 'react';
+
+export const Header = () => (
+  // @snippet:start header
+  <header className="main-header">
+    <h1>Nmbl Code Snippets</h1>
+  </header>
+  // @snippet:end header
+);
+```
+
+[comment]: # "@snippet:end preserve-snippets"
+
+### The Markdown:
+
+````md
+```tsx file=./src/header/header.tsx snippet=header
+
+```
+````
+
+### The Output:
+
+```tsx file=./src/header/header.tsx snippet=header
+  <header className="main-header">
+    <h1>Nmbl Code Snippets</h1>
+  </header>
+```
+
+If you're reading this on an actual website (not the source code, silly), and there is output above, then I have proven my point. Convinced? Here's some further reading:
+
+*   [Installing](installing)
+*   [Preserving Snippets](preserving-snippets)
+
+Not convinced? That's ok, too. Here's a llama:
+
+> ```plaintext
+> \\
+> l'>
+> ll
+> llama~
+> || ||
+> '' ''
+> ```
+>
+> Source: https://ascii.co.uk/art/llama