From e1bb907050bbf1598f58a53fc64e2432753d5b24 Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Wed, 24 Dec 2014 03:26:51 -0800 Subject: rearrange contents docs--type, tables, images, forms, etc--into own docs section --- docs/components/buttons.md | 118 --------- docs/components/code.md | 49 ---- docs/components/forms.md | 517 ------------------------------------ docs/components/images.md | 37 --- docs/components/tables.md | 593 ------------------------------------------ docs/components/typography.md | 354 ------------------------- 6 files changed, 1668 deletions(-) delete mode 100644 docs/components/buttons.md delete mode 100644 docs/components/code.md delete mode 100644 docs/components/forms.md delete mode 100644 docs/components/images.md delete mode 100644 docs/components/tables.md delete mode 100644 docs/components/typography.md (limited to 'docs/components') diff --git a/docs/components/buttons.md b/docs/components/buttons.md deleted file mode 100644 index ac2ccc6cf..000000000 --- a/docs/components/buttons.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -layout: page -title: Buttons ---- - -Use any of the available button classes to quickly create a styled button. - -{% example html %} - - - - - - - - - - - - - - - - - -{% endexample %} - -
-

Conveying meaning to assistive technologies

-

Using color to add meaning to a button only provides a visual indication, which will not be conveyed to users of assistive technologies – such as screen readers. Ensure that information denoted by the color is either obvious from the content itself (the visible text of the button), or is included through alternative means, such as additional text hidden with the .sr-only class.

-
- -## Button tags - -Use the button classes on an ``, ` - - -{% endexample %} - -
-

Links acting as buttons

-

If the <a> elements are used to act as buttons – triggering in-page functionality, rather than navigating to another document or section within the current page – they should also be given an appropriate role="button".

-
- -
-

Cross-browser rendering

-

As a best practice, we highly recommend using the <button> element whenever possible to ensure matching cross-browser rendering.

-
- -## Sizes - -Fancy larger or smaller buttons? Add `.btn-lg`, `.btn-sm`, or `.btn-xs` for additional sizes. - -{% example html %} - - -{% endexample %} - -{% example html %} - - -{% endexample %} - -{% example html %} - - -{% endexample %} - -Create block level buttons—those that span the full width of a parent—by adding `.btn-block`. - -{% example html %} - - -{% endexample %} - -## Active state - -Buttons will appear pressed (with a darker background, darker border, and inset shadow) when active. **There's no need to add a class to ` - -{% endexample %} - -As `` elements don't support the `disabled` attribute, you must add the `.disabled` class to fake it. - -{% example html %} -Primary link -Link -{% endexample %} - -
-

Cross-browser compatibility

-

If you add the disabled attribute to a <button>, Internet Explorer 9 and below will render text gray with a nasty text-shadow that we cannot fix.

-
- -
-

Link functionality caveat

-

This class uses pointer-events: none to try to disable the link functionality of <a>s, but that CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 11. In addition, even in browsers that do support pointer-events: none, keyboard navigation remains unaffected, meaning that sighted keyboard users and users of assistive technologies will still be able to activate these links. So to be safe, use custom JavaScript to disable such links.

-
- -
-

Context-specific usage

-

While button classes can be used on <a> and <button> elements, only <button> elements are supported within our nav and navbar components.

-
diff --git a/docs/components/code.md b/docs/components/code.md deleted file mode 100644 index 19c02c84e..000000000 --- a/docs/components/code.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -layout: page -title: Code ---- - -Styles for inline code snippets and longer, multiline blocks of code. - -## Inline code - -Wrap inline snippets of code with `code`. Be sure to escape HTML angle brackets. - -{% example html %} -For example, <section> should be wrapped as inline. -{% endexample %} - -## User input - -Use the `` to indicate input that is typically entered via keyboard. - -{% example html %} -To switch directories, type cd followed by the name of the directory.
-To edit settings, press ctrl + , -{% endexample %} - -## Preformatted text - -Or, code blocks. Use `
`s for multiple lines of code. Once again, be sure to escape any angle brackets in the code for proper rendering.
-
-{% example html %}
-
<p>Sample text here...</p>

-{% endexample %}
-
-You may optionally add the `.pre-scrollable` class, which will set a max-height of 350px and provide a y-axis scrollbar.
-
-## Variables
-
-For indicating variables use the `` tag.
-
-{% example html %}
-y = mx + b
-{% endexample %}
-
-## Sample output
-
-For indicating blocks sample output from a program use the `` tag.
-
-{% example html %}
-This text is meant to be treated as sample output from a computer program.
-{% endexample %}
diff --git a/docs/components/forms.md b/docs/components/forms.md
deleted file mode 100644
index 7d274c2a0..000000000
--- a/docs/components/forms.md
+++ /dev/null
@@ -1,517 +0,0 @@
----
-layout: page
-title: Forms
----
-
-Bootstrap normalizes common HTML5 form elements and adds a number of layout options for building forms of all sizes.
-
-## Example form
-
-Individual form controls automatically receive some global styling. All textual ``, `
-{% endexample %}
-
-### Checkboxes and radios
-
-Checkboxes are for selecting one or several options in a list, while radios are for selecting one option from many.
-
-A checkbox or radio with the `disabled` attribute will be styled appropriately. To have the `