AfroTech Directory
Searchable Event Data

What this project represents

I use the AfroTech Directory project to show how scattered event and community information can become a searchable product. People generate valuable links, sessions, resources, and recommendations, but that information often disappears into chats, notes, and one-off lists.

My approach is to turn that sprawl into a structured directory with clear ingestion, validation, tagging, and search. I am careful not to overstate fake outcomes here; the value is in the product pattern and the implementation thinking.

Problem: high-value information, low structure

Event communities often have the same pain points:

• Links and recommendations disappear into chat history.
• Speaker sessions or resources are hard to find later.
• Participants cannot quickly answer simple questions about what exists.

I treat a directory as a structured layer above the raw stream of messages and content.

Solution: a directory pipeline

I design directory products as a pipeline. First, I collect inputs from approved sources and keep provenance. Then I normalize items into a schema with fields like title, link, tags, summary, source, and timestamp.

From there, I add curation and validation so the directory does not become another messy pile. The final UI should support keyword search, tags, categories, and browsing without making maintenance painful.

Why it fits the broader portfolio

This project fits my broader work because it combines product thinking, data structure, and practical UI. The same patterns show up in community tools, internal knowledge bases, resource hubs, and searchable operational systems.