a0d2892cad
As WPCS and PHPCompatibility were for a little while (May - July 2017) not compatible with PHPCS 3.x, the library tags cloned were previously fixed to prevent issues with that.
As both WPCS as well as the PHPCompatibility standard are now compatible with PHPCS 3.x, the changes made in PR 1110 and PR 1183 can be reverted.
Notes:
* PHPCS - use `master`.
WPCS uses a limited set of sniffs from PHPCS itself.
Most of these sniffs are long established, stable and rarely get updated, so using PHPCS `master` should be safe.
* WPCS - use the latest release `0.14.0`.
WPCS is the main source of CS violations and is under active development. This means that new versions of WPCS will easily break the build, so should be managed.
* PHPCompatibility - use `master`.
PHPCompatibility checks PHP cross-version compatibility.
It is actively developed and heavily unit tested, so any new violations found in `_s` because of changes in that library, should actually be addressed in `_s` ASAP.
The PHPCompatibility library became compatible with PHPCS 3.x and improved compatibility with Composer installs in version `8.0.0` which was a breaking change.
To account for that, the location where the library is cloned to and the `phpcs --installed_paths` command have been updated.
Ref: https://github.com/wimg/PHPCompatibility/pull/446
|
||
|---|---|---|
| .github | ||
| inc | ||
| js | ||
| languages | ||
| layouts | ||
| sass | ||
| template-parts | ||
| .jscsrc | ||
| .jshintignore | ||
| .travis.yml | ||
| 404.php | ||
| LICENSE | ||
| README.md | ||
| archive.php | ||
| comments.php | ||
| footer.php | ||
| functions.php | ||
| header.php | ||
| index.php | ||
| page.php | ||
| phpcs.xml.dist | ||
| readme.txt | ||
| rtl.css | ||
| screenshot.png | ||
| search.php | ||
| sidebar.php | ||
| single.php | ||
| style.css | ||
| woocommerce.css | ||
README.md
_s
Hi. I'm a starter theme called _s, or underscores, if you like. I'm a theme meant for hacking so don't use me as a Parent Theme. Instead try turning me into the next, most awesome, WordPress theme out there. That's what I'm here for.
My ultra-minimal CSS might make me look like theme tartare but that means less stuff to get in your way when you're designing your awesome theme. Here are some of the other more interesting things you'll find here:
- A just right amount of lean, well-commented, modern, HTML5 templates.
- A helpful 404 template.
- A custom header implementation in
inc/custom-header.phpjust add the code snippet found in the comments ofinc/custom-header.phpto yourheader.phptemplate. - Custom template tags in
inc/template-tags.phpthat keep your templates clean and neat and prevent code duplication. - Some small tweaks in
inc/template-functions.phpthat can improve your theming experience. - A script at
js/navigation.jsthat makes your menu a toggled dropdown on small screens (like your phone), ready for CSS artistry. It's enqueued infunctions.php. - 2 sample CSS layouts in
layouts/for a sidebar on either side of your content. - Smartly organized starter CSS in
style.cssthat will help you to quickly get your design off the ground. - Licensed under GPLv2 or later. :) Use it to make something cool.
Getting Started
If you want to keep it simple, head over to https://underscores.me and generate your _s based theme from there. You just input the name of the theme you want to create, click the "Generate" button, and you get your ready-to-awesomize starter theme.
If you want to set things up manually, download _s from GitHub. The first thing you want to do is copy the _s directory and change the name to something else (like, say, megatherium-is-awesome), and then you'll need to do a five-step find and replace on the name in all the templates.
- Search for
'_s'(inside single quotations) to capture the text domain. - Search for
_s_to capture all the function names. - Search for
Text Domain: _sinstyle.css. - Search for
_s(with a space before it) to capture DocBlocks. - Search for
_s-to capture prefixed handles.
OR
- Search for:
'_s'and replace with:'megatherium-is-awesome' - Search for:
_s_and replace with:megatherium_is_awesome_ - Search for:
Text Domain: _sand replace with:Text Domain: megatherium-is-awesomeinstyle.css. - Search for:
_sand replace with:Megatherium_is_Awesome - Search for:
_s-and replace with:megatherium-is-awesome-
Then, update the stylesheet header in style.css, the links in footer.php with your own information and rename _s.pot from languages folder to use the theme's slug. Next, update or delete this readme.
Now you're ready to go! The next step is easy to say, but harder to do: make an awesome WordPress theme. :)
Good luck!