Skip to content

Conversation

@tippi-fifestarr
Copy link
Contributor

Summary

Transforms the documentation landing page from a list of jargon into clear value propositions, and reorganizes content to prioritize what developers need most.

Key Changes

1. One-liners that explain value - Augmented links and jargon with brief descriptions of what each feature actually does:

  • "Randomness" → "Verifiable random numbers for fair games, lotteries, & drops."
  • "Keyless Accounts" → "Onboard users and sign without wallets or seed phrases"
  • "Query On-Chain Data (Indexer)" → explains it's GraphQL for balances, transactions, NFTs

2. Reorganized from 4 boxes to 6 boxes - Better content hierarchy addressing user feedback that developers "don't know where to go":

  • Getting Started (new, top-left) - Clear first steps
  • Tools - Moved AI Chatbot to top, highlighting AI-first developer experience
  • Smart Contracts (new) - Dedicated space for Move learning resources
  • On-Chain Features - Reordered to lead with Sponsored Transactions
  • Resources + Connect remain

3. Highlighted AI tooling:

  • MCP (AI coding assistant) with full description made prominent
  • AskAptos AI Chatbot moved to top of Tools
  • Added Vibe Code interactive tutorial from Learn

Technical: Added star and pencil icons to astro.config.mjs, hero buttons use down-arrow, added id="getting-started" anchor.

All changes consistently applied across English, Spanish, and Chinese versions.

Added NEW! to titles: Passkeys, Orderless, AI Development (MCP), AskAptos Chatbot

Features: rename Keyless -> Keyless Accounts; add one-liners (Keyless, Passkeys, Sponsored, Orderless, Randomness, Parallel Execution & ~250ms Blocks with Block-STM spelled out)

Tooling: add MCP at top with one-liner; add one-liners for CLI, Official SDKs, Indexer API, AskAptos Chatbot, Testnet Faucet; reorder SDKs (TS, Go, Java (soon!), Python, Rust, .NET)

Removed: VSCode Extension, Faucet API, Gas & Storage Fees, Fee Payer
- EN: tighten Tooling lines; move LLMs.txt to Resources; minor MCP/Chatbot phrasing

- ES: update Features/Tooling one‑liners; add MCP, Chatbot; add LLMs.txt (Recursos)

- ZH: update Features/Tooling one‑liners; add MCP, Chatbot; add LLMs.txt(资源)

- Fix: internal link to /llms-txt (was /build/llms-txt)
@vercel
Copy link

vercel bot commented Oct 10, 2025

@tippi-fifestarr is attempting to deploy a commit to the AptosLabs Team on Vercel.

A member of the Team first needs to authorize it.

@gregnazario gregnazario requested review from gregnazario and moonclavedev and removed request for moonclavedev October 17, 2025 20:06
@gregnazario gregnazario force-pushed the feat/landing-page-refresh branch from aa32727 to b1df3a9 Compare October 20, 2025 01:01
@vercel
Copy link

vercel bot commented Oct 20, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
aptos-docs Ready Ready Preview Comment Oct 20, 2025 1:10am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

@moonclavedev
Copy link
Collaborator

moonclavedev commented Oct 23, 2025

Hey @tippi-fifestarr! We need to do something about the formatting here. The additional context for these links might be helpful (and possibly contribute to homepage SEO), however the font size and line height creates way too much cognitive load on the page for this component in it's current form, as <LinkList> wasn't designed to be used in this way:

image

Also, anytime we have "NEW!" - it should never be inlined as part of the text content for the item - but rather used as a badge like this: https://starlight.astro.build/components/badges/ - however this component might also need to be updated to allow for this.

I would say this PR bleeds into design system conversation / component architecture to provide a better UX for a change like this.

@gregnazario

@tippi-fifestarr
Copy link
Contributor Author

Hey @moonclavedev, great feedback - I totally agree! I plan on spending some more time on this next week to improve the formatting even more.

That being said, this change addresses a couple issues I've seen in user testing (namely, people not being able to find the "Your First Move Module", and people not knowing what the Aptos jargon means). From the user testing I've done, new users have a much easier time finding the right link now (they do end up doing a bit of reading) instead of glancing at it and then clicking around in the sidebar.

Would it be alright to take improving the formatting as a follow up item?

  • Line height / spacing / text size
  • Badges
  • Design system conversation / component architecture

The next couple weeks I'm also working on the the Getting Started page, and want to be pulling that into the landing page and out of Guides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants