Rename ./specification to ./docs (#469)

* Rename ./specification to ./docs

* Add Hugo front matter, and some README copyedits

README.md

@@ -2,7 +2,7 @@
 
 [![Build Check](https://github.com/open-telemetry/opentelemetry-proto/workflows/Build%20Check/badge.svg?branch=main)](https://github.com/open-telemetry/opentelemetry-proto/actions?query=workflow%3A%22Build+Check%22+branch%3Amain)
 
-This repository contains the [OTLP protocol specification](specification/otlp.md)
+This repository contains the [OTLP protocol specification](docs/specification.md)
 and the corresponding Language Independent Interface Types ([.proto files](opentelemetry/proto)).
 
 ## Language Independent Interface Types
@@ -56,7 +56,7 @@ Components marked `Stable` provide the following guarantees:
 - Service names and service package names will not change.
 - Service method names will not change. [from 1.0.0]
 - Service method parameter names will not change. [from 1.0.0]
-- Service method parameter types and return types will not change. [from 1.0.0] 
+- Service method parameter types and return types will not change. [from 1.0.0]
 - Service method kind (unary vs streaming) will not change.
 - Names of messages and enums will not change. [from 1.0.0]
 - Numbers assigned to enum choices will not change.

docs/README.md

@@ -0,0 +1,16 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: OTLP
+aliases:
+  - /docs/reference/specification/protocol
+  - /docs/specs/otel/protocol
+spelling: cSpell:ignore otel OTLP
+--->
+
+# OpenTelemetry Protocol (OTLP)
+
+This is the specification of the OpenTelemetry Protocol (OTLP).
+
+- [Design Goals](design-goals.md)
+- [Requirements](requirements.md)
+- [Specification](specification.md)
+- [SDK Exporter](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md)

docs/design-goals.md

@@ -1,3 +1,11 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: Design goals
+aliases:
+  - /docs/reference/specification/protocol/design-goals
+  - /docs/specs/otel/protocol/design-goals
+spelling: cSpell:ignore backpressure otel
+--->
+
 # Design Goals for OpenTelemetry Wire Protocol
 
 We want to design a telemetry data exchange protocol that has the following characteristics:

docs/requirements.md

@@ -1,3 +1,11 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: Requirements
+aliases:
+  - /docs/reference/specification/protocol/requirements
+  - /docs/specs/otel/protocol/requirements
+spelling: cSpell:ignore backpressure dealocations otel reconnections
+--->
+
 # OpenTelemetry Protocol Requirements
 
 This document will drive OpenTelemetry Protocol design and RFC.

docs/specification.md

@@ -1,3 +1,13 @@
+<!--- Hugo front matter used to generate the website version of this page:
+title: OTLP Specification
+linkTitle: Specification
+aliases:
+  - /docs/reference/specification/protocol/otlp
+  - /docs/specs/otel/protocol/otlp
+spelling:
+  cSpell:ignore backpressure dealocations otel otlp protobuf reconnections retryable OTEP
+--->
+
 # OpenTelemetry Protocol Specification
 
 **Status**: [Stable](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/document-status.md)

specification/README.md

@@ -1,8 +0,0 @@
-# OpenTelemetry Protocol
-
-This is the specification of new OpenTelemetry protocol (OTLP).
-
-- [Design Goals](design-goals.md).
-- [Requirements](requirements.md).
-- [Specification](otlp.md).
-- [SDK Exporter](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md).