Fix: Blog pagination and category routing

[yugalkaushik]

Description

Blog

Previously, pagination from https://meshery.io/blog redirected users to https://meshery.io/page/2 , which is incorrect. This has now been fixed to correctly route pagination to https://meshery.io/blog/page/2

Before

After

Category

Previously, selecting a category on the https://meshery.io/blog/category page resulted in a 404 error for each category page.

Signed commits

• Yes, I signed my commits.

[netlify]

✅ Deploy Preview for mesheryio-preview ready!

Name	Link
🔨 Latest commit	73e44ab
🔍 Latest deploy log	https://app.netlify.com/projects/mesheryio-preview/deploys/69598c676eee90000800f89b
😎 Deploy Preview	https://deploy-preview-2516--mesheryio-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[gemini-code-assist]

Summary of Changes

Hello @yugalkaushik, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses critical routing issues within the blog section of the website. It involves migrating the underlying pagination system to a new Jekyll plugin and updating various configuration and template files. These changes ensure that blog post pagination and category page links function correctly, resolving incorrect redirects and 404 errors previously experienced by users.

Highlights

• Pagination Plugin Migration: The pull request migrates the blog's pagination system from the older octopress-paginate gem to the more modern and actively maintained jekyll-paginate-v2.
• Blog Pagination Routing Fix: Corrected the routing for blog pagination, ensuring that subsequent pages (e.g., page 2) now correctly navigate to /blog/page/2/ instead of the previously incorrect /page/2.
• Blog Category Routing Fix: Resolved 404 errors encountered when selecting blog categories by updating their URLs to include the /blog/ prefix and a trailing slash, e.g., /blog/category/my-category/.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully fixes issues with blog pagination and category routing by migrating from octopress-paginate to the more modern jekyll-paginate-v2 plugin. The configuration and template changes correctly update the URL structures. My review includes a couple of suggestions to improve the implementation further by using plugin-provided variables for generating pagination links, which enhances maintainability, and by ensuring all internal links are portable, adhering to the project's conventions.

[Bhumikagarggg]

hello @yugalkaushik
i can't find which issue you are solving? in PR please mention issue no.

[CodexRaunak]

@yugalkaushik Thank you for your contribution! Let's discuss this during the website call today at 6:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