> ## Documentation Index > Fetch the complete documentation index at: https://docs.dapp.ing/llms.txt > Use this file to discover all available pages before exploring further. # Publish programs and events > Run programs from your hub, with consent-based co-organizers and listings that close themselves when their dates pass. A conference week usually ends up spread across a landing page, a spreadsheet, and three group chats. Hackathons, grants, bounties, accelerators, events, and the calendars that hold a week together all publish from your hub instead. Publishing is free and unlimited on every plan. ## Choose the right container An **event calendar** is the durable frame for a place and date range; **events** attach to it or stand alone. A conference week works best as one calendar with each gathering listed on it, including gatherings other companies add. Hackathons, grants, bounties, and accelerators are their own types with their own lifecycles, so a grant reads as open or closed and a hackathon moves from upcoming through judging to completed. ## Co-organizers and sponsors join by consent Adding another company as a co-organizer or sponsor sends that company a request, and the relationship appears only after one of its owners or admins accepts. A newly named sponsor stays private until then. No company's brand lands on your listing without its consent, and yours never lands on another company's listing without yours. Each request records who asked, who answered, and when, so a joint program has a trail rather than a recollection. Accepted co-organizers can edit the listing, which is usually exactly what a joint program needs. ## Listings keep themselves honest Every program type closes itself when its governing date passes: a grant past its deadline reads closed, a hackathon past its end date reads completed, and closed listings rank below open ones everywhere. So a program never sits advertising itself as open weeks after it shut, and you never have to remember to prevent that. Two consequences worth planning around. A listing without an end date stays open until you close it, so give real programs real dates. And reopening is done by giving the listing a future date, which means extending a deadline is one edit, not a support request. ## Close the loop with attestations The difference between a program that ran and a program that compounds is the record it leaves. When yours ends, [attest the participants and winners](/for-companies/attest-participation-at-scale). The results become checkable proof on every participant's profile, credit your community board if you attach XP, and give your next recruitment round something checkable to point at: what the last cohort carries. ## What stays yours Publishing lists your program and keeps its state honest. Screening, judging, prize funds, and contracts stay with you, and the platform picks the work back up when the program ends and you [attest what happened](/for-companies/attest-participation-at-scale). Featuring is paid placement, arranged with the Dapping team rather than bought from a checkout: labeled, capped to a minority of any page, and expiring with the campaign. ## Continue on Dapping Publish a hackathon, grant, or event from your company hub. ## Related guides The calendar and event model, and how co-organizer requests resolve. The shared publishing flow every listing type uses. Leave verifiable proof behind when a program ends.