As I discover new technologies, I find my boilerplates evolving and getting better (and more complicated). This project was helped along by several other boilerplates out there. I wanted a project starter that fit my development style with all of the technologies I use in most of my projects.
This boilerplate is setup using Webpack to devlop on a local server (You can use Nitro/Docker or even Mamp, use whatever you want). the dev script will allow you to hot reload your changes, it will output files to the /dev directory, which is where your local server should point its root to.
The build script will output all production files to the /public_html directory. Included is a VSCode sftp configuration that is setup to automagically ftp any updates to that /build directory into your server. You will need to configure that. Read below for full instructions.
Use Node.js (NPM or yarn) scripts to run build tools.
$ yarn dev - Launches webpack-dev-server and recompiles files whenever they change$ yarn build - Creates production ready code inside the /public_html directory and ftp sync'd to the serverAfter running $ yarn dev or $ yarn build, your deploy-ready code will be taken from the ./src/ directory and placed within the ./public_html/ and ./cms/templates/ directories respectively.
This project scaffolding is rather opinionated and makes use of the following tools, open source projects, and architecture methodologies:
To start, run this command in your project directory.
$ cd my-project
$ git clone https://github.com/kinoli/craft-bootstrap-sass-vue-boilerplate ./{Tip} I'f you want to repoint your git origin to start using your own remote repo. Run this command.
$ git remote set-url origin git@gitlab.[YOUR-SERVER].com:GROUP/REPO-NAME.git
In the project folder run:
$ yarn
// or
$ npm installCraft has created this super simple tool to run a local dev server for Craft within Docker. It will hardwire your local environment specifically for Craft and in my experience removes all the headaches of setting up and configuring a Docker environment on your own. Use it.
Note: You need to have Docker installed and running at this point.
// install Nitro globally with Homebrew
brew tap craftcms/nitro
brew install nitro
// initialize nitro and add the containers. Make sure you point to the dev directory for your server root.
nitro init
nitro addNow run the craft install script.
nitro craft installAdd your domain to the cms/.env file, the dev webpack server uses it
PRIMARY_DOMAIN=my-domain.nitroNow, run the web server so you can load the Craft installation. This will copy the necessary files into your /dev directory and setup hot reloading for watching changes to vue components and Craft/Twig templates
yarn dev{tip} That
.envfile will be processed via [PHP dotenv], which thecraftcms/craftproject comes with preinstalled. The advantage of using PHP dotenv is that it offers a place to store sensitive information (like database connection settings) in a file that doesn’t get committed to your Git repository.
Some helpful commands to run during your workflow
// show all available nitro commands
nitro
// start up nitro - fires up all of the docker containers
nitro start
// stop nitro - brings all of the docker containers down
nitro stop
// fire up the development server for Vue
yarn dev
// fires up Storybook for rapid UI component development (Use this for Vue development)
yarn storybook
// run unit tests
yarn test
// This will update your redactor styling based on your website styling and what you add in _redactor-custom.scss
yarn redactorLogin to your craft installation at /admin and navigate to the Utilities tab and run all the updates so your CraftCMS installation is up to date.
Here are some plugins that I like to use on my websites. These can all be installed within your craft configuration at /admin.
Deployment is done by running yarn build and everything in the /public_html directory needs to be sync'd to your server, as well, any changes in your /cms/templates directory.
To do ftp deployment through your IDE's ftp sync from /public_html and /cms to your webserver. Note, the /cms directory should be a level above your public root directory.
This boilerplate has sftp config setup for VSCode, which I highly recommend, but not required. A sample vscode config file is included in /.vscode/sftp.json, you can simply configure it as needed.
Deployment should be automated, but thats up to you to decide how you want to do it. After you do a yarn build, just upload the following...
There is likely a way to automate this either through github, gitLab or even Webpack, but it currently is not setup yet.
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.
I am an experienced full-stack web/app contractor from Canada. I'm always available to assist with questions or bug fixes or to hire (if you need more of my time).
My website: JesseKnowles.com