-
Notifications
You must be signed in to change notification settings - Fork 81
Base MiniKit Docs Revamp #200
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
base: master
Are you sure you want to change the base?
Conversation
…Growth pillars; add manifest doc; add starters; introduce mini-kit CLI (lint-copy, validate-assets, doctor, scaffold); add CI workflow and issue template; update templates/starters guide; add TASKS.md
🟡 Heimdall Review Status
|
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v4 | ||
- uses: actions/setup-node@v4 | ||
with: | ||
node-version: "18" | ||
- name: Install CLI deps | ||
run: npm ci --prefix tools/minikit-cli || npm install --prefix tools/minikit-cli | ||
- name: Run doctor (Base App only) | ||
run: node tools/minikit-cli/bin/mini-kit.mjs doctor docs/base-app |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 10 days ago
To fix the problem, add a permissions
block to the workflow to explicitly set the minimum required permissions for the GITHUB_TOKEN
. Since the workflow appears to only check out code and run a CLI tool, it likely only needs read access to repository contents. The best way to fix this is to add permissions: contents: read
at the top level of the workflow file, just below the name
key and above the on
key. This will apply the permission restriction to all jobs in the workflow. No other changes are needed.
-
Copy modified lines R1-R2
@@ -1,3 +1,5 @@ | ||
permissions: | ||
contents: read | ||
name: MiniKit Doctor | ||
on: | ||
pull_request: |
@@ -0,0 +1,20 @@ | |||
name: MiniKit Doctor |
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.
suggestion: Could we scale this PR back to just the docs update for now? There's a lot going on in this action and I don't think it's currently running, so it's also hard to verify.
I'd also ask that we get rid of the starters/*
folder, since we have templates and examples in the onchainkit repo. We've spread that sort of thing around in the past, and IMO it'd be nice to keep it it one place. The onchainkit repo makes the most sense to me, as we run tests against the templates when we make changes to OnchainKit.
PR: Base MiniKit Docs Revamp — Comprehensive Change List
Navigation and IA
docs/docs.json
(Base App tab):base-app/miniapps/manifest
to Quick StartNew pages (Base App)
Quality Bar & Publishing
docs/base-app/quality/checklist.mdx
: Mandatory Quality Bar checklistdocs/base-app/quality/getting-featured.mdx
: Featuring criteria and processdocs/base-app/quality/submission-workflow.mdx
: Submission guidedocs/base-app/quality/validation.mdx
: Local and CI validation instructionsDesign & UX Standards
docs/base-app/design/principles.mdx
: HIG-inspired principles for webviewdocs/base-app/design/ui-patterns.mdx
: Copy-paste patterns (first-run, skeletons, optimistic UI, toast vs modal)docs/base-app/design/accessibility.mdx
: Safe areas, motion, semantics, contrastdocs/base-app/design/figma-ui-kit.mdx
: Figma kit (placeholder link)Performance & Assets
docs/base-app/performance/budgets.mdx
: Budgets (TTI, TBT, CLS, payload caps) + optimization snippetsdocs/base-app/performance/asset-specifications.mdx
: Unified spec with sizes/bytes + server/CDN guidancedocs/base-app/performance/optimization-techniques.mdx
: Practical recipes (preload, responsive images, caching)Supporting Guides
docs/base-app/guides/authentication.mdx
: Guest‑first patterns; browse-first vs action-gated flowsdocs/base-app/guides/language-tone.mdx
: Copy rules (ban jargon, outcome‑oriented CTAs)docs/base-app/guides/error-handling.mdx
: Error taxonomy and UX patternsdocs/base-app/guides/templates-starters.mdx
: Starters overview + local usageGrowth & Analytics
docs/base-app/growth/event-schema.mdx
: Recommended events (MINI_APP_OPEN, TX_SUCCESS, etc.)docs/base-app/growth/analytics-integration.mdx
: PostHog/Segment examplesdocs/base-app/growth/distribution-categories.mdx
: Category guidance and dos/don’tsQuick Start adjunct
docs/base-app/miniapps/manifest.mdx
: Manifest schema with explicit byte capsNew tooling
tools/minikit-cli
bin/mini-kit.mjs
lint-copy [path]
: Scans for banned terms, ignores code fences/inline code, prints suggestionsvalidate-assets [path]
: Validates dimensions/byte caps for icon/splash/hero/OGdoctor [path]
: Runs copy + assets checksscaffold <name> --template=... --immediate-auth=true|false
: Creates starter skeletons (browse-first, action-gated)minikit.config.json
.github/workflows/mini-kit.yml
→ runsmini-kit doctor
on PRs.github/ISSUE_TEMPLATE/miniapp-featuring-request.md
(Featuring request template)Starter templates (local)
starters/
:starters/browse-first
: Guest‑first browse value → optional personalize → gate actionsstarters/action-gated
: Value-first screen; optional immediate auth in scaffoldstarters/game-loop
: Daily streak mechanic (customizedsrc/App.tsx
)index.html
,src/main.tsx
,src/App.tsx
,package.json
,README.md
docs/base-app/guides/templates-starters.mdx
explains local runNotable edits
figma-ui-kit.mdx
Follow-ups (not in this PR)