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

Add user manual to footer #5873

Merged
merged 1 commit into from
Oct 17, 2024
Merged

Add user manual to footer #5873

merged 1 commit into from
Oct 17, 2024

Conversation

jorg-vr
Copy link
Contributor

@jorg-vr jorg-vr commented Oct 17, 2024

This pull request adds a link to our documentation to the footer of our website.
I also grouped the Facebook and twitter icons so that the footer doesn't take up too much height on small screens.

image

image

@jorg-vr jorg-vr added the enhancement A change that isn't substantial enough to be called a feature label Oct 17, 2024
@jorg-vr jorg-vr self-assigned this Oct 17, 2024
Copy link

coderabbitai bot commented Oct 17, 2024

Walkthrough

The changes involve modifications to the footer section of the HTML template located in app/views/layouts/_footer.html.erb. The social media links for Twitter and Facebook have been reorganized into a new <div> element for better content structure. Additionally, a new link has been added to direct users to the documentation for Dodona, with a URL that dynamically reflects the current locale. All existing links related to support, contact, status, privacy statement, data, publications, and version information remain unchanged.

Changes

File Path Change Summary
app/views/layouts/_footer.html.erb Restructured social media links into a new <div> element; added a new link for Dodona documentation with dynamic locale URL. Existing links retained.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Footer
    participant Documentation

    User->>Footer: Access footer links
    Footer->>User: Display social media links
    Footer->>User: Display documentation link
    User->>Documentation: Click on documentation link
    Documentation-->>User: Redirect to documentation page
Loading

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

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: 0

🧹 Outside diff range and nitpick comments (2)
app/views/layouts/_footer.html.erb (2)

7-14: Approved: Good restructuring of social media links

The encapsulation of social media links in a new <div> improves the organization and aligns with the PR objective. The use of target="_blank" with rel="noopener" is a good security practice.

Consider adding aria-label attributes to the social media links for better accessibility. For example:

- <a href="https://twitter.com/DodonaEdu" target="_blank" rel="noopener">
+ <a href="https://twitter.com/DodonaEdu" target="_blank" rel="noopener" aria-label="Dodona on Twitter">
  <i class="mdi mdi-twitter"></i>
</a>
- <a href="https://facebook.com/DodonaEdu" target="_blank" rel="noopener">
+ <a href="https://facebook.com/DodonaEdu" target="_blank" rel="noopener" aria-label="Dodona on Facebook">
  <i class="mdi mdi-facebook"></i>
</a>

16-16: Approved: Good addition of the user manual link

The new link to the user manual is well-placed and aligns with the PR objective. The use of I18n for localization is a good practice.

For consistency with other links in the footer, consider adding a CSS class to the link. For example:

- <%= link_to t("layout.menu.manual"), "https://docs.dodona.be/#{I18n.locale}" %>
+ <%= link_to t("layout.menu.manual"), "https://docs.dodona.be/#{I18n.locale}", class: "d-none d-lg-inline" %>

This change would make the manual link behave similarly to other links that are hidden on smaller screens.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 400854d and 81e2797.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • app/views/layouts/_footer.html.erb (1 hunks)
🧰 Additional context used
🔇 Additional comments (1)
app/views/layouts/_footer.html.erb (1)

Line range hint 1-27: Overall: Good implementation of footer changes

The changes to the footer align well with the PR objectives. The restructuring of social media links and the addition of the user manual link improve the footer's organization and functionality. The implementation is solid, with good practices such as using rel="noopener" for external links and I18n for localization.

Minor suggestions have been made for improving accessibility and maintaining consistency with existing styles. These small tweaks would further enhance the user experience and code quality.

@jorg-vr jorg-vr merged commit c24eded into main Oct 17, 2024
16 checks passed
@jorg-vr jorg-vr deleted the enhance/add-docs-to-footer branch October 17, 2024 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement A change that isn't substantial enough to be called a feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants