1132 policies and data

[erinz2020]

1. cherry-pick 17 bumps prs in this pr
2. add privacies and data menu in header -> Resources. it has 3 sub menus: privacy policies, terms of use, and citing wildbook
3. add flag to control show/hide how to photograph page
4. add a new page About us, under Resources
5. add wildbook documentation under Resources
6. move individual gallery and encounter calendar from "Animals" to "Data"

PR fixes #1132

[codecov-commenter]

Codecov Report

❌ Patch coverage is 27.17391% with 134 lines in your changes missing coverage. Please review.
✅ Project coverage is 52.54%. Comparing base (a486d20) to head (bac8445).

Files with missing lines	Patch %	Lines
...tend/src/pages/PoliciesAndData/PoliciesAndData.jsx	0.00%	83 Missing ⚠️
frontend/src/pages/HowToPhotograph.jsx	0.00%	20 Missing ⚠️
...tend/src/components/header/HeaderDropdownItems.jsx	65.62%	11 Missing ⚠️
frontend/src/pages/AboutUs.jsx	0.00%	5 Missing ⚠️
...ages/ReportsAndManagamentPages/ReportEncounter.jsx	50.00%	5 Missing ⚠️
frontend/src/constants/navMenu.js	40.00%	3 Missing ⚠️
frontend/src/pages/Login.jsx	40.00%	3 Missing ⚠️
frontend/src/AuthenticatedSwitch.jsx	66.66%	2 Missing ⚠️
frontend/src/UnAuthenticatedSwitch.jsx	71.42%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1402      +/-   ##
==========================================
- Coverage   53.36%   52.54%   -0.83%     
==========================================
  Files         274      278       +4     
  Lines        9918    10066     +148     
  Branches     2955     3097     +142     
==========================================
- Hits         5293     5289       -4     
- Misses       4378     4524     +146     
- Partials      247      253       +6     

Flag	Coverage Δ
backend	52.54% <27.17%> (-0.83%)	⬇️
frontend	52.54% <27.17%> (-0.83%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[erinz2020]

@claude You are reviewing a code change as a senior engineer in an existing production codebase.

Your goal is to find only the most important issues that should realistically be addressed before merge.

Review principles:

Prioritize correctness, reliability, data flow, async behavior, state consistency, and real maintainability risks.
Do not comment on personal preference, code style, naming, or optional refactors.
Do not propose architecture changes unless the current implementation is clearly dangerous or broken.
Respect existing project conventions and favor minimal changes.
Do not invent missing requirements.
Be conservative: if something is acceptable, do not flag it.
Pay special attention to:

null / undefined access
React effect dependency mistakes
stale closures
race conditions
duplicate or inconsistent state
controlled/uncontrolled form issues
loading / error / empty-state logic
accidental rerenders with real impact
incorrect assumptions around async requests, polling, or derived data
Output:

Start with one line only:

"No merge-blocking issues found"
or "Found X important issues"
Then provide up to 3 issues only.

For each issue, use:

Severity: blocker | high | medium
Location: file / function / component
Problem:
Impact:
Minimal fix:
Do not include praise.
Do not include optional improvements.
Do not include “consider”, “might”, or “could” comments unless there is a concrete risk.

[erinz2020]

@claude You are reviewing a code change as a senior engineer in an existing production codebase.

Your goal is to find only the most important issues that should realistically be addressed before merge.

Review principles:

Prioritize correctness, reliability, data flow, async behavior, state consistency, and real maintainability risks.
Do not comment on personal preference, code style, naming, or optional refactors.
Do not propose architecture changes unless the current implementation is clearly dangerous or broken.
Respect existing project conventions and favor minimal changes.
Do not invent missing requirements.
Be conservative: if something is acceptable, do not flag it.
Pay special attention to:

null / undefined access
React effect dependency mistakes
stale closures
race conditions
duplicate or inconsistent state
controlled/uncontrolled form issues
loading / error / empty-state logic
accidental rerenders with real impact
incorrect assumptions around async requests, polling, or derived data
Output:

Start with one line only:

"No merge-blocking issues found"
or "Found X important issues"
Then provide up to 3 issues only.

For each issue, use:

Severity: blocker | high | medium
Location: file / function / component
Problem:
Impact:
Minimal fix:
Do not include praise.
Do not include optional improvements.
Do not include “consider”, “might”, or “could” comments unless there is a concrete risk.

[claude]

Claude finished @erinz2020's task in 3m 32s —— View job

---

No merge-blocking issues found

Two findings from the previous review were false positives and are now corrected:

• Lazy imports: All three new pages (HowToPhotograph, AboutUs, PoliciesAndData) are already wrapped in React.lazy() in both AuthenticatedSwitch.jsx and UnAuthenticatedSwitch.jsx. There are no static imports to fix.
• Nav menu href mismatch: Both the authenticated menu (line 71) and unauthenticated menu (line 362) in navMenu.js already use ?section=privacy_policy as the "Policies and Data" parent href. There is no inconsistency.

The async PDF loading in PoliciesAndData.jsx correctly uses a cancelled flag to prevent stale state updates on fast section switching. The agree checkbox logic is consistently enforced in both Login.jsx (button disabled state) and ReportEncounter.jsx (button disabled state + runtime guard in handleSubmit). URL/state sync via the sectionParam effect is sound.

[JasonWildMe]

Reviewed with Codex. Approved. Thank you for addressing feedback.