feat: rename static to assets. (#157)

- Remove no-timber.html since it's no longer in use - Introduce sub structure in the assets folder for modern development - Update readme file to reflect these changes
timber · May 14, 2024 · 0129442 · 0129442
1 parent 9d50b75
commit 0129442
Show file tree

Hide file tree

Showing 6 changed files with 1 addition and 11 deletions.
diff --git a/README.md b/README.md
@@ -25,7 +25,7 @@ Small tip: You can make use of Composer’s [autoloading functionality](https://
 
 ## What else is there?
 
-- `static/` is where you can keep your static front-end scripts, styles, or images. In other words, your Sass files, JS files, fonts, and SVGs would live here.
+- `assets/` is where you can keep your front-end scripts, styles, or images. In other words, your Sass files, JS files, fonts, and SVGs would live here.
 - `views/` contains all of your Twig templates. These pretty much correspond 1 to 1 with the PHP files that respond to the WordPress template hierarchy. At the end of each PHP template, you’ll notice a `Timber::render()` function whose first parameter is the Twig file where that data (or `$context`) will be used. Just an FYI.
 - `tests/` ... basically don’t worry about (or remove) this unless you know what it is and want to.
 

diff --git a/assets/fonts/.gitkeep b/assets/fonts/.gitkeep
diff --git a/assets/images/.gitkeep b/assets/images/.gitkeep
diff --git a/static/site.js → assets/scripts/site.js b/static/site.js → assets/scripts/site.js
diff --git a/assets/styles/.gitkeep b/assets/styles/.gitkeep
diff --git a/static/no-timber.html b/static/no-timber.html