compony 0.11.11 → 0.11.13

data/doc/file.edit.html

@@ -63,11 +63,11 @@
 <p><a href="/doc/guide/pre_built_components_md.html">List of pre-built components</a></p>
 </li></ul>
 
-<h1 id="label-Pre-built+components-3A+Edit">Pre-built components: Edit</h1>
+<h1 id="pre-built-components-edit">Pre-built components: Edit</h1>
 
 <p>This component is the Compony equivalent to a typical Rails controller’s <code>edit</code> and <code>update</code> actions.</p>
 
-<p><code>Compony::Components::Edit</code> is a resourceful standalone component based on href="./with_form_md.html"></a> that listens to two verbs:</p>
+<p><code>Compony::Components::Edit</code> is a resourceful standalone component based on <a href="./with_form_md.html"><code>WithForm</code></a> that listens to two verbs:</p>
 <ul><li>
 <p>GET will cause the Edit component to load a record given by ID and render the form based on that record. If the record does not exist, a HTTP 404 code is returned.</p>
 </li><li>
@@ -99,7 +99,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:47 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.example.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Example">Example</h1>
+<h1 id="example">Example</h1>
 
 <p>To get you a rough idea what working with Compony feels like, let’s look at a small dummy application using Compony from scratch, to make this example as explicit as possible. In practice, much of the logic shown here would be moved to abstract components that you can inherit from.</p>
 
@@ -70,7 +70,7 @@
 
 <p>Let’s implement a simple user management page with Compony. User’s have a name, an integer age, a comment, as well as a role (which we will conveniently model using <code>AnchorModel</code>: <a href="https://github.com/kalsan/anchormodel">github.com/kalsan/anchormodel</a>). We want to be able to list, show, create, edit and destroy users. Users having the role Admin shall not be destroyed.</p>
 
-<h2 id="label-The+User+model">The User model</h2>
+<h2 id="the-user-model">The User model</h2>
 
 <p>We’ll assume a model that has the standard Rails schema:</p>
 
@@ -108,7 +108,7 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<h2 id="label-The+Show+component">The Show component</h2>
+<h2 id="the-show-component">The Show component</h2>
 
 <p>This components loads a user by reading the param <code>id</code>. It then displays a simple table showing all the fields defined above.</p>
 
@@ -164,11 +164,11 @@
 
 <p>Here is what our Show component looks like when we have a layout with the bare minimum and no styling at all:</p>
 
-<p><img src="/doc/imgs/intro-example-show.png"></p>
+<p><img src="/doc/imgs/intro-example-show.png" alt="Screenshot"> of our component with an absolutely minimal layout</p>
 
 <p>It is important to note that button styles, navigation, notifications etc. are handled by the application layout. In this and the subsequent screenshots, we explicitely use minimalism, as it makes the generated HTML clearer.</p>
 
-<h2 id="label-The+Destroy+component">The Destroy component</h2>
+<h2 id="the-destroy-component">The Destroy component</h2>
 
 <p>Compony has a built-in abstract <code>Destroy</code> component which displays a confirmation message and destroys the record if the verb is <code>DELETE</code>. This is a good example for how DRY code can become for “boring” components. Since everything is provided with an overridable default, components without special logic can actually be left blank:</p>
 
@@ -178,9 +178,9 @@
 
 <p>Note that this component is fully functional. All is handled by the class it inherits from:</p>
 
-<p><img src="/doc/imgs/intro-example-destroy.png"></p>
+<p><img src="/doc/imgs/intro-example-destroy.png" alt="Screenshot"> of the destroy component</p>
 
-<h2 id="label-The+New+component+and+the+Form+component">The New component and the Form component</h2>
+<h2 id="the-new-component-and-the-form-component">The New component and the Form component</h2>
 
 <p>Compony also has a pre-built abstract <code>New</code> component that handles routing and resource manipulation. It combines the controller actions <code>new</code> and <code>create</code>, depending on the HTTP verb of the request. Since it’s pre-built, any “boring” code can be omitted and our <code>New</code> components looks like this:</p>
 
@@ -212,9 +212,9 @@
 
 <p>This is enough to render a fully functional form that creates new users:</p>
 
-<p><img src="/doc/imgs/intro-example-new.png"></p>
+<p><img src="/doc/imgs/intro-example-new.png" alt="New"> form</p>
 
