Skip to content

Fixed homepage links#391

Merged
palisadoes merged 3 commits into
PalisadoesFoundation:developfrom
palisadoes:homepage
Dec 8, 2025
Merged

Fixed homepage links#391
palisadoes merged 3 commits into
PalisadoesFoundation:developfrom
palisadoes:homepage

Conversation

@palisadoes

@palisadoes palisadoes commented Dec 8, 2025

Copy link
Copy Markdown
Contributor

Fixed homepage links

Summary by CodeRabbit

  • Style

    • Standardized code formatting and string quotes in configuration files.
  • Chores

    • Updated homepage call-to-action buttons: first now links to documentation, second now links to GitHub repository.
    • Updated navigation footer with Forums link and GitHub references.

✏️ Tip: You can customize this high-level summary in your review settings.

@palisadoes palisadoes added the ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files label Dec 8, 2025
@github-actions

github-actions Bot commented Dec 8, 2025

Copy link
Copy Markdown

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

🎯 Contacting the person who assigned the mentors is not advised unless they make a request. Do not @ the person who did the assignment otherwise.

@coderabbitai

coderabbitai Bot commented Dec 8, 2025

Copy link
Copy Markdown

Walkthrough

Documentation configuration and homepage navigation updates: quote normalization (single to double quotes) and spacing adjustments in Docusaurus config, plus updates to CTA button links and text on the homepage.

Changes

Cohort / File(s) Summary
Documentation configuration
docs/docusaurus.config.ts
Quote style normalization (single to double quotes), path standardization (sidebars, customCss), favicon/baseUrl adjustments, navigation updates (Slack → Forums with link to community.talawa.io), and formatting cleanup.
Homepage UI
docs/src/pages/index.tsx
Updated primary CTA link from /docs/installation to /docs, secondary CTA changed from "Community" link to GitHub repository with target="_blank" and rel="noopener noreferrer" attributes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify all quote normalizations are consistent across the config file
  • Confirm the updated CTA links are correct (/docs and GitHub repository URL)
  • Ensure the rel="noopener noreferrer" attribute is properly set for security on the external link

Poem

🐰 Docusaurus gets a fresh coat of paint,
Double quotes where singles weren't (or ain't),
Forums shine brighter than old Slack threads,
Homepage now points where the documentation spreads!
GitHub links open in windows so wide, 🚀

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description check ⚠️ Warning The description is minimal and lacks required template sections including issue number, change type, summary/motivation, breaking changes disclosure, and test coverage checklist items. Expand the description to include: what kind of change this is, the issue number being fixed, clear motivation/summary of changes, breaking change assessment, and completion of the provided checklist items.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Fixed homepage links' directly matches the main changes in the pull request, which update homepage action button links and targets in docs/src/pages/index.tsx.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1bba102 and d039afb.

📒 Files selected for processing (1)
  • docs/src/pages/index.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • docs/src/pages/index.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Test Application

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov

codecov Bot commented Dec 8, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.94%. Comparing base (5e802b8) to head (d039afb).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #391      +/-   ##
===========================================
+ Coverage    82.53%   85.94%   +3.40%     
===========================================
  Files          105      128      +23     
  Lines         6961    10797    +3836     
  Branches         0      749     +749     
===========================================
+ Hits          5745     9279    +3534     
- Misses        1216     1503     +287     
- Partials         0       15      +15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
docs/docusaurus.config.ts (1)

89-93: Remove duplicate colorMode configuration.

The colorMode object is defined twice in themeConfig (lines 89-93 and 150-154), with conflicting values for respectPrefersColorScheme (false vs. true). JavaScript objects only retain the last definition, making this confusing and error-prone.

Apply this diff to remove the first definition and keep only the second:

-    colorMode: {
-      defaultMode: "light",
-      disableSwitch: false,
-      respectPrefersColorScheme: false,
-    },
     footer: {
       style: "dark",

Also applies to: 150-154

🧹 Nitpick comments (1)
docs/docusaurus.config.ts (1)

1-3: Quote normalization improves consistency.

The formatting changes standardize string literals to use double quotes throughout the configuration file, improving code consistency and likely aligning with project linting rules.

Also applies to: 10-10, 13-13, 19-19, 22-22, 30-31, 36-36, 39-39, 43-44, 47-47

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e802b8 and 1bba102.

📒 Files selected for processing (3)
  • docs/docusaurus.config.ts (4 hunks)
  • docs/package.json (1 hunks)
  • docs/src/pages/index.tsx (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2025-09-04T20:04:37.212Z
Learnt from: Abhi-MS
Repo: PalisadoesFoundation/switchmap-ng PR: 337
File: docs/docs/frontend/types/graphql/GetZoneDevices.md:59-64
Timestamp: 2025-09-04T20:04:37.212Z
Learning: Documentation files in docs/docs/frontend/ are autogenerated by TypeDoc from TypeScript source code and should not be manually edited. Changes should be made to the source TypeScript files instead.

Applied to files:

  • docs/src/pages/index.tsx
  • docs/docusaurus.config.ts
📚 Learning: 2025-07-24T19:36:00.577Z
Learnt from: Abhi-MS
Repo: PalisadoesFoundation/switchmap-ng PR: 330
File: docs/src/components/HeroImage/HeroSection.css:12-15
Timestamp: 2025-07-24T19:36:00.577Z
Learning: In Docusaurus projects, using !important declarations may be necessary to override framework-injected styles that have high specificity from CSS modules or inline styles, especially when increasing selector specificity alone is insufficient.

Applied to files:

  • docs/docusaurus.config.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Test Application
🔇 Additional comments (3)
docs/src/pages/index.tsx (1)

16-22: Simplified entry point looks good.

Changing the "Get Started" link from the specific installation page to the general docs landing page (/docs) provides a better initial user experience, allowing users to explore the documentation structure before diving into installation.

docs/docusaurus.config.ts (1)

100-104: The community forums URL is correct.

The link update from Slack to Forums pointing to https://community.talawa.io/ is valid. This is the official Talawa Community forum (XenForo-based) and includes dedicated sections for Switchmap-NG discussions alongside other community resources.

docs/package.json (1)

48-48: The packageManager field correctly enforces pnpm@10.18.3 with an integrity hash. pnpm version 10.18.3 is a confirmed release, and using the packageManager field with Corepack is the recommended approach for reproducible builds and version enforcement.

Comment thread docs/src/pages/index.tsx
@palisadoes palisadoes merged commit 0e859b5 into PalisadoesFoundation:develop Dec 8, 2025
13 checks passed
@palisadoes palisadoes deleted the homepage branch December 8, 2025 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ignore-sensitive-files-pr The contributor has a legitimate reason for editiing protected files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant