<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: What does Stripe use for API documentation? in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/What-does-Stripe-use-for-API-documentation/m-p/743058#M60413</link>
    <description>&lt;P&gt;Markdoc accompanies two particular Respond renderers: a renderer that powerfully constructs the Respond virtual DOM tree on the client side, and a static renderer that transpiles the record to JavaScript code. We utilize the dynamic renderer in our documentation stage at Stripe&lt;A href="https://www.arcannwaste.com/" target="_blank" rel="noopener"&gt;,&lt;/A&gt; however the static renderer is helpful in situations where you need to treat a piece of Markdoc content like it is a Respond part or JavaScript module. For instance, the static renderer makes it conceivable to execute a Markdoc loader for Webpack in just five lines of code.&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jan 2023 06:52:43 GMT</pubDate>
    <dc:creator>edwinjoe</dc:creator>
    <dc:date>2023-01-18T06:52:43Z</dc:date>
    <item>
      <title>What does Stripe use for API documentation?</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/What-does-Stripe-use-for-API-documentation/m-p/743052#M60412</link>
      <description>&lt;P&gt;Stripe use for API documentation.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2023 06:44:06 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/What-does-Stripe-use-for-API-documentation/m-p/743052#M60412</guid>
      <dc:creator>MSam6</dc:creator>
      <dc:date>2023-01-18T06:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: What does Stripe use for API documentation?</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/What-does-Stripe-use-for-API-documentation/m-p/743058#M60413</link>
      <description>&lt;P&gt;Markdoc accompanies two particular Respond renderers: a renderer that powerfully constructs the Respond virtual DOM tree on the client side, and a static renderer that transpiles the record to JavaScript code. We utilize the dynamic renderer in our documentation stage at Stripe&lt;A href="https://www.arcannwaste.com/" target="_blank" rel="noopener"&gt;,&lt;/A&gt; however the static renderer is helpful in situations where you need to treat a piece of Markdoc content like it is a Respond part or JavaScript module. For instance, the static renderer makes it conceivable to execute a Markdoc loader for Webpack in just five lines of code.&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2023 06:52:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/What-does-Stripe-use-for-API-documentation/m-p/743058#M60413</guid>
      <dc:creator>edwinjoe</dc:creator>
      <dc:date>2023-01-18T06:52:43Z</dc:date>
    </item>
  </channel>
</rss>

