Build a daily.dev news site with rules you can actually test

Define the feed and the editorial layer separately

Thanks to daily.dev for sponsoring this video.

daily.dev supplies personalised feed data, metadata, images and original links. The app adds the presentation and editorial rules.

1. Identify the feed data the site needs and preserve original publisher links.
2. Use a server route for the private API token so it is not sent to the browser.
3. Describe what qualifies as Breaking, Worth Building and Deep Read before asking Claude to build the sections.

Inspect the first build with live stories

The first site looks polished, but the section classifications are not useful. A working search and attractive cards cannot establish editorial quality.

1. Test search, story links and discussion links on the first reveal.
2. Read representative original stories and compare them with their assigned section.
3. Record concrete misclassifications rather than asking for a vaguely smarter feed.
4. Revise the rules so each label reflects something a reader can verify.

Deploy and test the same questions again

The walkthrough uses GitHub and Netlify for deployment, then runs the real-world test and corrections.

1. Inspect the deployment and confirm the token remains in server-side configuration.
2. Repeat the search, source-link and classification checks on the live URL.
3. Compare the corrected section outputs with the saved failures.
4. Keep source attribution intact as you refine the presentation.

Adapt this brief

Build a news desk from this personalised feed. Keep its API token on the server and preserve publisher attribution and original links. Define observable rules for each section. Test the labels against real stories, list misclassifications and revise the rules before calling the site useful.

The takeaway

The roughly 20-minute build is an account of this example, not a delivery guarantee. A feed API supplies data; the editorial decisions still need testing.