<liclass="toctree-l1 current active has-children"><aclass="current reference internal" href="#">Tagging guidelines</a><detailsopen="open"><summary><spanclass="toctree-toggle" role="presentation"><iclass="fa-solid fa-chevron-down"></i></span></summary><ul>
<liclass="toctree-l2"><aclass="reference internal" href="MEP/MEP12.html">MEP12: Improve Gallery and Examples</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="MEP/MEP13.html">MEP13: Use properties for Artists</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="MEP/MEP14.html">MEP14: Text handling</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="MEP/MEP15.html">MEP15: Fix axis autoscaling when limits are specified for one axis only</a></li>
<h2>What gets a tag?<aclass="headerlink" href="#what-gets-a-tag" title="Link to this heading">#</a></h2>
<p>Every gallery example should be tagged with:</p>
<ulclass="simple">
<li><p>1+ content tags</p></li>
<li><p>structural, domain, or internal tag(s) if helpful</p></li>
</ul>
<p>Tags can repeat existing forms of organization (e.g. an example is in the Animation
folder and also gets an <codeclass="docutils literal notranslate"><spanclass="pre">animation</span></code> tag).</p>
<p>Tags are helpful to denote particularly good "byproduct" examples. E.g. the explicit
purpose of a gallery example might be to demonstrate a colormap, but it's also a good
demonstration of a legend. Tag <codeclass="docutils literal notranslate"><spanclass="pre">legend</span></code> to indicate that, rather than changing the
<liclass="toctree-l2"><aclass="reference internal" href="tag_glossary.html#api-tags-what-content-from-the-api-reference-is-in-the-example">API tags: what content from the API reference is in the example?</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="tag_glossary.html#structural-tags-what-format-is-the-example-what-context-can-we-provide">Structural tags: what format is the example? What context can we provide?</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="tag_glossary.html#domain-tags-what-discipline-s-might-seek-this-example-consistently">Domain tags: what discipline(s) might seek this example consistently?</a></li>
<liclass="toctree-l2"><aclass="reference internal" href="tag_glossary.html#internal-tags-what-information-is-helpful-for-maintainers-or-contributors">Internal tags: what information is helpful for maintainers or contributors?</a></li>
</ul>
</li>
</ul>
</div>
</div>
<divclass="sd-card-footer docutils">
<pclass="sd-card-text">See <aclass="reference internal" href="tag_glossary.html"><spanclass="doc">Tag Glossary</span></a> for a complete list</p>
</div>
</div>
</section>
<sectionid="proposing-new-tags">
<h2>Proposing new tags<aclass="headerlink" href="#proposing-new-tags" title="Link to this heading">#</a></h2>
<olclass="arabic simple">
<li><p>Review existing tag list, looking out for similar entries (i.e. <codeclass="docutils literal notranslate"><spanclass="pre">axes</span></code> and <codeclass="docutils literal notranslate"><spanclass="pre">axis</span></code>).</p></li>
<li><p>If a relevant tag or subcategory does not yet exist, propose it. Each tag is two
parts: <codeclass="docutils literal notranslate"><spanclass="pre">subcategory:</span><spanclass="pre">tag</span></code>. Tags should be one or two words.</p></li>
<li><p>New tags should be added when they are relevant to existing gallery entries too.
Avoid tags that will link to only a single gallery entry.</p></li>
<li><p>Tags can recreate other forms of organization.</p></li>
</ol>
<p>Tagging organization aims to work for 80-90% of cases. Some examples fall outside of the
tagging structure. Niche or specific examples shouldn't be given standalone tags that