Skip to content

Conversation

@coolchigi
Copy link

Problem

The URL https://microcks-io.vercel.app/documentation/getting-started/ returns a 404 error. Users trying to access the shorter URL path encounter a broken link.

Solution

Added a redirect file that automatically redirects requests from /documentation/getting-started/ to the correct location at /documentation/tutorials/getting-started/.

Changes

  • Created content/documentation/getting-started/_index.md with redirect layout
  • Uses Hugo's built-in redirect template to provide a clean HTTP redirect

Testing

After merge, the following URL should redirect properly:

  • https://microcks.io/documentation/getting-started/https://microcks.io/documentation/tutorials/getting-started/

Type of Change

  • Bug fix (broken link fix)

…on/tutorials/getting-started/

Signed-off-by: Chigo <72313512+coolchigi@users.noreply.github.com>
@coolchigi coolchigi force-pushed the fix/add-getting-started-redirect branch from 4ffadee to fe30965 Compare December 10, 2025 01:25
@Caesarsage
Copy link
Contributor

Caesarsage commented Dec 11, 2025

Hello @coolchigi
Thanks for your contributions.

Where is this broken link referenced on the website ?

I think the existing get started page (https://microcks.io/documentation/tutorials/getting-started/) is okay and there is no need to create a separate page just to redirect to it Except it's a broken link on a page that need to be fixed and not creation of a new page

@coolchigi
Copy link
Author

Hello @coolchigi Thanks for your contributions.

Where is this broken link referenced on the website ?

I think the existing get started page (https://microcks.io/documentation/tutorials/getting-started/) is okay and there is no need to create a separate page just to redirect to it Except it's a broken link on a page that need to be fixed and not creation of a new page

hii @Caesarsage, thanks for reviewing!

To clarify the issue: the broken link is on the Vercel preview deployment at https://microcks-io.vercel.app/documentation/getting-started/, not on the main site.

Screenshot 2025-12-11 at 10 51 45 AM

Vercel deploys from this same repo, and since there's no folder at [getting-started], Hugo generates a 404 for that path. The actual page lives at /documentation/tutorials/getting-started/. My PR creates the missing folder & file with a redirect to prevent the 404, following the same pattern already used for /discord-invite/

Happy to explore other alternatives if you have a different approach in mind. Let me know your thoughts!

@Caesarsage
Copy link
Contributor

Hello @coolchigi Thanks for your contributions.
Where is this broken link referenced on the website ?
I think the existing get started page (https://microcks.io/documentation/tutorials/getting-started/) is okay and there is no need to create a separate page just to redirect to it Except it's a broken link on a page that need to be fixed and not creation of a new page

hii @Caesarsage, thanks for reviewing!

To clarify the issue: the broken link is on the Vercel preview deployment at https://microcks-io.vercel.app/documentation/getting-started/, not on the main site.

Screenshot 2025-12-11 at 10 51 45 AM Vercel deploys from this same repo, and since there's no folder at [getting-started], Hugo generates a 404 for that path. The actual page lives at `/documentation/tutorials/getting-started/`. My PR creates the missing folder & file with a redirect to prevent the 404, following the same pattern already used for `/discord-invite/`

Happy to explore other alternatives if you have a different approach in mind. Let me know your thoughts!

@coolchigi, thanks. The broken link is on the Vercel preview deployment.

Updating the link on the Vercel preview deployment to point directly to the correct page (/documentation/tutorials/getting-started/) might be a better approach. Since the actual site doesn't reference the broken link, it's likely not affecting many users.

Creating a redirect page might add redundancy, especially if it's not referenced elsewhere.

Other suggestions are welcome

cc @yada @lbroudoux

@yada
Copy link
Member

yada commented Dec 12, 2025

Hello @coolchigi Thanks for your contributions.
Where is this broken link referenced on the website ?
I think the existing get started page (https://microcks.io/documentation/tutorials/getting-started/) is okay and there is no need to create a separate page just to redirect to it Except it's a broken link on a page that need to be fixed and not creation of a new page

hii @Caesarsage, thanks for reviewing!
To clarify the issue: the broken link is on the Vercel preview deployment at https://microcks-io.vercel.app/documentation/getting-started/, not on the main site.
Screenshot 2025-12-11 at 10 51 45 AM
Vercel deploys from this same repo, and since there's no folder at [getting-started], Hugo generates a 404 for that path. The actual page lives at /documentation/tutorials/getting-started/. My PR creates the missing folder & file with a redirect to prevent the 404, following the same pattern already used for /discord-invite/
Happy to explore other alternatives if you have a different approach in mind. Let me know your thoughts!

@coolchigi, thanks. The broken link is on the Vercel preview deployment.

Updating the link on the Vercel preview deployment to point directly to the correct page (/documentation/tutorials/getting-started/) might be a better approach. Since the actual site doesn't reference the broken link, it's likely not affecting many users.

Creating a redirect page might add redundancy, especially if it's not referenced elsewhere.

Other suggestions are welcome

cc @yada @lbroudoux

Thanks @coolchigi, ideally you should have open an issue on this topic before a PR ;) As yes and fully agree with @Caesarsage : this is not an issue on the public website and BTW, Vercel is outdated (our fault here...), see: #333

We should clean it up and close #333 (remove Vercel) and move forward on #334 to setup Netlify correctly :) If you have expertise on Netlify or want to dig further to make it efficient, you are more than welcome :)

@yada
Copy link
Member

yada commented Dec 18, 2025

Close as superseded by #334

@yada yada closed this Dec 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants