title: Use partial views for custom MVC html controls
body: <p>I have a bunch of button-styled links throughout my web app:</p>
  
  <pre><code>&lt;a href="@Url.Action("Index", "Home")" class="btn btn-default btn-lg btn-right"&gt;
      &lt;span class="glyphicon glyphicon-home"&gt;&lt;/span&gt;
      &lt;h3&gt;Store Home&lt;/h3&gt;
  &lt;/a&gt;
  </code></pre>
  
  <p>Sometimes they get an additional tag to indicate a direction arrow, or some other decoration:</p>
  
  <pre><code>&lt;a href="@Url.Action("Payment", "Checkout")" class="btn btn-primary btn-lg btn-right"&gt;
      &lt;h3&gt;&lt;&lt;&lt;/h3&gt;
      &lt;span class="glyphicon glyphicon-credit-card"&gt;&lt;/span&gt;
      &lt;h3&gt;Back to Payment&lt;/h3&gt;
  &lt;/a&gt;
  </code></pre>
  
  <p>My question is, rather than peppering my markup with subtly different flavors of this button copy and pasted, is it appropriate to use a partial view so that the knowledge of how to make a button and its various flavors is all in one place? EDIT: for clarity, I mean a partial view with nothing other than the button markup, and potentially a "button view model" object with the various settings for the view to act on.</p>
  
  <p>It seems like the purpose of partial views is to promote reusability and maintainability, but I'm not sure if I'm taking that too far, or if there's some kind of performance constraint I'm unaware of that makes this a bad idea.</p>