Skip to content

Style privacy policy#4

Merged
danmooney merged 1 commit into
mainfrom
develop
May 13, 2026
Merged

Style privacy policy#4
danmooney merged 1 commit into
mainfrom
develop

Conversation

@danmooney
Copy link
Copy Markdown
Owner

@danmooney danmooney commented May 13, 2026

Summary by CodeRabbit

  • Style

    • Significantly enhanced the visual appearance and responsiveness of the privacy policy page, including improvements to typography, color styling, content spacing, and layout optimization for mobile and tablet viewing experiences.
    • Updated the footer's privacy policy link to use the correct URL path.
  • Chores

    • Code formatting improvements and whitespace normalization.

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 13, 2026

📝 Walkthrough

Walkthrough

The PR updates the privacy policy link in the site footer from /privacy.html to /privacy, adds comprehensive embedded CSS styling to the privacy page covering layout, typography, links and responsive design, and normalizes trailing whitespace in stylesheet files.

Changes

Privacy Page Setup

Layer / File(s) Summary
Privacy page routing and styling
public/index.html, public/privacy.html
Footer privacy link updated to /privacy; public/privacy.html now includes embedded CSS defining theme variables, .content-section layout, typography (h1, h2, p, ul, li), link styling with hover behavior, and responsive max-width rules.
Whitespace normalization
src/styles/layout.css, src/styles/variables.css
Trailing whitespace removed from end-of-file closing brace in variables.css and blank line normalized within the @media (max-width: 600px) block in layout.css.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • danmooney/dict2json#3: Both PRs modify the footer privacy-policy link routing while establishing the /privacy page endpoint and styling.

Poem

🐰 A privacy page takes its graceful bow,
With CSS styling, all structured now,
The footer points true, no .html in sight,
Whitespace trimmed clean—design done right! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Style privacy policy' directly and specifically describes the main change in the changeset: adding CSS styling to the privacy policy page.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch develop

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

Copy link
Copy Markdown

@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

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@public/index.html`:
- Line 94: Update the anchor href that currently points to "/privacy" so it
targets the actual static file (change the <a href="/privacy"> link in
public/index.html to "/privacy.html") or alternatively add server-side/static
dev-server rewrite rules to map the path "/privacy" to "privacy.html" (modify
the anchor in index.html or configure your dev server's rewrite/history fallback
accordingly).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1979e858-3fa2-4a78-9139-658809f34eb3

📥 Commits

Reviewing files that changed from the base of the PR and between 5ff56c9 and 7f508ab.

📒 Files selected for processing (4)
  • public/index.html
  • public/privacy.html
  • src/styles/layout.css
  • src/styles/variables.css

Comment thread public/index.html
</ul>
<p class="affiliate-disclosure"><small>As an Amazon Associate, we earn from qualifying purchases. This site may contain affiliate links; we may earn a commission at no extra cost to you.</small></p>
<p><small><a href="/privacy.html">Privacy Policy</a></small></p>
<p><small><a href="/privacy">Privacy Policy</a></small></p>
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot May 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check what privacy page file exists in the repo and where /privacy is referenced.
fd -a 'privacy(\.html|/index\.html)$' public
rg -n 'href="/privacy"' public/index.html public/privacy.html

Repository: danmooney/dict2json

Length of output: 191


🏁 Script executed:

# Check for web server configuration files
find . -type f \( -name ".htaccess" -o -name "nginx.conf" -o -name "*.config.js" -o -name "vercel.json" -o -name ".netlify" -o -name "next.config.js" \) 2>/dev/null

Repository: danmooney/dict2json

Length of output: 106


🏁 Script executed:

# Check for other href patterns in index.html to see the general pattern used
rg -n 'href="/' public/index.html | head -20

Repository: danmooney/dict2json

Length of output: 199


🏁 Script executed:

# Check project type and main dependencies to understand deployment model
cat package.json 2>/dev/null | head -30

Repository: danmooney/dict2json

Length of output: 776


🏁 Script executed:

# Check for any README or deployment documentation
fd -i readme public . -x head -50 {} \;

Repository: danmooney/dict2json

Length of output: 45


🏁 Script executed:

cat webpack.config.js

Repository: danmooney/dict2json

Length of output: 907


🏁 Script executed:

# Check if privacy.html is referenced in the build process or if there's any routing/rewrite configuration
rg -n 'privacy' webpack.config.js

Repository: danmooney/dict2json

Length of output: 45


🏁 Script executed:

# Check the actual public directory structure to see what gets deployed
ls -la public/

Repository: danmooney/dict2json

Length of output: 473


Change /privacy link to /privacy.html or add server rewriting.

The link will 404 in the dev server and likely on most deployment platforms without URL rewriting configured. The actual file is privacy.html, but the href points to /privacy with no extension. The webpack configuration has no rewrite rules (no historyApiFallback or URL rewrites configured), and the static file serving in the dev server will not automatically resolve extensionless paths.

Either update the link to href="/privacy.html" or configure server rewriting rules to map /privacy to privacy.html.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@public/index.html` at line 94, Update the anchor href that currently points
to "/privacy" so it targets the actual static file (change the <a
href="/privacy"> link in public/index.html to "/privacy.html") or alternatively
add server-side/static dev-server rewrite rules to map the path "/privacy" to
"privacy.html" (modify the anchor in index.html or configure your dev server's
rewrite/history fallback accordingly).

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it works fine

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danmooney, thanks for confirming! I'll note that the /privacy route resolves correctly in your deployment setup so this isn't flagged again in future reviews.


✏️ Learnings added
Learnt from: danmooney
Repo: danmooney/dict2json PR: 4
File: public/index.html:94-94
Timestamp: 2026-05-13T14:44:09.330Z
Learning: In the `danmooney/dict2json` repository, the `/privacy` (extensionless) URL route works correctly and resolves to `public/privacy.html`. The server or deployment platform handles the extensionless URL rewriting automatically. Do not flag `/privacy` href links as potentially broken in this project.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

@danmooney danmooney merged commit d011b91 into main May 13, 2026
2 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.

1 participant