• do
InterCourses
CoursesBlogs
0
← DOM Manipulation with JavaScript
○The page is a tree○Exercise: follow the document reference○Load a script when the page is ready○Exercise: initialize a deferred script○Find one element by id or CSS selector○Exercise: select a notice and label○Compare DOM properties, HTML attributes, and node types○Exercise: inspect a room input and its nodes✦Module Quiz
○Find every match with querySelectorAll○Exercise: label every trail stop○Move from a child to its relatives○Exercise: trace a nested card○Check for missing elements and search within a card○Exercise: update only the chosen card○Compare a live HTMLCollection with a static NodeList○Exercise: safely expand a live collection✦Module Quiz
○Safe text and HTML○Exercise: render a safe notice○Read and change link attributes○Exercise: update an accessible link○Data attributes and conditional text○Exercise: announce session availability○Boolean attributes and DOM properties○Exercise: unlock a volunteer sign-up✦Module Quiz
○Add, remove, and check classes○Exercise: mark a favourite card○Toggle a panel accessibly○Exercise: toggle the help panel○Inline styles, classes, and hidden○Exercise: style and hide a notice○Change a CSS custom property from JavaScript○Exercise: change a workshop card accent✦Module Quiz
○Create and Append a Text Node○Exercise: Add a Reading List Item○Place Nodes Before and Between○Exercise: Order the Workshop Agenda○Remove, Replace, and Clear Safely○Exercise: Refresh a Museum Display○Clone a Card and Insert a Batch○Exercise: Clone Two Exhibit Cards✦Module Quiz
○Listen for Clicks with a Named Handler○Exercise: Check Library Hours○Event Target, Current Target, and Delegation○Exercise: Delegate Pantry Actions○Keyboard Events Without Trapping Keys○Exercise: Search the Recipe Box○Once, Remove, and Bubble○Exercise: Control Workshop Notifications✦Module Quiz
○Read a field while someone types○Build a live name preview○Handle submit without leaving the page○Validate a library request○Keep a selection in sync on change and reset○Sync a preference and its reset state○Read multiple checked values with FormData○Build a checkbox-based garden request✦Module Quiz
○Filter a list as someone types○Build a live trail finder○Toggle an accessible disclosure○Build a guide menu disclosure○Create and remove items with one delegated listener○Build a neighborhood task board○Sort a workshop table with accessible buttons○Build an accessible sortable resource table✦Module Quiz
○Read selectable cards and detail updates○Build directory cards and a selected profile○Trace live search and an empty state●Add live search to the community directory○Trace safe additions and delegated removal○Add and remove community directory cards✦Module Quiz
○Read and update a live itinerary○Build the workshop itinerary○Add a validated item through a form○Add a workshop session○Filter and remove live entries○Finish the workshop planner✦Module Quiz
○Fetch JSON and render safe text○Exercise: load recipe cards○Handle loading, empty, and failed responses○Exercise: handle alert states○Build a query with URLSearchParams○Exercise: search the catalog○Abort outdated requests○Exercise: keep the latest result✦Module Quiz
○Load a dashboard from an offline API fixture○Build an events dashboard○Query a dashboard with URLSearchParams○Add event search to the dashboard○Retry requests without stale results○Finish a resilient event dashboard✦Module Quiz

Add live search to the community directory

The starter is the completed card-selection directory from step one, with a labelled search field and status elements added. Selection already works; focus on filtering rather than rewriting it. The preceding bicycle-route demo used different IDs and route data.

Keep every member card in the DOM. On each input event, compare a trimmed, case-insensitive query against both its name and skill. Toggle hidden on each card, update the live count, and show the empty-state paragraph only when none match. Clearing the field must restore all cards.

Recall the route-search demo: filtering changes visibility, not the underlying list. In a different recipe index, a normalized query could drive one card like this:

javascript
const query = document.querySelector("#recipe-query").value.trim().toLowerCase();
const recipe = document.querySelector("[data-dish]");
recipe.hidden = !recipe.dataset.dish.toLowerCase().includes(query);

An empty string matches every dish. For the directory, repeat the comparison for every card, check both name and skill, count visible cards, and update the status and empty state together.

Your Task

  1. Make #result-count a polite live status with role="status" and aria-live="polite".
  2. Filter the three existing cards by name or skill on each input, ignoring case and surrounding spaces; clearing the query restores all three.
  3. Update #result-count to report the visible number of members after a search.
  4. Show #empty-state only when no cards match, and hide it again when results return.
  5. If filtering hides the selected card, clear its selected state and restore the detail panel’s default text.

Try BIKE, then zzz, then clear. The next step starts from this solution, so your selected-card behavior remains intact.

Loading editor…
READY
intercourses
javascript