Issue 5385 - Create Site Header Component for Help Center

static/scss/base/_utilities.scss

+// This file is part of help.eyeo.com.

[juliandoucette, 2017/07/19 18:03:34]

I think that everything in this file belongs in website-defaults.

+// Copyright (C) 2017 Eyeo GmbH
+//
+// help.eyeo.com is free software: you can redistribute it and/or modify
+// it under the terms of the GNU General Public License as published by
+// the Free Software Foundation, either version 3 of the License, or
+// (at your option) any later version.
+//
+// help.eyeo.com is distributed in the hope that it will be useful,
+// but WITHOUT ANY WARRANTY; without even the implied warranty of
+// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+// GNU General Public License for more details.
+//
+// You should have received a copy of the GNU General Public License
+// along with help.eyeo.com.  If not, see <http://www.gnu.org/licenses/>.
+
+// Screen reader ///////////////////////////////////////////////////////////////
+
+// Use this class to add screen reader / web crawler only content
+//
+// EG:
+// - An h1 for SEO that is not visible
+// - A skip-to link for screen readers
+
+.sr-only
+{
+  position: absolute;
+  overflow: hidden;
+  clip: rect(0, 0, 0, 0);
+  width: 1px;
+  height: 1px;
+  margin: -1px;
+  padding: 0;
+  border: 0;
+}
+
+// Clearfix ///////////////////////////////////////////////////////////////
+
+.clearfix:after
+{
+  display: table;
+  clear: both;
+  content: "";
+}
+
+// Responsive ///////////////////////////////////////////////////////////////
+
+.mobile-only
+{
+  @media (min-width: $mobile-breakpoint)
+  {
+    display: none;
+  }
+}
+
+.tablet-and-mobile-only
+{
+  @media (min-width: $tablet-breakpoint)
+  {
+    display: none;
+  }
+}
+
+.tablet-and-desktop-only
+{
+  @media (max-width: $mobile-breakpoint)
+  {
+    display: none;
+  }
+}
+
+.desktop-only
+{
+  @media (max-width: $tablet-breakpoint)
+  {
+    display: none;
+  }
+}
+
+// Unstyled ///////////////////////////////////////////////////////////////
+
+.unstyled

[ire, 2017/07/17 09:31:37]

It just occurred to me that I'm replicating the reset here :/ But I'd like to
get your opinion on whether this style is still needed. The button element is
not included in the reset, but in the case of the #toggle-searchform element I
want it to be unstyled. If I add the button element to the reset, then it will
apply to *all* buttons, which isn't necessarily what we want. What do you think?

[juliandoucette, 2017/07/19 18:03:34]

I think we want to completely standardize all form element styles across
website/browser in website-defaults to avoid unexpected behaviour ( especially
relevant to gnu/linux and dark themes like mine O:) ). 

I think that an .unstyled class is very useful for content.

I think that we should avoid using .unstyled on components ( where we want to
keep all applicable styles together e.g. the whole point of BEM; I think :/ )

+{
+  margin: 0;
+  padding: 0;
+  border: 0;
+  background: none;
+}