Added Acing the Frontend Interview

[stjepanjurekovic]

Hi,

Stjepan from Manning here. I thought this title might be a good match for your list. Thank you for considering it.

Best,

What does this PR do?

Which issue is this PR related to?

If not related to any issue leave blank.

Does this PR follows our contribution guidelines?

Summary by CodeRabbit

• Documentation
  • Updated the Books section to include “Acing the Frontend Interview” with a link to the publisher.
  • Clarifies available learning resources without altering application behavior.
  • No changes to features, APIs, or configuration.

[coderabbitai]

Walkthrough

A documentation-only update adds a new book entry, “Acing the Frontend Interview,” with a link to Manning, under the Books section of README.md. No code, API, or behavioral changes.

Changes

Cohort / File(s)	Summary
Documentation README.md	Added a new bullet for "Acing the Frontend Interview" with a Manning link under the Books section; no code/API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers, flip a page,
A book hops in—new learning stage!
No code disturbed, just docs that gleam,
A tidy shelf for the frontend dream.
Thump-thump—approved! 📚🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

README.md (2)

373-373: Place the new book in alphabetical order within Books.

Awesome lists prefer alphabetical sorting. Move this entry to the top of the Books list to keep ordering consistent.

 ## Books :books:
 
+* [Acing the Frontend Interview](https://www.manning.com/books/acing-the-frontend-interview) – Stand out from the crowd in frontend interviews.
 * [CSS: The Definitive Guide, 4th Edition](http://shop.oreilly.com/product/0636920012726.do)  - Visual Presentation for the Web
 * [CSS: The Missing Manual](http://shop.oreilly.com/product/0636920036357.do) – Really Helpful in Advancing your Design Skills to a whole new Level
 * [CSS Secrets](http://shop.oreilly.com/product/0636920031123.do) – Better Solutions to Everyday Web Design Problems
 * [Every Layout: Relearn CSS Layout](https://every-layout.dev/) – Solving responsive layout problems using algorithmic design.
 * [Tiny CSS Projects](https://www.manning.com/books/tiny-css-projects) – Improve the way you write CSS as you build 12 tiny projects.
-
-* [Acing the Frontend Interview](https://www.manning.com/books/acing-the-frontend-interview) – Stand out from the crowd in frontend interviews.

---

373-373: Confirm list-marker style vs markdownlint MD004.

Static analysis flags “Expected: dash; Actual: asterisk”, but this file predominantly uses asterisks. Either keep asterisks and adjust markdownlint config, or switch the entire file in a separate PR—don’t mix markers within a section.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 7d0f2e4 and c26f014.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

README.md

373-373: Unordered list style
Expected: dash; Actual: asterisk

(MD004, ul-style)

🔇 Additional comments (1)

README.md (1)

373-373: Scope check: is this book CSS-focused enough for this list?

The title targets frontend interviews broadly, not CSS specifically. Please confirm it aligns with the list’s scope or suggest a more fitting section.