Skip to content

Add Blog Link to Navbar#299

Merged
ashutoshamazix merged 2 commits intostagingfrom
chore/navbar-changes
May 7, 2025
Merged

Add Blog Link to Navbar#299
ashutoshamazix merged 2 commits intostagingfrom
chore/navbar-changes

Conversation

@ashutoshamazix
Copy link
Collaborator

@ashutoshamazix ashutoshamazix commented May 7, 2025

Description

  • Added Blog hosted on subdomain link to the navbar

How Has This Been Tested?

  • Locally

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Summary by CodeRabbit

  • New Features
    • Added a new navigation menu item linking to the external PillarX blog.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 7, 2025

Walkthrough

A new external blog link was added to the navigation menu in the header component of the landing page. This link appears as a third menu item alongside the existing navigation options and directs users to "https://blog.pillarx.app/" using a standard anchor tag.

Changes

File(s) Change Summary
src/components/LandingPage/Header/index.jsx Added a new list item with an external anchor link to the blog URL in the navigation menu.

Poem

Hopping through menus, what do I see?
A shiny new link, as bright as can be!
Now with a blog, our journey extends,
More stories and updates for all our friends.
🐰✨

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ashutoshamazix ashutoshamazix requested review from IAmKio and RanaBug May 7, 2025 14:56
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a7fa2fe and 6463dd5.

📒 Files selected for processing (1)
  • src/components/LandingPage/Header/index.jsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: unit-tests
  • GitHub Check: lint
  • GitHub Check: Cloudflare Pages

Comment on lines +73 to +75
<li>
<a href="https://blog.pillarx.app/">Blog</a>
</li>
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Ensure external blog link opens in a new tab and mitigate security risks
The new <a> tag points to an external site. For consistency with the Twitter link and to prevent reverse tabnabbing, please add target="_blank" and rel="noopener noreferrer":

               <ul id="menu" onClick={() => setShowMobileMenu(!showMobileMenu)}>
                 <li>
                   <NavLink
                     to="/waitlist"
                     className={({ isActive }) => (isActive ? 'active' : '')}
                   >
                     Testing Campaign
                   </NavLink>
                 </li>
-                <li>
-                  <a href="https://blog.pillarx.app/">Blog</a>
-                </li>
+                <li>
+                  <a
+                    href="https://blog.pillarx.app/"
+                    target="_blank"
+                    rel="noopener noreferrer"
+                  >
+                    Blog
+                  </a>
+                </li>
               </ul>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<li>
<a href="https://blog.pillarx.app/">Blog</a>
</li>
<ul id="menu" onClick={() => setShowMobileMenu(!showMobileMenu)}>
<li>
<NavLink
to="/waitlist"
className={({ isActive }) => (isActive ? 'active' : '')}
>
Testing Campaign
</NavLink>
</li>
<li>
<a
href="https://blog.pillarx.app/"
target="_blank"
rel="noopener noreferrer"
>
Blog
</a>
</li>
</ul>

@ashutoshamazix ashutoshamazix merged commit a44369e into staging May 7, 2025
7 checks passed
@ashutoshamazix ashutoshamazix deleted the chore/navbar-changes branch May 7, 2025 15:48
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.

2 participants