你刚刷到这条消息，本来准备顺手划走，但又怕自己错过了真正会影响下一步判断的那一点。
最容易做错的，是sponsors / calesthio；代价往往是如果只盯表面热闹，你很容易在错误方向上花掉时间、预算和注意力。；我先给一个保守判断：Sponsor页先写任务，不先写权益。。
Here is the call: a Sponsor page should lead with the work, not the perks.
Why I think that: GitHub's own setup points that way. A Sponsors profile can feature up to 6 repositories, which is a fairly direct signal that the page should foreground the work and the outcomes funding makes possible.
Paid tiers are optional, and that detail matters. GitHub allows up to 10 one-time tiers and 10 monthly tiers, but that cap is a ceiling, not a script. This is not an anti-tier take. It is an order-of-operations take.
OpenMontage makes the stronger case in practice. The persuasive material shows up before the sponsor ask: 演示（demo） output, cost, 工作流程（workflow）, and platform entry points. The README is doing the conversion work before the button does. A post is worth your time not because it lists more features, but because it changes your next decision.
What to do with that: this read is based on the GitHub Sponsors docs and the current OpenMontage public materials I reviewed on June 25, 2026. If you're about to rewrite a Sponsor page, move the work above the perk table first. If you know a maintainer doing that now, share this with them before they build the benefits grid.
真正该讨论的是：sponsors / calesthio