This isn't ideal, since these functions aren't defined with @function,
but there's not really a better place to put it. It certainly doesn't
make sense in the built-in module documentation anymore.
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.
This is intentionally not linked anywhere yet. It exists as a landing
page for links from dev versions of Sass and the migrator, and will be
updated as phase 1 comes closer to launching.
See sass/sass#2565
This is intentionally not linked anywhere yet. It exists as a landing
page for links from dev versions of Sass and the migrator, and will be
updated as phase 1 comes closer to launching.
See sass/sass#2565
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
