This is the third post from my n8n intake classifier, a practice project for a fictional automation agency that I built with an AI collaborator. The first was about the classification prompthttps://coderlegion.com/31215/each-fix-to-my-classification-...

In my previous posthttps://tarek-elzoghby.hashnode.dev/each-fix-to-my-classification-prompt-exposed-the-next-problem, I wrote about the problems I found while defining the categories for an AI intake classifier. I left ambiguous and invalid for anoth...

In my previous posthttps://tarek-elzoghby.hashnode.dev/each-fix-to-my-classification-prompt-exposed-the-next-problem, I wrote about the problems I found while defining the categories for an AI intake classifier. I left ambiguous and invalid for anoth...

This comes from my first n8n project with an LLM in it: an intake classifier for an automation agency. It's a practice brief, so the agency and the client are fictional, and I built it with an AI collaborator. The workflow and my full process notes a...

This comes from my first n8n project with an LLM in it: an intake classifier for an automation agency. It's a practice brief, so the agency and the client are fictional, and I built it with an AI collaborator. The workflow and my full process notes a...

Originally published on Hashnode: https://tarek-elzoghby.hashnode.dev/what-a-100-accessibility-score-didn-t-check Lighthouse gave my practice site a 100 for accessibility. Then I went through it by hand, checking what Lighthouse doesn't, and found a...

Agents and screen readers share the same semantic layer. A green Accessibility category is not proof that money-page actions have roles, names, and landmarks machines can use. The accessibility tree is the structured layer the browser builds from th...

This is the second half of a two-part writeup on an n8n lead-intake workflow. Part11 covered the Webhook payload break — this one covers the rest of the build. The first post about this workflow covered the Webhook payload break — the moment the Fo...