-<h2 id="label-The+Edit+component">The Edit component</h2>
+<h2 id="the-edit-component">The Edit component</h2>
 
 <p>Just like <code>New</code>, <code>Edit</code> is a pre-built component that handles routing and resource manipulation for editing models, combinding the controller actions <code>edit</code> and <code>update</code> depending on the HTTP verb. It uses that same <code>Form</code> component we wrote above and thus the code is as simple as:</p>
 
@@ -224,9 +224,9 @@
 
 <p>It then looks like this:</p>
 
-<p><img src="/doc/imgs/intro-example-edit.png"></p>
+<p><img src="/doc/imgs/intro-example-edit.png" alt="Edit"> form</p>
 
-<h2 id="label-The+Index+component">The Index component</h2>
+<h2 id="the-index-component">The Index component</h2>
 
 <p>This component should list all users and provide buttons to manage them. We’ll build it from scratch and make it resourceful, where <code>@data</code> holds the ActiveRecord relation.</p>
 
@@ -273,7 +273,7 @@
 
 <p>The result looks like this:</p>
 
-<p><img src="/doc/imgs/intro-example-index.png"></p>
+<p><img src="/doc/imgs/intro-example-index.png" alt="Index"> component</p>
 
 <p>Note how the admin’s delete button is disabled due to the feasibility framework. Pointing the mouse at it causes a tooltip saying: “Cannot destroy admins.”, as specified in the model’s prevention.</p>
 
@@ -281,7 +281,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:46 2026 by
+  Generated on Tue Aug 18 14:36:33 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.example_advanced.html

@@ -60,13 +60,13 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Advanced+example">Advanced example</h1>
+<h1 id="advanced-example">Advanced example</h1>
 
 <p><a href="/doc/guide/example_md.html">example.md</a> shows the basics. This one combines patterns you hit in real apps: a custom form, feasibility, exposed intents, a CSV export endpoint, a <code>before_render</code> guard, and a virtual-model launch form for a background job.</p>
 
 <p>Domain: invoicing. An <code>Invoice</code> has line items, can be locked, exported as CSV, and a background “send reminders” job can be launched from a non-persistent form.</p>
 
-<h2 id="label-The+models">The models</h2>
+<h2 id="the-models">The models</h2>
 
 <pre class="code ruby"><code class="ruby"><span class='comment'># app/models/invoice.rb
 </span><span class='kw'>class</span> <span class='const'>Invoice</span> <span class='op'>&lt;</span> <span class='const'>ApplicationRecord</span>
@@ -99,7 +99,7 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<h2 id="label-Index+with+a+CSV+export+endpoint+and+exposed+intents">Index with a CSV export endpoint and exposed intents</h2>
+<h2 id="index-with-a-csv-export-endpoint-and-exposed-intents">Index with a CSV export endpoint and exposed intents</h2>
 
 <p>One component, two routes: the HTML list and a <code>.csv</code> download. The CSV intent is exposed so the layout renders a “Download CSV” button in the page header.</p>
 
@@ -137,14 +137,14 @@
 
 <p>Notes:</p>
 <ul><li>
-<p><code>respond :csv</code> handles <code>GET /invoices.csv</code>. Because overriding <code>respond</code> <strong>skips the  default <code>authorize</code></strong> (see <a href="/doc/guide/gotchas_md.html#3-overriding-respond-skips-authorization">gotchas.md</a>),  the CSV branch re-checks the ability itself.</p>
+<p><code>respond :csv</code> handles <code>GET /invoices.csv</code>. Because overriding <code>respond</code> <strong>skips the default <code>authorize</code></strong> (see <a href="/doc/guide/gotchas_md.html#3-overriding-respond-skips-authorization">gotchas.md</a>), the CSV branch re-checks the ability itself.</p>
 </li><li>
 <p><code>path: { format: :csv }</code> on the exposed intent makes its button point at <code>.csv</code>.</p>
 </li><li>
-<p>The layout renders exposed intents of <code>Compony.root_comp</code> — see  <a href="/doc/guide/intents_md.html#rendering-exposed-intents">intents.md</a>.</p>
+<p>The layout renders exposed intents of <code>Compony.root_comp</code> — see <a href="/doc/guide/intents_md.html#rendering-exposed-intents">intents.md</a>.</p>
 </li></ul>
 
-<h2 id="label-A+custom+Form+with+nested+line+items">A custom Form with nested line items</h2>
+<h2 id="a-custom-form-with-nested-line-items">A custom Form with nested line items</h2>
 
 <p><code>Edit</code>/<code>New</code> look for <code>Components::Invoices::Form</code> by default. We write it with <code>accepts_nested_attributes_for</code> via <code>simple_form</code>‘s <code>simple_fields_for</code>, and whitelist the nested params with a raw <code>schema_line</code>.</p>
 
