feat: [es] Create /docs/contributing/new-content.md

.htmltest.yml

@@ -12,7 +12,6 @@ IgnoreDirs:
   - zh/docs/contributing/pr-checks
 IgnoreInternalURLs: # list of paths
 IgnoreURLs: # list of regexs of paths or URLs to be ignored
-  - ^/api$
   - ^((/..)?/docs/languages/\w+|\.\.)/(api|examples|registry)/$
   - ^(/..)?/docs/collector/registry/$
   - ^(/..)?/docs/languages/net/(metrics-api|traces-api)/

content/en/api-docs.md

@@ -0,0 +1,15 @@
+---
+title: API Documentation
+linkTitle: Docs
+---
+
+{{% blocks/section color="white" %}}
+
+## {{% param title %}}
+
+Below you will find links to all the API references available for the different
+implementations of the OpenTelemetry API & SDK
+
+{{% apidocs %}}
+
+{{% /blocks/section %}}

content/en/docs/contributing/issues.md

@@ -5,50 +5,8 @@ description:
   improvement.
 weight: 10
 cSpell:ignore: prepopulated
-_issues: https://github.com/open-telemetry/opentelemetry.io/issues
-_issue: https://github.com/open-telemetry/opentelemetry.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A
 ---
 
-## Fixing an existing issue
-
-One of the best ways to help make OTel docs better is to fix an existing issue.
-
-1. Browse through the list of [issues]({{% param _issues %}}).
-2. Select an issue that you would like to work on, ideally one that you can fix
-   in a short amount of time.
-
-   <!-- prettier-ignore -->
-   <a name="first-issue"></a>
-   {{% alert title="First time contributing? " %}}
-
-   Select an issue with the following labels:
-
-   - [Good first issue]
-   - [Help wanted]
-
-   <!-- prettier-ignore -->
-   > **NOTE**: we **_do not_ assign issues** to those who
-   > have not already made contributions to the [OpenTelemetry
-   > organization][org].
-   {.mt-3}
-
-   <!-- prettier-ignore -->
-   [good first issue]: {{% param _issue %}}%22good+first+issue%22
-   [help wanted]: {{% param _issue %}}%3A%22help+wanted%22
-   [org]: https://github.com/open-telemetry
-
-   {{% /alert %}}
-
-3. Read through the issue comments, if any.
-4. Ask maintainers if this issue is still relevant, and ask any questions you
-   need for clarification by posting comments over the issue.
-5. Share your intention to work on the issue by adding add a comment to this
-   effect.
-6. Work on fixing the issue. Let maintainers know if you run into any problems.
-7. When ready, [submit your work through a pull request](../pull-requests) (PR).
-
-## Reporting an issue
-
 If you notice an error or want to suggest improvements to existing content, open
 an issue.
 

content/en/docs/contributing/pull-requests.md

@@ -68,14 +68,14 @@ A([fa:fa-user New<br>Contributor]) --- id1[(open-telemetry/opentelemetry.io<br>G
 subgraph tasks[Changes using GitHub]
 direction TB
     0[ ] -.-
-    1[1. Edit this page] --> 2[2. Use GitHub markdown<br>editor to make changes]
-    2 --> 3[3. fill in Propose file change]
+    1[Edit this page] --> 2[Use GitHub markdown<br>editor to make changes]
+    2 --> 3[fill in Propose file change]
 
 end
 subgraph tasks2[ ]
 direction TB
-4[4. select Propose file change] --> 5[5. select Create pull request] --> 6[6. fill in Open a pull request]
-6 --> 7[7. select Create pull request]
+4[select Propose file change] --> 5[select Create pull request] --> 6[fill in Open a pull request]
+6 --> 7[select Create pull request]
 end
 
 id1 --> tasks --> tasks2
@@ -289,15 +289,15 @@ Figure 4 shows the steps to open a PR from your fork to
 flowchart LR
 subgraph first[ ]
 direction TB
-1[1. Go to opentelemetry.io repository] --> 2[2. Select New Pull Request]
-2 --> 3[3. Select compare across forks]
-3 --> 4[4. Select your fork from<br>head repository drop-down menu]
+1[Go to opentelemetry.io repository] --> 2[Select New Pull Request]
+2 --> 3[Select compare across forks]
+3 --> 4[Select your fork from<br>head repository drop-down menu]
 end
 subgraph second [ ]
 direction TB
-5[5. Select your branch from<br>the compare drop-down menu] --> 6[6. Select Create Pull Request]
-6 --> 7[7. Add a description<br>to your PR]
-7 --> 8[8. Select Create pull request]
+5[Select your branch from<br>the compare drop-down menu] --> 6[Select Create Pull Request]
+6 --> 7[Add a description<br>to your PR]
+7 --> 8[Select Create pull request]
 end
 
 first --> second

content/en/docs/languages/_index.md

@@ -48,9 +48,9 @@ references are available:
 
 {{% apidocs %}}
 
-{{% alert title="Note" color="info" %}}
+{{% alert title="Tip" color="info" %}}
 
-The list above is aliased to [`/api`](/api).
+You can find a list of available API references at </api-docs>.
 
 {{% /alert %}}