<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ide on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/ide/</link>
    <description>Recent content in Ide on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/ide/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted GraphQL IDE and Playground Tools: Altair vs GraphQL Voyager vs GraphiQL</title>
      <link>https://www.pistack.xyz/posts/2026-05-07-self-hosted-graphql-ide-playground-altair-voyager-graphiql-guide/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-07-self-hosted-graphql-ide-playground-altair-voyager-graphiql-guide/</guid>
      <description>&lt;p&gt;GraphQL has become the standard for building flexible APIs, but testing and exploring GraphQL endpoints requires the right tooling. While cloud-hosted IDEs are common, self-hosting your GraphQL playground gives you full control over your development workflow, ensures API keys stay on your network, and eliminates dependency on third-party services.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