@@ -176,9 +176,9 @@
 <span class='kw'>end</span>
 </code></pre>
 
-<p><code>schema_field :customer</code> (association name) lets Compony add <code>customer_id</code> automatically — passing <code>:customer_id</code> here would not work (<a href="/doc/guide/gotchas_md.html#4-schema_field-with-the-foreign-key-name">gotchas.md</a>).</p>
+<p><code>schema_field :customer</code> (association name) lets Compony add <code>customer_id</code> automatically —passing <code>:customer_id</code> here would not work (<a href="/doc/guide/gotchas_md.html#4-schema_field-with-the-foreign-key-name">gotchas.md</a>).</p>
 
-<h2 id="label-Edit-3A+thin-2C+plus+a+guard+and+a+custom+redirect">Edit: thin, plus a guard and a custom redirect</h2>
+<h2 id="edit-thin-plus-a-guard-and-a-custom-redirect">Edit: thin, plus a guard and a custom redirect</h2>
 
 <p><code>Edit</code> inherits all CRUD wiring. We only add a <code>before_render</code> guard (independent of HTTP verb) and override where a successful save lands.</p>
 
@@ -200,7 +200,7 @@
 
 <p><code>Components::Invoices::New</code>, <code>Show</code>, <code>Destroy</code> can stay empty — the pre-built parents do the work.</p>
 
-<h2 id="label-A+virtual-model+launch+form+for+a+background+job">A virtual-model launch form for a background job</h2>
+<h2 id="a-virtual-model-launch-form-for-a-background-job">A virtual-model launch form for a background job</h2>
 
 <p>“Send reminders” should pop a small form (which customers? how many days overdue?) and, on submit, queue a job — nothing is persisted. Inherit <code>New</code>, back it with a <code>Compony::VirtualModel</code>, and take over <code>on_created_respond</code>.</p>
 
@@ -247,7 +247,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:46 2026 by
+  Generated on Tue Aug 18 14:36:33 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.feasibility.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Feasibility">Feasibility</h1>
+<h1 id="feasibility">Feasibility</h1>
 
 <p>When a user has the permission to perform an action in general, but it is currently not feasible (for instance if the concerned object is incomplete, or if right now is not the right time to do the action), buttons pointing to that action should be disabled and a HTML <code>title</code> attribute should cause a tooltip explaining why this action cannot be performed right now.</p>
 
@@ -105,7 +105,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:46 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.form.html

@@ -63,13 +63,13 @@
 <p><a href="/doc/guide/pre_built_components_md.html">List of pre-built components</a></p>
 </li></ul>
 
-<h1 id="label-Pre-built+components-3A+Form">Pre-built components: Form</h1>
+<h1 id="pre-built-components-form">Pre-built components: Form</h1>
 
-<p>This component holds a form and should only be instantiated by the <code>form_comp</code> call of a component that inherits from href="./with_form_md.html"></a>.</p>
+<p>This component holds a form and should only be instantiated by the <code>form_comp</code> call of a component that inherits from <a href="./with_form_md.html"><code>WithForm</code></a>.</p>
 
-<p><code>Compony::Components::Form</code> is an abstract base class for any components presenting a regular form. This class comes with a lot of tooling for rendering forms and inputs, as well as validating parameters. When the component is rendered, the Gem SimpleForm is used to create the actual form: <a href="https://github.com/heartcombo/simple_form">github.com/heartcombo/simple_form</a>.</p>
+<p><code>Compony::Components::Form</code> is an abstract base class for any components presenting a regular form. This class comes with a lot of tooling for rendering forms and inputs, as well as validating parameters. When the component is rendered, the Gem SimpleForm is used to create the actual form: <a href="https://github.com/heartcombo/simple_form">https://github.com/heartcombo/simple_form</a>.</p>
 
