# Dapp

#### [Fork from](https://github.com/solana-labs/dapp-scaffold)

### [Getting Started](broken-reference) <a href="#user-content-getting-started" id="user-content-getting-started"></a>

This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).

The responsive version for wallets and wallet adapters may not function or work as expected for mobile based on plugin and wallet compatibility.&#x20;

### [Installation](broken-reference) <a href="#user-content-installation" id="user-content-installation"></a>

```
npm install
# or
yarn install
```

### [Build and Run](broken-reference) <a href="#user-content-build-and-run" id="user-content-build-and-run"></a>

Next, run the development server:

```
npm run dev
# or
yarn dev
```

Open [http://localhost:3000](http://localhost:3000/) with your browser to see the result.

You can start editing the page by modifying `pages/index.tsx`. The page auto-updates as you edit the file.

[API routes](https://nextjs.org/docs/api-routes/introduction) can be accessed at [http://localhost:3000/api/hello](http://localhost:3000/api/hello). This endpoint can be edited in `pages/api/hello.ts`.

The `pages/api` the directory is mapped to `/api/*`. Files in this directory are treated as [API routes](https://nextjs.org/docs/api-routes/introduction) instead of React pages.

### [Features](broken-reference) <a href="#user-content-features" id="user-content-features"></a>

Each Scaffold will contain at least the following features:

```
Wallet Integration with Auto Connect / Refresh

State Management

Components: One or more components demonstrating state management

Web3 Js: Examples of one or more uses of web3 js including a transaction with a connection provider

Sample navigation and page changing to demonstrate the state

Clean Simple Styling 

Notifications (optional): Example of using a notification system

```

A Solana Components Repo will be released in the near future to house a common components library.

#### [Structure](broken-reference) <a href="#user-content-structure" id="user-content-structure"></a>

The scaffold project structure may vary based on the front-end framework being utilized. Below is an example structure for the Next js Scaffold.

```
├── public: publically hosted files
├── src: primary code folders and files 
│   ├── Components: should house anything considered a reusable UI component
│   ├── contexts`: any context considered reusable and useful to many components that can be passed down through a component tree
│   ├── hooks`: any functions that let you 'hook' into react state or lifecycle features from function components
│   ├── models`: any data structure that may be reused throughout the project
│   ├── pages`: the pages that host metadata and the intended `View` for the page
│   ├── stores`: stores used in state management
│   ├── styles`: contain any global and reusable styles
│   ├── utils`: any other functionality considered reusable code that can be referenced
│   ├── views`: contains the actual views of the project that include the main content and components within
style, package, configuration, and other project files

```

### [Contributing](broken-reference) <a href="#user-content-contributing" id="user-content-contributing"></a>

Anyone is welcome to create an issue to build, discuss, or request a new feature or update to the existing code base. Please keep in mind the following when submitting an issue. We consider merging high-value features that may be utilized by the majority of scaffold users. If this is not a common feature or fix, consider adding it to the component library or cookbook. Please refer to the project's architecture and style when contributing.

If submitting a feature, please reference the project structure shown above and try to follow the overall architecture and style presented in the existing scaffold.

#### [Committing](broken-reference) <a href="#user-content-committing" id="user-content-committing"></a>

To choose a task or make your own, do the following:

1. [Add an issue](https://github.com/solana-dev-adv/solana-dapp-next/issues/new) for the task and assign it to yourself or comment on the issue
2. Make a draft PR referencing the issue.

The general flow for making a contribution:

1. Fork the repo on GitHub
2. Clone the project to your own machine
3. Commit changes to your own branch
4. Push your work back up to your fork
5. Submit a Pull request so that we can review your changes

**NOTE**: Be sure to merge the latest from "upstream" before making a pull request!

You can find tasks on the [project board](https://github.com/solana-dev-adv/solana-dapp-next/projects/1) or create an issue and assign it to yourself.

### [Learn More Next Js](broken-reference) <a href="#user-content-learn-more-next-js" id="user-content-learn-more-next-js"></a>

To learn more about Next.js, take a look at the following resources:

* [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
* [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.

You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!

### [Deploy on Vercel](broken-reference) <a href="#user-content-deploy-on-vercel" id="user-content-deploy-on-vercel"></a>

The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template\&filter=next.js\&utm_source=create-next-app\&utm_campaign=create-next-app-readme) from the creators of Next.js.

Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.
