Add overview description

Author: craigshoemaker

articles/static-apps/overview.md

@@ -34,6 +34,16 @@ Back-end API functionality is powered by Azure Functions which provides automati
 - **Back-end routing rules** enabling full control over the content and routes you serve.
 - **Generated staging versions** powered by pull requests enabling preview versions of your site before publishing.
 
+## Overview
+
+The workflow of Azure Static Web Apps is tailored to a developer's daily workflow. Apps are built and deployed based off GitHub interactions.
+
+When you create a Azure Static Web Apps resource, you point a GitHub repository and select a branch to track. As commits are pushed or PRs are accepted against this branch, a GitHub Actions workflow starts. The workflow builds the app for production and deploys it to Azure.
+
+Static web apps are commonly built using libraries and frameworks like Angular, React, Svelte, or Vue. These apps include HTML, CSS, JavaScript, and image assets that make up the application. With a traditional web server, these assets are served from a single server alongside any required API endpoints.
+
+In a Static Web Apps site, static assets are separated from a traditional web server and are instead served from points geographically distributed around the world. This distribution makes serving files much faster as files are physically closer to end users. In addition, API endpoints are hosted using a [serverless architecture](../azure-functions/functions-overview.md), which avoids the need for a full back-end server all together.
+
 ## What you can do with Static Web Apps
 
 - **Build modern JavaScript applications** with frameworks and libraries like [Angular](https://angular.io/), [React](https://reactjs.org/), [Svelete](https://svelte.dev/), [Vue](https://vuejs.org/) with an [Azure Functions](https://azure.microsoft.com/services/functions/) back-end.