> For the complete documentation index, see [llms.txt](https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website/for-users/basic-user-manual.md).

# User manual

## First thing first: Install Napture.

<figure><img src="/files/QdDISvjRmCyyZ53RhtNx" alt=""><figcaption><p>Bussin Napture v1.2.2</p></figcaption></figure>

This is the guide to install **Bussin Napture**, the official Web X browser.

### Linux

* Download [Rust](https://www.rust-lang.org/tools/install). Then, you just need to open `install-linux.sh` as an executable (if you can't execute it, first do `sudo chmod +x ./install-linux.sh`, then you should be able to install).

### macOS

* Download [Rust](https://www.rust-lang.org/tools/install) and [Homebrew](https://brew.sh). Then, you just need to open `install-macos.sh` as an executable (if you can't execute it, first do `chmod +x ./install-macos.sh`, then you should be able to install).

### Windows

* Install the executable from the [release tab](https://github.com/face-hh/webx/releases). It's a self-extractor with WinRAR because it has a lot of DLLs.

### Arch Linux

Run **`yay -S napture`**. It's available on AUR.

### Nix\[OS]

**Flakes**: The repository provides a flake which exposes an overlay providing the webx package, so you could just add the input in your flake.nix file

```nix{3}
{
    inputs = {
        webx.url = "github:face-hh/webx";
    };
}
```

Then add it to your overlays and install it

```nix{3}
{ inputs, ... }: {
    nixpkgs.overlays = [
        inputs.webx.overlays.x86_64-linux.default
    ];
}
```

> For now, only tested on x86\_64-linux, but may work on others aswell, just change the arch

Add it to either home.packages (home manager) or environment.systemPackages (global packages).

```nix{2}
home.packages = with pkgs; [
    webx
];
```

Then you could just launch it using `webx` in your terminal.

{% hint style="info" %}
Go [here](https://github.com/face-hh/webx/releases) for the releases tab. Always download the **Latest** one.
{% endhint %}

## **Next: Using it!**

It's very easy. This is your startpage:

<figure><img src="/files/OGjbyLK8iBrDCfPR4wyQ" alt=""><figcaption><p>buss://dingle.it</p></figcaption></figure>

This is Dingle, WebX's official search engine. Just like a normal search engine, type in a query, and then click on one of the results to visit a website.

![Screenshot](/files/1F5399OpbAFYuFd4ZljV)

Websites may not have a description. That depends if the developer added a [description](/bussin-web-x-how-to-make-a-website/for-developers/html++.md#head-metadata-in-html) or not.

Also, don't forget you can click on the **Tab** name to bring up the **About** popup, which contains all the **shortcuts**.

And that's pretty much it! Enough to have some fun browsing the Web X.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://facedev.gitbook.io/bussin-web-x-how-to-make-a-website/for-users/basic-user-manual.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
