index.html

---
layout: home
---
<div class="jumbotron">
  <div class="container">
    <h1>Facility <small>API Framework</small></h1>
    <p>Design, implement, consume, and document APIs with tools and libraries that work with simple API definitions.</p>
    <p>
      <a href="/why" class="btn btn-primary">Why Facility?</a>
      <a href="/start" class="btn btn-primary">Get Started</a>
  </div>
</div>
<div class="container">
  <div class="row">
    <div class="col-sm-6 col-lg-3">
      <h3>Design</h2>
      <p>Use the <a href="/editor">Live Editor</a> (or any text editor) to design your API using the simple <a href="/define/fsd">FSD format</a>, or convert an <a href="/define/swagger">OpenAPI</a> spec to FSD.</p>
      <p>Each method of your API has a name and a corresponding HTTP path. Clients POST the JSON request and receive a JSON response.</p>
      <p>Make your API less RPC-ish and more RESTful by adding <a href="/define/fsd#attributes">attributes</a> to your FSD methods and data fields.</p>
      <p>Commit your API definition to source control for revision tracking and peer review.</p>
      <p>Run <a href="/generate">command-line tools</a> from your automated builds to validate the syntax and ensure that generated code and documentation stays up-to-date.</p>
    </div>
    <div class="col-sm-6 col-lg-3">
      <h3>Implement</h2>
      <p>Facility <a href="/generate/csharp">generates a C# interface</a> with one method for each method of your API.</p>
      <p>You write a C# class that implements that interface and then <a href="/generate/aspnet">integrate that class</a> into an ASP.NET app (Web API or Core).</p>
      <p>Facility takes care of the HTTP mapping so you can focus on the implementation logic.</p>
      <p>Your C# class is easily unit tested, encourages good separation of concerns, and is more flexible than a hand-coded controller.</p>
      <p>Edit the FSD and regenerate the code to rapidly add new features to your API.</p>
      <p>Alternatively, <a href="/define/swagger">convert your FSD to OpenAPI</a> and find support for your favorite API framework among the many <a href="https://swagger.io/tools/">supported tools</a>.</p>
      <p>Better yet, help us support your favorite framework by <a href="/contribute">contributing</a> to this open source project.
    </div>
    <div class="col-sm-6 col-lg-3">
      <h3>Consume</h2>
      <p>Facility generates client libraries in <a href="/generate/csharp">C#</a> and <a href="/generate/javascript">JavaScript/TypeScript</a>.</p>
      <p>Publish to <a href="https://www.nuget.org/">NuGet</a> and <a href="https://www.npmjs.com/">npm</a> to make it easy for clients to use your API.</p>
      <p>The generated code is designed to avoid breaking changes even as your API evolves.</p>
      <p>Don't repeat yourself: The C# client library and the server implementation use the same C# interfaces and classes.</p>
      <p>Generate TypeScript to leverage type information while maintaining JavaScript compatibility.</p>
      <p>To build client libraries for other languages and frameworks, <a href="/define/swagger">convert your FSD to OpenAPI</a> and use any of the <a href="https://swagger.io/tools/">supported tools</a>.</p>
      <p>Better yet, help us support your favorite language by <a href="/contribute">contributing</a> to this open source project.
    </div>
    <div class="col-sm-6 col-lg-3">
      <h3>Document</h2>
      <p><a href="/generate/markdown">Generate Markdown documentation</a> for your API.</p>
      <p>Push the documentation to <a href="https://github.com/">GitHub</a> for easy reading at your GitHub repository.</p>
      <p>Better yet, use the Markdown support of <a href="https://pages.github.com/">GitHub Pages</a> to display the documentation on your project website.</p>
      <p>You can also <a href="/define/fsd/swagger">convert your FSD to OpenAPI</a> and use <a href="https://swagger.io/swagger-ui/">Swagger UI</a>.</p>
    </div>
  </div>
</div>