PHPackages                             cornell-custom-dev/laravel-starter-kit - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. cornell-custom-dev/laravel-starter-kit

ActiveLibrary[Framework](/categories/framework)

cornell-custom-dev/laravel-starter-kit
======================================

Cornell University Custom Development Laravel Starter Kit

v0.4.0(1y ago)1200[4 issues](https://github.com/CornellCustomDev/CD-LaravelStarterKit/issues)[3 PRs](https://github.com/CornellCustomDev/CD-LaravelStarterKit/pulls)MITPHPPHP ^8.2

Since Jan 10Pushed 8mo ago14 watchersCompare

[ Source](https://github.com/CornellCustomDev/CD-LaravelStarterKit)[ Packagist](https://packagist.org/packages/cornell-custom-dev/laravel-starter-kit)[ RSS](/packages/cornell-custom-dev-laravel-starter-kit/feed)WikiDiscussions main Synced today

READMEChangelog (5)Dependencies (8)Versions (14)Used By (0)

Laravel Starter Kit
===================

[](#laravel-starter-kit)

A Cornell University CIT Custom Development starter kit and library for Laravel.

Goals
-----

[](#goals)

- Reduce time to build Laravel apps
- Increase consistency in configuration, third-party packages, and architecture
- Increase code visibility, code quality, and team collaboration
- Continuously improve code and practices
- Lower barriers for support and reduce support time

Usage
-----

[](#usage)

The Starter Kit can be used [as a starter kit for a new site](#as-a-starter-kit-for-a-new-site) or [as a library for an existing site](#as-a-library-for-an-existing-site).

### As a Starter Kit for a New Site

[](#as-a-starter-kit-for-a-new-site)

Used as a starter kit, this package deploys the cwd\_framework\_lite infrastructure and standard configuration files. The steps below get from a fresh Laravel install to a working site.

1. Follow [standard Laravel project creation](https://laravel.com/docs/9.x/installation#your-first-laravel-project), namely

    ```
    composer create-project --no-dev laravel/laravel your-app-name
    ```

    This is done with the `--no-dev` option, because we will be committing the vendor dir and don't need that extra baggage.

    > **NOTE**: If you have GitHub CLI installed, you can immediately add this to GitHub as a repo with the following commands (be sure to replace the "your-app-name" references with your project info):
    >
    > ```
    > cd your-app-name
    > git init
    > git add . && git commit -m "Initial commit"
    > git branch -m main
    > gh repo create --private CU-CommunityApps/CD-your-app-name
    > git push --set-upstream origin main
    > ```
2. Composer require the LaravelStarterKit

    ```
    composer require --update-no-dev cornell-custom-dev/laravel-starter-kit
    ```

    Similar to the `create-project` option, the `--update-no-dev` keeps us from adding baggage to the vendor dir.
3. Install the Starter Kit

    ```
    php artisan starterkit:install
    ```

    The `starterkit:install` command prompts for a set of install options:

    - publish configured [project files](project) to the base directory and update the `composer.json` file to match
    - publish HTML/CSS/JS theme assets from [cwd\_framework\_lite](https://github.com/CU-CommunityApps/cwd_framework_lite)
    - publish a set of [view components](https://laravel.com/docs/10.x/blade#layouts-using-components) that can be used to begin a layout
    - publish [example blade files](resources/views/examples) to see usage of the layout

    > **NOTE**: The "project files" option updates `.gitignore` so that the vendor directory is no longer excluded. The next commit will be large because it includes everything in the vendor directory.
    >
    > ```
    >  git add . && git commit -m "Starter Kit install"
    >  git push
    > ```
4. Testing the site
    You can confirm the site is working with Lando, since the Starter Kit install process adds a `.lando.yml` file.

    ```
    lando start
    ```

    Then visit  and you should see the default Laravel page. To see the Laravel Starter Kit example page, edit `/resources/views/welcome.blade.php` to be:

    ```
    @include('cd-index')
    ```

### As a Library for an Existing Site

[](#as-a-library-for-an-existing-site)

For an existing Laravel site, this package can be composer-required to provide the library of classes and optionally install some components.

1. Composer require the LaravelStarterKit

    ```
    composer require cornell-custom-dev/laravel-starter-kit
    ```
2. Install the Starter Kit

    ```
    php artisan starterkit:install
    ```

    Note: When using as a library or updating an installation, you will not want to install the project files. You may still want to install the theme assets, view components, and possibly example files. Be aware that these will overwrite existing files.

Libraries
---------

[](#libraries)

The libraries included in the Starter Kit are documented in their respective README files:

- [Contact/PhoneNumber](src/Contact/README.md): A library for parsing and formatting a phone number.
- [CUAuth](src/CUAuth/README.md): A middleware for authorizing Laravel users, mostly for Apache mod\_shib authentication.

Deploying a site
----------------

[](#deploying-a-site)

Once a Media3 site has been created, you have confirmed you can reach the default site via a web browser, and you have access to the site login by command line, the code can be deployed.

You will likely need to map the `php` command to the correct version by editing `~/.bashrc` to include this alias (for this to take effect, run `source ~/.bashrc` or just log in again):

```
# User specific aliases and functions
alias php="/usr/local/bin/ea-php81"
```

Since `www/your-site/public` will already exist, you need to do a little moving things around to git clone your site repo from GitHub:

```
cd www/your-site
mv public public.default
git clone --bare https://github.com/CU-CommunityApps/CD-your-app-name.git .git
git init && git checkout main
```

At this point you can configure the `www/your-site/.env` file:

```
cp .env.example .env
php artisan key:generate
nano .env
```

Be sure to set your `APP_*` values to appropriate values, based on whether it is production:

```
APP_NAME="Your Site"
APP_ENV=production
APP_DEBUG=false
APP_URL=https://your-site.edu
```

```
APP_NAME="Your Site - TEST"
APP_ENV=testing
APP_DEBUG=true
APP_URL=https://test.your-site.edu
```

If you visit your site now, you should see the Laravel site working.

Contributing
------------

[](#contributing)

Anyone on the Custom Development team should be welcome and able to contribute. See [CONTRIBUTING](CONTRIBUTING.md) for details on how be involved and provide quality contributions.

###  Health Score

30

—

LowBetter than 62% of packages

Maintenance31

Infrequent updates — may be unmaintained

Popularity12

Limited adoption so far

Community14

Small or concentrated contributor base

Maturity56

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 95.1% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~163 days

Recently: every ~120 days

Total

6

Last Release

451d ago

PHP version history (2 changes)v0.1.0PHP ^8.1

v0.4.0PHP ^8.2

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/5258410?v=4)[Eric Woods](/maintainers/woodseowl)[@woodseowl](https://github.com/woodseowl)

![](https://avatars.githubusercontent.com/u/5116057?v=4)[Irina Naydich](/maintainers/inaydich)[@inaydich](https://github.com/inaydich)

---

Top Contributors

[![woodseowl](https://avatars.githubusercontent.com/u/5258410?v=4)](https://github.com/woodseowl "woodseowl (176 commits)")[![richmarisa](https://avatars.githubusercontent.com/u/6989734?v=4)](https://github.com/richmarisa "richmarisa (9 commits)")

###  Code Quality

TestsPHPUnit

Code StyleLaravel Pint

### Embed Badge

![Health badge](/badges/cornell-custom-dev-laravel-starter-kit/health.svg)

```
[![Health](https://phpackages.com/badges/cornell-custom-dev-laravel-starter-kit/health.svg)](https://phpackages.com/packages/cornell-custom-dev-laravel-starter-kit)
```

###  Alternatives

[filament/support

Core helper methods and foundation code for all Filament packages.

2331.0M245](/packages/filament-support)[ysfkaya/filament-phone-input

A phone input component for Laravel Filament

3161.3M24](/packages/ysfkaya-filament-phone-input)[nasirkhan/laravel-starter

A CMS like modular Laravel starter project.

1.4k2.7k](/packages/nasirkhan-laravel-starter)[stephenjude/filament-jetstream

A Laravel starter kit built with Filament inspired by Jetstream.

17760.2k3](/packages/stephenjude-filament-jetstream)[relaticle/custom-fields

User Defined Custom Fields for Laravel Filament

16354.2k](/packages/relaticle-custom-fields)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
