feat: internal documentation building (#154)

Author: MihalyToth20

.changeset/afraid-seals-crash.md

@@ -0,0 +1,5 @@
+---
+"@calycode/cli": patch
+---
+
+chore: remove tailwind cdn from docs [#131](https://github.com/calycode/xano-tools/issues/131)

.changeset/upset-teeth-fetch.md

@@ -0,0 +1,7 @@
+---
+'@calycode/core': minor
+'@calycode/cli': minor
+---
+
+feat: new command `generate-internal-docs` that creates a directory of docsfiy powered browseable documentation for your workspace rendered from markdown on client (Docsify)
+chore: update docs to include the new command

.changeset/wise-yaks-scream.md

@@ -0,0 +1,6 @@
+---
+"@calycode/core": patch
+"@calycode/cli": patch
+---
+
+fix: fixing multiple issues with the generated markdown of the workspace, that was causing broken links

docs/commands/export-backup.md

@@ -24,9 +24,9 @@ Usage: xano export-backup [options]
 Backup Xano Workspace via Metadata API
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance
-                           configuration. The value provided at the setup
-                           command.
+  --instance <instance>    The instance name. This is used to fetch the
+                           instance configuration. The value provided at the
+                           setup command.
   --workspace <workspace>  The workspace name. This is used to fetch the
                            workspace configuration. Same as on Xano interface.
   --branch <branch>        The branch name. This is used to select the branch

docs/commands/generate-code.md

@@ -32,13 +32,13 @@ $ xano generate-code --help
 Usage: xano generate-code [options]
 
 Create a library based on the OpenAPI specification. If the openapi
-specification has not yet been generated, this will generate that as well as the
-first step.
+specification has not yet been generated, this will generate that as well as
+the first step.
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance
-                           configuration. The value provided at the setup
-                           command.
+  --instance <instance>    The instance name. This is used to fetch the
+                           instance configuration. The value provided at the
+                           setup command.
   --workspace <workspace>  The workspace name. This is used to fetch the
                            workspace configuration. Same as on Xano interface.
   --branch <branch>        The branch name. This is used to select the branch

docs/commands/generate-oas.md

@@ -31,9 +31,9 @@ Scalar API Reference. + this command brings the Swagger docs to OAS 3.1+
 version.
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance
-                           configuration. The value provided at the setup
-                           command.
+  --instance <instance>    The instance name. This is used to fetch the
+                           instance configuration. The value provided at the
+                           setup command.
   --workspace <workspace>  The workspace name. This is used to fetch the
                            workspace configuration. Same as on Xano interface.
   --branch <branch>        The branch name. This is used to select the branch

docs/commands/generate-repo.md

@@ -32,13 +32,14 @@ API to offer the full details. However that is enriched with the Xanoscripts
 after Xano 2.0 release.
 
 Options:
-  -I, --input <file>       Workspace yaml file from a local source, if present.
+  -I, --input <file>       Workspace yaml file from a local source, if
+                           present.
   -O, --output <dir>       Output directory (overrides default config), useful
                            when ran from a CI/CD pipeline and want to ensure
                            consistent output location.
-  --instance <instance>    The instance name. This is used to fetch the instance
-                           configuration. The value provided at the setup
-                           command.
+  --instance <instance>    The instance name. This is used to fetch the
+                           instance configuration. The value provided at the
+                           setup command.
   --workspace <workspace>  The workspace name. This is used to fetch the
                            workspace configuration. Same as on Xano interface.
   --branch <branch>        The branch name. This is used to select the branch

docs/commands/generate-xs-repo.md

@@ -21,15 +21,15 @@ $ xano generate-xs-repo [options]
 $ xano generate-xs-repo --help
 Usage: xano generate-xs-repo [options]
 
-Process Xano workspace into repo structure. Supports table, function and apis as
-of know. Xano VSCode extension is the preferred solution over this command.
+Process Xano workspace into repo structure. Supports table, function and apis
+as of know. Xano VSCode extension is the preferred solution over this command.
 Outputs of this process are also included in the default repo generation
 command.
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance
-                           configuration. The value provided at the setup
-                           command.
+  --instance <instance>    The instance name. This is used to fetch the
+                           instance configuration. The value provided at the
+                           setup command.
   --workspace <workspace>  The workspace name. This is used to fetch the
                            workspace configuration. Same as on Xano interface.
   --branch <branch>        The branch name. This is used to select the branch

docs/commands/registry-add.md

@@ -21,17 +21,17 @@ $ xano registry-add [options]
 $ xano registry-add --help
 Usage: xano registry-add [options] <components...>
 
-Add a prebuilt component to the current Xano context, essentially by pushing an
-item from the registry to the Xano instance.
+Add a prebuilt component to the current Xano context, essentially by pushing
+an item from the registry to the Xano instance.
 
 Arguments:
   components               Space delimited list of components to add to your
                            Xano instance.
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance
-                           configuration. The value provided at the setup
-                           command.
+  --instance <instance>    The instance name. This is used to fetch the
+                           instance configuration. The value provided at the
+                           setup command.
   --workspace <workspace>  The workspace name. This is used to fetch the
                            workspace configuration. Same as on Xano interface.
   --branch <branch>        The branch name. This is used to select the branch

docs/commands/registry-scaffold.md

@@ -18,14 +18,15 @@ $ xano registry-scaffold --help
 Usage: xano registry-scaffold [options]
 
 Scaffold a Xano registry folder with a sample component. Xano registry can be
-used to share and reuse prebuilt components. In the registry you have to follow
-the [registry](https://calycode.com/schemas/registry/registry.json) and
+used to share and reuse prebuilt components. In the registry you have to
+follow the [registry](https://calycode.com/schemas/registry/registry.json) and
 [registry item](https://calycode.com/schemas/registry/registry-item.json)
 schemas.
 
 Options:
   --output <path>        Local output path for the registry
   --instance <instance>  The instance name. This is used to fetch the instance
-                         configuration. The value provided at the setup command.
+                         configuration. The value provided at the setup
+                         command.
   -h, --help             display help for command
 ```