From 230e781b6e0a261d7b6f1c8b137f7f043d0d326d Mon Sep 17 00:00:00 2001 From: Hugo Giraudel Date: Thu, 23 Jul 2015 23:55:20 +0200 Subject: [PATCH] Removed a lot of irrelevant further reads --- en/_architecture.md | 5 ----- en/_comments.md | 1 - en/_introduction.md | 2 -- en/_mixins.md | 2 -- en/_sass.md | 11 ----------- en/_syntax.md | 4 ---- en/_tools.md | 4 ---- 7 files changed, 29 deletions(-) diff --git a/en/_architecture.md b/en/_architecture.md index 27acac7d..2846705f 100644 --- a/en/_architecture.md +++ b/en/_architecture.md @@ -17,12 +17,8 @@ I, myself, use an approach that happens to be quite similar to [SMACSS](https:// ###### Further reading -* [Architecture for a Sass project](http://www.sitepoint.com/architecture-sass-project/) * [A Look at Different Sass Architectures](http://www.sitepoint.com/look-different-sass-architectures/) -* [SMACSS](https://smacss.com/) * [An Introduction to OOCSS](http://www.smashingmagazine.com/2011/12/12/an-introduction-to-object-oriented-css-oocss/) -* [Atomic Web Design](http://bradfrost.com/blog/post/atomic-web-design/) -* [Sass, une architecture composée](http://slides.com/hugogiraudel/sass-une-architecture-composee) ## Components @@ -204,5 +200,4 @@ There is an interesting concept that has been made popular by [Harry Roberts](ht ###### Further reading -* [shame.css](http://csswizardry.com/2013/04/shame-css/) * [shame.css - full .net interview](http://csswizardry.com/2013/04/shame-css-full-net-interview/) diff --git a/en/_comments.md b/en/_comments.md index 8cf97706..fae2777c 100644 --- a/en/_comments.md +++ b/en/_comments.md @@ -53,5 +53,4 @@ Here is an example of a mixin extensively documented with SassDoc: ###### Further reading -* [SassDoc](http://sassdoc.com) * [SassDoc: a Documentation Tool for Sass](http://www.sitepoint.com/sassdoc-documentation-tool-sass/) diff --git a/en/_introduction.md b/en/_introduction.md index a0ca8d1b..ccb3c924 100644 --- a/en/_introduction.md +++ b/en/_introduction.md @@ -52,6 +52,4 @@ An example of styleguide extension can be found on the [SassDoc repository](http ###### Further reading -* [KISS principle](http://en.wikipedia.org/wiki/KISS_principle) -* [DRY principle](http://en.wikipedia.org/wiki/Don%27t_repeat_yourself) * [Keep Sass Simple](http://www.sitepoint.com/keep-sass-simple/) diff --git a/en/_mixins.md b/en/_mixins.md index 6be27020..1e03bfab 100644 --- a/en/_mixins.md +++ b/en/_mixins.md @@ -21,7 +21,6 @@ Another valid example would be a mixin to size an element, defining both `width` * [Sass Mixins to Kickstart your Project](http://www.sitepoint.com/sass-mixins-kickstart-project/) * [A Sass Mixin for CSS Triangles](http://www.sitepoint.com/sass-mixin-css-triangles/) -* [Building a Linear-Gradient Mixin](http://www.sitepoint.com/building-linear-gradient-mixin-sass/) ## Argument-less mixins @@ -69,5 +68,4 @@ Please keep in mind this is a poor solution. For instance, it cannot deal with c ###### Further reading -* [Autoprefixer](https://github.com/postcss/autoprefixer) * [Building a Linear-Gradient Mixin](http://www.sitepoint.com/building-linear-gradient-mixin-sass/) diff --git a/en/_sass.md b/en/_sass.md index 52ba97ba..c1f96f36 100644 --- a/en/_sass.md +++ b/en/_sass.md @@ -15,8 +15,6 @@ That being said, there are many ways to use these features. Some good, some bad, ###### Further reading -* [Sass](http://sass-lang.com) -* [Sass documentation](http://sass-lang.com/documentation/file.SASS_REFERENCE.html) * [SitePoint Sass Reference](http://sitepoint.com/sass-reference/) ## Ruby Sass or LibSass @@ -31,9 +29,7 @@ On non-Ruby projects that need a workflow integration, LibSass is probably a bet ###### Further reading -* [LibSass](https://github.com/sass/libsass) * [Getting to know LibSass](http://webdesign.tutsplus.com/articles/getting-to-know-libsass--cms-23114) -* [Sass-Compatibility](http://sass-compatibility.github.io) * [Switching from Ruby Sass to LibSass](http://www.sitepoint.com/switching-ruby-sass-libsass/) ## Sass or SCSS @@ -69,10 +65,3 @@ You can think of postprocessors as a polyfill for unsupported CSS features. For The idea behind postprocessors is that once browsers support new features (e.g. CSS variables), the postprocessor does not compile them anymore and lets browsers take over. While providing tomorrow’s syntax today is something of a noble idea, I have to say I still prefer using Sass for most tasks. However, there are some occasions where I believe postprocessors are more suited than Sass and the like - CSS prefixing for instance - but we’ll get back to this. - -###### Further reading - -* [LESS](http://lesscss.org/) -* [Stylus](http://learnboost.github.io/stylus/) -* [cssnext](https://cssnext.github.io/) -* [PostCSS](https://github.com/postcss/postcss) diff --git a/en/_syntax.md b/en/_syntax.md index be67d13c..cc395cd8 100644 --- a/en/_syntax.md +++ b/en/_syntax.md @@ -307,12 +307,8 @@ Because of this, I will not impose a choice in this styleguide. Pick the one you ###### Further reading -* [CSS Comb](https://github.com/csscomb/csscomb.js) -* [Concentric CSS](https://github.com/brandon-rhodes/Concentric-CSS) -* [Idiomatic CSS](https://github.com/necolas/idiomatic-css) * [On Declaration Sorting](http://meiert.com/en/blog/20140924/on-declaration-sorting/) * [Reduce File Size With CSS Sorting](http://peteschuster.com/2014/12/reduce-file-size-css-sorting/) -* [Poll Results: How Do You Order Your CSS Properties?](http://css-tricks.com/poll-results-how-do-you-order-your-css-properties/) ## Selector Nesting diff --git a/en/_tools.md b/en/_tools.md index 164befe5..4fda86be 100644 --- a/en/_tools.md +++ b/en/_tools.md @@ -23,7 +23,6 @@ Anyway, I do not forbid the use of Compass although I would not recommend it eit ###### Further reading -* [Compass](http://compass-style.org/) * [Sass Frameworks: Compass or Bourbon](http://www.sitepoint.com/compass-or-bourbon-sass-frameworks/) * [Why I don't use Compass anymore](http://www.sitepoint.com/dont-use-compass-anymore/) * [Is Compass to Sass with jQuery is to JavaScript?](http://www.sitepoint.com/compass-sass-jquery-javascript/) @@ -42,10 +41,8 @@ Or you can head over to something a bit more casual, like [csswizardry-grids](ht ###### Further reading -* [Singularity](http://singularity.gs/) * [Singularity: Grids Without Limits](http://fourword.fourkitchens.com/article/singularity-grids-without-limits) * [Singularity Grid System](http://www.mediacurrent.com/blog/singularity-grid-system) -* [Susy](http://susy.oddbird.net/) * [Build Web Layouts Easily with Susy](http://css-tricks.com/build-web-layouts-easily-susy/) * [A Complete Tutorial to Susy 2](http://www.zell-weekeat.com/susy2-tutorial/) * [Sass Grids: From Neat to Susy](http://www.sitepoint.com/sass-grids-neat-susy/) @@ -70,7 +67,6 @@ Fortunately, SCSS-lint recommendations are very similar to those described in th ###### Further reading -* [SCSS-lint](https://github.com/causes/scss-lint) * [Clean Up your Sass with SCSS-lint](http://blog.martinhujer.cz/clean-up-your-sass-with-scss-lint/) * [Improving Sass code quality on theguardian.com](http://www.theguardian.com/info/developer-blog/2014/may/13/improving-sass-code-quality-on-theguardiancom) * [grunt-scss-lint](https://github.com/ahmednuaman/grunt-scss-lint)