Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Tech Debt] Clean up docs_link_service organization so that strings are in the right categories #3208

Closed
joshuarrrr opened this issue Jan 7, 2023 · 2 comments · Fixed by #3685
Assignees
Labels
docs Improvements or additions to documentation good first issue Good for newcomers technical debt If not paid, jeapardizes long-term success and maintainability of the repository.

Comments

@joshuarrrr
Copy link
Member

Is your feature request related to a problem? Please describe.

In

We organize links to documentation in 3 categories:

  1. opensearch - these should be documentation links at https://opensearch.org/docs/latest/opensearch
  2. opensearchDashboards - these should be documentation links at https://opensearch.org/docs/latest/dashboards
  3. noDocumentation - these should only be documentation link placeholders where no valid documentation exists

Describe the solution you'd like

As far as I can tell, existing links in opensearch and opensearchDashboards are all correctly categorized and formatted.

But for links defined under noDocumentation:

  1. If an actual documentation link is defined (more than just the documentation homepage)
  2. Replace any hard-coded path with ${OPENSEARCH_DASHBOARDS_VERSIONED_DOCS} or ${OPENSEARCH_VERSIONED_DOCS} as appropriate
  3. If there's no comment with the absolute URL to the doc link, add a comment above the property
  4. Move the property to opensearch or opensearchDashboards property as appropriate
  5. Update the DocLinksStart interface
  6. Update any references in code from .noDocumentation. to the appropriate property
  7. Some links that appear to be valid are not. For example https://opensearch.org/docs/latest/downloads/beats/auditbeat redirects to the documentation homepage. These links should be corrected if actual documentation pages exist, or updated to be ${OPENSEARCH_WEBSITE_DOCS}, which will make it more clear that the documentation is really missing
@joshuarrrr joshuarrrr added good first issue Good for newcomers technical debt If not paid, jeapardizes long-term success and maintainability of the repository. docs Improvements or additions to documentation labels Jan 7, 2023
@sayuree
Copy link
Contributor

sayuree commented Mar 23, 2023

I have some questions regarding this issue:
Move the property to opensearch or opensearchDashboards property as appropriate

  1. So we need to create noDocumentation on both opensearch and opensearchDashboards, dividing URLs starting from https://opensearch.org/docs/latest/opensearch/ and https://opensearch.org/docs/latest/dashboards respectively. Is it right?
  2. These links should be corrected if actual documentation pages exist, or updated to be ${OPENSEARCH_WEBSITE_DOCS}, which will make it more clear that the documentation is really missing
    How can we find links to documentation pages? For example, currently, the links below automatically redirect to the docs homepage:
    https://opensearch.org/docs/latest/downloads/beats/auditbeat
    https://opensearch.org/docs/latest/downloads/beats/filebeat
    https://opensearch.org/docs/latest/downloads/beats/metricbeat
    https://opensearch.org/docs/latest/downloads/beats/heartbeat
    In the documentation, I found only Tools page, containing links to the download page of these items, e.g.
    https://www.elastic.co/downloads/past-releases/auditbeat-oss-7-12-1 for Auditbeat

Can you also please assign this issue to me?

@joshuarrrr
Copy link
Member Author

So we need to create noDocumentation on both opensearch and opensearchDashboards, dividing URLs starting from https://opensearch.org/docs/latest/opensearch/ and https://opensearch.org/docs/latest/dashboards respectively. Is it right?

No, not quite - basically remove the property from the noDocumentation object and add it to openSearch or openSearchDashboards objects instead

How can we find links to documentation pages?

This mostly involves searching around and poking through the documentation site: https://opensearch.org/docs/latest/

Google site search may also be useful to find if there are any documentation pages.

sayuree added a commit to sayuree/OpenSearch-Dashboards that referenced this issue Apr 11, 2023
Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
joshuarrrr pushed a commit that referenced this issue Apr 13, 2023
Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
opensearch-trigger-bot bot pushed a commit that referenced this issue Apr 13, 2023
Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
(cherry picked from commit 4e14aae)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
aoguan1990 pushed a commit to aoguan1990/OpenSearch-Dashboards that referenced this issue Apr 14, 2023
…ct#3685)

Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
AMoo-Miki pushed a commit that referenced this issue Apr 15, 2023
)

* Add noDocumentation links (#3208) (#3685)

Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
(cherry picked from commit 4e14aae)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

* update changelog

Signed-off-by: Josh Romero <rmerqg@amazon.com>

---------

Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Signed-off-by: Josh Romero <rmerqg@amazon.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Josh Romero <rmerqg@amazon.com>
sikhote pushed a commit to sikhote/OpenSearch-Dashboards that referenced this issue Apr 24, 2023
…ct#3685)

Signed-off-by: sabina.zaripova <sabina.zaripova@nu.edu.kz>
Signed-off-by: David Sinclair <david@sinclair.tech>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation good first issue Good for newcomers technical debt If not paid, jeapardizes long-term success and maintainability of the repository.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants