Initial structure

Author: rcastley

content/en/conf/1-extensions.md

@@ -0,0 +1,22 @@
+---
+title: OpenTelemetry Collector Extensions
+linkTitle: 1. Extensions
+weight: 1
+---
+
+Extensions are available primarily for tasks that do not involve processing telemetry data. Examples of extensions include health monitoring, service discovery, and data forwarding. Extensions are optional.
+
+```yaml
+extensions:
+  health_check:
+  pprof:
+    endpoint: 0.0.0.0:1777
+  zpages:
+    endpoint: 0.0.0.0:55679
+```
+
+## Health Check
+
+## Performance Profiler
+
+## zPages

content/en/conf/2-receivers.md

@@ -0,0 +1,7 @@
+---
+title: OpenTelemetry Collector Receivers
+linkTitle: 1. Receivers
+weight: 2
+---
+
+A receiver, which can be push or pull based, is how data gets into the Collector. Receivers may support one or more data sources.

content/en/conf/3-processors.md

@@ -0,0 +1,7 @@
+---
+title: OpenTelemetry Collector Processors
+linkTitle: 1. Processors
+weight: 3
+---
+
+Processors are run on data between being received and being exported. Processors are optional though some are recommended.

content/en/conf/4-exporters.md

@@ -0,0 +1,7 @@
+---
+title: OpenTelemetry Collector Exporters
+linkTitle: 1. Exporters
+weight: 4
+---
+
+An exporter, which can be push or pull based, is how you send data to one or more backends/destinations. Exporters may support one or more data sources.