Reorganized sources

Author: maheshwarip

src/content/docs/pipelines/build-with-pipelines/output-settings.mdx

@@ -1,11 +1,11 @@
 ---
-title: Customize output settings
+title: Configure output settings
 pcx_content_type: how-to
 sidebar:
   order: 3
 head:
   - tag: title
-    content: Customize output settings
+    content: Configure output settings
 ---
 
 import { Render, PackageManagers } from "~/components";

src/content/docs/pipelines/build-with-pipelines/http.mdx renamed to src/content/docs/pipelines/build-with-pipelines/sources/http.mdx

@@ -1,16 +1,16 @@
 ---
-title: Configure HTTP Endpoint
+title: Configure HTTP endpoint
 pcx_content_type: concept
 sidebar:
   order: 1
 head:
   - tag: title
-    content: Configure HTTP Endpoint
+    content: Configure HTTP endpoint
 ---
 
 import { Render, PackageManagers } from "~/components";
 
-Pipelines support data ingestion over HTTP. When you create a new pipeline, you will receive a globally scalable ingestion endpoint. To ingest data, make HTTP POST requests to the endpoint.
+Pipelines support data ingestion over HTTP. When you create a new pipeline using the default settings you will receive a globally scalable ingestion endpoint. To ingest data, make HTTP POST requests to the endpoint.
 
 ```sh
 $ npx wrangler@latest pipelines create my-clickstream-pipeline --r2-bucket my-bucket
@@ -56,15 +56,6 @@ curl -X POST https://<PIPELINE-ID>.pipelines.cloudflare.com \
 {"success":true,"result":{"committed":3}}
 ```
 
-## Turning HTTP ingestion off
-By default, ingestion via HTTP is turned on. You can turn it off by excluding it from the list of sources by using `--sources` when creating or updating a pipeline.
-
-```sh
-$ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --sources worker
-```
-
-Ingestion URLs are tied to your pipeline ID. Turning HTTP off, and then turning it back on, will not change the URL.
-
 ## Authentication
 You can secure your HTTP ingestion endpoint using Cloudflare API tokens. By default, authentication is turned off. To configure authentication, use the `--require-http-auth` flag while creating or updating a pipeline.
 

src/content/docs/pipelines/build-with-pipelines/sources/index.mdx

@@ -0,0 +1,26 @@
+---
+title: Sources
+pcx_content_type: concept
+sidebar:
+  order: 1
+  group:
+    hideIndex: false
+---
+
+Pipelines supports the following sources:
+* [HTTP Clients](/pipelines/build-with-pipelines/sources/http), with optional authentication and CORS settings
+* [Cloudflare Workers](/workers/), using the [Pipelines Workers API](/pipelines/build-with-pipelines/sources/workers-apis)
+
+Multiple sources can be active on a single pipeline simultaneously. For example, you can create a pipeline which accepts data from Workers and via HTTP. There is no limit to the number of source clients. Multiple workers can be configured to send data to the same pipeline.
+
+## Configuring allowed sources
+By default, ingestion via HTTP and from Workers is turned on. You can configure the allowed sources by using the `--source` flag while creating or updating a pipeline.
+
+For example, to create a pipeline which only accepts data via a Worker, you can run this command:
+```sh
+$ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --source worker
+```
+
+:::note
+HTTP ingestion URLs are tied to your pipeline ID. Turning HTTP off, and then turning it back on, will not change the URL.
+:::

src/content/docs/pipelines/build-with-pipelines/workers-apis.mdx renamed to src/content/docs/pipelines/build-with-pipelines/sources/workers-apis.mdx

