Add submodule (as file copy)

.github/workflows/main.yml

@@ -11,7 +11,9 @@ jobs:
     if: github.event_name != 'push'
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v1
+      - uses: actions/checkout@v2
+        with:
+          submodules: true
       - uses: actions/setup-node@v1
         with:
           node-version: '16.x'

.gitignore

@@ -3,3 +3,6 @@ yarn.lock
 .idea
 .docusaurus
 node_modules
+
+# These files are copied from the sqrl submodule
+docs/sqrl/*

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "sqrl"]
+	path = sqrl
+	url = git@github.com:DataSQRL/sqrl.git

docs/getting-started/concepts/datasqrl.md

@@ -26,7 +26,7 @@ DataSQRL compiles the SQL script and output specification into a data pipeline t
 
 DataSQRL has a pluggable engine architecture which allows it to support various stream processors, databases, data warehouses, data streams, and API servers. Feel free to contribute your favorite data technology as a DataSQRL engine to the open-source, wink wink.
 
-DataSQRL can generate data pipelines with multiple topologies. Take a look at the [types of data products](/docs/reference/concepts/data-product#types) that DataSQRL can build. You can further customize those pipeline topologies in the DataSQRL [package configuration](/docs/reference/sqrl/datasqrl-spec/) which defines the data technologies at each stage of the resulting data pipeline. 
+DataSQRL can generate data pipelines with multiple topologies. Take a look at the [types of data products](/docs/reference/concepts/data-product#types) that DataSQRL can build. You can further customize those pipeline topologies in the DataSQRL [package configuration](/docs/sqrl/datasqrl-spec) which defines the data technologies at each stage of the resulting data pipeline. 
 
 DataSQRL compiles executables for each engine in the pipeline which can be deployed on the data technologies and cloud services you already use.
 In addition, DataSQRL provides development tooling that makes it easy to run and test data pipelines locally to speed up the development cycle.

docs/getting-started/concepts/when-datasqrl.md

@@ -65,7 +65,7 @@ That said, if you have multiple orange data products, DataSQRL is still worth it
 
 DataSQRL is a compiler that generates data pipelines using proven data technologies like Apache Flink, Kafka, or Postgres. DataSQRL has a pluggable engine architecture that supports various types of databases, stream processors, and API servers. Hence, the other thing to consider is whether DataSQRL supports the data technologies you are already using or plan to use in your data pipelines.
 
-Take a look at the [engines documentation](/docs/reference/sqrl/datasqrl-spec#engines) to see whether your favorite data technologies are supported. And if not, [reach out to us](/contact) to see if and when DataSQRL will support the data technology of your choice. DataSQRL is still young and we are continuously expanding support.
+Take a look at the [engines documentation](/docs/sqrl/datasqrl-spec#engines) to see whether your favorite data technologies are supported. And if not, [reach out to us](/contact) to see if and when DataSQRL will support the data technology of your choice. DataSQRL is still young and we are continuously expanding support.
 
 ### Expressivity
 

docs/getting-started/intro/deploy.md

@@ -96,7 +96,7 @@
 [//]: # (The package configuration specifies what engines DataSQRL compiles to. DataSQRL calls the data technologies that execute the components of a data pipeline "**engines**". For example, DataSQRL supports [Apache Flink](https://flink.apache.org/) as a stream engine, [Apache Kafka](https://kafka.apache.org/) as a log engine, [Postgres](https://www.postgresql.org/) as a database engine, and [Vert.x](https://vertx.io/) as a server engine.)
 
 [//]: # ()
-[//]: # (Check out [all the engines](/docs/reference/operations/engines/overview) that DataSQRL supports and how to configure them in the [package configuration](/docs/reference/sqrl/datasqrl-spec/#packagejson). )
+[//]: # (Check out [all the engines](/docs/reference/operations/engines/overview) that DataSQRL supports and how to configure them in the [package configuration](/sqrl/datasqrl-spec/#packagejson). )
 
 [//]: # ()
 [//]: # (That concludes our introductory tutorial! Great job and enjoy building with data(sqrl)!)

docs/intro.md

@@ -111,7 +111,7 @@ You can also learn more about [DataSQRL](../getting-started/concepts/datasqrl),
 
 - Jump into our [Getting Started Guide](../getting-started)  for a quick introduction to the basics of DataSQRL.
 - Explore the Interactive Tutorial and [Quickstart](../getting-started/quickstart)  to see DataSQRL in action.
-- Check out the [reference documentation](../reference/sqrl/datasqrl-spec) covers all aspects of DataSQRL in detail. If you want more information on how to use DataSQRL or are looking for comprehensive documentation, this is your place to go.
+- Check out the [reference documentation](/docs/sqrl/datasqrl-spec) covers all aspects of DataSQRL in detail. If you want more information on how to use DataSQRL or are looking for comprehensive documentation, this is your place to go.
 - Learn more about advanced features and customization in our How-to Guides.
 
 ## Join the DataSQRL community

docs/reference/sqrl/bak.md

@@ -151,7 +151,7 @@
 [//]: # (### Dependency)
 
 [//]: # ()
-[//]: # (Dependencies are declared in the [package configuration](/docs/reference/sqrl/datasqrl-spec/#packagejson#dependency). Dependencies can point to local package folders or be downloaded from a [repository](../../operations/repository) at compile time.)
+[//]: # (Dependencies are declared in the [package configuration](/sqrl/datasqrl-spec/#packagejson#dependency). Dependencies can point to local package folders or be downloaded from a [repository](../../operations/repository) at compile time.)
 
 [//]: # ()
 [//]: # (By default, DataSQRL looks up any missing packages in the [repository](https://dev.datasqrl.com). A package is missing if it is not declared as dependencies and cannot be resolved locally. If the missing package can be located in the repository, a dependency on the most recent version of that package is added to the package configuration.)