Correcting & clarifying docs (#72)

* Fix clean_urls config example

* Clarify purpose and usage of these CNBs

Author: mars

README.md

@@ -1,8 +1,19 @@
 # Heroku Cloud Native Buildpacks: Front-end Web
 
-🚧 **This repo is experimental.** Use at your own risk. 🚧
+This repository is the home of Heroku Cloud Native Buildpacks for Front-end Web apps, also known as: websites, static web apps (SWA), single-page apps (SPA), progressive web apps (PWA), and browser apps.
 
-This repository is the home of Heroku Cloud Native Buildpacks for Front-end Web apps, also known as: static websites, static web apps (SWA), single-page apps (SPA), and browser apps.
+## What It Is
+
+These Front-end Web buildpacks produce an OCI (container image) that launches a web server to host a directory of HTML, CSS, and Javascript files. The build process can run Javascript or other programs to produce the website, or simply read a directory of files as the web root. All front-end frameworks are supported, while some popular frameworks are optimized with preset web server configuration.
+
+The result is a static website:
+* high-efficiency, high-performance server
+* secure by default with minimal, purpose-built features
+* separates front-end development (web UIs) from server-side programming (backend APIs).
+
+### What It Is Not
+
+This static web server does not run custom code on the server. If an app requires a custom server-side web process, then use the appropriate [language-specific CNBs](https://github.com/heroku/buildpacks).
 
 ## Included Buildpacks
 
@@ -18,18 +29,20 @@ Buildpacks that provide a specific server-side component.
 
 ### Framework Buildpacks
 
-Lower-level buildpacks that detect specific source layouts, frameworks, or tools, to automate configuration of build process and heroku/static-web-server.
+Lower-level buildpacks that detect specific source layouts, frameworks, or tools, to automate configuration of build process and `heroku/static-web-server`.
 
 | ID                           | Name                                                              | Provides                            |
 |------------------------------|-------------------------------------------------------------------|-------------------------------------|
-| `heroku/website-ember`       | [Website (Ember.js)](buildpacks/website-ember/README.md)          | auto-detect for ember-cli           |
-| `heroku/website-nextjs`      | [Website (Next.js)](buildpacks/website-nextjs/README.md)          | auto-detect for Next.js             |
+| `heroku/website-ember`       | [Website (Ember.js)](buildpacks/website-ember/README.md)          | auto-detect for [Ember.js](https://cli.emberjs.com) |
+| `heroku/website-nextjs`      | [Website (Next.js)](buildpacks/website-nextjs/README.md)          | auto-detect for [Next.js](https://nextjs.org) ([static exports](https://nextjs.org/docs/app/guides/static-exports)) |
 | `heroku/website-public-html` | [Website (Public HTML)](buildpacks/website-public-html/README.md) | auto-detect for `public/index.html` |
-| `heroku/website-vite`        | [Website (Vite)](buildpacks/website-vite/README.md)               | auto-detect for vite                |
+| `heroku/website-vite`        | [Website (Vite)](buildpacks/website-vite/README.md)               | auto-detect for [Vite](https://vite.dev) |
 
 ## Usage
 
-See the individual buildpack documentation, linked in the above table.
+[Configure the Static Web Server](buildpacks/static-web-server/README.md) as the last buildpack for your app, along with other language buildpacks the build might require.
+
+The framework buildpacks are optional. They automate detection of static web apps in source code when using [`heroku/builder`](https://github.com/heroku/cnb-builder-images), such as when building a CNB app on Heroku, but are not required when manually configuring buildpacks.
 
 ## Dev Notes
 
@@ -39,14 +52,6 @@ See the individual buildpack documentation, linked in the above table.
 cargo test -- --include-ignored
 ```
 
-### Updating Node.js
-
-These buildpacks include the heroku/nodejs buildpack, packaged at a specific version. To update the Node.js buildpack:
-
-1. check the [Docker Hub listing](https://hub.docker.com/r/heroku/buildpack-nodejs/tags) for the latest version
-1. update the version specified in the website-nodejs [buildpack](meta-buildpacks/website-nodejs/buildpack.toml) & [package](meta-buildpacks/website-nodejs/package.toml) specifications
-1. ensure integration tests still pass, see [Run Tests](#run-tests)
-
 ### Releasing A New Version
 
 [Action workflows](https://github.com/heroku/buildpacks-frontend-web/actions) are used to automate the release process:

buildpacks/static-web-server/README.md

@@ -297,8 +297,8 @@ sampling_thereafter = 1000
 Support for pretty, extensionless URLs, leaving `.html` off of the request path.
 
 ```toml
-[com.heroku.static-web-server.caddy_server_opts.clean_urls]
-enabled = true
+[com.heroku.static-web-server.caddy_server_opts]
+clean_urls = true
 ```
 
 For example, a request to `example.com/support` will be tried in the document root: