Reposition Eido as an end-to-end generative-art toolkit

The hero, Scope page, and README all opened with 'declarative,
data-driven image language' — accurate but abstract. Users asking
'can I use Eido for my practice?' had to infer the answer from the
features list and the limitations page's alternatives section.

Front-loaded two claims in the voice the artists we're talking to
already use:

1. It's an end-to-end toolkit. The same scene targets screens
   (PNG/GIF/animated SVG), print (real units, DPI, archival TIFF),
   and fabrication (stroke-only SVG with pen layers, polyline
   export). The Scope page now breaks this down explicitly.

2. It's an art tool, not a charting library. The Scope page says
   this directly, and the hero subtitle links to it so readers who
   land on the home page don't have to read to the bottom of
   /limitations/ to learn the tool's orientation.

No code changes — only landing hero, Scope 'What Eido Is' section,
and README opener.

Author: leifericf

README.md

@@ -1,9 +1,17 @@
 # Eido
 
-**Eido — describe what you see**
-
-Eido is a declarative, data-driven image language for Clojure.
-Describe what you see as plain data — not drawing instructions.
+**An end-to-end Clojure toolkit for generative artists — from REPL sketch to screen, print, and plotter.**
+
+Eido is a declarative, data-first library for generative art. You
+describe images as plain data — maps, vectors, keywords — and render
+the same scene to whatever medium you're working in: raster PNG,
+animated GIF or SVG, archival TIFF for print, or stroke-only SVG for
+pen plotters and CNC.
+
+Eido is an art tool, not a charting library — it was designed around
+the practice of generative artists, plotter artists, and edition
+makers. Data visualization is possible, but a dedicated charting
+library will serve you better there.
 
 <p align="center">
   <img src="https://eido.leifericf.com/images/galaxy.gif" width="200" alt="Particle galaxy" />

examples/site/pages.clj

@@ -2326,12 +2326,19 @@ CircleOp{...original-shape...}"]]
     :title "What Eido Is"
     :content
     [:div
-     [:p "Eido is a " [:strong "declarative, data-first Clojure library"] " for computational and generative art. You describe images as plain data — maps, vectors, keywords — and Eido renders them."]
+     [:p "Eido is a " [:strong "declarative, data-first Clojure library for generative art"] ". You describe images as plain data — maps, vectors, keywords — and Eido renders them to the medium you're working in."]
+     [:p "It's an " [:strong "end-to-end toolkit"] " for the full arc of a generative art practice — from REPL sketching to finished output. One library covers:"]
+     [:ul
+      [:li [:strong "Screen"] " — raster PNG, animated GIF, and animated SVG for digital editions and screens."]
+      [:li [:strong "Print"] " — real-world units, paper presets, DPI control, and archival TIFF for giclée and fine-art printing."]
+      [:li [:strong "Fabrication"] " — stroke-only SVG with pen layers, deduplication, and travel optimization for pen plotters, and polyline export for CNC mills and laser cutters."]
+      [:li [:strong "Editions"] " — deterministic seed-driven series with parameter specs, trait manifests, and contact sheets."]]
+     [:p "The design commitments that keep the toolkit small:"]
      [:ul
       [:li [:strong "A library, not a framework."] " Every function takes data and returns data. You bring your own workflow, editor, and REPL."]
       [:li [:strong "Zero production dependencies."] " Just Clojure and the standard library. Nothing to install, nothing to break."]
-      [:li [:strong "REPL-driven."] " The primary development loop is edit → evaluate → inspect → adjust. No compile step, no build tool."]
-      [:li [:strong "Designed for"] " screen output, print production, plotter art, long-form edition series, and exploratory generative work."]]]}
+      [:li [:strong "REPL-driven."] " The primary development loop is edit → evaluate → inspect → adjust. No compile step, no build tool."]]
+     [:p [:strong "Eido is an art tool."] " It was designed around the practice of generative artists — plotter artists, edition makers, creative coders — not around the needs of data visualization, dashboards, or scientific charting. Data-viz work is possible with the same primitives, but the API, gallery, defaults, and documentation all pull toward artmaking. If your primary goal is communicating data, reach for a dedicated charting library instead (see " [:a {:href "#alternatives"} "When to Use Something Else"] ")."]]}
 
    {:id "practical-limits"
     :title "Practical Limits"

examples/site/render.clj

@@ -1383,8 +1383,13 @@
        "Beta — The core API is stabilizing. Breaking changes may still occur between releases, but the fundamentals are in place."]
       [:section.hero
        [:h1.hero-title "Eido"]
-       [:p.hero-tagline "Describe what you see as plain data"]
-       [:p {:style "color: #6a6a7a; font-size: 0.85rem; margin-top: 0.3rem; font-style: italic;"} "From Greek " [:em "eido"] " \u2014 \"I see\""]
+       [:p.hero-tagline
+        "An end-to-end Clojure toolkit for generative artists — "
+        "from REPL sketch to screen, print, and plotter."]
+       [:p {:style "color: #6a6a7a; font-size: 0.85rem; margin-top: 0.3rem; font-style: italic;"}
+        "From Greek " [:em "eido"] " \u2014 \"I see.\" "
+        "A tool for making art, not charts — see "
+        [:a {:href "./limitations/" :style "color: #8a8a9a"} "Scope"] "."]
        [:div#hero-images.hero-images]
        [:div.hero-links
         [:a.hero-link.hero-link--primary {:href "./gallery/"} "Browse Gallery"]