Don't version controll CSS and JS

Build a website from scratch with Statamic

In most cases or if deploy via any kind of automation (Laravel Forge, GitHub Actions, GitLab Pipelines ...), you don't want to version controll your CSS and JavaScript assets. I will show you how I am settings up assets for productions.

Introduction (1:52)
Why we won't use Peak (1:19)
A Statamic project overview (6:09)
The public folder (3:58)

Create layout and template files (11:17)
Activate the new Antlers parser (1:28)
Globals in Statamic and how they can be used (23:55)

Article collection and blueprint (8:59)
Optimize collections index view (3:11)
Update the user blueprint (2:27)

Which frontend options does Statamic offer (2:32)
Render a collection with Antlers (17:28)
A home blueprint and Antlers refactoring (14:10)

Compile CSS and Javascript with Laravel Mix (4:03)
Don't version controll CSS and JS (2:27)

Redirect to GitHub

Don't version controll CSS and JS

Build a website from scratch with Statamic

Before we start

Templating

Collections and Blueprints

Frontend with Antlers

CSS and JavaScript assets