Repository navigation
Redesign the README: banner, Example walkthrough, flow card and status - #40
Merged
Merged
Conversation
- Add a banner, Example-mode walkthrough and flow cards (light and dark) rendered from a local production build in docs/readme/ - Restructure into How it works, Ecosystem integrations, Markets and flags, Status, Run it locally and Documentation; long reference material moves into collapsible sections - Fix the RVAClassic link (it pointed at x.com/operatoruplift) and document npm 11, which CI pins: npm 10 cannot run npm ci on this lockfile - Cover every .env.example variable and all migrations in the deploy steps; drop the undated 737-of-832 DBC badge count Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01TZhsuWjATuivuiFYJGpbY5
- Description from the project's own one-liner, homepage lotline.dev (the metadataBase, sitemap and Supabase site_url), and the GitHub repository; the lockfile is unaffected Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01TZhsuWjATuivuiFYJGpbY5
- Restore the redesign delivery, technical walkthrough, pitch source and historical screenshots links from the old Product materials list Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01TZhsuWjATuivuiFYJGpbY5
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The README was a long verification document with no visuals. This rebuilds it in the same house style as the Allowance README, so Lotline, RWA Lens, Buffer and Allowance read as one family, in Lotline's own forest green.
.env.example. Deploy, storage and limits, install and Seeker, dependency review and repository layout move into collapsible sections.Fixes:
x.com/operatoruplift; it now points atx.com/rvaclassic.npm ciwithout an npm version. With npm 10 (Node 22's bundled npm, 10.9.4 here)npm cistops withMissing: [email protected] from lock file; CI installs npm 11 first for exactly this reason. The README now says so.supabase/migrations/. It now says to apply all of them in timestamp order (supabase db push) and keeps the guest-execution caution.package.jsongainsdescription,homepageandrepository(separate commit; the lockfile is unaffected).Removed or folded in, with the reason:
All images live in
docs/readme/(five PNGs, about 1 MB). Screenshots come from a local production build (npm run buildandnext start, no credentials) in Example mode, so every figure on them is synthetic. The three phone screens come fromdocs/dapp-store/screenshots, captured from lotline.dev byscripts/generate-store-kit.mjs.Checks
npx -y npm@11 ci: installed 793 packages. Plainnpm ciwith npm 10.9.4 fails as described above.npm run lint: passed with zero warnings.npm run typecheck: passed.npm test: 74 files passed, 3 skipped; 783 tests passed, 4 skipped.npm run build: passed (Next.js 16.4.3), with no Supabase or RPC credentials.test:e2eandtest:e2e:markets), which need a CI-style build with fixture Supabase settings. CI runs both on every push and pull request, and this PR changes no application code.main(4 high, 4 moderate). Dependency changes are out of scope here; the high-severity Meteora SDK chain is analysed indocs/dependency-review-20260926.md.Suggested repository settings
These live outside the code, so they are not in this PR:
https://lotline.devalready matches the app'smetadataBase, sitemap and Supabasesite_url.nextjs,pwa,solana,supabase,xstocks; consider addingtoken-2022,tokenized-stocks,jupiter,pythandsolana-mobile.docs/readme/banner.png(2400 × 1200) under Settings → General → Social preview.https://claude.ai/code/session_01TZhsuWjATuivuiFYJGpbY5
Generated by Claude Code