Brain dump from new contributors to the platform

Thoughts from @IsaiahPaget:

• The fact that you have to commit the compiled assets. (It’s not yet obvious to me why there is not a php artisan winter:init command of some sorts (Potential feature?))
• How do the rest of the maintainers get around this issue where you have these settings tracked in the repo, after running npm i, composer install, php artisan mix:install, php artisan winter:install, php artisan winter:env, php artisan winter:mirror public --relative: I get this in my tracked changes.

=> git status
On branch develop
Your branch is up to date with 'origin/develop'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   config/app.php
        modified:   config/database.php
        modified:   config/mail.php
        modified:   modules/backend/assets/css/winter.css
        modified:   modules/backend/assets/less/layout/layout.less
        modified:   modules/system/traits/AssetMaker.php

no changes added to commit (use "git add" and/or "git commit -a")

• I was hoping to find a tutorial similar to the twitter clone on the Laravel site. Maybe something like that could go /blog/category/tutorials of the winter site
• Is there or would it be a welcome change to make a composer run dev feature like how it works in Laravel, such that when you change the asset files, like js, less, etc it automatically compiles, does that already exist? I see there is a mix:watch and vite:watch, but no single command that runs the server at the same time

Treat the report as several separate questions: inspect the tracked changes in config/app.php, config/database.php, config/mail.php, modules/backend/assets/css/winter.css, modules/backend/assets/less/layout/layout.less, and modules/system/traits/AssetMaker.php. Review the listed npm, composer, Artisan, mix:watch, and vite:watch commands first. Done requires narrowing this brain dump to a decided scope, with either clarified setup documentation or a specifically defined development-workflow feature.