Skip to content

Commit 2c87fa9

Browse files
eric-stacksgitbook-bot
authored andcommitted
GITBOOK-53: update Build A Frontend page
1 parent 47295b0 commit 2c87fa9

File tree

13 files changed

+43
-55
lines changed

13 files changed

+43
-55
lines changed

docs/build/SUMMARY.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,6 @@
9696
* [Creating a Bitcoin Transaction](more-guides/verify-bitcoin-transactions-clarity/creating-btc-tx.md)
9797
* [Parsing a Bitcoin Transaction](more-guides/verify-bitcoin-transactions-clarity/parsing-a-bitcoin-transaction.md)
9898
* [c32check](more-guides/c32check.md)
99-
* [Community Tutorials](more-guides/community-tutorials.md)
10099

101100
***
102101

docs/build/clarinet/overview.md

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,6 @@ For the latest releases and versions of Clarinet, check out the open-source repo
1616

1717
<div data-with-frame="true"><figure><img src="../.gitbook/assets/clarinet-diagram.png" alt=""><figcaption></figcaption></figure></div>
1818

19-
#### Announcements
20-
21-
{% updates format="full" %}
22-
{% update date="2025-11-05" %}
23-
## Clarinet was migrated to Stacks Labs
24-
25-
* The Clarinet repository now belongs to the stx-labs organization.
26-
* The NPM packages are now published under the `@stacks` organization.
27-
* The VSCode extension is now published under the Stacks Labs organization.
28-
* Check out the [announcement](/broken/pages/MJwczGlRXtiBGKy9CNxu) to see how to migrate older projects.
29-
{% endupdate %}
30-
{% endupdates %}
31-
3219
## Key features
3320

