# laravel.com-next

**Repository Path**: mirrors_laravel/laravel.com-next

## Basic Information

- **Project Name**: laravel.com-next
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2020-08-09
- **Last Updated**: 2025-10-19

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Laravel Website

This is the source of the official [Laravel website](https://laravel.com).

## Local Development

If you want to work on this project on your local machine, you may follow the instructions below. These instructions assume you are serving the site using Laravel Valet out of your `~/Sites` directory:

1. Fork this repository
2. Open your terminal and `cd` to your `~/Sites` folder
3. Clone your fork into the `~/Sites/laravel` folder, by running the following command *with your username placed into the {username} slot*:

    ```bash
    git clone git@github.com:{username}/laravel.com laravel
    ```

4. CD into the new directory you just created:

    ```bash
    cd laravel
    ```

5. Run the `setup.sh` bin script, which will take all the steps necessary to prepare your local install:

    ```bash
    ./bin/setup.sh
    ```

### Torchlight Integration

This project relies on Torchlight for syntax highlighting. You will need to create an account at [torchlight.dev](https://torchlight.dev/) and generate a free personal token for use in this project. Once generated, add your token to your .env file:

```ini
TORCHLIGHT_TOKEN=your-torchlight-token
```

### Syncing Upstream Changes Into Your Fork

This [GitHub article](https://help.github.com/en/articles/syncing-a-fork) provides instructions on how to pull the latest changes from this repository into your fork.

### Updating After Remote Code Changes

If you pull down the upstream changes from this repository into your local repository, you'll want to update your Composer and NPM dependencies, as well as update your documentation branches. For convenience, you may run the `bin/update.sh` script to update these things:

```bash
./bin/update.sh
```