> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/get-started/build-a-frontend.md).

# Build a Frontend

Interact with your contracts with a proper frontend app

<div data-with-frame="true"><figure><img src="https://284917788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZz9BLmTU9oydDpL3qiUh%2Fuploads%2FrfjDyteJnuvkHu2kJuBG%2Fbuild-a-frontend.jpg?alt=media&amp;token=06626a33-8dfe-4522-9e63-5b641c2c8301" alt=""><figcaption></figcaption></figure></div>

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.

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

### Basic components to your Stacks frontend app

* [Authentication](/get-started/build-a-frontend/authentication.md)
* [Post-Conditions](/get-started/build-a-frontend/post-conditions.md)
* [Sending Transactions](/get-started/build-a-frontend/sending-transactions.md)

### Stacks brand designs for your app's UI

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.

{% embed url="<https://www.figma.com/design/afyAaHa2vGCR0KU1BHiske/Stacks-Brand?node-id=256-790&t=qXPWrrQ10iytre1c-1>" %}

***

### Additional Resources

* \[[Hiro Blog](https://www.hiro.so/blog/lean-devops-strategies-for-your-web3-project)] Lean DevOps Strategies for Your Web3 Project
* \[[Hiro Blog](https://www.hiro.so/blog/introducing-stacks-js-starters-launch-a-frontend-in-just-a-few-clicks)] Introducing Stacks.js Starters: Launch a Frontend in Just a Few Clicks


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stacks.co/get-started/build-a-frontend.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.