CSS selector page template

Note: Remove this whole explanatory note before publishing

Page front matter:

The frontmatter at the top of the page is used to define "page metadata". The values should be updated appropriately for the particular selector.

title: :NameOfTheSelector
slug: Web/CSS/:NameOfTheSelector
page-type: css-selector OR css-pseudo-class OR css-pseudo-element OR css-combinator
  - experimental
  - deprecated
  - non-standard
browser-compat: css.selectors.NameOfTheSelector

Title heading displayed at the top of the page. Format as :NameOfTheSelector. For example, the :hover selector has a title of :hover.


The end of the URL path after https://developer.mozilla.org/en-US/docs/). This will be formatted like Web/CSS/:NameOfTheSelector. For example, the :hover selector slug is Web/CSS/:hover.


The page-type key for CSS properties is one of css-selector, css-pseudo-class, or css-pseudo-element, depending on whether the selector is a pseudo-class, a pseudo-element, a combinator, or a basic selector.


Flags describing the status of this feature. An array which may contain one or more of the following: experimental, deprecated, non-standard. This key should not be set manually: it is set automatically based on values in the browser compatibility data for the feature. See "How to add or update feature statuses".


Replace the placeholder value css.selectors.NameOfTheSelector with the query string for the selector in the Browser compat data repo. The toolchain automatically uses the key to populate the compatibility and specifications sections (replacing the {{Compat}} and {{Specifications}} macros in those sections, respectively).

Note that you may first need to create/update an entry for the selector and its specification in our Browser compat data repo. See our guide on how to do this.

Top-of-page macros

A number of macro calls appear at the top of the content section (immediately below the page frontmatter). These macros are automatically added by the toolchain (there is no need to add/remove):

  • {{SeeCompatTable}} — this generates a This is an experimental technology banner that indicates the technology is experimental. If it is experimental, and the technology is hidden behind a pref in Firefox, you should also fill in an entry for it in the Experimental features in Firefox page.
  • {{Deprecated_Header}} — this generates a Deprecated banner that indicates that use of the technology is discouraged.
  • {{Non-standard_Header}} — this generates a Non-standard banner that indicates that the feature is not part of any specification.

You should update or delete the following macros according to the advice below:

  • {{CSSRef}} — this must be present on every CSS selector page. It generates a suitable CSS sidebar, depending on what tags are included on the page. Remember to remove the {{MDNSidebar}} macro when you copy this page.

Do not provide status header macros manually. Refer to the section "How to add or update feature statuses" to add these statuses to the page.

Samples of the Experimental, Deprecated, and Non-standard banners are shown right after this note block.

Syntax section ({{CSSSyntax}})

The content of the Syntax section is generated using the {{CSSSyntax}} macro. For these to populate, you must ensure an appropriate entry has been filled in for the selector in our selectors.json data file. See selectors.md for more information.

Remember to remove this whole explanatory note before publishing

Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Non-standard: This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

The summary paragraph — start by naming the selector and saying what it does. This should ideally be one or two short sentences.

/* Insert code block showing common use cases */



To use this macro, remove the backticks and backslash in the markdown file.


Note that we use the plural "Examples" even if the page only contains one example.

A descriptive heading

Each example must have an H3 heading (###) naming the example. The heading should be descriptive of what the example is doing. For example, "A simple example" does not say anything about the example and therefore, not a good heading. The heading should be concise. For a longer description, use the paragraph after the heading.

See our guide on how to add code examples for more information.

Note: Sometimes, you will want to link to examples given on another page.

Scenario 1: If you have some examples on this page and some more examples on another page:

Include an H3 heading (###) for each example on this page and then a final H3 heading (###) with the text "More examples", under which you can link to the examples on other pages. For example:

## Examples

### Using the fetch API

Example of Fetch

### More examples

Links to more examples on other pages

Scenario 2: If you only have examples on another page and none on this page:

Don't add any H3 headings; just add the links directly under the H2 heading "Examples". For example:

## Examples

For examples of this API, see [the page on fetch()](https://example.org).

Accessibility concerns

Optionally, warn of any potential accessibility concerns with using this selector and how to work around them. Remove this section if there is no list.



To use this macro, remove the backticks and backslash in the markdown file.

Browser compatibility


To use this macro, remove the backticks and backslash in the markdown file.

See also

Include links to reference pages and guides related to the current selector. For more guidelines, see the See also section in the Writing style guide.

  • link1
  • link2