-
Notifications
You must be signed in to change notification settings - Fork 109
Add Get Featured Section & Requirements #327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Heimdall Review Status
|
docs/docs.json
Outdated
@@ -450,6 +450,12 @@ | |||
"mini-apps/quickstart/launch-checklist" | |||
] | |||
}, | |||
{ | |||
"group": "Get Featured", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Get Featured on Base App is more descriptive
@@ -0,0 +1,122 @@ | |||
--- | |||
title: "Requirements for Featured Placement" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, was even thinking of adding an "Overview" page in this section that provides more context and details on the submission process. Then keeping this "Requirements" page focused on the raw requirements
To submit your app for featured placement, fill out the [submission form](https://buildonbase.deform.cc/getstarted/). | ||
</Info> | ||
|
||
In order to be eligible for featured placement, your app must meet the requirements outlined in this document. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will likely need to add a disclaimer that completing all the requirements doesn't guarantee being featured, and it also depends on XYZ criteria (active users, onchain actions, retention, transaction volume etc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, can reach out to Arman about the right disclaimer language.
Approved review 3211953756 from hughescoin is now dismissed due to new commit. Re-request for approval.
|
||
## Client-Agnostic | ||
|
||
There must be no client‑specific behaviors or wording that degrade the experience in the Base app. You must also ensure that you don't redirect the user to another client for functionality supported in the Base app. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should call out using the sdk actions over deeplinks
**Acceptance criteria** | ||
- Do not hardcode client‑specific URLs (e.g., Farcaster‑only links) | ||
- Use neutral language in UI (e.g. use "Share to Feed" instead of "Share to Farcaster") | ||
- Eliminate buttons that deeplink to other clients for features supported in the Base app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we dont need to call this out imo because we now support every sdk action other than notifications and add miniapp
Added the Get Featured Section.
As of now, this section only has one document, the "Requirements" document.