gruntwork-io
diff --git a/‎.mise.toml
Lines changed: 3 additions & 0 deletions b/‎.mise.toml
Lines changed: 3 additions & 0 deletions
diff --git a/‎.yarnrc.yml
Lines changed: 1 addition & 0 deletions b/‎.yarnrc.yml
Lines changed: 1 addition & 0 deletions
diff --git a/‎README.md
Lines changed: 21 additions & 66 deletions b/‎README.md
Lines changed: 21 additions & 66 deletions
diff --git a/‎_docs-sources/courses.mdx
Lines changed: 0 additions & 57 deletions b/‎_docs-sources/courses.mdx
Lines changed: 0 additions & 57 deletions
diff --git a/‎_docs-sources/developer-portal/link-github-id.md
Lines changed: 0 additions & 27 deletions b/‎_docs-sources/developer-portal/link-github-id.md
Lines changed: 0 additions & 27 deletions
diff --git a/‎_docs-sources/ecs-deploy-runner/how-it-works/index.md
Lines changed: 0 additions & 84 deletions b/‎_docs-sources/ecs-deploy-runner/how-it-works/index.md
Lines changed: 0 additions & 84 deletions
@@ -0,0 +1,3 @@
+[tools]
+yarn = "1.22.19"
+
@@ -0,0 +1 @@
+nodeLinker: node-modules
@@ -1,30 +1,21 @@
 # Docs Site
 
-This website is built using [Docusaurus 2](https://docusaurus.io/), a modern
+This website is built using [Docusaurus 3](https://docusaurus.io/), a modern
 static website generator.
 
 ## Overview
 
 ### Docs Sourcer
 
-All of the content that we see on the docs site is rendered to the top level
-`docs/` folder by the
-[docs-sourcer](https://github.com/gruntwork-io/docs-sourcer). `docs-sourcer` is
-a process which can pull content from our GitHub repos as well as pre-process
-the MarkDown files which comprise the docs site's manually authored content (in
-`_docs-sources/`). At present, `docs-sourcer` isn't augmenting the content all
-that much, but in the future, the idea is that `docs-sourcer` will be able to
-pull in tagged content from other files, located in other GitHub repos, pull in
-images and auto-correct links. This will allow content creators to have more
-features when authoring content.
-
-### Content creation
-
-All manually created MarkDown source content lives in the `_docs-sources/`
-folder. The top level `docs/` folder contains the _generated_ output that
-results after the `docs-sourcer` processes the `_docs-sources/` directory.
-Grunts should **never edit any of the MarkDown files in the `docs/` folder
-directly**. We should always be editing the content in `_docs-sources/`.
+The vast majority of content in the `docs` folder is maintained by developers and not automation.
+There are, however, some types of docs that are maintained by a tool called `docs-sourcer`. You can
+identify those files by the `##DOCS-SOURCER-START` tag at the end of the file. In general
+this is content that is pulled from external sources, such as change logs, release notes and
+GitHub discussions.
+
+Docs Sourcer is generally run in CI or via webhooks and doesn't have to be run locally. If, however, you do need
+to run it locally you will need access to various secrets.  These secrets live in 1password under a secure note called
+"docs sourcer .env file".
 
 ## Installing dependencies
 
@@ -39,23 +30,7 @@ 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. This
-command also begins watching the `_docs-sources` directory for file changes. If
-you edit a file in `_docs-sources/` then the `docs-sourcer` will automatically
-re-run to regenerate the output files. Docusaurus will then hot-reload that
-content so that to the end user, they have "live reloading" while authoring.
-
-### Committing changes
-
-While authoring local content, you will exclusively be making your changes in
-the `_docs-sources/` folder. The `docs-sourcer` will then pre-process and
-generate output for you. To get your content _published_ you will need to commit
-**both** the "source" files in `_docs-sources/` as well as the generated content
-in the top level `docs/` folder.
-
-Generated content should be up to date if you are previewing locally while
-editing but you may wish to manually regenerate the output (see section below)
-to ensure it is totally up to date.
+Most changes are reflected live without having to restart the server.
 
 ### Running a production build locally
 
@@ -66,41 +41,21 @@ yarn build && yarn serve
 This will create and serve a production build. This can be used to verify the
 expected behaviors in a production environment and view the Google analytics.
 
-### Manually generating docs output
+# Customizable Values
 
-It's possible to manually regenerate output content from the sources in
-`_docs-sources/`:
-
-```sh
-yarn regenerate:local
-```
+It's often useful to present the user with the ability to edit a variable inline to documentation.  For example, you're about to present a block of code that references an S3 bucket name.  Rather than put in a fixed placeholder like <BUCKET_NAME> which the user has to manually edit, you can use our CustomizableValue component.  This component will render as a clickable text field which, when clicked, switches to an input. Any inputted characters will be auto-propegated to all other instances of the component that share the same ID.  You can use this component both as a React component and inline to MDX code blocks.  We have swizzled the CodeBlock components to make this possible.
 
-This command can be run at any time, regardless of whether `yarn start` is
-currently running.
+Example usage:
 
-### Generating sidebars for guides
-
-We utilize explicit sidebar definitions for most of our docs content. Doing so enables authors to easily provide titles
-for all category labels, as well as define the relative ordering of pages in a maintainable way. Long-form docs with
-many sections receive a dedicated sidebar to provide a focused reading experience (e.g. /guides/build-it-yourself/\*).
-
-A tool is provided to automatically generate sidebars for any new guide. To
-run it, specify the path to the directory you wish to create a sidebar for in
-either `_docs-sources/` or the output `docs/` path, relative to your current
-working directory.
-
-```sh
-yarn sidebar docs/guides/build-it-yourself/my-new-guide/
+As a component:
+```js
+<CustomizableValue id="BUCKET_NAME">
 ```
 
-Once generated, you're free to adjust the names of each category, which only
-appear in the sidebar itself. You may also reorder any of the linked pages
-within each section, which will be reflected in the rendered output.
-
-See the usage instructions with `yarn sidebar --help` to learn how to add a
-back button or specify an output file. The resulting file should be placed in
-the `sidebars/` directory. You'll also need to require this file in
-`sidebars.js`, and then re-run `yarn start` to see your changes.
+Using the \$\$ID\$\$ syntax inside a code block
+```md
+This is inside a code block, $$BUCKET_NAME$$
+```
 
 
 # Automated Pull Request Flows