Props @michaelArestad @hugobeta, and @jacklenox.
* Give prefix to variable files. This avoids confusion with files of similar names like typography. It also helps with the visual recognition over what file does what.
* Set up mixins-master.
* Setting foundation for encouraging in larger projects use of more than one mixing file. This creates a master mixins file that we can then bring subs into if the project grows.
* Fixed line breaks, spacing and new lines. Props @gregrickaby.
* Nest widget select. Props @gregrickaby.
* Make variables be variables-site. Makes this the global variables folder. People can then use sub folders in sections for local only variables.
* Change content directory to be site directory.
* Remove zip. Revert `style.css` to not be auto generated version.
* Fixes rem size issue on body font.
* Fixes for differences between `_s` and `_sass`. Fixed font sizes, added in display block to classes so they compile and the theme check
passes.
* Remove text domain and clean up css.
- Fix entry-footer inconsistency between content-*.php files
- Move in a function <code>_s_entry_meta()</code> to avoid duplication
---
At the moment there is an inconsistency between content.php and
content-single.php regarding the .entry-footer output.
In my opinion content.php output is would be better to use because it's
easier to translate and allow more customisation.
Finally by moving it into <code>inc/template-tags.php</code> we are
getting rid of some duplicated code.
Sometimes the title length of a previous or next post would cause
the arrow (larr/rarr) in the link to be wrapped to the next line.
Adding a non-breaking space between the title and the arrow will stick
it to the last word in the title.
A default background color is needed for any time there is no custom background color.
This happens to use the browser's default `#fff`, and is meant more as a reminder for theme authors.
See #515.
First pass at creating a search-dedicated post template. Simplifies `content.php` and makes use of the template hierarchy.
Eventually we can think about removing more meta information, as appropriate.
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.