<?xml version='1.0' encoding='UTF-8'?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://blog.readthedocs.com</id>
  <title>Read the Docs Blog - Posts tagged badges</title>
  <updated>2023-07-08T10:50:30.051239+00:00</updated>
  <link href="https://blog.readthedocs.com"/>
  <link href="https://blog.readthedocs.com/archive/tag/badges/atom.xml" rel="self"/>
  <generator uri="https://ablog.readthedocs.org/" version="0.10.26">ABlog</generator>
  <entry>
    <id>https://blog.readthedocs.com/badge-support/</id>
    <title>Badge Support</title>
    <updated>2014-08-14T00:00:00+00:00</updated>
    <author>
      <name>Eric Holscher</name>
    </author>
    <content type="html">&lt;section id="badge-support"&gt;

&lt;p&gt;Documentation is an often overlooked part of a software project.
Today we are releasing badges for your docs,
so that people can easily see that your docs are up-to-date.&lt;/p&gt;
&lt;section id="status-badges"&gt;
&lt;h2&gt;Status Badges&lt;/h2&gt;
&lt;p&gt;The main use of badges is to show the status of your project’s build.
They will display in green for passing,
red for failing,
and yellow for unknown states.&lt;/p&gt;
&lt;p&gt;Here are a few examples:&lt;/p&gt;
&lt;p&gt;&lt;img alt="green" src="http://img.shields.io/badge/Docs-latest-green.svg" /&gt; &lt;img alt="red" src="http://img.shields.io/badge/Docs-release--1.6-red.svg" /&gt; &lt;img alt="yellow" src="http://img.shields.io/badge/Docs-No%20Builds-yellow.svg" /&gt;&lt;/p&gt;
&lt;p&gt;You can see it in action in the &lt;a class="reference external" href="https://github.com/rtfd/readthedocs.org/blob/master/README.rst"&gt;Read the Docs README&lt;/a&gt;.
They will link back to your project’s documentation page on Read the Docs.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="project-pages"&gt;
&lt;h2&gt;Project Pages&lt;/h2&gt;
&lt;p&gt;You will now see badges embedded in your &lt;a class="reference external" href="https://readthedocs.org/projects/pip/"&gt;project page&lt;/a&gt;.
The default badge will be pointed at the &lt;em&gt;default version&lt;/em&gt; you have specified for your project.
The badge URLs look like this:&lt;/p&gt;
&lt;div class="highlight-default notranslate"&gt;&lt;div class="highlight"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;https://readthedocs.org/projects/pip/badge/?version=latest
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;You can replace the version argument with any version that you want to show a badge for.
If you click on the badge icon,
you will be given snippets for RST, Markdown, and HTML;
to make embedding it easier.&lt;/p&gt;
&lt;p&gt;If you leave the version argument off,
it will default to your latest version.
This is probably best to include in your README,
since it will stay up to date with your Read the Docs project.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="design"&gt;
&lt;h2&gt;Design&lt;/h2&gt;
&lt;p&gt;We have often wondered what we might make our badges look like.
Luckily,
there is a developing standard and service to support badges.
&lt;a class="reference external" href="http://shields.io"&gt;http://shields.io&lt;/a&gt; is what we’ll be using to generate our badges,
and they look beautiful.&lt;/p&gt;
&lt;/section&gt;
&lt;section id="feature-requests"&gt;
&lt;h2&gt;Feature Requests&lt;/h2&gt;
&lt;p&gt;This is an initial attempt at adding badges to Read the Docs,
it’s a feature we’ve wanted to add for some time.
We have some plans to improve badges further,
but be sure to get in touch with us if you have any feedback on how you would like to see badges used.&lt;/p&gt;
&lt;p&gt;Feel free to &lt;a class="reference external" href="https://github.com/rtfd/readthedocs.org/issues"&gt;file an issue&lt;/a&gt;,
or you can always reach us at &lt;a class="reference external" href="mailto:readthedocs&amp;#37;&amp;#52;&amp;#48;gmail&amp;#46;com"&gt;readthedocs&lt;span&gt;&amp;#64;&lt;/span&gt;gmail&lt;span&gt;&amp;#46;&lt;/span&gt;com&lt;/a&gt;.&lt;/p&gt;
&lt;/section&gt;
&lt;/section&gt;
</content>
    <link href="https://blog.readthedocs.com/badge-support/" rel="alternate"/>
    <summary>Documentation is an often overlooked part of a software project.
Today we are releasing badges for your docs,
so that people can easily see that your docs are up-to-date.The main use of badges is to show the status of your project’s build.
They will display in green for passing,
red for failing,
and yellow for unknown states.</summary>
    <category term="feature" label="feature"/>
    <category term="badges" label="badges"/>
    <published>2014-08-14T00:00:00+00:00</published>
  </entry>
</feed>
