Skip to content

Conversation

@0xLisanAlGaib
Copy link
Contributor

Summary

This PR refocuses the Cadence homepage to position the language as the premier choice for building Consumer DeFi applications, moving away from generic smart contract messaging.

Key Changes

Messaging & Positioning:

  • Updated hero section to emphasize "Build the future of Consumer DeFi"
  • Changed site tagline from "Best Programming Language for Smart Contracts" to "Best Programming Language for Consumer DeFi"
  • Reframed all content through the lens of financial application development

Code Example:

  • Replaced NFT example with Vault resource demonstrating DeFi primitives (deposit, withdraw, balance management)
  • Better showcases resource-oriented programming for handling financial assets

Content Updates:

  • Security Section: Emphasized how user assets staying in accounts (vs contract storage) dramatically reduces attack surfaces and makes exploits exponentially harder
  • Composability Section: Added Flow Actions and Scheduled Transactions as key differentiators for building sophisticated DeFi experiences
  • Scale Section: Highlighted infrastructure readiness (1M+ MAU, fast finality, low costs) and rapid development cycles
  • Transactions Section: Focused on atomic DeFi operations (swap + stake + deposit) instead of NFT examples
  • Removed "Easy to learn" and "Tooling" sections to focus on DeFi value propositions

Strategic Links Added:

  • Flow Actions documentation
  • Scheduled Transactions documentation
  • Cadence getting started guide
  • Resource-oriented programming docs

Target Audience

DeFi developers building financial applications for mainstream consumer audiences who need:

  • Institutional-grade security
  • Consumer-friendly UX
  • Fast time-to-market
  • Infrastructure that scales to millions of users

This positioning aligns with Flow's strategic focus on Consumer DeFi and targets developers building the next generation of accessible financial applications.

Update homepage to emphasize Cadence as the premier language for building Consumer DeFi applications. Changes include:

- Update hero section and tagline to focus on Consumer DeFi
- Replace NFT code example with DeFi Vault resource demonstrating financial primitives
- Reframe intro text to highlight resource-oriented security model and user asset protection
- Emphasize DeFi-specific security benefits and attack surface reduction
- Add Flow Actions and Scheduled Transactions as key differentiators
- Highlight infrastructure scalability, low costs, and fast development cycles
- Focus feature sections on DeFi use cases: composability, atomic transactions, and consumer scale
- Update meta description and site tagline
- Add strategic links to developer resources

The new positioning targets DeFi developers building financial applications for mainstream audiences.
@vercel
Copy link

vercel bot commented Nov 6, 2025

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

Project Deployment Preview Comments Updated (UTC)
cadence-lang-org Ready Ready Preview Comment Nov 13, 2025 11:19pm

Update the homepage code example to showcase DeFi-specific features:
- Demonstrates Flow Actions composing atomic operations (claim → swap → restake)
- Shows Scheduled Transactions for recurring automation
- Better illustrates the unique capabilities that enable Consumer DeFi
- Updated syntax highlighter to support transaction keywords and comments

This example directly showcases the key differentiators mentioned in the homepage content.
Copy link
Contributor

@briandoyle81 briandoyle81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking so we can validate example code with cadence engineer

@chasefleming
Copy link
Member

A few notes:

  • Can we make the code window wider? Seeing what's happening in the tx is cutoff.
  • What about adding a few bullet points higher up the page describing why its built for DeFi before we dive down lower to read more detail?
  • The card sections feel a little long to read. Could these be shortened?
  • The text/video and cards are misaligned.
  • The page "Flow Actions" links to could use a description of what Flow Actions are.
  • Why a backpack image for "built to scale?"

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.

5 participants