Portal Community

Identity Fields

FieldDescriptionRequired
LogoSquare image (128x128px recommended). Displayed at the top of the profile and as icon on package cards.Strongly recommended
Display NameThe public-facing name of the publisher organization. Max 80 chars.Yes
Publisher SlugURL-safe identifier. Used in the profile URL: /publishers/{slug}. Set once, cannot be changed.Yes
BioShort description of the publisher — who you are, what you build, your specialty. Max 500 chars. Markdown supported.Strongly recommended
Website URLPrimary website or product page for the publisher organization.Recommended
Social LinksGitHub organization URL, LinkedIn page, Twitter/X handle. Up to 3 links.Optional
Member SinceAuto-set from publisher account creation date. Displayed on profile as "Member since [Month Year]".Automatic

Verified Domain Badge

Publishers who verify their domain ownership earn a blue verified checkmark displayed next to their name on the profile and on all their package cards. Domain verification is the primary trust signal that a publisher is who they claim to be.

Domain Verification Process

1

Enter Your Domain

In the Publisher Workspace settings, enter the domain you want to verify (e.g., acme-corp.com).

2

Get Your Verification Token

MarketHub generates a unique token: bizfirstai-verify=abc123def456

3

Add DNS TXT Record

In your DNS provider, add a TXT record for your domain with the verification token as the value. Propagation typically takes 5–60 minutes.

4

Verify

Click "Verify Now" in the Publisher Workspace. MarketHub performs a DNS lookup and grants the verified badge when the record is found. Verification is re-checked monthly.

Publisher tip: verify your domain on day one

Domain verification is the single highest-impact profile action for building user trust. Do it before publishing your first package — users who see an unverified publisher with no packages have no reason to invest attention in evaluating your work.