Updated description

Author: akclace

config/_default/languages.en.toml

@@ -2,30 +2,30 @@ languageCode = 'en-us'
 languageName = "English"
 weight = 1
 
-title = "Clace : Hypermedia driven web tools platform"
+title = "Clace : Web App Deployment Platform"
 copyright = "Copyright © 2024 ClaceIO, LLC"
 
 
 [languages]
-  [languages.en]
-    [languages.en.params]
-        displayName = "EN"
-        isoCode = "en"
-        rtl = false
-        dateFormat = "2 January 2006"
-        description = "Hypermedia driven web tools platform"
+[languages.en]
+[languages.en.params]
+displayName = "EN"
+isoCode = "en"
+rtl = false
+dateFormat = "2 January 2006"
+description = "Web app deployment platform"
 
 [params]
-  mainSections = ["Features", "Docs", "Blog", "About"]
+mainSections = ["Features", "Docs", "Blog", "About"]
 
 [params.author]
-  name = "Clace"
-  headline = "Hypermedia Driven Web Tools Platform"
-  links = [
-     { email = "mailto:[email protected]" },
-     { github = "https://github.com/claceio" },
-     { twitter = "https://twitter.com/akclace" },
-     # { linkedin = "https://www.linkedin.com/company/claceio"},
-     { rss = "https://clace.io/blog/index.xml"},
-     { discord = "https://discord.gg/t2P8pJFsd7"},
-  ]
+name = "Clace"
+headline = "Web App Deployment Platform"
+links = [
+    { email = "mailto:[email protected]" },
+    { github = "https://github.com/claceio" },
+    { twitter = "https://twitter.com/akclace" },
+    # { linkedin = "https://www.linkedin.com/company/claceio"},
+    { rss = "https://clace.io/blog/index.xml" },
+    { discord = "https://discord.gg/t2P8pJFsd7" },
+]

content/_index.md

@@ -17,16 +17,16 @@ cascade:
 
 <h2>What is Clace?</h2>
 
-Clace is an Apache-2.0 licensed project building a platform to develop and deploy hypermedia driven web apps for internal tools. For running multiple web applications on a single machine, Clace provides functionality which usually requires stitching together multiple services: reverse proxy like nginx/caddy (for domain/path based routing, TLS certs, static file serving), application server like uwsgi/gunicorn with micro-framework like flask (for API handling) and deployment infrastructure like containers/VMs/k8s (for isolation across apps, versioning and staged deployments, gitops). For internal tools, Clace provides similar functionality in a single lightweight binary.
+Clace is an Apache-2.0 licensed project building a platform to develop and deploy web apps for internal tools. For running multiple web applications on a single machine, Clace provides functionality which usually requires stitching together multiple services: reverse proxy like nginx/caddy (for domain/path based routing, TLS certs, static file serving), application server like uwsgi/gunicorn with micro-framework like flask (for API handling) and deployment infrastructure like containers/VMs/k8s (for isolation across apps, versioning and staged deployments). For internal tool deployment, Clace provides similar functionality in a single lightweight binary, with gitops workflow out of the box.
 
 <br>
 <h2>What can it do?</h2>
 <p>
-Clace can be used to easily develop and deploy hypermedia driven web applications which are secure and portable. Clace can run web apps for personal use and also host applications for access over the public internet. Clace can be used by teams to host internal applications. Clace supports building a hypermedia driven web interface for an existing API's, a backend-for-frontend type pattern. Developing a web UI for command line applications is another use-case. CRUD applications and applications which glue together backend APIs are good candidates for Clace apps.
+Clace can be used to easily develop and deploy web applications which are secure and portable. Clace can run web apps for personal use and also host applications for access over the public internet. Clace can be used by teams to host internal applications. Clace supports building a hypermedia driven web interface for an existing API's, a backend-for-frontend type pattern. Developing a web UI for command line applications is another use-case. CRUD applications and applications which glue together backend APIs are good candidates for Clace apps.
 <br>
 
 <h2>How does it work?</h2>
-Clace and its plugins are implemented in go. User applications are developed and configured in <a href="https://github.com/google/starlark-go">Starlark</a>, which uses a python inspired syntax. Users of Clace write only Starlark and HTML templates. The backend code runs in a security sandbox and access to plugins need to be explicitly permitted. The API routes are defined to be Hypermedia first, using template partials to drive the UI interactions. <a href="https://htmx.org/">HTMX</a> is used for server interactions from the UI.
+Clace and its plugins are implemented in go. User applications are developed and configured in <a href="https://github.com/google/starlark-go">Starlark</a>, which uses a python inspired syntax. Users of Clace write only Starlark and HTML templates. The backend code runs in a security sandbox and access to plugins need to be explicitly permitted. The API routes are defined to be Hypermedia first, using template partials to drive the UI interactions. <a href="https://htmx.org/">HTMX</a> is used for server interactions from the UI. Application backends can be defined in a Dockerfile, Clace builds and deploys the containers to serve the application.
 
 There are no Python or Javascript dependencies to install, no containers to create, no yaml files to manage. Application updates are done with a gitops workflow, with no-build step. Staging and preview environments are available for apps. Clace integrates with TailwindCSS/DaisyUI for UI styling and has <a href="https://esbuild.github.io/">esbuild</a> built-in for <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules">ESM</a> support. Data persistence to sqlite is supported using a document store interface. Clace manages request routing and TLS certificates creation and renewal, so a separate web server is not required.