Exploring the Hub: Find Entities, Activities, and Public Talent Stories

The hub is Talentelly’s public front porch. It is where someone who has never seen your admin console asks: “Is this program real?” “When is the next audition?” “Who beat whom last Sunday?” If your entity invests in the hub, you reduce repetitive DMs and build trust before anyone fills a form. Marketing pages like home, pricing, and contact often point people here once they understand the product at a high level.

What you can browse (and what it means in practice)

Entities — org profiles on paths like /hub/entity/{id}: who you are, what you run, how to contact you. Think “homepage lite.” You maintain the source data from Entity in admin.
Activities — dated, discoverable events, matches, tournaments, showcases—often surfaced from what you publish in Events, Matches, and Tournaments.
People — public profiles participants choose to polish; shared links commonly look like /hub/profile/{id}. Individuals edit the underlying fields from Account profile.
Artifacts — shareable certificates or print-friendly records when published—often tied to print and certificate URLs under /hub/certificate/{id}.

Example: Maya, a parent, hears about River Rowing Club at school pickup. She opens the hub, finds the entity, sees “Learn to Row — April intake” with clear times, and clicks through to registration info—without emailing a coach who is on the water.

A good first session (no admin login)

Start at hub home or a deep link someone sent you.
Search for a sport, city, school name, or program keyword.
Open an entity — skim about, upcoming, past highlights.
Open an activity — check schedule, location, results if posted (paths often include /hub/match/{id} or /hub/tournament/{id} when shared).
Optionally open a participant profile linked from a results page.

Example: A journalist covering a local chess tournament opens the public tournament page, screenshots standings from the hub (with attribution), and links readers to the same URL—readers get live updates after corrections, unlike a static JPEG.

For organizations: what “strong hub presence” looks like

Weak signal	Strong signal
Empty about text	Two short paragraphs: who you serve, what geography, what ages
Stale events from last year	Current season pinned; old events archived or clearly dated
No contact path	Monitored email or form; response-time expectation in text
Profile photos broken or generic	Real facility or team imagery where allowed

Example: Urban STEM Lab links /hub/entity/... from their Instagram bio instead of only a Google Form. Inbound leads rise because people see the same programs the sales rep describes on the phone.

For participants: polishing your public story

Before audition season: Update profile headshot, instrument or position, notable achievements—what you want selectors to see in ten seconds.
Privacy: Understand what is public vs account-only; when in doubt, ask your org’s policy for minors—see security.
Share deep links: Send /hub/profile/{id} to a mentor rather than a PDF export that goes stale after one edit.

Example: Kiran applies for a national theater camp. He pins two hub-visible productions on his profile and shares the certificate link from last summer’s festival—admissions sees consistent names and dates across artifacts.

Mobile and real-world constraints

Short titles on activities—long names truncate in list views on phones.
Venue clarity: “Stadium Gate 4” beats “Main ground” for families coordinating rides.
Time zones if you run online events across regions—state IST, UTC, or local explicitly in description text if the product does not auto-label.

Tips

Weekly hub hygiene (5 min): Confirm next two weeks of activities are accurate; fix typos before they become printed programs—coordinate with reports owners.
Deep links in comms: Coaches paste hub URLs in WhatsApp; screenshots are for celebration, not logistics.
SEO mindset: Use plain words parents actually search—“kids cricket Mumbai weekend” in natural prose beats internal jargon.