Add an ANAF contact link and text to FAQ

[danniel]

Summary by CodeRabbit

• Documentation

  • Added new FAQ section explaining Code for Romania's role in platform support and technical assistance, with ANAF contact information for user inquiries.

• Chores

  • Updated translation infrastructure across multiple languages to support new content strings.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Updated translation catalogs (English, Armenian, Romanian) with new Code for Romania strings and adjusted source reference line numbers. Added explanatory paragraph to FAQ template detailing Code for Romania's role supporting the Redirecționează platform and providing ANAF contact information.

Changes

Cohort / File(s)	Summary
Translation Catalogs backend/locale/en/LC_MESSAGES/django.po, backend/locale/hy/LC_MESSAGES/django.po, backend/locale/ro/LC_MESSAGES/django.po	Updated POT-Creation-Date timestamps. Adjusted source file reference line numbers for donations/views/common/search.py and templates/v2/components/input/search-box.html. Added new translation entries for Code for Romania description and footer link with empty msgstr fields.
FAQ Content backend/templates/v2/public/faq.html	Added new paragraph block within the FAQ section explaining Code for Romania's role in supporting the platform and providing technical support, including a link to contact ANAF.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hop, hop, translations grow anew,
In English, Armenian, Romanian too,
FAQ blooms with guidance clear,
Code for Romania's purpose near,
A whisker's worth of helpful care! 🌟

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding ANAF contact information to the FAQ section.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/anaf-contact-link

---

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

[danniel]

Fixes #601

[greptile-apps]

Greptile Summary

Added a new informational paragraph to the FAQ page clarifying that Code for Romania provides technical support for the platform, while ANAF handles questions about the redirection procedure itself. The change includes a link to ANAF's contact page.

• Added new <p> element with ANAF contact information to faq.html
• Provided Romanian translation in ro/LC_MESSAGES/django.po
• English and Armenian translations marked as pending (empty msgstr)
• Updated line number references in all locale files due to code changes elsewhere

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Simple content addition to FAQ page with proper i18n handling, no logic changes or potential breaking changes
• No files require special attention

Important Files Changed

Filename	Overview
backend/templates/v2/public/faq.html	Added new paragraph with ANAF contact link and clarification about support scope
backend/locale/ro/LC_MESSAGES/django.po	Added Romanian translation for new ANAF contact text, updated line references
backend/locale/en/LC_MESSAGES/django.po	Added English message template for ANAF contact text (translation pending), updated line references
backend/locale/hy/LC_MESSAGES/django.po	Added Armenian message template for ANAF contact text (translation pending), updated line references

_{Last reviewed commit: a769f73}