update headings and ecosystem

www/public/css/app.css

@@ -30,7 +30,7 @@ textarea {
   border:1px solid #ccc;
 }
 
-.psx-object > h1 {
+.psx-object > h3 {
   font-weight:bold;
   font-size:1em;
   margin:0;

www/resources/template/developer.php

@@ -22,7 +22,7 @@
   <hr>
 
   <a id="Generator"></a>
-  <h3>Generator</h3>
+  <h2>Generator</h2>
 
   <p>The following script is a very naive generator implementation which should show how to read a TypeAPI specification
   and produce a different output. In this case we simply generate a documentation format but it should give a good

www/resources/template/ecosystem.php

@@ -11,10 +11,12 @@
 
   <h1 class="display-4">Ecosystem</h1>
 
-  <p class="lead">The following page shows different services working with the TypeAPI specification.</p>
+  <p class="lead">The following page shows different services and tools working with the TypeAPI specification.</p>
 
   <hr>
 
+  <h2>Services</h2>
+
   <a id="SDKgen"></a>
   <h3><a href="https://sdkgen.app/">SDKgen</a></h3>
   <p>SDKgen is a service which provides a code generator as REST API, you can consume the API either manually or through
@@ -33,6 +35,21 @@
 
   <hr>
 
+  <h2>Tools</h2>
+
+  <a id="TypeAPI-Editor"></a>
+  <h3><a href="https://github.com/apioo/typeschema-angular-editor">TypeAPI-Editor</a></h3>
+  <p>Angular component which allows you to build and view TypeAPI specifications. We provide a current version at
+  our <a href="https://sandbox.typeapi.org/">Sandbox</a> page.</p>
+
+  <a id="SDKgen-Generator-Action"></a>
+  <h3><a href="https://github.com/apioo/sdkgen-generator-action">SDKgen-Generator-Action</a></h3>
+  <p>GitHub action which allows you to generate code through a GitHub workflow action.</p>
+
+  <a id="SDKgen-Generator-CLI"></a>
+  <h3><a href="https://github.com/apioo/sdkgen-cli">SDKgen-Generator-CLI</a></h3>
+  <p>A simple binary written in go which allows you to generate code.</p>
+
   <div class="typeschema-edit">
     <a href="https://github.com/apioo/typeapi/blob/main/www/resources/template/<?php echo pathinfo(__FILE__, PATHINFO_BASENAME); ?>"><i class="bi bi-pencil"></i> Edit this page</a>
   </div>

www/resources/template/index.php

@@ -24,13 +24,13 @@
     </div>
     <div class="col-md-6">
       <div class="psx-object">
-        <h1>TypeAPI</h1>
+        <h3>TypeAPI</h3>
         <div class="example-box"><pre><code class="json"><?php echo $example->schema; ?></code></pre></div>
       </div>
     </div>
     <div class="col-md-6">
       <div class="psx-object">
-        <h1>Client SDK</h1>
+        <h3>Client SDK</h3>
         <div class="example-box"><pre><code class="javascript"><?php echo htmlspecialchars($example->code); ?></code></pre></div>
       </div>
     </div>

www/resources/template/specification.php

@@ -37,23 +37,23 @@
   <hr>
 
   <a id="Goals"></a>
-  <h3>Goals</h3>
+  <h2>Goals</h2>
   <ul>
     <li>Provide a format to generate clean and ready to use code</li>
     <li>Provide a simple and stable specification where you can easily build a code generator</li>
     <li>Optimized for static typed and object-oriented programming languages</li>
   </ul>
 
   <a id="Non-Goals"></a>
-  <h3>Non-Goals</h3>
+  <h2>Non-Goals</h2>
   <ul>
     <li>Describe every possible REST API structure and JSON payload</li>
     <li>Supporting many different Content-Types like XML or <code>x-www-form-urlencoded</code></li>
     <li>Providing complex JSON validation capabilities</li>
   </ul>
 
   <a id="Reasoning"></a>
-  <h3>Reasoning</h3>
+  <h2>Reasoning</h2>
   <p>For a long time the OpenAPI community was divided into two communities, one building documentation tools and the
   other trying to build code generation tools. Building documentation tools has very different requirements than
   building code generation tools. For a documentation tool you can simply render and show all defined endpoints and