Skip to main content

Cross-Module Integration

Placement rules per surface

Placement rules per surface — documentation pending.

Complete

The Related Ecosystem Signals block has a specific position on every surface — always above the subscribe block, below the primary content. Position is locked because the user’s reading intent flows in this order: content → context → next-action.

Per-surface placement (locked)

Opportunity Detail
After eligibility & how-to-apply blocks. Before related opportunities. The reasoning: a user who has decided to apply needs preparation context next, not more options.
Founder Profile
After bio + linked startup section. Before social / contact. The reasoning: establish who, then surface the context around them.
Startup Showcase
After traction / market sections. Before team grid. The reasoning: market context flows into people behind it.
Founder File Reader
At ~80% scroll depth, after "What you’ll learn" or before the sponsor block. The reasoning: the reader is engaged; high-intent for next action.
Calendar Event Detail
After event details, before footer subscribe CTA. The reasoning: final ecosystem layer before the subscribe block.
Events Coverage
After article body, before Inline Signal CTA. Mirrors the editorial article placement.
Editorial Article
After article body, before Inline Signal CTA + next-article. The reasoning: complete the read, then offer context.

Universal placement constraints

  1. NEVER above the fold. Detail pages must serve their primary purpose first.
  2. ALWAYS above the footer. Do not bury below subscribe CTAs.
  3. SINGLE instance per page. No two Related Ecosystem Signals blocks on the same surface.
  4. Inline-Signal-CTA component goes AFTER. Order: content → related signals → subscribe → footer.
  5. Mobile = horizontal swipe-scroll. Do not stack 6 cards vertically on a phone.