3421
* [**Leverage a powerful CLI**](https://app.gitbook.com/s/GVj1Z9vMuEOMe7oH7Wnq/clarinet/cli-reference) - Create new projects, manage your smart contracts and their dependencies using clarinet requirements, and interact with your code through the built-in REPL.

docs/build/get-started/build-a-frontend/README.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,20 +4,28 @@ description: Interact with your contracts with a proper frontend app
44

55
# Build a Frontend
66

7-
<figure><img src="../../.gitbook/assets/build-a-frontend.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/3-reasons-the-future-of-apps-will-be-decentralized">Hiro Blog</a></p></figcaption></figure>
7+
<div data-with-frame="true"><figure><img src="../../.gitbook/assets/build-a-frontend.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/3-reasons-the-future-of-apps-will-be-decentralized">Hiro Blog</a></p></figcaption></figure></div>
88

99
A major part of building full-stack Stacks applications is creating a well designed UI with a solid UX. One of your primary tools for this is stacks.js, a JavaScript/Typescript library that simplifies working with contracts, wallets, and the Stacks network.
1010

1111
{% hint style="info" %}
1212
This section assumes you have basic knowledge in front-end development and bootstrapping frontend frameworks.
1313
{% endhint %}
1414

15-
### Components to your Stacks frontend app
15+
### Basic components to your Stacks frontend app
1616

1717
* [Authentication](authentication.md)
1818
* [Post-Conditions](post-conditions.md)
1919
* [Sending Transactions](sending-transactions.md)
2020

21+
### Stacks brand designs for your app's UI
22+
23+
Access the latest Stacks brand design resources at [stacks.co/brand](https://stacks.co/brand). Find and download Stacks brand design materials directly from the linked Figma space.
24+
25+
{% embed url="https://www.figma.com/design/afyAaHa2vGCR0KU1BHiske/Stacks-Brand?node-id=256-790&t=qXPWrrQ10iytre1c-1" %}
26+
27+
***
28+
2129
### Additional Resources
2230

2331
* \[[Hiro Blog](https://www.hiro.so/blog/rich-app-templates-in-the-hiro-platform)] Rich App Templates in the Hiro Platform: Accelerating Web3 Development

docs/build/get-started/build-a-frontend/authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# Authentication
22

3-
<figure><img src="../../.gitbook/assets/authentication.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/navigating-the-tension-between-web3-privacy-and-data-transparency">Hiro Blog</a></p></figcaption></figure>
3+
<div data-with-frame="true"><figure><img src="../../.gitbook/assets/authentication.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/navigating-the-tension-between-web3-privacy-and-data-transparency">Hiro Blog</a></p></figcaption></figure></div>
44

55
Authenticating (connecting wallets) with a Stacks-supported wallet is a common task when building Stacks apps. On a web2 app, authentication usually means sending credentials to a central provider, which then verifies you and controls access. In web3, authentication uses a wallet and cryptographic signatures with libraries like stacks.js, letting users prove identity without a central party holding the keys.
66

77
{% hint style="info" %}
8-
To learn more about how wallets and accounts work with Stacks, check out this [section](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/network-fundamentals/accounts) in Learn.
8+
To learn more about how wallets and accounts work with Stacks, check out this [section](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/network-fundamentals/wallets-and-accounts) in Learn.
99
{% endhint %}
1010

1111
Below is a simple example showing how to set up front-end authentication with `@stacks/connect` and access user data in the UI. The stacks.js monorepo contains several underlying packages specific to different use cases. The package `@stacks/connect` is the main connectivity package used in Stacks.

docs/build/get-started/build-a-frontend/sending-transactions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Sending Transactions
22

3-
<figure><img src="../../.gitbook/assets/send-transactions.jpg" alt=""><figcaption></figcaption></figure>
3+
<div data-with-frame="true"><figure><img src="../../.gitbook/assets/send-transactions.jpg" alt=""><figcaption></figcaption></figure></div>
44

55
Any Stacks app is going to require sending transactions at some point, so how do we do that?
66

docs/build/get-started/clarity-crash-course.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: >-
66

77
# Clarity Crash Course
88

9-
<figure><img src="../.gitbook/assets/clarity.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/write-better-smart-contracts-with-the-programming-language-clarity">Hiro Blog</a></p></figcaption></figure>
9+
<div data-with-frame="true"><figure><img src="../.gitbook/assets/clarity.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/write-better-smart-contracts-with-the-programming-language-clarity">Hiro Blog</a></p></figcaption></figure></div>
1010

1111
### Intro
1212

docs/build/get-started/developer-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Your 0→1 guide for building a Clarity contract and app on Stacks.
44

55
# Developer Quickstart
66

7-
<figure><img src="../.gitbook/assets/Frame 316125324 (1).jpg" alt=""><figcaption></figcaption></figure>
7+
<div data-with-frame="true"><figure><img src="../.gitbook/assets/Frame 316125324 (1).jpg" alt=""><figcaption></figcaption></figure></div>
88

99
**Welcome to the Stacks Developer Quickstart Guide!**\
1010
This is your fast-track path for understanding what you'll need to become a Stacks developer. In this guide, you’ll build a real Clarity smart contract, wire up a functioning Stacks app, and pick up about 75% of the practical knowledge every Stacks builder needs. Whether you’re shipping your first project or leveling up your skills, this guide takes you from zero to deployed—quickly and confidently.

docs/build/more-guides/community-tutorials.md

Lines changed: 0 additions & 27 deletions
This file was deleted.

docs/build/more-guides/sbtc/bridging-bitcoin/btc-to-sbtc.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -230,6 +230,7 @@ You could also fetch the deposit data from the API client. This will return data
230230

231231
{% code expandable="true" %}
232232
```typescript
233+
// https://sbtc-emily.com/deposit/<initial-deposit-txid>
233234
let depositInfo = await client.fetchDeposit(txid) // txid of initial bitcoin deposit
234235

235236
// example depositInfo result below

docs/build/post-conditions/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how post-conditions protect users from unexpected transaction
44

55
# Overview
66

7-
<figure><img src="../.gitbook/assets/post-conditions.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/a-developers-guide-to-post-conditions">Hiro Blog</a></p></figcaption></figure>
7+
<div data-with-frame="true"><figure><img src="../.gitbook/assets/post-conditions.jpg" alt=""><figcaption><p>source: <a href="https://www.hiro.so/blog/a-developers-guide-to-post-conditions">Hiro Blog</a></p></figcaption></figure></div>
88

99
### What are post-conditions?
1010

0 commit comments

Comments
 (0)