# Installation

URL: https://whitepaper.designervenkat.online/docs/coding-tutorials/installation
Markdown: https://whitepaper.designervenkat.online/llms.mdx/docs/coding-tutorials/installation
Site: White Papers - Designer Venkat
Author: Designer Venkat
Language: en

Clone the repository, install dependencies, and run the dev server in under a minute.





This guide walks through setting up a local copy of nxt-whitepapers — useful if you plan to contribute a paper, fork the project, or just want to read offline.

## Prerequisites [#prerequisites]

You'll need:

* **Node.js 20** or later (the build uses Turbopack, which expects modern Node)
* **npm 10** or later (or pnpm/yarn, but examples use npm)
* A terminal you're comfortable with

<Callout type="info">
  If you're on macOS and using Homebrew, `brew install node@20` will get you
  both Node and npm in one shot.
</Callout>

## Install [#install]

<Steps>
  <Step>
    ### Clone the repository [#clone-the-repository]

    Pull the source from GitHub. You can fork first if you plan to push changes back.

    <Tabs items="[&#x22;HTTPS&#x22;, &#x22;SSH&#x22;, &#x22;GitHub CLI&#x22;]">
      <Tab value="HTTPS">
        ```bash
        git clone https://github.com/your-org/nxt-whitepapers.git
        cd nxt-whitepapers
        ```
      </Tab>

      <Tab value="SSH">
        ```bash
        git clone git@github.com:your-org/nxt-whitepapers.git
        cd nxt-whitepapers
        ```
      </Tab>

      <Tab value="GitHub CLI">
        ```bash
        gh repo clone your-org/nxt-whitepapers
        cd nxt-whitepapers
        ```
      </Tab>
    </Tabs>
  </Step>

  <Step>
    ### Install dependencies [#install-dependencies]

    ```bash
    npm install
    ```

    This installs Next.js, Fumadocs, Tailwind, and a handful of MDX plugins. Expect 30–60 seconds on a cold cache.
  </Step>

  <Step>
    ### Start the dev server [#start-the-dev-server]

    ```bash
    npm run dev
    ```

    The site is now live at [http://localhost:3000](http://localhost:3000). Edits to `.mdx` files hot-reload — no restart needed.
  </Step>
</Steps>

## Verify [#verify]

Open the homepage and confirm the sidebar lists at least one section. If it's empty, the content pipeline hasn't picked up the MDX files — usually a stale `.source/` cache.

```bash
rm -rf .source
npm run dev
```

<Callout type="warn">
  Don't commit the `.source/` directory. It's generated at build time from
  `content/docs/` and is already in `.gitignore`.
</Callout>

## Next steps [#next-steps]

Once the dev server is running, head to [Configuration](/docs/coding-tutorials/configuration) to tailor the site name, theme, and search behavior. Or skip straight to [Writing your first whitepaper](/docs/coding-tutorials/first-whitepaper) if you're ready to publish.