-<p>Parameters are structured like typical Rails forms. For instance, if you have a form for a <code>User</code> model and the attribute is <code>first_name</code>, the parameter looks like <code>user[first_name]=Tom</code>. In this case, we will call <code>user</code> the <code>schema_wrapper_key</code>. Parameters are validated using Schemacop: <a href="https://github.com/sitrox/schemacop">github.com/sitrox/schemacop</a>.</p>
+<p>Parameters are structured like typical Rails forms. For instance, if you have a form for a <code>User</code> model and the attribute is <code>first_name</code>, the parameter looks like <code>user[first_name]=Tom</code>. In this case, we will call <code>user</code> the <code>schema_wrapper_key</code>. Parameters are validated using Schemacop: <a href="https://github.com/sitrox/schemacop">https://github.com/sitrox/schemacop</a>.</p>
 
 <p>The following DSL calls are provided by the Form component:</p>
 <ul><li>
@@ -113,7 +113,7 @@
 
 <p>Both calls respect Cancancan’s <code>permitted_attributes</code> directive. This means that you can safely declare <code>field</code> and <code>schema_field</code> in a form that is shared among users with different kinds of permissions. If the current user is not allowed to access a field, the input will be omitted automatically. Further, the parameter validation will exclude that field, effectively disallowing that user from submitting that parameter.</p>
 
-<h2 id="label-Handling+password+fields">Handling password fields</h2>
+<h2 id="handling-password-fields">Handling password fields</h2>
 
 <p>When using Rails’ <code>has_secure_password</code> method, which typically generates the attributes accessors <code>:password</code> and <code>password_confirmation</code>, do not declare these two as fields in your User model.</p>
 
@@ -150,7 +150,7 @@
   cannot :set_password, User # This prohibits setting and changing passwords of any user
 </code></pre>
 
-<h2 id="label-Dealing+with+multilingual+fields">Dealing with multilingual fields</h2>
+<h2 id="dealing-with-multilingual-fields">Dealing with multilingual fields</h2>
 
 <p>When using Gems such as <code>mobility</code>, Compony provides support for multilingual fields. For instance, assuming that a model has the attribute <code>label</code> translated in English and German, making <code>label</code> a virtual attribute reading either <code>label_en</code> and <code>label_de</code>, depending on the user’s language, Compony automatically generates a multilingual field if the following is used:</p>
 
@@ -185,7 +185,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:47 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.generators.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Rails+Generators+provided+by+Compony">Rails Generators provided by Compony</h1>
+<h1 id="rails-generators-provided-by-compony">Rails Generators provided by Compony</h1>
 
 <p>To make your life easier and coding faster, Compony comes with two generators:</p>
 <ul><li>
@@ -71,7 +71,7 @@
 <p><code>rails g components Users</code> will generate a set of the most used components.</p>
 </li></ul>
 
-<h3 id="label-Support+for+custom+base+components">Support for custom base components</h3>
+<h3 id="support-for-custom-base-components">Support for custom base components</h3>
 
 <p>Generators will automatically detect your <code>BaseComponents</code> (see <a href="./inheritance_md.html#best-practice">Inheritance: best practice</a>).</p>
 
@@ -79,7 +79,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:46 2026 by
+  Generated on Tue Aug 18 14:36:34 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>

data/doc/file.glossary.html

@@ -60,7 +60,7 @@
       <div id="content"><div id='filecontents'>
 <p><a href="/README_md.html#guide--documentation">Back to the guide</a></p>
 
-<h1 id="label-Glossary">Glossary</h1>
+<h1 id="glossary">Glossary</h1>
 
 <p>One-line definitions of Compony vocabulary. Deeper treatment is linked.</p>
 
@@ -74,131 +74,131 @@
 <tbody>
 <tr>
 <td><strong>Component</strong></td>
-<td>A Ruby class (‘Components::Family::Name`) bundling a route, controller action and view. See [basic_component.md](/doc/guide/basic_component.md).</td>
+<td>A Ruby class (<code>Components::Family::Name</code>) bundling a route, controller action and view. See <a href="/doc/guide/basic_component_md.html">basic_component.md</a>.</td>
 </tr>
 <tr>
 <td><strong>Family</strong></td>
-<td>The plural namespace grouping a model’s components, analogous to a Rails controller (‘Users`).</td>
+<td>The plural namespace grouping a model’s components, analogous to a Rails controller (<code>Users</code>).</td>
 </tr>
 <tr>
