d8a88d2097 brought the HTML5 support declaration close to how Twenty Thirteen and Twenty Fourteen do it, leaving post formats doing their own thing.
Let's make displaying array values consistent with the latest default themes.
We can safely increase the textarea width from 98% to 100%.
```box-sizing``` handles the layout nicely and it won't allow the overflow.
If more details is needed, please see: http://davidwalsh.name/textarea-width this is the best example I could find.
Minor CSS optimization for border and border color.
For the border itself, we don't need to include the color in ```border: {}```, color is already added in ```border-color: {}```.
Since the Theme uses shorthands for padding/margins, why not do the same for the border colors as well.
Change `widgettitle` to `widget-title` in 404 template for better consistency throughout all theme files. _s uses `widget-title` as its convention when declaring theme widgets, so we'll go with that.
```widgettitle``` doesn't really have any value here or in core. Proposing to change to ```widget-title``` instead and maybe add that into stylesheet too.
The class is available only in /widgets.php and not present in any of the stylesheet's, at least I could not locate one. As in my previous proposal, this is for the consistency reasons only.
The leading whitespace is needed to replace this `_s` instance with the theme name.
It's obviously a hack, since it also leaves the theme name with a leading white space, but short of adding a new replace logic for this specific line in `style.css`, it's the easiest way to achieve that.
See #304, where this was brought up before.
Since HTML5 captions removed the additional 10px that HTML4 versions
come with, the `max-width: 98%;` rule made images blurry. This slightly
simplifies caption styles while still providing support for both HTML4
and HTML5 versions.
See #443.
The referenced items are decisions we made for `_s`, that a re likely to be brought up again in pull requests or issues. Since our stance on them is not likely to change any time soon, let's include them in the Contributing FAQs.
See #464.
This might change in the future, based on our experiences, but should
be a good first draft of helpful and friendly guidelines for
contributing.
Props @bungeshea.
Fixes#381.