SVG element 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 element.

title: <NameOfTheElement>
slug: Web/SVG/Element/NameOfTheElement
page-type: svg-element
  - NameOfTheElement
  - SVG
  - Element
  - Reference
  - Experimental
  - Deprecated
  - Non-standard
browser-compat: svg.elements.NameOfTheElement

Title heading displayed at top of page. Format as <NameOfTheElement>. For example, the "g" element has a title of <g>.


The end of the URL path after This will be formatted like Web/SVG/Element/NameOfTheElement.


Always svg-element.


Always include the following tags: SVG, Reference, Element, the NameOfTheElement (e.g. g).

Include the following tags as appropriate:

  • Relevant category: SVG Container, SVG Animation, SVG Light Source, SVG Text Content, SVG Font.
  • Technology status: Experimental (if the technology is experimental), Deprecated (if it is deprecated), Non-standard (if it isn't on a standards track).
  • Any other tags that represent possible search terms for the element.

Replace the placeholder value svg.elements.NameOfTheElement with the query string for the element in the Browser compat data repo. The toolchain automatically uses the key to populate the compatibility and specification sections (replacing the {{Compat}} and {{Specifications}} macros).

Note that you may first need to create/update an entry for the element in our Browser compat data repo, and the entry will need to include specification information. 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). You should update or delete them according to the advice below:

  • {{SeeCompatTable}} — this generates a This is an experimental technology banner that indicates the technology is experimental. If the technology you are documenting is not experimental, you should remove this. 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. If it isn't, then you can remove the macro call.
  • {{SecureContext_Header}} — this generates a Secure context banner that indicates the technology is only available in a secure context. If it isn't, then you can remove the macro call. If it is, then you should also fill in an entry for it in the Features restricted to secure contexts page.
  • {{SVGRef}} — this generates the left-hand-side reference sidebar for the element. The content of the sidebar depends on the tags in the page metadata.
  • Remember to remove the {{MDNSidebar}} macro when you copy this page.

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.

The summary paragraph — start by naming the element and saying what it does. This should ideally be 1 or 2 short sentences.

Usage context


Note — for the correct information to appear here, you need to fill in an entry for the element in the {{svginfo}} macro, if it is not in there already.


Global attributes

Specific attributes

  • Include bulleted
  • list of all the
  • SVG attributes it can take

DOM Interface

This element implements the NameOfSVGDOMElement interface.


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()](


No specification found

No specification data found for
Check for problems with this page or contribute a missing spec_url to mdn/browser-compat-data. Also make sure the specification is included in w3c/browser-specs.

Browser compatibility

BCD tables only load in the browser

See also

  • Include list of
  • other links related to
  • this Element that might be useful