@@ -54,13 +54,6 @@ export default {
 ## Accepted data formats
 Pipelines accept arrays of valid JSON objects. You can send multiple objects in a single request, provided the total data volume is within the [documented limits](/pipelines/platform/limits). Sending data in a different format will result in an error.
 
-## Turning ingestion via a Worker off
-By default, ingestion via a Worker is turned on. You can turn it off by excluding it from the list of sources, by using `--sources` when creating or updating a pipeline.
-
-```sh
-$ npx wrangler pipelines create [PIPELINE-NAME] --r2-bucket [R2-BUCKET-NAME] --sources http
-```
-
 ## Workers API
 ### `Pipeline`
 A binding which allows a Worker to send messages to a Pipeline.

src/content/docs/pipelines/concepts/how-pipelines-work.mdx

@@ -13,8 +13,8 @@ Cloudflare Pipelines let you ingest data from a source and deliver to a sink. It
 
 ### Sources
 Pipelines supports the following sources:
-* [HTTP Clients](/pipelines/build-with-pipelines/http), with optional authentication and CORS settings
-* [Cloudflare Workers](/workers/), using the [Pipelines Workers API](/pipelines/build-with-pipelines/workers-apis)
+* [HTTP Clients](/pipelines/build-with-pipelines/sources/http), with optional authentication and CORS settings
+* [Cloudflare Workers](/workers/), using the [Pipelines Workers API](/pipelines/build-with-pipelines/sources/workers-apis)
 
 Multiple sources can be active on a single pipeline simultaneously. For example, you can create a pipeline which accepts data from Workers and via HTTP. Multiple workers can be configured to send data to the same pipeline. There is no limit to the number of source clients.
 

src/content/docs/pipelines/getting-started.mdx

@@ -133,7 +133,7 @@ Open the [R2 dashboard](https://dash.cloudflare.com/?to=/:account/r2/overview),
 
 ## Next steps
 
-* Learn about how to [setup authentication, or CORS settings](/pipelines/build-with-pipelines/http), on your HTTP endpoint.
-* Send data to your Pipeline from a Cloudflare Worker using the [Workers API documentation](/pipelines/build-with-pipelines/workers-apis).
+* Learn about how to [setup authentication, or CORS settings](/pipelines/build-with-pipelines/sources/http), on your HTTP endpoint.
+* Send data to your Pipeline from a Cloudflare Worker using the [Workers API documentation](/pipelines/build-with-pipelines/sources/workers-apis).
 
 If you have any feature requests or notice any bugs, share your feedback directly with the Cloudflare team by joining the [Cloudflare Developers community on Discord](https://discord.cloudflare.com).

src/content/docs/pipelines/index.mdx

@@ -77,11 +77,11 @@ While in beta, you will not be billed for Pipelines usage. You will be billed on
 ***
 ## Features
 
-<Feature header="HTTP as a source" href="/pipelines/build-with-pipelines/http/">
+<Feature header="HTTP as a source" href="/pipelines/build-with-pipelines/sources/http">
 Each pipeline generates a globally scalable HTTP endpoint, which supports authentication and CORS settings.
 </Feature>
 
-<Feature header="Workers API" href="/pipelines/build-with-pipelines/workers-apis/">
+<Feature header="Workers API" href="/pipelines/build-with-pipelines/sources/workers-apis/">
 Send data to a pipeline directly from a Cloudflare Worker.
 </Feature>
 

src/content/docs/pipelines/tutorials/send-data-from-client/index.mdx

@@ -380,7 +380,7 @@ By default, the HTTP ingestion endpoint for your pipeline does not allow cross-o
 npx wrangler pipelines update clickstream-pipeline-client --cors-origins http://localhost:8787
 ```
 
-Now when you run the development server locally, and open the website in a browser, clickstream data will be successfully sent to the pipeline. You can learn more about the CORS settings in the [Specifying CORS settings](/pipelines/build-with-pipelines/http/#specifying-cors-settings) documentation.
+Now when you run the development server locally, and open the website in a browser, clickstream data will be successfully sent to the pipeline. You can learn more about the CORS settings in the [Specifying CORS settings](/pipelines/build-with-pipelines/sources/http/#specifying-cors-settings) documentation.
 
 ## 8. Deploy the application