<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zach Shallbetter</title>
    <description>The latest articles on DEV Community by Zach Shallbetter (@zachshallbetter).</description>
    <link>https://dev.to/zachshallbetter</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1204522%2F90d77c86-bed4-43bc-9d9f-6b8975df5f23.jpeg</url>
      <title>DEV Community: Zach Shallbetter</title>
      <link>https://dev.to/zachshallbetter</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zachshallbetter"/>
    <language>en</language>
    <item>
      <title>A physics layer that draws nothing: reading interface forces back as CSS variables</title>
      <dc:creator>Zach Shallbetter</dc:creator>
      <pubDate>Thu, 19 Nov 2026 04:58:25 +0000</pubDate>
      <link>https://dev.to/zachshallbetter/a-physics-layer-that-draws-nothing-reading-interface-forces-back-as-css-variables-14lg</link>
      <guid>https://dev.to/zachshallbetter/a-physics-layer-that-draws-nothing-reading-interface-forces-back-as-css-variables-14lg</guid>
      <description>&lt;p&gt;Most interface physics runs one way. Something moves, and the page watches.&lt;/p&gt;

&lt;p&gt;I build Fundamental, a relational field runtime for interfaces. Elements bend a shared field, and the field bends them back. The second half is the part I care about. The field reports what it feels as live CSS variables, so the page can style itself from the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  Bodies
&lt;/h2&gt;

&lt;p&gt;A body is any element with a &lt;code&gt;data-body&lt;/code&gt; attribute. Its value is one or more force tokens.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;field-root&lt;/span&gt; &lt;span class="na"&gt;render&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"dots"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/field-root&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;h1&lt;/span&gt; &lt;span class="na"&gt;data-body&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"attract"&lt;/span&gt; &lt;span class="na"&gt;data-strength&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"1.2"&lt;/span&gt; &lt;span class="na"&gt;data-feedback&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Mass&lt;span class="nt"&gt;&amp;lt;/h1&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;button&lt;/span&gt; &lt;span class="na"&gt;data-body&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"repel"&lt;/span&gt; &lt;span class="na"&gt;data-range&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"240"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Keep clear&lt;span class="nt"&gt;&amp;lt;/button&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;&amp;lt;field-root&amp;gt;&lt;/code&gt; goes on the page once. It finds every &lt;code&gt;[data-body]&lt;/code&gt; element and wires it into the field. With &lt;code&gt;data-feedback&lt;/code&gt;, an element gets the write-back. Its &lt;code&gt;--d&lt;/code&gt; and &lt;code&gt;--field-density&lt;/code&gt; variables change as the field moves around it. Those are ordinary CSS variables. Any rule can read them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Nothing on screen by default
&lt;/h2&gt;

&lt;p&gt;A field created without a render mode draws nothing. It still runs the simulation and reports through &lt;code&gt;--field-*&lt;/code&gt; variables, events, queries and snapshots. The particle canvas is opt-in with &lt;code&gt;render: 'dots'&lt;/code&gt;, as above. The demo looks like particles, so this surprises people. The particles are one render surface, not the system.&lt;/p&gt;

&lt;p&gt;Trying it needs no build step.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;createField&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s1"&gt;'https://esm.sh/@fundamental-engine/vanilla'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="nf"&gt;createField&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;querySelector&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'canvas'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;render&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'dots'&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Where it stands
&lt;/h2&gt;

&lt;p&gt;It is a 0.x preview at 0.12.0, MIT licensed, with seven packages on npm. It ships in production apps and has no third-party adopters yet.&lt;/p&gt;

&lt;p&gt;The core API is frozen and grows additively. The query, snapshot, diff and replay APIs are experimental. Swift and Kotlin ports exist at preview status, built from source only.&lt;/p&gt;

&lt;p&gt;I haven't shown that this model fits every interface. It fits the ones where an element should behave according to what is near it.&lt;/p&gt;

&lt;p&gt;Elements bend the field. The test is what a page does when the field bends back.&lt;/p&gt;

&lt;p&gt;Related: &lt;a href="https://fundamentalengine.com/" rel="noopener noreferrer"&gt;https://fundamentalengine.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>css</category>
      <category>frontend</category>
      <category>ui</category>
      <category>webdev</category>
    </item>
    <item>
      <title>RE: Hoarded Drafts</title>
      <dc:creator>Zach Shallbetter</dc:creator>
      <pubDate>Sun, 08 Sep 2024 04:39:04 +0000</pubDate>
      <link>https://dev.to/zachshallbetter/re-hoarded-drafts-5c0o</link>
      <guid>https://dev.to/zachshallbetter/re-hoarded-drafts-5c0o</guid>
      <description>&lt;p&gt;(Letter to myself from myself)&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;From:&lt;/strong&gt; Zach - Dev.to &lt;a href="https://dev.to/zachshallbetter"&gt;https://dev.to/zachshallbetter&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Sent:&lt;/strong&gt; Thursday, September 7, 2024 10:45 AM&lt;br&gt;
&lt;strong&gt;To:&lt;/strong&gt; Zach - Medium &lt;a href="https://medium.com/zachshallbetter" rel="noopener noreferrer"&gt;https://medium.com/zachshallbetter&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Subject:&lt;/strong&gt; RE: Hoarded Drafts&lt;/p&gt;

&lt;p&gt;Hey,&lt;/p&gt;

&lt;p&gt;Gollum leans more “psychopath” than “sociopath,” but let’s not split hairs here.&lt;/p&gt;

&lt;p&gt;BTW, Dev.to supports markdown, which is /Chef’s kiss 🤌: perfection in draft form.&lt;/p&gt;

&lt;p&gt;I’ll start pulling those drafts and getting them posted here on Dev.to. No point in letting them sit around when they could be out there, finding their people. I’ll clean them up, put them out, and see where it leads. &lt;/p&gt;

&lt;p&gt;Thanks for the push. Time to stop guarding the hoard and hit publish.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zachshallbetter.com?/s=new&amp;amp;p=top&amp;amp;y=2024" rel="noopener noreferrer"&gt;&lt;strong&gt;Zachary S. 2024&lt;/strong&gt;&lt;/a&gt;&lt;br&gt;
Senior Draft Developer&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;From:&lt;/strong&gt; Zach - Medium Account &lt;a href="https://medium.com/zachshallbetter" rel="noopener noreferrer"&gt;medium.com/zachshallbetter&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Sent:&lt;/strong&gt; Thursday, September 7, 2024 10:32 AM&lt;br&gt;
&lt;strong&gt;To:&lt;/strong&gt; Zach - Dev.to Account &lt;a href="https://dev.to/zachshallbetter"&gt;dev.to/zachshallbetter&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;Subject:&lt;/strong&gt; Time to Move Your Unpublished Articles&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Hey Zach,&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;You've got a ton of drafts sitting in Medium and Notion that never see the light of day. It's time to get those unpublished articles out of the archives and somewhere they'll actually reach someone… anyone.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Not to push, but Dev.to seems like a solid space for what you've been working on—plenty of devs who are looking for exactly the kind of nonsense you've been writing to yourself like a sociopath (psychopath?).&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Stop letting good work gather dust.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zachshallbetter.com?/s=old&amp;amp;y=2024" rel="noopener noreferrer"&gt;&lt;em&gt;&lt;strong&gt;Zach Shallbetter&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The Gollum of Drafts&lt;/em&gt;&lt;br&gt;
&lt;em&gt;"My precious ideas…"&lt;/em&gt;&lt;/p&gt;

</description>
      <category>typescript</category>
      <category>productivity</category>
      <category>ui</category>
      <category>top7</category>
    </item>
  </channel>
</rss>
