Make config-based docs accessible through direct link

docs/connector-development/config-based/overview.md

@@ -3,7 +3,7 @@
 :warning: This framework is in alpha stage. Support is not in production and is available only to select users. :warning:
 
 The goal of this document is to give enough technical specifics to understand how config-based connectors work.
-When you're ready to start building a connector, you can start with [the tutorial](../../../config-based/tutorial/0-getting-started.md) or dive into the [reference documentation](https://airbyte-cdk.readthedocs.io/en/latest/api/airbyte_cdk.sources.declarative.html)
+When you're ready to start building a connector, you can start with [the tutorial](./tutorial/0-getting-started.md) or dive into the [reference documentation](https://airbyte-cdk.readthedocs.io/en/latest/api/airbyte_cdk.sources.declarative.html)
 
 ## Overview
 

docs/connector-development/config-based/tutorial/5-incremental-reads.md

@@ -90,7 +90,7 @@ The connector will now always read data for the start date, which is not exactly
 Instead, we would like to iterate over all the dates between the start_date and today and read data for each day.
 
 We can do this by adding a `DatetimeStreamSlicer` to the connector definition, and update the `path` to point to the stream_slice's `start_date`:
-More details on the stream slicers can be found [here](./link-to-stream-slicers.md) <FIXME: need to fix links>
+More details on the stream slicers can be found [here](../stream-slicers.md) <FIXME: need to fix links>
 
 Let's first define a stream slicer at the top level of the connector definition:
 
@@ -298,4 +298,4 @@ Next, we'll run the [Source Acceptance Tests suite to ensure the connector invar
 
 - [Incremental reads](../../cdk-python/incremental-stream.md)
 - [Stream slicers](../stream-slicers.md)
-- [Stream slices](../cdk-python/stream-slices.md)
+- [Stream slices](../../cdk-python/stream-slices.md)

docs/connector-development/config-based/tutorial/6-testing.md

@@ -39,7 +39,7 @@ $ python -m pytest integration_tests -p integration_tests.acceptance
 
 Next, we'll add the connector to the [Airbyte platform](https://docs.airbyte.com/connector-development/tutorials/cdk-tutorial-python-http/use-connector-in-airbyte).
 
-See your [Contributiong guide]() on how to get started releasing your connector.
+See your [Contributiong guide](../../../contributing-to-airbyte/README.md) on how to get started releasing your connector.
 
 ## Read more:
 

docs/connector-development/config-based/yaml-structure.md

@@ -137,7 +137,7 @@ In this example, outer.inner.k2 will evaluate to "MyKey is MyValue"
 Strings can contain references to previously defined values.
 The parser will dereference these values to produce a complete ConnectionDefinition
 
-References can be defined using a *ref(<arg>) string.
+References can be defined using a "*ref({arg})" string.
 
 ```yaml
 key: 1234

docusaurus/docusaurus.config.js

@@ -62,7 +62,6 @@ const config = {
                     sidebarPath: require.resolve('./sidebars.js'),
                     editUrl: 'https://github.com/airbytehq/airbyte/blob/master/docs',
                     path: '../docs',
-                    exclude: ['**/connector-development/config-based/**']
                 },
                 blog: false,
                 theme: {