Stonk
A community homepage is a welcome sign and a map. It should help a first-time visitor understand the group, find the current update, read the rules, and decide whether to join.
The StonkBuilder Community has two useful starting points: the live community dashboard for Mindshare, the official feed, saved posts, and campaign status; and Discover for published creator community pages. The getting-started guide walks through both creator and member paths.
Start with one sentence about who the community is for. Put the current update, join path, rules, and event calendar near the top. Keep private member information behind the appropriate account flow. A public link page can introduce those destinations; it should not expose private balances, submissions, or moderation tools.
Link by StonkBuilder’s community path is designed to connect a simple public page with a deeper community home as the product supports it.
Use a clear navigation hierarchy instead of a long list of destinations. Keep announcements dated, archive finished events, and make contact or moderation routes easy to find. Test the homepage with a new member who has no internal context; their first questions reveal whether the information architecture is doing its job.
Make each destination understandable
Name the job of each page in plain language. A leaderboard should explain its time window, data source, and empty state. A community feed should distinguish dated snapshots from live posts and link back to the original source. A creator page should make its rules and next action easy to find. A campaign should show whether it is a draft, gated, or open before inviting someone to participate.
For StonkBuilder Community, saved posts are stored in the visitor's browser. Community points stay with the community that reviewed a contribution and are non-redeemable. Payments and redemptions are disabled, and X-action rewards are blocked by the current policy gate. Keep those boundaries near participation prompts, not buried in a separate policy page.
For a practical walkthrough of the dashboard's score, scope, and evidence boundaries, see how to read a community leaderboard.
When a feature uses a snapshot, show its date and do not fill missing data with made-up examples. A zero or empty state can be useful if it says what is missing and how a creator or member can take the next step.
Compare the page patterns in link-in-bio examples.
Last reviewed 2026-09-23.