Skip to content
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

Feature/ux improvements #2968

Conversation

Abhi-MS
Copy link

@Abhi-MS Abhi-MS commented Jan 26, 2025

What kind of change does this PR introduce?

Update navbar and sidebar to match that of Talawa docs.

Navbar

Before:

Talawa-API.1.mp4

After:

Talawa-API.2.mp4

Sidebar

Before:

Talawa-API.3.mp4

After:

Talawa-API.4.mp4

Issue Number:

Fixes #2951 Part 1

Snapshots/Videos:

If relevant, did you update the documentation?

Not relevant

Summary

Fixes part of the issue #2951 by updating the navbar and sidebar to match that of Talawa docs.

Does this PR introduce a breaking change?

No

Checklist

CodeRabbit AI Review

  • I have reviewed and addressed all critical issues flagged by CodeRabbit AI
  • I have implemented or provided justification for each non-critical suggestion
  • I have documented my reasoning in the PR comments where CodeRabbit AI suggestions were not implemented

Test Coverage

  • I have written tests for all new changes/features
  • I have verified that test coverage meets or exceeds 95%
  • I have run the test suite locally and all tests pass

Other information

Have you read the contributing guide?

Yes

Summary by CodeRabbit

  • Documentation

    • Updated Docusaurus configuration with refined navigation settings
    • Modified logo and navigation item properties
    • Adjusted documentation site navigation links
  • Style

    • Updated CSS font sizes and padding
    • Added new class for external link visibility on the Navbar
    • Refined menu and link styling

Copy link

coderabbitai bot commented Jan 26, 2025

Walkthrough

The pull request introduces modifications to the documentation website's configuration and styling. The changes primarily focus on updating the navbar configuration in docusaurus.config.ts by refining navigation item links and properties. Additionally, minor CSS adjustments were made in custom.css, including font size modifications and the introduction of a new class for managing external link visibility.

Changes

File Change Summary
docs/docusaurus.config.ts - Updated logo configuration with href and target properties
- Removed tutorialSidebar navigation item
- Modified "General" item's href to point to more specific documentation section
docs/src/css/custom.css - Increased .menu * font size from 0.65rem to 0.7rem
- Commented out left padding and line height for menu items
- Renamed media query class from .menu_SIkG to .menu_Guh8
- Added new .iconExternalLink_zRin class to hide external link SVGs

Assessment against linked issues

Objective Addressed Explanation
Update navbar styling and links [#2951]
Ensure consistent navbar across documentation sites [#2951] Partial changes observed, full consistency requires additional verification

Possibly related PRs

Suggested labels

ignore-sensitive-files-pr

Suggested reviewers

  • palisadoes
  • tasneemkoushar

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5d59df2 and cea6f93.

📒 Files selected for processing (1)
  • docs/src/css/custom.css (4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (4)
docs/src/css/custom.css (4)

124-126: LGTM! Font size adjustment improves readability.

The increase in font size from 0.65rem to 0.7rem enhances text readability while maintaining the menu's visual hierarchy.


155-155: LGTM! Removal of fixed line height.

Allowing the default line spacing to take effect is appropriate for maintaining consistent typography across the documentation.


504-507: LGTM! Class name update maintains functionality.

The class name change from .menu_SIkG to .menu_Guh8 preserves the existing styling for menu items at larger screen sizes.


1299-1300: LGTM! Responsive image container implementation.

The new image container styles ensure proper image scaling while maintaining aspect ratios.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.

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. (Beta)
  • @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.

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.

Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

Copy link

codecov bot commented Jan 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 39.85%. Comparing base (425af24) to head (cea6f93).
Report is 1 commits behind head on develop-postgres.

Additional details and impacted files
@@                Coverage Diff                @@
##           develop-postgres    #2968   +/-   ##
=================================================
  Coverage             39.85%   39.85%           
=================================================
  Files                   453      453           
  Lines                 33203    33203           
  Branches                385      385           
=================================================
  Hits                  13234    13234           
  Misses                19969    19969           

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

Copy link

@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.yaml
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 425af24 and 5d59df2.

📒 Files selected for processing (2)
  • docs/docusaurus.config.ts (1 hunks)
  • docs/src/css/custom.css (4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: Run tests for talawa api
  • GitHub Check: Analyse Code With CodeQL (typescript)
🔇 Additional comments (2)
docs/docusaurus.config.ts (1)

64-65: LGTM! Navigation improvements look good.

The changes improve navigation consistency by:

  • Adding proper href to the logo
  • Ensuring links open in the same tab
  • Updating the "General" link to point to the docs section

Also applies to: 71-72

docs/src/css/custom.css (1)

124-126: LGTM! Menu styling improvements look good.

The increased font size improves readability.

docs/src/css/custom.css Show resolved Hide resolved
Copy link

Our Pull Request Approval Process

Thanks for contributing!

Testing Your Code

Remember, your PRs won't be reviewed until these criteria are met:

  1. We don't merge PRs with poor code quality.
    1. Follow coding best practices such that CodeRabbit.ai approves your PR.
  2. We don't merge PRs with failed tests.
    1. When tests fail, click on the Details link to learn more.
    2. Write sufficient tests for your changes (CodeCov Patch Test). Your testing level must be better than the target threshold of the repository
    3. Tests may fail if you edit sensitive files. Ask to add the ignore-sensitive-files-pr label if the edits are necessary.
  3. We cannot merge PRs with conflicting files. These must be fixed.

Our policies make our code better.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them.
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

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

  1. PRs with issues not assigned to you will be closed by the reviewer
  2. Fix the first comment in the PR so that each issue listed automatically closes

Other

  1. 🎯 Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.
  2. Read the CONTRIBUTING.md file make

@palisadoes
Copy link
Contributor

When the shared CSS is used (hopefully from docs.talawa.io), the vertical spacing of items in the left drawer will need to be reduced.

@palisadoes palisadoes merged commit 28859b2 into PalisadoesFoundation:develop-postgres Jan 26, 2025
16 of 18 checks passed
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