• 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

Build an events dashboard

Your community events page already has a list, status region, and Retry button. Its dashboardFetch is a declared offline fixture returning real Response objects, not a network call. Use the preceding trail demo as a model. The starter already fetches and parses JSON in loadEntries() and connects Retry; finish render() first, then add loading/error handling to loadEntries().

Here is a different inventory-list pattern for safe DOM text. replaceChildren() clears old results before inserting new nodes:

javascript
const shelf = document.querySelector("#shelf");
shelf.replaceChildren();
for (const product of products) {
  const row = document.createElement("li");
  row.textContent = product.name;
  shelf.append(row);
}

For your dashboard, the starter reads { items } from the fixture response; make one row per event. Before awaiting it, show Loading and clear old rows. A non-OK response must show an error with a visible Retry button. On success, show the count or an explicit empty message. Run the preview: the fixture includes a title with literal <em> characters; it must never create an em element.

Your Task

  1. In render(items), create safe text-only title and venue rows in #entries and announce the number found in #status. The request/JSON setup in loadEntries() is already supplied.
  2. Show Loading entries… as soon as a load starts, while its response Promise is pending.
  3. Check failed HTTP responses, show an error, and reveal Retry; clicking Retry starts a new load and hides the button after success.
  4. When the fixture returns zero items, clear prior rows and announce No matching entries..

A real endpoint belongs at the dashboardFetch(API_URL) call; use fetch("https://your-cors-enabled-api.example/events") there only when a service permits cross-origin browser requests via CORS and returns the documented { items } shape. This exercise remains fully offline.

Loading editor…
READY
intercourses
javascript