feat: rename static to assets.

[Levdbas]

Related:

• feat: rework of PHP files. #152
• feat: remove sidebar #153
• Feat: update composer file #154
• chore: cleanup license, rename and style.css #155
• feat: update template basis #156
• feat: rename static to assets. #157
• chore-add-pr-template #158
• chore: introduce phpcs and phpstan #159

Issue

Since the creation of the starter theme a lot has happened in PHP, WordPress and Timber. I want to make the starter-theme a more modern starting point for custom theme development.

The static folder is not really the way to go anymore in modern WordPress theme development.

Solution

This particular PR focusses on renaming the static folder to assets, make a sub-structure with .gitkeep files and remove the no-timber.html file.

Impact

a better starting point to start your theme development workflow.

Usage Changes

No

Considerations

• Not introducing all these folder?
• re-introduce a way to inform people that they have not installed Timber? That was once were the no-timber.html file was for.
• the style.css file is included in the head.html. I find myself using the enqueue functions to add compiled css/js files that way. Maybe we could one day in the future introduce a basic setup for this as well?

Testing

no

[gchtr]

• the style.css file is included in the head.html. I find myself using the enqueue functions to add compiled css/js files that way. Maybe we could one day in the future introduce a basic setup for this as well?

Let’s stick to wp_enqueue_style(). We don’t have to invent our own way to do it.