houseaccount 0.10.1 → 0.11.0

package/README.md

@@ -22,10 +22,10 @@ gem install houseaccount
 
 ```ruby
 # Gemfile
-gem 'houseaccount', '~> 0.10.0'
+gem 'houseaccount', '~> 0.11.0'
 ```
 
-`~> 0.10.0` stops short of `0.11`, since below 1.0 a minor release may break whatever it likes.
+`~> 0.11.0` stops short of `0.12`, since below 1.0 a minor release may break whatever it likes.
 Rails 8.1 and Ruby 3.2 are the minimum.
 
 ### From npm
@@ -59,7 +59,7 @@ Stimulus application rather than taking the house's:
 import WallController from 'houseaccount/controllers/wall_controller.js'
 ```
 
-Pin as a Gemfile does, and for the same reason: `"houseaccount": "~0.10.0"` stops short of `0.11`.
+Pin as a Gemfile does, and for the same reason: `"houseaccount": "~0.11.0"` stops short of `0.12`.
 
 A page takes the gem's layout, and wears the same head:
 
@@ -95,7 +95,7 @@ which Pages redirects away from.
 
 With the gem in the bundle an app serves `/css/houseaccount.css`, `/js/houseaccount.js`,
 `/theme/*`, `/font/*`, `/logo/*` and `/favicon/*` itself — and its own version's copy under
-`/v0.10.0/`, which is what the head helper links, cached for a year — answers a 400, 404, 406, 422 or 500
+`/v0.11.0/`, which is what the head helper links, cached for a year — answers a 400, 404, 406, 422 or 500
 with the house's own page, and has these helpers in every view:
 
 ```erb
@@ -240,12 +240,23 @@ Those follow the latest release. Every release is also kept whole under its own
 forever and cached for a year, for a page that would rather move on its own terms:
 
 ```html
-<link rel='stylesheet' href='https://design.houseaccount.com/v0.10.0/css/houseaccount.css'>
-<script type='module' src='https://design.houseaccount.com/v0.10.0/js/houseaccount.js'></script>
+<link rel='stylesheet' href='https://design.houseaccount.com/v0.11.0/css/houseaccount.css'>
+<script type='module' src='https://design.houseaccount.com/v0.11.0/js/houseaccount.js'></script>
 ```
 
-A host with a Content Security Policy allows that origin for `style-src`, `script-src` and
-`font-src`.
+The same two files come from any CDN that carries the npm package, for a page that would
+rather not depend on the site at all:
+
+```html
+<link rel='stylesheet' href='https://cdn.jsdelivr.net/npm/houseaccount@0.11.0/css/houseaccount.css'>
+<script type='module' src='https://cdn.jsdelivr.net/npm/houseaccount@0.11.0/js/houseaccount.js'></script>
+```
+
+The palettes are beside them, at `/theme/nord.css` and the rest. A published version is never
+written again, so that URL is owed its bytes for as long as npm stands.
+
+A host with a Content Security Policy allows whichever origin it names for `style-src`,
+`script-src` and `font-src`.
 
 ## What is in the bundle
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "houseaccount",
-  "version": "0.10.1",
+  "version": "0.11.0",
   "description": "HouseAccount's front end: Bootstrap 6 with the house customizations, the Stimulus controllers behind every HouseAccount page, and the brand's own CSS.",
   "license": "MIT",
   "type": "module",
@@ -10,6 +10,10 @@
     "app/fonts",
     "app/javascript",
     "app/stylesheets",
+    "public/css",
+    "public/font",
+    "public/js",
+    "public/theme",
     "vendor",
     "MIT-LICENSE"
   ],