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

Website: Generic FAQ for fundraisers #979

Merged
merged 4 commits into from
Dec 10, 2024
Merged

Conversation

ssandino
Copy link
Member

@ssandino ssandino commented Dec 10, 2024

Summary by CodeRabbit

  • New Features

    • Added new sections in the FAQ for "campaign" and "campaign-ismatu" with detailed information on direct cash transfers and fundraising for Ebola survivors.
    • Enhanced the "recipients" section with updated criteria for selection and links to local partners.
    • Introduced link functionality in the campaign page's FAQ section for improved navigation.
  • Bug Fixes

    • Streamlined the "contributors" section by removing outdated questions.
  • Chores

    • Improved the overall structure and clarity of the FAQ content across multiple languages.

Copy link

vercel bot commented Dec 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
public ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 10, 2024 3:44pm

Copy link

coderabbitai bot commented Dec 10, 2024

📝 Walkthrough

Walkthrough

The pull request introduces significant updates to the website-faq.json files across multiple languages, enhancing the content related to the Social Income initiative. New sections titled "campaign" and "campaign-ismatu" have been added, providing detailed information on direct cash transfers and fundraising efforts for Ebola survivors. The "recipients" section has been revised to clarify the selection process and include links to local partners. Additionally, a new redirection case has been implemented in the middleware to handle requests for a specific campaign URL.

Changes

File Path Change Summary
shared/locales/de/website-faq.json Added "campaign" and "campaign-ismatu" sections; updated "recipients" section with new link.
shared/locales/en/website-faq.json Added "campaign" and "campaign-ismatu" sections; updated "recipients" and removed a question in "contributors."
shared/locales/fr/website-faq.json Added "campaign" and "campaign-ismatu" sections; updated "recipients" section with a new link.
shared/locales/it/website-faq.json Added "campaign" and "campaign-ismatu" sections; updated "recipients" section with a new link.
website/src/middleware.ts Added a new case in redirectMiddleware for /liberty path; no changes to public entity declarations.

Possibly related PRs

  • feature(website): add ngo partners page #924: The main PR and this PR both involve enhancements to the FAQ sections related to the Social Income initiative, specifically focusing on the operational details and partnerships with NGOs.
  • Update README.md #940: This PR updates the README to clarify the recipient selection process, which is relevant to the main PR's focus on the operational aspects of recipient selection in the Social Income initiative.
  • [Web]: Fix mobile view Issues on "recipient selection page" #966: Although primarily focused on mobile view issues, this PR relates to the recipient selection page, which is a topic addressed in the main PR regarding the selection criteria and operational details.

Suggested labels

feature

Suggested reviewers

  • socialincome-dev
  • mkue

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7f1d60e and 7029235.

📒 Files selected for processing (1)
  • website/src/app/[lang]/[region]/(website)/campaign/[campaign]/page.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • website/src/app/[lang]/[region]/(website)/campaign/[campaign]/page.tsx

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

Visit the preview URL for this PR (updated for commit de1714b):

https://si-admin-staging--pr979-sandino-fundraiser-g-kma4j6ll.web.app

(expires Tue, 17 Dec 2024 14:56:07 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: b7b0969384059dce6ea8fad1ee1d1737e54e6676

@ssandino
Copy link
Member Author

@ssandino ssandino marked this pull request as ready for review December 10, 2024 15:12
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)
shared/locales/en/website-faq.json (1)

203-234: Consider reducing content duplication.

The campaign section contains questions that are duplicated from other sections:

  • "What are Direct Cash Transfers?" (duplicated from UBI section)
  • "Why Sierra Leone?" (duplicated from recipients section)

Consider using a shared content structure or references to avoid maintaining duplicate content.

shared/locales/fr/website-faq.json (1)

207-238: Consider using content references instead of duplication

The campaign section reuses content from other sections. Consider implementing a content reference system to avoid maintenance overhead when the source content needs updates.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 43c070f and de1714b.

📒 Files selected for processing (5)
  • shared/locales/de/website-faq.json (3 hunks)
  • shared/locales/en/website-faq.json (2 hunks)
  • shared/locales/fr/website-faq.json (2 hunks)
  • shared/locales/it/website-faq.json (2 hunks)
  • website/src/middleware.ts (1 hunks)
🔇 Additional comments (7)
website/src/middleware.ts (1)

49-50: LGTM: New redirection case follows existing pattern.

The implementation is consistent with other redirection cases.

shared/locales/en/website-faq.json (2)

107-113: LGTM: Improved clarity in recipient selection criteria.

The updated text clearly states the age requirement and income criteria, with a helpful link to partners.


Line range hint 235-252: LGTM: Clear and comprehensive campaign-specific FAQ.

The campaign-ismatu section effectively explains:

  • Collaboration details
  • Fund distribution mechanism
  • Selection criteria for Ebola survivors
shared/locales/de/website-faq.json (1)

111-117: LGTM: German translation accurately mirrors English content.

The translation maintains consistency with the English version while being culturally appropriate.

Also applies to: 207-238, 239-252

shared/locales/fr/website-faq.json (1)

111-117: LGTM: Enhanced transparency with partner information

The addition of the partners link improves transparency around the beneficiary selection process.

shared/locales/it/website-faq.json (2)

111-117: LGTM: Consistent with French locale

The changes maintain consistency with the French version while preserving proper Italian localization.


207-238: LGTM: Well-translated campaign information

The campaign section maintains structural consistency with the French version while providing natural Italian translations.

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 (1)
website/src/app/[lang]/[region]/(website)/campaign/[campaign]/page.tsx (1)

Line range hint 316-351: LGTM with minor security enhancement suggestions

The FAQ section implementation is well-structured with proper type safety and accessibility. Consider these security enhancements for external links:

-<Link href={link.href} target="_blank" rel="noreferrer" className="no-underline">
+<Link href={link.href} target="_blank" rel="noopener noreferrer" className="no-underline">

Add noopener to prevent potential exploitation of window.opener API when opening external links.

🧰 Tools
🪛 Biome (1.9.4)

[error] 337-337: Avoid passing content using the dangerouslySetInnerHTML prop.

Setting content using code can expose users to cross-site scripting (XSS) attacks

(lint/security/noDangerouslySetInnerHtml)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between de1714b and 7f1d60e.

📒 Files selected for processing (1)
  • website/src/app/[lang]/[region]/(website)/campaign/[campaign]/page.tsx (3 hunks)
🔇 Additional comments (1)
website/src/app/[lang]/[region]/(website)/campaign/[campaign]/page.tsx (1)

28-28: LGTM: Import statement is correctly placed

The addition of the Next.js Link component import is appropriate for the new FAQ links feature.

@mkue mkue merged commit 4285c81 into main Dec 10, 2024
16 checks passed
@mkue mkue deleted the sandino/fundraiser-generic-faq branch December 10, 2024 17:12
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