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
tags:
  - NameOfTheElement
  - SVG
  - Element
  - Reference
  - Experimental
  - Deprecated
  - Non-standard
browser-compat: svg.elements.NameOfTheElement
---

title

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

slug

The end of the URL path after https://developer.mozilla.org/en-US/docs/). This will be formatted like Web/SVG/Element/NameOfTheElement.

tags

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.

browser-compat

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