Skip to content

fix: Broken links (SEO agency) #20928

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

Open
wants to merge 8 commits into
base: main
Choose a base branch
from
Open

Conversation

adam-cobb532
Copy link
Contributor

Summary

⚠️ If you're contributing to a plugin please read this section of the contribution guidelines 🧑‍🎓 before submitting this PR ⚠️

Fixed a number of broken links in plugin documentation

@cq-bot
Copy link
Contributor

cq-bot commented Jun 30, 2025

@cq-bot
Copy link
Contributor

cq-bot commented Jun 30, 2025

@cq-bot
Copy link
Contributor

cq-bot commented Jun 30, 2025

@adam-cobb532 adam-cobb532 changed the title Fix broken links seo Fix: Broken links (SEO agency) Jun 30, 2025
@adam-cobb532 adam-cobb532 changed the title Fix: Broken links (SEO agency) fix: Broken links (SEO agency) Jun 30, 2025
@@ -1,4 +1,4 @@
The Hacker News Source plugin for CloudQuery extracts configuration from the [Hacker News API](https://github.com/HackerNews/API) and loads it into any supported CloudQuery destination (e.g. PostgreSQL, BigQuery, Snowflake, and [more](/docs/plugins/destinations/overview)).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we want to keep the relative link here /docs/plugins/destinations/overview.
See https://hub.cloudquery.io/plugins/source/cloudquery/hackernews/latest/docs

Since the link is relative, when you click more it opens in the same tab. If you'd use the full path it will open in a new table.
Also full paths won't work in Vercel deploy previews (they'll always point to the main deploy instead of the preview deploy)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. Does that definitely land in the right place though?
http://cloudquery.io/docs/plugins/destinations/overview currently goes to https://docs.cloudquery.io/docs/plugins/destinations/overview - is that what would happen when deployed?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In plugins docs the path would be relative to the Hub so. We map it from /docs/plugins/destinations/overview to /plugins/destination so it will end up as https://hub.cloudquery.io/plugins/destination

The mapping is done for compatibility reasons https://github.com/cloudquery/frontend/blob/f4fe12059928dbcc2de64a65a3b87b92089d75bc/apps/hub/src/components/plugin/sections/documentation/utils/index.tsx#L53 here (docs are versioned so old versions have the old links)

We could change it to /plugins/destination and it should work the same I think

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.

3 participants