Brings sass into _s
Sass now comes with _s - you can simply check an option on underscores.me and get a version with Sass.
Props to: @gregrickaby @bradp @hugobaeta @obenland @sabreuse @MichaelArestad @jacklenox @karmatosed
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.
- 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.
Tammie Lister
Firdaus Zahari
Mike Griffiths
Konstantin Obenland
Philip Arthur Moore
Philip Arthur Moore
Fränk Klein
Greg Rickaby
Lucas Cherkewski
Thomas Guillot
sixhours
Konstantin Kovshenin
Jack Lenox
Emil Uzelac
Slobodan Manic
Kazue Igarashi