PHPackages pennebaker/craft - 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. pennebaker/craft ActiveProject pennebaker/craft ================ pennebaker Craft 3 CMS scaffolding project 1.0.27(7y ago)743[1 issues](https://github.com/Pennebaker/craft/issues)MITJavaScriptPHP >=7.0.0 Since Nov 26Pushed 7y ago8 watchersCompare [ Source](https://github.com/Pennebaker/craft)[ Packagist](https://packagist.org/packages/pennebaker/craft)[ Docs](https://craftcms.com/)[ RSS](/packages/pennebaker-craft/feed)WikiDiscussions master Synced 6d ago READMEChangelogDependencies (51)Versions (19)Used By (0) About pennebaker/craft ---------------------- [](#about-pennebakercraft) This is an alternate scaffolding package for Craft 3 CMS projects to nystudio107's canonical [nystudio107/craft](https://github.com/nystudio107/craft) package. Brew Packages ------------- [](#brew-packages) nystudio107's ImageOptimize plugin may need some additional packages installed on OSX for valet to function. ``` brew install jpegoptim optipng svgo gifsicle pngquant pngcrush webp ``` Using pennebaker/craft ---------------------- [](#using-pennebakercraft) This project package works exactly the way nystudio107's [nystudio107/craft](https://github.com/nystudio107/craft) package works; you create a new project by first creating & installing the project: ``` composer create-project pennebaker/craft PATH ``` Make sure that `PATH` is the path to your project, including the name you want for the project, e.g.: ``` composer create-project pennebaker/craft craft3 ``` Create your dev database locally (ex. `yoursite_cmsdb_dev`) and use that database name for the next step. Then `cd` to your new project directory, and run Craft's `setup` console command to create your `.env` environments and optionally install: ``` cd PATH ./craft setup ``` Copy your local database name (ex. `yoursite_cmsdeb_dev`) into `pen-setup` under the section `LOCAL_DB_NAME` and set `default` to `yoursite_cmsdb_dev`. Finally, run the `pen-setup` command to configure Craft-Scripts & Craft 3 Multi-Environment based on your newly created `.env` settings: ``` ./pen-setup ``` That's it, enjoy! If you ever delete the `vendor` folder or such, just re-run: ``` ./pen-setup ``` ...and it will re-create the symlink to your `.env.sh`; don't worry, it won't stomp on any changes you've made. ### Valet Setup [](#valet-setup) ``` valet link domain valet secure domain ``` ### Yarn [](#yarn) For local gulp development use: ``` yarn start ``` For production build use: ``` yarn build ``` Below is the entire intact, slightly modified† `README.md` from nystudio107's [nystudio107/craft](https://github.com/nystudio107/craft): † Removed line about tailwindcss ..... About nystudio107/craft ----------------------- [](#about-nystudio107craft) This is an alternate scaffolding package for Craft 3 CMS projects to Pixel & Tonic's canonical [craftcms/craft](https://github.com/craftcms/craft) package. In addition to setting up a new Craft 3 CMS project, this project sets up: - [Craft 3 Multi-Environment](https://github.com/nystudio107/craft3-multi-environment) as described in the [Multi-Environment Config for Craft CMS](https://nystudio107.com/blog/multi-environment-config-for-craft-cms) article - [Craft-Scripts](https://github.com/nystudio107/craft-scripts) as described in the [Database & Asset Syncing Between Environments in Craft CMS](https://nystudio107.com/blog/database-asset-syncing-between-environments-in-craft-cms), [Mitigating Disaster via Website Backups](https://nystudio107.com/blog/mitigating-disaster-via-website-backups) & [Hardening Craft CMS Permissions](https://nystudio107.com/blog/hardening-craft-cms-permissions) articles ...and sets up some other base scaffolding as described to the following articles: - [A Better package.json for the Frontend](https://nystudio107.com/blog/a-better-package-json-for-the-frontend) - [A Gulp Workflow for Frontend Development Automation](https://nystudio107.com/blog/a-gulp-workflow-for-frontend-development-automation) - [Implementing Critical CSS on your website](https://nystudio107.com/blog/implementing-critical-css) - [Simple Static Asset Versioning in Craft CMS](https://nystudio107.com/blog/simple-static-asset-versioning) - [Enhancing a Craft CMS 3 Website with a Custom Module](https://nystudio107.com/blog/enhancing-a-craft-cms-3-website-with-a-custom-module) It also installs a few base plugins that I use on every project. You can read more about it in the [Setting up a New Craft 3 CMS Project](https://nystudio107.com/blog/setting-up-a-craft-cms-3-project) article. Assumptions Made ---------------- [](#assumptions-made) Since this is boilerplate that nystudio107 uses for projects, it is by definition opinionated, and has a number of assumptions: - Gulp is used as a the frontend workflow automation tool - [Vue](https://github.com/vuejs/vue) is used as the frontend JavaScript framework, with [Axios](https://github.com/axios/axios) providing the http client - Nginx with `ssi on;` is used as the web server - Redis is used as the PHP Session and Craft data caching method - Critical CSS is used site-wide - FontFaceObserver is used for font loading - Craft-Scripts are used for db/asset synching - Craft 3 Multi-Environment is used for the Craft 3 multi-environment setup Obviously you're free to remove whatever components you don't need/want to use. Using nystudio107/craft ----------------------- [](#using-nystudio107craft) This project package works exactly the way Pixel & Tonic's [craftcms/craft](https://github.com/craftcms/craft) package works; you create a new project by first creating & installing the project: ``` composer create-project nystudio107/craft PATH ``` Make sure that `PATH` is the path to your project, including the name you want for the project, e.g.: ``` composer create-project nystudio107/craft craft3 ``` Then `cd` to your new project directory, and run Craft's `setup` console command to create your `.env` environments and optionally install: ``` cd PATH ./craft setup ``` Finally, run the `nys-setup` command to configure Craft-Scripts & Craft 3 Multi-Environment based on your newly created `.env` settings: ``` ./nys-setup ``` That's it, enjoy! If you ever delete the `vendor` folder or such, just re-run: ``` ./nys-setup ``` ...and it will re-create the symlink to your `.env.sh`; don't worry, it won't stomp on any changes you've made. Below is the entire intact, unmodified `README.md` from Pixel & Tonic's [craftcms/craft](https://github.com/craftcms/craft): ..... About Craft CMS --------------- [](#about-craft-cms) Craft is a content-first CMS that aims to make life enjoyable for developers and content managers alike. It is optimized for bespoke web and application development, offering developers a clean slate to build out exactly what they want, rather than wrestling with a theme. Learn more about Craft at [craftcms.com](https://craftcms.com). How to Install Craft 3 Beta --------------------------- [](#how-to-install-craft-3-beta) Installation instructions can be found in the [Craft 3 documentation](https://github.com/craftcms/docs/blob/master/en/installation.md). Resources --------- [](#resources) #### Official Resources [](#official-resources) - [Craft 3 Documentation](https://github.com/craftcms/docs) - [Craft 3 Plugins](https://github.com/craftcms/plugins) - [Demo site](https://demo.craftcms.com/) - [Craft Slack](https://craftcms.com/community#slack) - [Craft CMS Stack Exchange](http://craftcms.stackexchange.com/) #### Community Resources [](#community-resources) - [Mijingo](https://mijingo.com/craft) – Video courses and other learning resources - [Envato Tuts+](https://webdesign.tutsplus.com/categories/craft-cms/courses) – Video courses - [Straight Up Craft](http://straightupcraft.com/) – Articles, tutorials, and more - [Craft Cookbook](https://craftcookbook.net/) – Quick answers for common tasks - [pluginfactory.io](https://pluginfactory.io/) – Craft plugin scaffold generator ### Health Score 30 — LowBetter than 64% of packages Maintenance17 Infrequent updates — may be unmaintained Popularity13 Limited adoption so far Community14 Small or concentrated contributor base Maturity67 Established project with proven stability Bus Factor1 Top contributor holds 50.2% 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 ~21 days Recently: every ~64 days Total 17 Last Release 2757d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/8ed3fd356bd09284c5dd6c8de466599777730ebe560d9a0aa0c2942b80264891?d=identicon)[spAnser](/maintainers/spAnser) --- Top Contributors [![khalwat](https://avatars.githubusercontent.com/u/7570798?v=4)](https://github.com/khalwat "khalwat (108 commits)")[![spAnser](https://avatars.githubusercontent.com/u/193938?v=4)](https://github.com/spAnser "spAnser (61 commits)")[![darith27](https://avatars.githubusercontent.com/u/3331878?v=4)](https://github.com/darith27 "darith27 (28 commits)")[![squiddot](https://avatars.githubusercontent.com/u/27028426?v=4)](https://github.com/squiddot "squiddot (18 commits)") --- Tags cmsprojectCraftcraftcms ### Embed Badge ![Health badge](/badges/pennebaker-craft/health.svg) ``` [![Health](https://phpackages.com/badges/pennebaker-craft/health.svg)](https://phpackages.com/packages/pennebaker-craft) ``` PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)