-<td>**Comp name**</td>
-<td>The component’s own name, analogous to a Rails action (‘show`).</td>
+<td><strong>Comp name</strong></td>
+<td>The component’s own name, analogous to a Rails action (<code>show</code>).</td>
 </tr>
 <tr>
-<td>**‘setup`**</td>
+<td><strong><code>setup</code></strong></td>
 <td>Class-level block holding nearly all component config; parent’s runs before child’s.</td>
 </tr>
 <tr>
-<td>**Content block**</td>
-<td>A named (‘:main` default) view block rendered via Dyny inside a RequestContext.</td>
+<td><strong>Content block</strong></td>
+<td>A named (<code>:main</code> default) view block rendered via Dyny inside a RequestContext.</td>
 </tr>
 <tr>
-<td>**‘before_render`**</td>
+<td><strong><code>before_render</code></strong></td>
 <td>Hook chain run before content; if it sets a response body (e.g. redirect) content is skipped.</td>
 </tr>
 <tr>
 <td><strong>Standalone</strong></td>
-<td>A ‘standalone` config that makes Compony emit a Rails route for the component. See [standalone.md](/doc/guide/standalone.md).</td>
+<td>A <code>standalone</code> config that makes Compony emit a Rails route for the component. See <a href="/doc/guide/standalone_md.html">standalone.md</a>.</td>
 </tr>
 <tr>
-<td>**Standalone name**</td>
-<td>Identifier for one of several routes a component exposes; ‘nil` = the main one.</td>
+<td><strong>Standalone name</strong></td>
+<td>Identifier for one of several routes a component exposes; <code>nil</code> = the main one.</td>
 </tr>
 <tr>
 <td><strong>Verb</strong></td>
-<td>An HTTP method config inside a standalone (‘verb :get do … end`).</td>
+<td>An HTTP method config inside a standalone (<code>verb :get do ... end</code>).</td>
 </tr>
 <tr>
-<td>**‘authorize`**</td>
-<td>Mandatory per-verb block; truthy grants access, falsy raises ‘CanCan::AccessDenied`.</td>
+<td><strong><code>authorize</code></strong></td>
+<td>Mandatory per-verb block; truthy grants access, falsy raises <code>CanCan::AccessDenied</code>.</td>
 </tr>
 <tr>
-<td>**‘respond`**</td>
+<td><strong><code>respond</code></strong></td>
 <td>Per-verb block overriding the controller response; overriding it skips the default authorize step.</td>
 </tr>
 <tr>
 <td><strong>Resourceful</strong></td>
-<td>A component that auto-loads a record/relation into ‘@data` (mixin or pre-built parent). See [resourceful.md](/doc/guide/resourceful.md).</td>
+<td>A component that auto-loads a record/relation into <code>@data</code> (mixin or pre-built parent). See <a href="/doc/guide/resourceful_md.html">resourceful.md</a>.</td>
 </tr>
 <tr>
-<td>**‘@data`**</td>
+<td><strong><code>@data</code></strong></td>
 <td>The record (or AR relation) a resourceful component operates on.</td>
 </tr>
 <tr>
-<td>**‘data_class`**</td>
+<td><strong><code>data_class</code></strong></td>
 <td>The model class a resourceful component expects; defaults from the family name.</td>
 </tr>
 <tr>
-<td>**Lifecycle hooks**</td>
-<td>‘load_data → after_load_data → authorize → assign_attributes → after_assign_attributes → store_data`.</td>
+<td><strong>Lifecycle hooks</strong></td>
+<td><code>load_data → after_load_data → authorize → assign_attributes → after_assign_attributes → store_data</code>.</td>
 </tr>
 <tr>
 <td><strong>Intent</strong></td>
-<td>A gateway object to a target component carrying context (model, path, feasibility, label). See [intents.md](/doc/guide/intents.md).</td>
+<td>A gateway object to a target component carrying context (model, path, feasibility, label). See <a href="/doc/guide/intents_md.html">intents.md</a>.</td>
 </tr>
 <tr>
-<td>**Exposed intent**</td>
+<td><strong>Exposed intent</strong></td>
 <td>An intent a component declares for its parent/layout to render (e.g. an actions toolbar).</td>
 </tr>
 <tr>
-<td>**‘Compony.path`**</td>
+<td><strong><code>Compony.path</code></strong></td>
 <td>Helper that builds a Rails path string via an intent (use for redirects).</td>
 </tr>
 <tr>
-<td>**‘render_intent`**</td>
+<td><strong><code>render_intent</code></strong></td>
 <td>Content/view helper that renders a link or button to another component.</td>
 </tr>
 <tr>
-<td>**‘render_sub_comp`**</td>
+<td><strong><code>render_sub_comp</code></strong></td>
 <td>Content helper that instantiates and nests another component.</td>
 </tr>
 <tr>
-<td>**Sub comp / parent comp**</td>
-<td>A component instantiated inside another; the outer one is its ‘parent_comp`.</td>
+<td><strong>Sub comp / parent comp</strong></td>
+<td>A component instantiated inside another; the outer one is its <code>parent_comp</code>.</td>
 </tr>
 <tr>
-<td>**Root comp**</td>
-<td>The top component of the current render tree (no parent); ‘Compony.root_comp`.</td>
+<td><strong>Root comp</strong></td>
+<td>The top component of the current render tree (no parent); <code>Compony.root_comp</code>.</td>
 </tr>
 <tr>
 <td><strong>RequestContext</strong></td>
-<td>Dslblend object content blocks run in: providers are the component, controller, helpers. See [internal_datastructures.md](/doc/guide/internal_datastructures.md).</td>
+<td>Dslblend object content blocks run in: providers are the component, controller, helpers. See <a href="/doc/guide/internal_datastructures_md.html">internal_datastructures.md</a>.</td>
 </tr>
 <tr>
 <td><strong>Backfire</strong></td>
 <td>Dslblend mechanism copying instance vars set in a block back onto the component.</td>
 </tr>
 <tr>
-<td>**Button / style**</td>
-<td>A presenter component for an intent; ‘style` (`:css_button`, `:link`, custom) selects the class.</td>
+<td><strong>Button / style</strong></td>
+<td>A presenter component for an intent; <code>style</code> (<code>:css_button</code>, <code>:link</code>, custom) selects the class.</td>
 </tr>
 <tr>
 <td><strong>Feasibility</strong></td>
-<td>Framework where model ‘prevent` blocks disable buttons/links to an action with a reason. See [feasibility.md](/doc/guide/feasibility.md).</td>
+<td>Framework where model <code>prevent</code> blocks disable buttons/links to an action with a reason. See <a href="/doc/guide/feasibility_md.html">feasibility.md</a>.</td>
 </tr>
 <tr>
-<td>**‘prevent`**</td>
+<td><strong><code>prevent</code></strong></td>
 <td>Model class DSL declaring a feasibility prevention for one or more actions.</td>
 </tr>
 <tr>
 <td><strong>Field</strong></td>
-<td>A model-level declaration (‘field :name, :type`) of a UI-relevant attribute and its formatting. See [model_fields.md](/doc/guide/model_fields.md).</td>
+<td>A model-level declaration (<code>field :name, :type</code>) of a UI-relevant attribute and its formatting. See <a href="/doc/guide/model_fields_md.html">model_fields.md</a>.</td>
 </tr>
 <tr>
-<td>**Ownership / ‘owned_by`**</td>
-<td>Declares a model conceptually part of another, adjusting redirects/top actions. See [ownership.md](/doc/guide/ownership.md).</td>
+<td><strong>Ownership / <code>owned_by</code></strong></td>
+<td>Declares a model conceptually part of another, adjusting redirects/top actions. See <a href="/doc/guide/ownership_md.html">ownership.md</a>.</td>
 </tr>
 <tr>
-<td>**Virtual model**</td>
-<td>A non-persistent ActiveType-backed model usable as a form target. See [virtual_models.md](/doc/guide/virtual_models.md).</td>
+<td><strong>Virtual model</strong></td>
+<td>A non-persistent ActiveType-backed model usable as a form target. See <a href="/doc/guide/virtual_models_md.html">virtual_models.md</a>.</td>
 </tr>
 <tr>
 <td><strong>Dyny</strong></td>
-<td>The HTML-as-Ruby templating gem content blocks are written in ([repo](<a href="https://github.com/kalsan/dyny">github.com/kalsan/dyny</a>)).</td>
+<td>The HTML-as-Ruby templating gem content blocks are written in (<a href="https://github.com/kalsan/dyny">repo</a>).</td>
 </tr>
 <tr>
-<td>**Abstract component**</td>
-<td>A component never routed directly, only inherited from (e.g. an app’s ‘BaseComponents::*`).</td>
+<td><strong>Abstract component</strong></td>
+<td>A component never routed directly, only inherited from (e.g. an app’s <code>BaseComponents::*</code>).</td>
 </tr>
 </tbody>
 </table>
@@ -207,7 +207,7 @@
 </div></div>
 
       <div id="footer">
-  Generated on Sat Jun  6 09:14:47 2026 by
+  Generated on Tue Aug 18 14:36:35 2026 by
   <a href="https://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
   0.9.34 (ruby-3.4.9).
 </div>