Skip to content

website: Fix links to Docsy styles and shortcodes#4424

Open
Ishan-AI-coder wants to merge 1 commit into
kubeflow:masterfrom
Ishan-AI-coder:patch-2
Open

website: Fix links to Docsy styles and shortcodes#4424
Ishan-AI-coder wants to merge 1 commit into
kubeflow:masterfrom
Ishan-AI-coder:patch-2

Conversation

@Ishan-AI-coder

Copy link
Copy Markdown
Contributor

What this PR does

This PR fixes broken and outdated documentation links related to the Docsy theme.

Changes

1. Fix broken Docsy submodule GitHub links

The documentation previously linked to files inside the themes/docsy Git submodule through the kubeflow/website repository. These URLs returned 404 because GitHub does not resolve submodule contents through the parent repository's tree view.

Updated the following links to point directly to the corresponding files in the upstream google/docsy repository at the pinned commit used by Kubeflow:

  • assets/scss directory
  • _variables.scss

Using the specific commit hash ensures the links remain consistent with the version of Docsy currently used by the website.

2. Update Docsy shortcode documentation links

Updated the Docsy shortcode documentation links from the older path:

  • /docs/adding-content/shortcodes/

to the current canonical path:

  • /docs/content/shortcodes/

This affects references to:

  • blocks-cover
  • blocks-link-down

The existing URLs still resolve via redirects, but updating them avoids relying on legacy paths and reduces the risk of future link rot.

Why

These changes improve the accuracy and maintainability of the documentation by:

  • Fixing broken GitHub links that resulted in 404 errors.
  • Pointing readers to the current canonical Docsy documentation.
  • Reducing future maintenance caused by stale or redirected URLs.

How I tested it

  • Verified that the updated GitHub URLs resolve to the correct files in the upstream Docsy repository (no 404s).
  • Verified that the updated Docsy documentation page contains the #blocks-cover and #blocks-link-down anchors and that both links navigate correctly.

Description of Changes

Related Issues

Closes: #

Related: #

Checklist

## What this PR does

This PR fixes broken and outdated documentation links related to the Docsy theme.

### Changes

#### 1. Fix broken Docsy submodule GitHub links

The documentation previously linked to files inside the `themes/docsy` Git submodule through the `kubeflow/website` repository. These URLs returned **404** because GitHub does not resolve submodule contents through the parent repository's tree view.

Updated the following links to point directly to the corresponding files in the upstream **google/docsy** repository at the pinned commit used by Kubeflow:

* `assets/scss` directory
* `_variables.scss`

Using the specific commit hash ensures the links remain consistent with the version of Docsy currently used by the website.

#### 2. Update Docsy shortcode documentation links

Updated the Docsy shortcode documentation links from the older path:

* `/docs/adding-content/shortcodes/`

to the current canonical path:

* `/docs/content/shortcodes/`

This affects references to:

* `blocks-cover`
* `blocks-link-down`

The existing URLs still resolve via redirects, but updating them avoids relying on legacy paths and reduces the risk of future link rot.

## Why

These changes improve the accuracy and maintainability of the documentation by:

* Fixing broken GitHub links that resulted in 404 errors.
* Pointing readers to the current canonical Docsy documentation.
* Reducing future maintenance caused by stale or redirected URLs.

## How I tested it

* Verified that the updated GitHub URLs resolve to the correct files in the upstream Docsy repository (no 404s).
* Verified that the updated Docsy documentation page contains the `#blocks-cover` and `#blocks-link-down` anchors and that both links navigate correctly.


Signed-off-by: Ishan Sarkar <sarkarishan2005@gmail.com>
@google-oss-prow

Copy link
Copy Markdown

Hi @Ishan-AI-coder. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@google-oss-prow google-oss-prow Bot requested review from varodrig and zijianjoy July 6, 2026 18:47
@google-oss-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign juliusvonkohout for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown

🚫 This command cannot be processed. Only organization members or owners can use the commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant