Logdown seems to be basically unmaintained, its servers are
unreliable, and it's been causing some mixed-content errors lately.
This moves all blog posts to sass-lang.com itself; I'll set up
redirects from the blog as best I can once this lands.
Closes#401Closes#402Closes#403
* [docNav] Moved h3 title into nav wrapper
* [docNav] Init styles for doc navigation component
* [docNav] Import doc navigation component into sass.css.scss
* [docNav] Functional to make doc navigation sticky on scroll
* [docNav] Rename js class name and changed from single to double quotes
* [docNav] Change class name to sl-js-nav--is-sticky
* [docNav] renamed doc-navigation to navigation and removed nesting
* [docNav] renamed doc-navigation to navigation
* [docNav] Added carriage return after h3
This hierarchy is now going to document built-in modules, which mostly
contain functions but can also contain mixins and may potentially
contain variables in the future.
These used to redirect from /documentation/, but we tweaked the way
URLs work and now they redirect from /documentation. Making them
absolute avoids even the potential for that breakage.
This renders the tabs and all the jQuery classes server-side, so that
the code examples are rendered correctly on the page's first load
rather than waiting for the JavaScript to activate. This also has a
side effect of making them look correct with JavaScript disabled.
This also adds a little additional styling in the noscript stylesheet
to make code examples look better on a narrow viewport with JavaScript
disabled.
Tables of contents are now statically rendered in their appropriately
open/closed states, rather than updated via JavaScript, so they render
correctly on the first page load. In order to make the "page sections"
table still usable without JS, this adds a stylesheet in a <noscript>
tag that forces the sections into an open state.
* Add more margin above headers to visually associate them with the
prose below, rather than above.
* Reduce the margin around normal block elements to more clearly
associate them with one another.
* Increase the size of prose and medium/large headers to make them
easier to see.
* Reduce the font weight of intro paragraphs to make them more
visually distinct from the rest of the documentation.
Based on @slimekat's suggestions.
Closes#313
This gives us a place to disambiguate between implementation statuses
that refer to the entire feature under discussion, and those that just
refer to sub-features.
* Make the font smaller to make them less prominent and help visually
associate the callout with the list.
* Decrease the top margin to more clearly associate them with their
preceding header.
* Lighten the callout background when in another callout to make it
more visible.
* Animate the expand button.
