PHPackages                             makewp/theme - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Framework](/categories/framework)
4. /
5. makewp/theme

ActiveLibrary[Framework](/categories/framework)

makewp/theme
============

Make WordPress themes, better.

0.2.0(1y ago)09MITPHPPHP >=7.4

Since Oct 7Pushed 3w ago1 watchersCompare

[ Source](https://github.com/makewp-dev/theme)[ Packagist](https://packagist.org/packages/makewp/theme)[ Docs](https://makewp-dev.github.io/theme)[ RSS](/packages/makewp-theme/feed)WikiDiscussions main Synced 1w ago

READMEChangelogDependenciesVersions (4)Used By (0)

MakeWP\\Theme
=============

[](#makewptheme)

> Make WordPress themes, better.

Opinionated development
-----------------------

[](#opinionated-development)

### File structure

[](#file-structure)

```
- blocks/      - blocks can be auto-registered
- functions/   - code-split functions.php
- parts/
- patterns/
- src/
  - scripts/    - JS files; built into ../scripts
  - styles/     - Sass files; built into ../styles
- scripts/      - JS files, built or no
- styles/       - CSS files, built or no
- templates/
- composer.json
- functions.php
- package.json
- style.css     - only [main stylesheet header fields]((https://developer.wordpress.org/themes/core-concepts/main-stylesheet/))
- theme.json

```

You can put your theme's CSS in `/styles` or, if you prefer Sass, put those files in `/src/styles` and they will be built into `/styles`. You can also do both of these, but be aware of file name conflicts. A Sass build step will overwrite existing files.

As with styles, the same pattern is available with `/scripts` and `/src/scripts`.

Load features
-------------

[](#load-features)

Declare the features you want. Only those files are required and run.

```
// functions.php