Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

“Base Threaded Comments Styling” refers to a legacy CSS-Tricks example for styling nested WordPress comments—not to Basecamp. Treat its list-based selectors as a starting point, not drop-in CSS: WordPress says themes must be specially coded to display threaded comments properly, and your active theme’s rendered markup determines which rules will work.

What the base styling covers

The CSS-Tricks search-result excerpt for this title shows a traditional list-oriented approach, with selectors for a comment list, individual comments, author and avatar details, reply controls, child lists, and depth-specific styles. That structure can help distinguish replies from top-level comments, but the excerpt does not establish that the original code matches current themes or their markup.

In a threaded discussion, replies appear beneath their parent comment. Styling therefore has two jobs: make the relationship between parent and reply apparent, and keep each comment readable as nesting increases. A progressively indented layout is one possible visual cue; relying on indentation alone can leave deep replies with too little room, especially on narrow screens.

Enable threading and confirm theme support

In WordPress, open Settings → Discussion and enable threaded (nested) comments. The settings also let you choose the nesting depth, up to a maximum of ten levels. WordPress notes that themes need to be specially coded to display threaded comments properly, so the setting alone does not guarantee nested output.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
#1 Best Overall
WordPress 2.7 Cookbook
  • Used Book in Good Condition

The Discussion settings also support pagination of top-level comments. If a page has long discussions, consider how pagination and nesting work together in the theme: readers should be able to follow replies without losing their place or confusing separate threads.

Adapt the CSS to your theme’s actual markup

  1. Inspect the rendered comments. Open a page with comments and use your browser’s developer tools to inspect the comment list, comment items, child lists, reply links, and any depth-related classes. Identify the selectors the active theme actually renders.
  2. Review existing theme styles. Look for rules already controlling list indentation, margins, widths, avatars, metadata, and reply links. Adapt or override those rules rather than assuming an old example’s selectors are present.
  3. Apply styles to the markup you found. The older example’s selectors, such as ol.commentlist, child comment lists, and depth classes, are illustrative only. If your theme uses different elements or class names, those selectors will not reliably target its comments.
  4. Check different nesting depths and screen widths. Confirm that a reply remains visibly connected to its parent, while comment text still has enough width to read at deeper levels and on narrow screens. Adjust indentation or spacing when it consumes too much room.
  5. Test keyboard and heading behavior. Navigate reply controls and other interactive elements by keyboard, verify that focus remains visible, and ensure any headings used in comments follow a logical sequence.

Choose visual cues that preserve readability

Indentation, spacing, borders, or background differences can help readers distinguish nested replies. Whichever cues you use, make the parent–reply relationship easy to trace without shrinking the text area at every level. Check that author, date, and reply information remain identifiable and that links and controls are not obscured.

These are design checks rather than a tested recipe for a particular modern theme. There is no universal CSS rule set that can be recommended without matching it to the theme’s HTML and existing styles.

Keep the presentation accessible

  • Keyboard access: Check that reply links and other controls can be reached and used with a keyboard, and that the focus indicator stays visible.
  • Readable structure: If the comment design uses headings, keep their levels sequential rather than choosing a heading level just for its visual size.
  • Responsive layout: Review the deepest displayed replies on a narrow viewport as well as a wide one; avoid allowing indentation to leave an impractically narrow text column.
  • Clear metadata: Keep author and date details distinguishable from the comment body and reply controls.

These checks reflect general accessibility and component-design guidance, not a claim that the legacy CSS-Tricks snippet has been tested against a particular accessibility standard. See Basecamp’s accessibility guidance for general considerations such as focus visibility and keyboard navigation, and Atlassian’s comment component guidance for its recommendations on comment structure and heading order.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What CSS comments do

In a stylesheet, /* … */ marks a CSS comment. It is ignored by the browser and does not change the page layout. Use comments to explain why a rule exists, not as a way to activate styling; see MDN’s CSS comments reference.

Quick Recap

Bestseller No. 1
WordPress 2.7 Cookbook
WordPress 2.7 Cookbook
Used Book in Good Condition
$45.99
Bestseller No. 2
Bestseller No. 3
Bestseller No. 4
WordPress 2.8 Theme Design
WordPress 2.8 Theme Design
Used Book in Good Condition
$45.99
Rank #4
WordPress 2.8 Theme Design
  • Used Book in Good Condition

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.