<?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: Galascribe</title>
    <description>The latest articles on DEV Community by Galascribe (@galascribe).</description>
    <link>https://dev.to/galascribe</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%2F4214321%2F1efa7128-e45b-413d-aad6-06cdd391a892.png</url>
      <title>DEV Community: Galascribe</title>
      <link>https://dev.to/galascribe</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/galascribe"/>
    <language>en</language>
    <item>
      <title>Intuit paid about $12B for Intuit Mailchimp in 2021</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Sat, 21 Nov 2026 05:51:11 +0000</pubDate>
      <link>https://dev.to/galascribe/intuit-paid-about-12b-for-intuit-mailchimp-in-2021-53gm</link>
      <guid>https://dev.to/galascribe/intuit-paid-about-12b-for-intuit-mailchimp-in-2021-53gm</guid>
      <description>&lt;p&gt;Yesterday it sold it for $3.68B. The buyer is Bending Spoons, the Italian company that already owns Evernote, Vimeo and now Miro. That is roughly 70% of the value gone in five years. No pricing or plan changes were announced. If you have used a Bending Spoons product after an acquisition, you know what usually comes next. They run a clear playbook: cut cost, raise price, keep the product alive. It works financially. Customers should plan accordingly. Long term: by 2030 a handful of roll-up owners control most mature SaaS brands from the 2010s. Short term: Intuit Mailchimp raises prices or shrinks its free tier within 12 months of close.&lt;/p&gt;

</description>
      <category>merger</category>
      <category>saas</category>
      <category>saaspocalypse</category>
      <category>productivity</category>
    </item>
    <item>
      <title>SEO you do not have to think about</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Fri, 20 Nov 2026 08:05:49 +0000</pubDate>
      <link>https://dev.to/galascribe/seo-you-do-not-have-to-think-about-308f</link>
      <guid>https://dev.to/galascribe/seo-you-do-not-have-to-think-about-308f</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://blog.galascribe.com/seo-you-do-not-have-to-think-about/" rel="noopener noreferrer"&gt;https://blog.galascribe.com/seo-you-do-not-have-to-think-about/&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Search and social presentation is a handful of small facts in a page's head: which address is the canonical one, how the page is described, which picture appears when someone shares a link. Each is easy to get slightly wrong, and a template that gets one wrong gets it wrong on every site it builds. So we audited a live test site of our own. Here is what that audit found, what we changed, and what testing the changes found in turn.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the audit found
&lt;/h2&gt;

&lt;p&gt;The test site was built with template 4.0.0. The audit found, among others:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Canonical addresses without a trailing slash, which GitHub Pages answered with a redirect; eight of the nine sitemap entries redirected too.&lt;/li&gt;
&lt;li&gt;A seeded heading that polluted generated descriptions: starter posts opened with their own title as a heading, and the fallback description could read heading text.&lt;/li&gt;
&lt;li&gt;A description that was just the site name: a site created without a tagline falls back to its title, and the home page title repeated the name.&lt;/li&gt;
&lt;li&gt;No social preview image and no favicon.&lt;/li&gt;
&lt;li&gt;Thin author controls over how a site and its posts appear in search and in shared links.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these breaks a site, but a template carries each of them to every site it builds, which is why we treated them as defects in the template and not in one site.&lt;/p&gt;

&lt;h2&gt;
  
  
  One address per page
&lt;/h2&gt;

&lt;p&gt;Under the default route profile a page is built as a directory. GitHub Pages serves &lt;code&gt;/about/&lt;/code&gt; directly and answers &lt;code&gt;/about&lt;/code&gt; with a 301 redirect to it. Our canonical links and our sitemap used the slash-less form, so following either started with a redirect. We want a sitemap to contain no address that a redirect would serve.&lt;/p&gt;

&lt;p&gt;So there is now one rule, decided by one helper that every emitter calls. Under the default profile every public page address ends in a slash, and the root stays &lt;code&gt;/&lt;/code&gt;. That covers the canonical link, &lt;code&gt;og:url&lt;/code&gt;, the sitemap, the feeds, the llms files, the structured data, the search index and every internal link. Fixed files such as &lt;code&gt;/sitemap.xml&lt;/code&gt;, &lt;code&gt;/feed/rss.xml&lt;/code&gt; and &lt;code&gt;/assets/…&lt;/code&gt; are unchanged, and so is the &lt;code&gt;explicit-file&lt;/code&gt; profile.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;route            if emitted bare               emitted now
/                200                           /
/about           301 to /about/                /about/
/archive/2026    301 to /archive/2026/         /archive/2026/
/page/2          301 to /page/2/               /page/2/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;We check this by building a fixture site and parsing the output instead of reading it by eye. The condition is that no page address in any of those places lacks its slash, and that the sitemap lists nothing a redirect would serve. It passes in the template release, 4.3.0.&lt;/p&gt;

&lt;p&gt;One cost is worth stating. Tag and series pages now use their readable name alone, and add a ten-character hash only when two names collide or the readable name is empty, so existing hashed tag addresses change. We emit no redirects for them, because they are low-value listing pages. If you linked to one, that link will break.&lt;/p&gt;

&lt;h2&gt;
  
  
  Descriptions you write
&lt;/h2&gt;

&lt;p&gt;A description is the line under a title in a search result and in a shared-link card. Our rule is that a person writes it. A post's subtitle is its default search description, and the editor lets a post override both that and its search title. The title override allows up to 70 characters, with the site name added after it on every page except the home page; the description override allows up to 300.&lt;/p&gt;

&lt;p&gt;The editor shows a search-result preview built from the same fields and suffix, with counters and four checks: the title plus suffix is at most 60 characters, the description is between 70 and 160, a social image is chosen, and every image has a description. Those numbers are our own checks, not promises about how a search engine will display the text.&lt;/p&gt;

&lt;p&gt;For the site as a whole there is a tagline, set when the site is created or later in Settings, and a language. Without a tagline the description falls back to the site's name, and when the two are the same the home page title shows the name once. If a post has no written description at all, the renderer falls back to text from the page, and that fallback now skips headings.&lt;/p&gt;

&lt;h2&gt;
  
  
  A picture for shared links
&lt;/h2&gt;

&lt;p&gt;Link cards need an image. A site can have a default social image, uploaded in Settings as PNG, JPEG or WebP (we recommend 1200 by 630 pixels) and stored in the repository under &lt;code&gt;assets/brand/&lt;/code&gt;. A post can choose its own from the pictures in its body or its hero, or upload one. A brand mark uploaded under Look gives the site an icon, an Apple touch icon and a theme colour from its palette, with a dark-mode variant when there is one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an author can control
&lt;/h2&gt;

&lt;p&gt;Collected in one place:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Per post:&lt;/strong&gt; search title, search description, social image, a canonical address under an Advanced fold for syndicated or moved content, and a switch that hides the post from search engines.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per site:&lt;/strong&gt; tagline, language, social links, which feed the organisation's structured data as &lt;code&gt;sameAs&lt;/code&gt;, a default social image, and a switch that allows or blocks AI crawlers in &lt;code&gt;robots.txt&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Addresses:&lt;/strong&gt; change a published post's address and the old one is added to its redirects automatically, up to 32, with a note that the old address will redirect.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Hiding is not the same as unlisted. An unlisted post is reachable by link, left out of the site's lists and not indexed. A hidden post stays listed on the site, sends &lt;code&gt;noindex, follow&lt;/code&gt;, and is left out of the sitemap, feeds, llms files and search index. Site settings are saved as a pending change in your repository and go live with the next publish, like any other edit. The site's canonical base is deliberately not editable: it changes only when a domain is attached or removed on the Domain page.&lt;/p&gt;

&lt;h2&gt;
  
  
  What testing the fixes found
&lt;/h2&gt;

&lt;p&gt;We checked the changes with scripted browser journeys on a local stack that print facts from the parsed output, not screenshots. Three of its five journeys failed on the first run.&lt;/p&gt;

&lt;p&gt;The first failure was easy to miss. The settings saved, but the publish step refused the default social image and the brand assets, so the tagline, social links, social image, icon and crawler setting never reached the built site. An author would have filled in every field and seen nothing change. We extended the publish step to accept them, and the journey now finds each of them in the built output.&lt;/p&gt;

&lt;p&gt;The second was in the editor. Reopening a published post from a device draft dropped its reference to the published version, so the redirect note, the redirects and the updated time were skipped, and after Publish the app wrongly said it could not reach Galascribe. The editor now attaches that reference on every draft restore. A rename in our test harness also stalled, because its stand-in for GitHub could not apply deletions; real GitHub can. The app now says a slow commit is still saving instead of claiming it is offline.&lt;/p&gt;

&lt;p&gt;Fixed, here, means released and checked on a local stack: the renderer changes are in template 4.3.0 and the contract changes in schemas 3.12.0. We then built this blog on the same renderer and requested every address in its sitemap: all 13 answered 200 with no redirect, and every canonical link matched the address it was served from.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we left out
&lt;/h2&gt;

&lt;p&gt;A navigation editor, &lt;code&gt;hreflang&lt;/code&gt; (the model has no translations), per-author search fields and a sitemap index for very large sites are out of scope. None of this promises traffic. It removes avoidable mistakes, so that what a crawler or a link card reads is what you wrote.&lt;/p&gt;

&lt;p&gt;To try this on a site of your own, the start flow is at &lt;a href="https://app.galascribe.com/" rel="noopener noreferrer"&gt;https://app.galascribe.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>html</category>
      <category>seo</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Likes and comments on a static site</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Sun, 15 Nov 2026 08:20:41 +0000</pubDate>
      <link>https://dev.to/galascribe/likes-and-comments-on-a-static-site-42aj</link>
      <guid>https://dev.to/galascribe/likes-and-comments-on-a-static-site-42aj</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://blog.galascribe.com/likes-and-comments-on-a-static-site/" rel="noopener noreferrer"&gt;https://blog.galascribe.com/likes-and-comments-on-a-static-site/&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A Galascribe site is a folder of files served by GitHub Pages, and a built page used to make no request to anything but its own files; its content-security policy said so. We deferred likes and comments in an early plan, then reversed that: they are core to what we are building. Files cannot add a like to a count, cannot tell who is pressing the button, and cannot slow down someone who presses it a thousand times. Something outside the site has to do those jobs. This post describes how it works, from the build specification we wrote on 8 October 2026, and what we left out.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a static site cannot do alone
&lt;/h2&gt;

&lt;p&gt;Three things stand in the way.&lt;/p&gt;

&lt;p&gt;A count is shared state. Two readers must see the same number, so it has to live somewhere both can write to. A comment has the same need, plus it has to outlast the reader's tab.&lt;/p&gt;

&lt;p&gt;Identity is the second. Writing on someone's site needs a name attached, or comments answer to nobody. A github.io page has no account system and cannot keep a secret: any key in its script is readable by every visitor.&lt;/p&gt;

&lt;p&gt;Limits are the third. Rate limits, link limits and moderation need a place that sees every request, and a static host sees none.&lt;/p&gt;

&lt;p&gt;So the platform's API has to hold the state, the identities and the rules, and the page has to ask it questions. The cost belongs up front: we store reactions and comments in our database, not in the creator's repository, and there is no export of comments or likes today. The settings live in the repository; the readers' data does not.&lt;/p&gt;

&lt;h2&gt;
  
  
  How a page talks to the API
&lt;/h2&gt;

&lt;p&gt;The module is off unless the repository says otherwise. A file, &lt;code&gt;gala/modules/interactions.json&lt;/code&gt;, holds the author's choices for reactions, comments, thread depth and public counts, and with no file the built page gets no markup, no script and no requests. Our web app edits that file as a repository change, following the precedent of theme selection.&lt;/p&gt;

&lt;p&gt;Each article gets a section at its foot, carrying the publication id, the article's id, the canonical address and the API origin as data attributes. One script, loaded on article pages only, does the rest, building the interface with DOM calls and never inserting fetched data as HTML.&lt;/p&gt;

&lt;p&gt;Reading is public. The script asks the API for the article's reactions and a first page of comments from endpoints that answer cross-origin requests from any site, take no cookies, and report counts in buckets, which we come back to below.&lt;/p&gt;

&lt;p&gt;Writing needs a reader, and our own sign-in does not help. The platform's session cookie is host-only and &lt;code&gt;SameSite=Lax&lt;/code&gt;, so a browser does not attach it to requests a github.io page makes to our API. The page needs a credential of its own, handed over without cookies. We use a full-page redirect and an OAuth authorization code with PKCE, in four steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The script makes a random state value and a code verifier, stores them in &lt;code&gt;sessionStorage&lt;/code&gt; with what the reader was trying to do, and sends the tab to our app's connect page.&lt;/li&gt;
&lt;li&gt;The app signs the reader in with GitHub if needed and asks the API for a one-time code that lasts 60 seconds. The API refuses any return address that does not begin with the publication's recorded address.&lt;/li&gt;
&lt;li&gt;The reader lands back on the article with the code in the URL fragment. The script removes the fragment from the history at once, checks the state value, and trades code and verifier for a token.&lt;/li&gt;
&lt;li&gt;The token is valid for 30 days and good for one publication only. It sits in that site's &lt;code&gt;localStorage&lt;/code&gt;; the API stores only its hash. Every write sends it as a bearer header with credentials omitted.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A pending like is then applied, and a half-written comment is put back in the box, not posted for the reader. Readers can see and revoke every site they have connected from their Account page.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this does to the content-security policy
&lt;/h2&gt;

&lt;p&gt;Until now every built page carried a content-security policy that allowed connections to the site itself and nothing else. A like button must connect elsewhere, so we changed one directive. The policy, with line breaks added:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;default-src 'none';
base-uri 'none';
object-src 'none';
form-action 'none';
script-src 'self';
style-src 'self';
img-src 'self';
font-src 'self';
connect-src 'self' https://api.galascribe.com;
media-src 'self';
manifest-src 'self';
worker-src 'none'
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The line that matters is &lt;code&gt;connect-src&lt;/code&gt;, which used to be &lt;code&gt;'self'&lt;/code&gt; alone. Everything else stays closed: scripts only from the site's own files, no frames or forms, images only from the site itself. That last rule is why avatars are initials. A reader's profile picture would have meant opening &lt;code&gt;img-src&lt;/code&gt;, and we chose not to.&lt;/p&gt;

&lt;p&gt;Three consequences follow.&lt;/p&gt;

&lt;p&gt;First, the policy allows the API origin on every site, interactions on or off. The policy is a fixed constant hashed into what we call the render-policy identity, so any change moves that identity, and every place that checks it (the template, the theme tooling, the publish step) has to change together.&lt;/p&gt;

&lt;p&gt;Second, every build's manifest and provenance record carries an &lt;code&gt;interactionBearing&lt;/code&gt; field that the schemas pin to &lt;code&gt;false&lt;/code&gt;. Making it a plain boolean means a schema release, not a template tweak.&lt;/p&gt;

&lt;p&gt;Third, a token in &lt;code&gt;localStorage&lt;/code&gt; can be read by any script running on that origin, so &lt;code&gt;script-src 'self'&lt;/code&gt; is not decoration: only files served from the site itself can run beside the token.&lt;/p&gt;

&lt;h2&gt;
  
  
  Abuse limits
&lt;/h2&gt;

&lt;p&gt;Anyone can call the public endpoints, so we put the limits on the API. Its defaults: 60 reactions a minute; 5 comments a minute and 30 an hour; 10 comments an hour for accounts under a day old; 20 reports an hour. They are runtime settings enforced in the database, and a breach answers 429 with a retry hint.&lt;/p&gt;

&lt;p&gt;Comments are plain text, 1 to 10,000 characters, with at most 10 links, each marked &lt;code&gt;nofollow ugc&lt;/code&gt;. Text that looks like a credential, such as a GitHub token or a private-key header, is refused, and a required idempotency key stops a double click posting twice.&lt;/p&gt;

&lt;p&gt;A new comment is visible at once and scanned afterwards: deterministic spam checks always run. A language-model classifier can also run, but only where the server has been given a key for it. The scan can flag a comment or hold it from view, both reversible. Only a person removes a comment, and report counts alone never do.&lt;/p&gt;

&lt;p&gt;Public counts are reported as lower bounds: exact up to 9, then 10+, 20+, 50+ and so on, worded "At least 50 likes", never "people". Exact numbers go to the site's owner only.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we left out on purpose
&lt;/h2&gt;

&lt;p&gt;There is no reader login of our own: no passwords and no new providers. A reader is an existing Galascribe account, signed in with GitHub. The trade-off is plain: a reader without a GitHub account cannot comment, and we have not tried to solve that.&lt;/p&gt;

&lt;p&gt;We left out popups, frames, cross-window messaging and FedCM. The spec records the popup-and-message approach as the one that failed in v1. The page uses no cookies or third-party requests, and the redirect costs the reader a page load.&lt;/p&gt;

&lt;p&gt;Comments are plain text, with no images or formatting. A site without the configuration file is simply off. If our API is down, the article loads as before and the section says responses are unavailable. Without JavaScript there are no interactions at all.&lt;/p&gt;

&lt;p&gt;To set up a site of your own, the start flow is at &lt;a href="https://app.galascribe.com/" rel="noopener noreferrer"&gt;https://app.galascribe.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>backend</category>
      <category>webdev</category>
    </item>
    <item>
      <title>116 tokens: a default theme for light, dark and a phone</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Fri, 13 Nov 2026 08:10:18 +0000</pubDate>
      <link>https://dev.to/galascribe/116-tokens-a-default-theme-for-light-dark-and-a-phone-263f</link>
      <guid>https://dev.to/galascribe/116-tokens-a-default-theme-for-light-dark-and-a-phone-263f</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://blog.galascribe.com/116-tokens-a-default-theme-for-light-dark-and-a-phone/" rel="noopener noreferrer"&gt;https://blog.galascribe.com/116-tokens-a-default-theme-for-light-dark-and-a-phone/&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Our default theme was a skin over a fixed page. When I approved a new design for it, five decisions shaped what followed. This post covers what they produced: a closed list of 116 typed tokens, a light and a dark value for each, and a way for a creator to pick their own colours without making the page unreadable.&lt;/p&gt;

&lt;h2&gt;
  
  
  Five decisions
&lt;/h2&gt;

&lt;p&gt;I approved a working preview and asked for the production theme to be replaced with it. The decisions that went with it:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;No backwards compatibility. Only test users were onboarded, so we broke contracts and bumped majors, with no migration shims.&lt;/li&gt;
&lt;li&gt;The template owns layout. Themes supply design values, the tokens, plus optional skin CSS.&lt;/li&gt;
&lt;li&gt;A site script is allowed, but every page must read completely with JavaScript off. The script only enhances: search, copy buttons, the menu, the colour-mode toggle.&lt;/li&gt;
&lt;li&gt;"Most read" was dropped, because we have no visit data. The newsletter panel became a link to a sign-up address the author sets, hidden when none is set. There are no forms.&lt;/li&gt;
&lt;li&gt;The official token list grows to the preview's full set of values, each with a strict type.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  116, counted
&lt;/h2&gt;

&lt;p&gt;Decision 5 said "about 100 tokens". The contract list that came out of it has 116 entries and replaces a list of 35. Keys are sorted and each has a fixed type, so the list is closed. By type, counted from the list:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;type          count   may differ between light and dark
color           40    yes
paint            4    yes
border           8    yes
shadow           5    yes
font-family      5    no
font-weight      5    no
length          28    no
box              3    no
number           2    no
duration         3    no
easing           2    no
keyword         11    no
total          116    57 may differ, 59 must be byte-equal
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A token is a key, a type, a light value and a dark value, and nothing else. The value grammars are allow-lists. A colour is a lowercase &lt;code&gt;#rrggbb&lt;/code&gt; or &lt;code&gt;#rrggbbaa&lt;/code&gt;. A length is a number with &lt;code&gt;px&lt;/code&gt;, &lt;code&gt;rem&lt;/code&gt;, &lt;code&gt;em&lt;/code&gt; or &lt;code&gt;%&lt;/code&gt;. No value may contain &lt;code&gt;url(&lt;/code&gt;, &lt;code&gt;var(&lt;/code&gt;, &lt;code&gt;calc(&lt;/code&gt;, &lt;code&gt;attr(&lt;/code&gt;, &lt;code&gt;expression&lt;/code&gt;, a semicolon, braces, a backslash or a quote, apart from a few fixed keywords.&lt;/p&gt;

&lt;p&gt;The allow-list is partly about safety and partly about checking. Because a colour is always a literal, we can compute the contrast of any pair before a page is served. Run-time functions such as &lt;code&gt;var()&lt;/code&gt; would make that impossible, so the grammar excludes them. To convert the preview, we resolved every &lt;code&gt;var()&lt;/code&gt; to its literal value for each mode and turned &lt;code&gt;color-mix()&lt;/code&gt; into its computed hex. The preview's component CSS had no theme-specific selectors, so everything a theme varies is a token, and we kept it that way.&lt;/p&gt;

&lt;h2&gt;
  
  
  Light and dark are both authored
&lt;/h2&gt;

&lt;p&gt;Every token carries a value for each mode. The 57 whose types may differ are the colours, paints, borders and shadows. The other 59 (fonts, weights, lengths and the rest) must be byte-equal in light and dark, and the contract enforces it. Dark mode cannot quietly change your spacing or your type.&lt;/p&gt;

&lt;p&gt;One mistake is worth owning. Look, the page where a creator styles a site, has a "Visitors see" control that saves a default colour mode. While reading code for the palette work, we found that the template never read it. The page script started from the reader's stored choice or the system setting, and without the script the page rendered light. The setting was saved and did nothing. The fix renders the author's default on the page root and, when it is light or dark, as the server-resolved mode. A reader's stored choice still wins, and when a creator allows only one mode there is no toggle.&lt;/p&gt;

&lt;h2&gt;
  
  
  The phone, and no script
&lt;/h2&gt;

&lt;p&gt;We audited the designs in a real browser instead of trusting static checks, at 320, 360, 390, 414, 768, 820, 1024 (touch) and 1440 pixels and on a phone on its side at 844 by 390. It asserted rows, overflow, overlap and tap-target sizes, and it caught the header and the reaction bar (the row with Like and the emoji reactions) wrapping onto two lines, which the static checks had missed.&lt;/p&gt;

&lt;p&gt;The header's mobile menu is a &lt;code&gt;&amp;lt;details&amp;gt;&lt;/code&gt; element, which opens and closes without script. The contents list comes from the article's second-level headings when there are at least two. A card without a cover image gets a placeholder painted from tokens. Everything the script adds degrades to plain links or &lt;code&gt;&amp;lt;details&amp;gt;&lt;/code&gt; when it is off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Letting a creator choose colours
&lt;/h2&gt;

&lt;p&gt;A theme's colours are literals in its &lt;code&gt;theme.json&lt;/code&gt;, so a creator who wanted their own accent had nowhere to put it. There are three roles, Accent, Background and Text, each an explicit light and dark pair. A role left unpicked uses the theme's own value. Six named presets live in a list in the app, and "Theme colours" always comes first.&lt;/p&gt;

&lt;p&gt;Three colours cannot drive 116 tokens, and they should not. A theme can bind them to at most 40: the three seeds, 24 more colours such as links, chips, header and footer, all four paints, seven of the eight borders and two shadows. The other 17 stay with the theme: code blocks and their syntax colours, the status colours, the overlay, form inputs, and the card and dialog shadows.&lt;/p&gt;

&lt;p&gt;Each theme says which seed each of its colours follows. When a creator picks an accent, the build moves every colour that follows it by the same perceptual change that turns the theme's accent into theirs, in OKLCH, a colour space with hue, chroma and lightness as its axes. A colour whose seed has not changed keeps the theme's literal exactly, so the default palette reproduces today's colours by construction.&lt;/p&gt;

&lt;p&gt;Two limits apply to what the creator picks. Background must be light enough in light mode and dark enough in dark mode: lightness of at least 0.90 and at most 0.30 on the OKLab scale, where our six themes measure 0.951 to 1.000 and 0.145 to 0.191. Text must reach 4.5:1 against Background in each mode. The creator's colours are used exactly as chosen. If a pick fails, Save is disabled and the reason is shown, for example "Hard to read in dark: 3.1 of 4.5".&lt;/p&gt;

&lt;p&gt;Derived colours are different. Links, chip text and similar colours are computed from the pick, so we adjust them. We check 21 pairs in each mode on the final values: the 17 pairs already checked for every theme at 4.5:1, focus on canvas at 3:1, and the three status colours at 4.5:1. Where a pair's foreground follows the palette, the build moves its lightness by the smallest step that clears the minimum plus 0.1, aiming at 4.6 so that the browser and the build agree on a pass. A failing pair whose foreground belongs to the theme is never adjusted. It fails.&lt;/p&gt;

&lt;p&gt;That has a visible cost: a pure yellow accent gives olive links. In our calculations on the Editorial theme in light mode, a yellow of &lt;code&gt;#ffd60a&lt;/code&gt; gives links of &lt;code&gt;#f1ca00&lt;/code&gt; at 1.38:1, which the adjustment moves to &lt;code&gt;#7f6900&lt;/code&gt; at 4.64:1.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it is checked
&lt;/h2&gt;

&lt;p&gt;The check runs in five places: in the app while a creator picks, where a failing role shows its ratio; in the API at save, which checks shape, lowercase hex, the background band and text on background; in the template at render, which is the authority and refuses the build with &lt;code&gt;APPEARANCE_PALETTE_CONTRAST&lt;/code&gt;, naming the pair, the mode and the ratio; at theme release, against a stress corpus of palettes; and in a test that runs every preset and every theme's default palette through all six themes in both modes.&lt;/p&gt;

&lt;p&gt;Every preset's pass through each theme's bindings is proved by that test, not by arithmetic, and a failing preset is retuned before it ships, with the one exception noted below.&lt;/p&gt;

&lt;p&gt;A contrast audit found zero violations. By hand we measured one preset, Graphite, at 4.05 to 4.25:1 for muted meta text over the page glow in two themes, below our 4.5:1 aim, and it is not fixed yet.&lt;/p&gt;

&lt;p&gt;To set up a site and try the colour choices in Look, the start flow is at &lt;a href="https://app.galascribe.com/" rel="noopener noreferrer"&gt;https://app.galascribe.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>css</category>
      <category>design</category>
      <category>frontend</category>
      <category>ui</category>
    </item>
    <item>
      <title>A theme is not a template: it supplies values, not layout</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Sun, 08 Nov 2026 08:08:37 +0000</pubDate>
      <link>https://dev.to/galascribe/a-theme-is-not-a-template-it-supplies-values-not-layout-1dm6</link>
      <guid>https://dev.to/galascribe/a-theme-is-not-a-template-it-supplies-values-not-layout-1dm6</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://blog.galascribe.com/a-theme-is-a-renderer-not-a-template/" rel="noopener noreferrer"&gt;https://blog.galascribe.com/a-theme-is-a-renderer-not-a-template/&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A Galascribe site is built from three parts that know little about each other: your content, a theme, and the renderer we call the template, the package that builds your pages. Most of our decisions about themes come down to who is allowed to decide what. This post covers the division we settled on, how a build chooses its theme, and what the division costs us.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why five themes were not enough
&lt;/h2&gt;

&lt;p&gt;We had five themes: Default, Amaze, Flashy, Minimal and Zebra. They were token skins over one fixed page skeleton. The template owned the markup: header, breadcrumb, article header, contents rail, body, footer and a single listing style. A theme could not add a magazine grid, a featured-story hero, an author page with a portrait or a different article header.&lt;/p&gt;

&lt;p&gt;My review of them was blunt: "not even a kid will use these themes." The cause was structural, not a matter of colour. Every theme was the same page in a different coat, and the coats (Zebra's diagonal stripes, Flashy's gradients, Amaze's serif) read as gimmicks on an unchanged skeleton. Better palettes would not have fixed it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Layout moved into the template
&lt;/h2&gt;

&lt;p&gt;The fix went into the renderer, not into the themes. Template 4 carries the layouts, and we named the directions by purpose instead of by adjective: Editorial, Personal, Newsletter, Visual and Developer. Each has its own home, article and author layout. The five existing themes were upgraded in place to one direction each, and a sixth theme, Editorial, was added.&lt;/p&gt;

&lt;p&gt;What a theme still owns is values. It is a package of files: &lt;code&gt;theme.json&lt;/code&gt;, &lt;code&gt;tokens.css&lt;/code&gt;, &lt;code&gt;components.css&lt;/code&gt;, an optional &lt;code&gt;utilities.css&lt;/code&gt;, &lt;code&gt;print.css&lt;/code&gt; and any passive assets. &lt;code&gt;theme.json&lt;/code&gt; says which composition the theme uses, declares 116 typed tokens with a light and a dark value each, lists digests for the files, and gives the range of template versions the theme works with.&lt;/p&gt;

&lt;p&gt;The template ships its own base layer, &lt;code&gt;gala-base&lt;/code&gt;, and the stylesheet layers have a fixed order: base, tokens, components, utilities, print. The base comes first, so a theme can override it but cannot reorder it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The lock file decides
&lt;/h2&gt;

&lt;p&gt;Which theme builds your site? The lock file in your site repository decides, not whatever is newest. That rule shipped on 2026-10-04. Your repository carries two records. &lt;code&gt;gala/appearance.json&lt;/code&gt; holds your choice as a range, for example &lt;code&gt;@rathnasgala2/theme-default@^4.0.0&lt;/code&gt;. &lt;code&gt;gala.lock.json&lt;/code&gt; holds the resolved result: an exact row for the schemas package, one for the template and one for the theme, plus a digest of the whole lock. The build reads the lock, requires the exact theme version, and compares the lock's theme row byte for byte with the row the toolchain knows. By toolchain we mean the publish tool your workflow pins, plus the template and theme packages it installs.&lt;/p&gt;

&lt;p&gt;Before it renders anything, the template treats the theme as lower-trust input than your own writing. &lt;code&gt;theme.json&lt;/code&gt; is validated against the theme contract schema first. Its &lt;code&gt;contractVersion&lt;/code&gt;, &lt;code&gt;stylingContractDigest&lt;/code&gt; and &lt;code&gt;templateRange&lt;/code&gt; are checked against the template's own styling contract. Every declared file's length and SHA-256 is compared with the bytes read, and the theme's size budgets are enforced.&lt;/p&gt;

&lt;p&gt;While writing the design below we found a gap in how the theme folder is located. As of our design note of 12 October, the resolver looked first in the repository's own &lt;code&gt;node_modules&lt;/code&gt; and checked only name and version strings, so a theme folder committed by an author would render while the provenance still named the registry digest. The design recommends closing it by resolving themes for managed builds only from the toolchain's own install. That change has not shipped.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two generations at once (a proposal)
&lt;/h2&gt;

&lt;p&gt;None of this is built yet. Today the toolchain serves one generation, and a site on the previous one has to be migrated by hand. This mattered the day the toolchain moved to generation 4. It could no longer build the two sites still on generation 3, and we migrated them by hand. The toolchain could hold only one version of each theme package: one catalog row per package, one directory per name, an exact version check. A second step did the actual damage, the sweep that moves every site's publish workflow to the newest toolchain pin.&lt;/p&gt;

&lt;p&gt;The goal we wrote down: a toolchain update never breaks a live site, and a site changes generation only when a person asks.&lt;/p&gt;

&lt;p&gt;What follows is the design's intent. A theme generation would be the template's major version, which is also the styling contract's major version and the &lt;code&gt;contractVersion&lt;/code&gt; in the lock's template row. The template already enforces that binding, and inside a generation the contract does not move: the styling contract file stayed unchanged from template 3.0.0 through 3.2.1. The catalog would be keyed by package and generation. The toolchain would serve the newest generation and one before it, installed side by side under local alias names in the one install root, so there would still be one lockfile, one audit and one SBOM.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;gala.lock.json                         what the toolchain would serve
  schemas   exact row  --+
  template  exact row  --+--&amp;gt; must byte-equal the rows of ONE generation
  theme     exact row  --+
  lockDigest

generation 3   template 3.2.1   contract 3.0.0   schemas 3.3.0   5 themes
generation 4   template 4.0.0   contract 4.0.0   schemas 3.8.0   6 themes

all three rows match one generation ....... build
older minor or patch of that generation ... LOCK_ROW_STALE
rows from two generations ................. LOCK_THEME_GENERATION_MIXED
generation retired ........................ THEME_GENERATION_RETIRED
anything else ............................. LOCK_THEME_GENERATION_UNKNOWN
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The rows are the ones in the design when we wrote it, and the finding names are the design's. Galascribe would refresh a stale row inside a served generation. The other findings would be refusals with a plain recovery message, such as "Choose the theme again in Look."&lt;/p&gt;

&lt;p&gt;The sweep would follow the same rule. It could refresh a row within its generation, and move the workflow pin when the new toolchain still serves the site's generation. It would never change the template's major, the theme package or the contract version. Moving to generation 4 would be an explicit appearance change that rewrites the lock's three rows and the theme range. It would go through the normal publish workflow like any edit, and if its build failed, the live site would keep serving its previous artifact.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this costs
&lt;/h2&gt;

&lt;p&gt;Every theme must satisfy a contract, and the contract is strict. A theme with a bad digest, a template range that excludes the renderer, an exceeded size budget or an invalid &lt;code&gt;theme.json&lt;/code&gt; is refused. Since template 4.1.0, a theme with no &lt;code&gt;palette&lt;/code&gt; block is refused too, with the code &lt;code&gt;THEME_PALETTE_MISSING&lt;/code&gt;. A mismatch refuses the build instead of falling back to something close.&lt;/p&gt;

&lt;p&gt;There are other costs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A theme author who wants a layout we do not have cannot add one. The layout has to be added to the template, where every theme can use it.&lt;/li&gt;
&lt;li&gt;The toolchain would carry more. In the design, seven package entries become thirteen aliases, and every pairing of generation and theme gets its own test.&lt;/li&gt;
&lt;li&gt;Each generation we kept serving would be one we have to retire eventually.&lt;/li&gt;
&lt;li&gt;The hand migration of our own two sites was a small version of the bill. Strictness moves work onto the people who ship themes, and onto us.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why that is the point
&lt;/h2&gt;

&lt;p&gt;A site here lives in your repository and builds in a workflow you can read. If the build quietly accepted a theme that did not match the lock, you would have no way to know that the page differed from what you chose. A refusal that names the row and the reason is less pleasant on the day, but it leaves you a record you can trust. We prefer a build that does what the lock says or says why it will not.&lt;/p&gt;

&lt;p&gt;Splitting the page from its values has a second payoff: a theme becomes checkable data, so what a theme may contain can be tested before it ships.&lt;/p&gt;

&lt;p&gt;To start a site of your own, the start flow is at &lt;a href="https://app.galascribe.com/" rel="noopener noreferrer"&gt;https://app.galascribe.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>frontend</category>
      <category>softwaredevelopment</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Write, preview, publish: how a post becomes a page</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Fri, 06 Nov 2026 08:08:06 +0000</pubDate>
      <link>https://dev.to/galascribe/write-preview-publish-how-a-post-becomes-a-page-4fkh</link>
      <guid>https://dev.to/galascribe/write-preview-publish-how-a-post-becomes-a-page-4fkh</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://blog.galascribe.com/write-preview-publish-how-a-post-becomes-a-page/" rel="noopener noreferrer"&gt;https://blog.galascribe.com/write-preview-publish-how-a-post-becomes-a-page/&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;When you press Publish, your text passes through four places: your browser, our API, your site repository on GitHub, and a workflow that runs inside that same repository. We designed each step so that it can fail without losing what you wrote, and without claiming a result it has not seen. This post follows one post through all of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The whole path
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Browser         API              Your repository    Your workflow
   |             |                      |                 |
   | type; the preview is drawn here
   |             |                      |                 |
   |- plan ------&amp;gt;                      |                 |
   |             |- text as blobs ------&amp;gt;                 |
   |- confirm ---&amp;gt;                      |                 |
   |             |- commit, PR ---------&amp;gt;                 |
   |             |                      |                 |
   |- publish ---&amp;gt;                      |                 |
   |             |- merge (GitHub App) -&amp;gt;                 |
   |             |- dispatch -----------------------------&amp;gt;
   |             |                      |                 | build, deploy to Pages
   |             &amp;lt;------------------------------ receipt -|
                 | fetch marker from the public site
   &amp;lt;- "Live" ----|
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each stage below says what it guarantees.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the preview is drawn
&lt;/h2&gt;

&lt;p&gt;The preview is rendered in your browser while you type, and nothing leaves it. We render the body with the same Markdown library the site renderer uses, pinned to the same version and configured the same way: raw HTML off, automatic link detection off, typographic replacements off. The result goes into a sandboxed frame with no permissions granted, styled with the site theme's published CSS.&lt;/p&gt;

&lt;p&gt;It is labelled a draft preview, with the words "Your published page may differ slightly". It shares the renderer's Markdown settings and the theme's styles, but it is not the build itself, and we say so. If the browser does not recognise the theme, it falls back to neutral styling and says so. The front matter block is read and written with the YAML package at the version the publish tool pins, so the file the editor writes is the file the publish tool reads.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a saved draft lives
&lt;/h2&gt;

&lt;p&gt;Once saved, your draft lives in your own site repository, on a change branch, and not in our database. Before the first save, your text is kept on your device: the editor writes an encrypted copy to your browser's storage half a second after you stop typing, and at least every two seconds while you keep typing. The key stays in the browser, so this protects against casual inspection, not against someone using your device. If the browser blocks storage, as a private window does, the editor still works and says the draft cannot be kept on this device.&lt;/p&gt;

&lt;p&gt;Saving is two requests.&lt;/p&gt;

&lt;p&gt;The first, a plan, carries the document paths, the text and a digest of each, plus the repository revision you started from. The API writes each document into your repository as a git blob, unreferenced until a commit points at it, using a token limited to that one repository. Our database holds paths, blob ids, sizes and digests, and never what you wrote.&lt;/p&gt;

&lt;p&gt;The second, confirm, builds the tree and a commit from those blob ids on a change branch, and opens a pull request. If a blob has disappeared by then, the change fails with no effect, and the app plans again from the draft. A saved, unpublished draft is therefore a branch in a repository you own.&lt;/p&gt;

&lt;p&gt;Paths are restricted to the content and asset folders your repository declares. A document write cannot touch the settings files, the lock file or the workflows. A change holds at most 20 documents, each at most 1 MiB.&lt;/p&gt;

&lt;p&gt;If someone else changed the main branch after you started, the API refuses with the live head instead of overwriting. Edits to different lines are merged for you. Where the same lines were edited, the browser shows three versions of the file: yours, theirs and the common starting point. Per field you keep yours or theirs, and overlapping body edits keep both sides with markers. The server never merges text and never writes conflict markers into a repository.&lt;/p&gt;

&lt;h2&gt;
  
  
  Publish: merged, built and deployed in your repository
&lt;/h2&gt;

&lt;p&gt;By default, publish merges that pull request through the Galascribe GitHub App, and there is no review step. Both are per-site settings. A site can require a review, in which case a reviewer approves first and the merge follows approval; it can also leave the merge to you in GitHub. After the merge, one deploy runs for the resulting main head.&lt;/p&gt;

&lt;p&gt;The deploy is the publish workflow, which runs in your repository, not on our servers. Your site repository holds the settings files, a lock file that pins the template and publisher versions and records the theme, and the publish workflow file itself, which calls a pinned version of the publish tool. It builds the site from your files and deploys it to GitHub Pages, which repository set-up enables with the workflow build type. When it finishes, the workflow reports a receipt back to us.&lt;/p&gt;

&lt;p&gt;A receipt says the workflow ran. It does not yet say your visitors are being served the result.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "live" means
&lt;/h2&gt;

&lt;p&gt;After the receipt, the deployment is in a state we call verifying, and a durable job checks the public site. It fetches a small marker file the build published, from the origins recorded on the deployment, never from an address supplied at check time, and compares three values with the ones we certified: artifact id, artifact digest and generation id. A match makes the deployment verified, and only then does the app say "live". If the site still serves the predecessor's digest, it is propagating and we try again with growing delays for about two minutes. If it serves anything else, we record a mismatch and never mark it verified. After the retries the deployment is marked degraded, and a reconcile, which the app now runs for you, can start the check again.&lt;/p&gt;

&lt;p&gt;Because the API fetches from an address a person chose, the fetch is restrictive. It uses https on port 443, refuses any address that is not globally reachable, connects to the address it vetted, sends no credentials, follows at most three redirects within the same origin, and reads at most 64 KiB.&lt;/p&gt;

&lt;p&gt;Two limits, stated plainly. This is the first of three tiers in the design; checks of critical routes and of the whole inventory are not built today. And the design document records why the check exists: when it was written, nothing in production code ever moved a deployment to verified, and tests set that state by writing to the database.&lt;/p&gt;

&lt;h2&gt;
  
  
  One thing that broke
&lt;/h2&gt;

&lt;p&gt;The cause recorded in our content-journey incident review was a single mismatch. A proposed version of a post is addressed by a revision, and the contract carries that revision in a tagged wire form. The admission check against the database compared it without normalising it first, so the two disagreed about the same revision. On the wire a revision is written &lt;code&gt;sha1:&lt;/code&gt; followed by the 40 hexadecimal characters of a git object id.&lt;/p&gt;

&lt;p&gt;The review's checklist runs in this order. We reproduced the mismatch with a failing API test, then made the API normalise the revision before database admission while keeping the tagged value on the wire. Nineteen targeted API document and asset tests passed, with formatting and style checks, and 183 browser checks across the source, content, review, release and publish journeys passed, at desktop and mobile widths where applicable. The fixed API image was promoted to production, and the image being served and an API canary were verified. One item was still open when the review was written: a signed-in person clicking the proposed-version link in production, which needs a real user session.&lt;/p&gt;

&lt;p&gt;If you want to try the path yourself, the start flow is at &lt;a href="https://app.galascribe.com/" rel="noopener noreferrer"&gt;https://app.galascribe.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>api</category>
      <category>architecture</category>
      <category>backend</category>
      <category>github</category>
    </item>
    <item>
      <title>No more humans visit your website. How warm are you in welcoming the new breed?</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Wed, 04 Nov 2026 06:20:40 +0000</pubDate>
      <link>https://dev.to/galascribe/no-more-humans-visit-your-website-how-warm-are-you-in-welcoming-the-new-breed-2ng0</link>
      <guid>https://dev.to/galascribe/no-more-humans-visit-your-website-how-warm-are-you-in-welcoming-the-new-breed-2ng0</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; My Cloudflare overview said 467 unique visitors in 24 hours. My own admin said zero real users. The AI crawler tab explained the gap: 229 crawler requests, the sitemap fetched 41 times, ClaudeBot at the top. We had spent a month laying out everything a bot could want, from llms.txt to a machine-readable licence, and a web search for our name still returns a glass-engraving pen. Readable is not cited. The bot's taste is borrowed from humans, so the only warmth that counts for the new breed is the warmth you show the few humans who still turn up.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Two dashboards, one evening
&lt;/h2&gt;

&lt;p&gt;On the evening of 3 November I had two tabs open.&lt;/p&gt;

&lt;p&gt;The first was the Cloudflare overview for galascribe.com, free plan, last 24 hours. Unique visitors: 467. A nice line with a peak around nine in the morning.&lt;/p&gt;

&lt;p&gt;The second was the Users page of our own operator dashboard. Eight accounts. Every one of them mine: test users from the last six weeks. Real users: zero.&lt;/p&gt;

&lt;p&gt;So many unique visitors, and still no early adopters. If you run a small site you know this feeling. You do not need me to explain the gap. But I went and looked at it anyway.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who the 467 are
&lt;/h2&gt;

&lt;p&gt;Cloudflare has an AI Crawlers tab now. For the same window it said:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;229 requests from AI crawlers, up 17.4% on the previous period.&lt;/li&gt;
&lt;li&gt;187 allowed, 42 unsuccessful, 155 answered with a 200.&lt;/li&gt;
&lt;li&gt;The most crawled path on the whole domain: &lt;code&gt;app.galascribe.com/sitemap.xml&lt;/code&gt;, 41 successful requests.&lt;/li&gt;
&lt;li&gt;64 requests from ClaudeBot alone. Anthropic 55 allowed, Google 49, OpenAI 30, Baidu 26, Amazon 14, Microsoft 12.&lt;/li&gt;
&lt;li&gt;Baidu's crawler pulled 1.63 MB of JavaScript.&lt;/li&gt;
&lt;li&gt;Perplexity: 1. Apple, ByteDance, Common Crawl: 0.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The humans in that 467 are a rounding error. The visitors are a new breed. They never sign up, never comment, never buy. They read the sitemap, pull the pages, and leave with what they came for.&lt;/p&gt;

&lt;p&gt;Then they answer questions about you to people you will never see in any dashboard.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we had already laid out for them
&lt;/h2&gt;

&lt;p&gt;I am not writing this as someone who ignored the bots. We had been setting the table for a month. From the commit log:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;5 October.&lt;/strong&gt; Every site our platform generates got JSON-LD, a &lt;code&gt;robots.txt&lt;/code&gt;, an &lt;code&gt;llms.txt&lt;/code&gt; and an &lt;code&gt;llms-full.txt&lt;/code&gt;, full-content feeds, article and image meta, a visible updated date.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;18 October.&lt;/strong&gt; Our own app got a public About page and its own &lt;code&gt;llms.txt&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;24 October.&lt;/strong&gt; We claimed the X, LinkedIn and GitHub profiles, pointed &lt;code&gt;sameAs&lt;/code&gt; at them from the Organization structured data, and made 32 public test repositories private so a crawler would stop finding scaffolding with our name on it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;29 October.&lt;/strong&gt; Per-site AI rights. Search and answer bots (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, Claude-User, PerplexityBot) and training crawlers (GPTBot, ClaudeBot, CCBot, Bytespider, Amazonbot and friends) became two classes a writer can allow or block separately. Blocking training adds &lt;code&gt;noai, noimageai&lt;/code&gt; to every page and writes a &lt;code&gt;/license.xml&lt;/code&gt; in Really Simple Licensing shape. Each article also ships its own Markdown at &lt;code&gt;index.md&lt;/code&gt;, exactly as the author wrote it, so a bot never has to scrape the HTML.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;2 November.&lt;/strong&gt; Public Trust and Status pages, &lt;code&gt;llms.txt&lt;/code&gt; rewritten around features and prices, an IndexNow key with a submit script, and an uptime worker publishing a status JSON every five minutes.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That is a warm welcome by any technical measure. The crawler tab agrees. 155 clean 200s a day.&lt;/p&gt;

&lt;h2&gt;
  
  
  Then I searched for us
&lt;/h2&gt;

&lt;p&gt;Same evening, three queries in a plain web search.&lt;/p&gt;

&lt;p&gt;"Galascribe reddit review": nothing with our name. The engine offered Glasscribe, a transcription tool on Capterra, and the Glascribe Pen, a tungsten-carbide tip for engraving glass.&lt;/p&gt;

&lt;p&gt;"Galascribe writing platform": nothing. It offered Glæmscribe, which transcribes Tolkien's invented scripts.&lt;/p&gt;

&lt;p&gt;"what is galascribe.com": nothing. It offered Gale's G Scrib and ElevenLabs Scribe.&lt;/p&gt;

&lt;p&gt;Three queries, our name corrected to four other products, our own site absent from every list. While 229 crawler requests a day read our sitemap.&lt;/p&gt;

&lt;p&gt;That was the lesson of the evening, and it is the one I want to hand you: &lt;strong&gt;readable is not cited.&lt;/strong&gt; You can make every page machine-perfect and the answer engines will still have nothing to say about you, because they do not answer from your pages. They answer from what other people said about your pages.&lt;/p&gt;

&lt;h2&gt;
  
  
  What most people say, and what I think
&lt;/h2&gt;

&lt;p&gt;Most people I talk to believe SEO is dying and a new animal called AIO (AI optimisation, generative engine optimisation, pick this month's name) has replaced it, and that nobody really understands the animal.&lt;/p&gt;

&lt;p&gt;I think that is half right. SEO is not dying. It is turning into something no single human brain holds any more: crawler classes, licence files, structured data, answer bots versus training bots, a dozen vendors with a dozen user agents, and on top of it all a retrieval layer that decides what to cite from what it found elsewhere.&lt;/p&gt;

&lt;p&gt;The difference is what you do about not being able to hold it all. I do not think a writer should try. The plumbing above is an afternoon of work for a platform and a lifetime of maintenance for an individual. Let a tool do the plumbing. Spend yourself on the one part no tool can do.&lt;/p&gt;

&lt;h2&gt;
  
  
  The objection I had to answer
&lt;/h2&gt;

&lt;p&gt;A reader will say: that is a vendor talking. "It is too hard, buy my tool." Your own numbers say the tooling bought you nothing.&lt;/p&gt;

&lt;p&gt;Fair. So here is the part I actually believe, and it is not about tooling.&lt;/p&gt;

&lt;p&gt;A bot has no taste. It fetched my sitemap 41 times and the search engine still thinks I am a glass pen. Why would one genuinely useful post get an assistant to cite you before a site with a thousand mediocre ones?&lt;/p&gt;

&lt;p&gt;The same reason Reddit is worth so much to the people building these models. In February 2024 Reuters reported that Google pays Reddit about $60 million a year for its content. Not for Reddit's HTML. Reddit's HTML is terrible. For the human talk: people asking, answering, arguing and recommending to each other.&lt;/p&gt;

&lt;p&gt;The bot's taste is borrowed. It is borrowed from humans who interacted with your writing, and said so somewhere a crawler could read.&lt;/p&gt;

&lt;p&gt;That changes what "warm welcome" means. The new breed does not want a warmer &lt;code&gt;llms.txt&lt;/code&gt;. It wants evidence that humans found you useful. And the only way to produce that evidence is to be useful to the few humans who still arrive.&lt;/p&gt;

&lt;h2&gt;
  
  
  What that looks like for us
&lt;/h2&gt;

&lt;p&gt;This is the bet Galascribe is built on, and it is a constraint, not a feature.&lt;/p&gt;

&lt;p&gt;There is no feed. A reader who lands on a Galascribe site gets a small number of pieces, and the expectation we set is that each one is useful for a real job in their life: my career, my mental health, raising my kids, looking after my parents, staying in touch with them, planning a trip. Comments and feedback are measured as the thing that matters, because they are the only signal the new breed will ever trust about you.&lt;/p&gt;

&lt;p&gt;Limited quantity, very high quality. It makes a slow site. It also makes every human who shows up worth far more than one of the 467, and every comment they leave worth more than another thousand crawler fetches.&lt;/p&gt;

&lt;p&gt;I am writing this with zero real users, so take it as a bet, not a result. But I would rather be useful to the next ten humans than readable to the next ten thousand bots. The bots will follow the humans. They always have.&lt;/p&gt;

&lt;p&gt;If you want to see the plumbing laid out for your own writing, it starts at &lt;a href="https://app.galascribe.com" rel="noopener noreferrer"&gt;https://app.galascribe.com&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>ai</category>
      <category>webdev</category>
      <category>startup</category>
    </item>
    <item>
      <title>Your hard work got stolen. What would you do?</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Sat, 31 Oct 2026 08:53:41 +0000</pubDate>
      <link>https://dev.to/galascribe/your-hard-work-got-stolen-what-would-you-do-cnf</link>
      <guid>https://dev.to/galascribe/your-hard-work-got-stolen-what-would-you-do-cnf</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; I led the rewrite of one of my company's most critical apps, and it shipped with almost no critical bugs.&lt;br&gt;
A colleague who was better at communication got promoted for it, and I heard in a team meeting, days after others&lt;br&gt;
knew. Ten years in, I wasn't short on technical skill; I was short on presenting and politics. I didn't fix that. I&lt;br&gt;
took my strength where it gets paid: two months of preparation, 40–60 applications, one 40% raise.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The announcement
&lt;/h2&gt;

&lt;p&gt;A colleague's promotion was announced in a team meeting. I'll call them X. The project behind it was one I'd led.&lt;/p&gt;

&lt;p&gt;X was in the same room as me, with others dialled in on the phone. More than six years on, I don't remember the exact&lt;br&gt;
words. I remember working out, somewhere in the middle of that announcement, that it had been known for a couple of&lt;br&gt;
days. Others had heard. I was kept in the dark until then.&lt;/p&gt;

&lt;p&gt;On the technical side, I owned it end to end: a full rewrite of a very complex, high-visibility app, one of the most&lt;br&gt;
sensitive in the whole enterprise. It shipped with close to zero P0 issues. Moving it to microservices made it over 50%&lt;br&gt;
more efficient, and many of the old version's pain points were eliminated in the design phase itself.&lt;/p&gt;

&lt;p&gt;X was good at communication and at getting the ducks in a row. X got promoted.&lt;/p&gt;

&lt;p&gt;It felt like my work had been stolen.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ten years in, and stuck
&lt;/h2&gt;

&lt;p&gt;It wasn't the first time. I'd watched others move up the career ladder ahead of me, and it wasn't always the strongest&lt;br&gt;
engineer who went up. I was about ten years into my career and had only grown to Staff level.&lt;/p&gt;

&lt;p&gt;I wasn't short on technical acumen. I was short on presenting my work in an interesting way, talking to non-technical&lt;br&gt;
folks, and playing the political games. Someone had hurt my ego, and I was frustrated.&lt;/p&gt;

&lt;p&gt;The usual answer to a moment like that is to give the job more of yourself: more hours than it asks for, and wait&lt;br&gt;
your turn. I believe you need grit instead, and the nerve to question the rule that says you stay and wait. Most of&lt;br&gt;
what stops you is in your head: what Ichiro Kishimi and Fumitake Koga's book calls &lt;em&gt;the courage to be disliked&lt;/em&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 11-year-old I'd lost
&lt;/h2&gt;

&lt;p&gt;When I was 11, I helped my dad tally his numbers every day. He did it religiously, and he couldn't sleep peacefully&lt;br&gt;
until every tally was accounted for. Around then I fell for computers and anything electronic: calculators, digital&lt;br&gt;
watches, Walkmans. Then BASIC, C, C++, Visual Basic, Java.&lt;/p&gt;

&lt;p&gt;Somewhere along the way that kid got lost in comfort, responsibilities and grievance. Looking inward, and finding that&lt;br&gt;
11-year-old again, is the best thing I did. I reinvented myself around what I'd always loved.&lt;/p&gt;

&lt;p&gt;My dad never went to sleep on a tally that didn't add up. I decided I wouldn't build a career on one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two months, on purpose
&lt;/h2&gt;

&lt;p&gt;So I set a goal: a better job, somewhere else. From the end of January to the middle of March 2020, I put 15 to 30&lt;br&gt;
hours a week into three things: data structures and algorithms, system design, and cloud architecture. I had support at home, and&lt;br&gt;
I'm really thankful for it. When lockdown arrived in March, it even handed back the hours I'd been losing to the&lt;br&gt;
commute.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The LeetCode grind.&lt;/li&gt;
&lt;li&gt;Mock interviews with friends.&lt;/li&gt;
&lt;li&gt;System design mocks on my own, with scenarios prepared in advance: the questions to ask, the assumptions I'd make,
and how I'd justify each one.&lt;/li&gt;
&lt;li&gt;Applications on LinkedIn, non-stop.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The funnel: 40 to 60 companies applied to, 10 interviews, 4 final rounds, two offers I went back and forth on, one yes.&lt;/p&gt;

&lt;h2&gt;
  
  
  2% or 40%
&lt;/h2&gt;

&lt;p&gt;Pushing back from inside would have fetched me another 2% raise. At best, 5%. I left with a 40% raise.&lt;/p&gt;

&lt;p&gt;I didn't fix my weakness first. I took my strength to where it gets paid.&lt;/p&gt;

&lt;p&gt;That was my rebellion: not fighting the people who decided who moved up, but refusing to wait for them. Living well&lt;br&gt;
really is the best revenge. It also pays better.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you can't leave this quarter
&lt;/h2&gt;

&lt;p&gt;"Just leave" is easy advice from someone it worked for. Maybe your visa, your family or the market says not now.&lt;/p&gt;

&lt;p&gt;You don't need permission to prepare. Leaving is the last step; getting ready is the first, and nobody can stop you&lt;br&gt;
taking it. In &lt;em&gt;The Shawshank Redemption&lt;/em&gt;, Andy Dufresne calls it a simple choice: "Get busy living or get busy dying."&lt;br&gt;
Either way, you'll get busy.&lt;/p&gt;

&lt;p&gt;So get busy on purpose, this week: one mock interview with a friend, one system design problem worked out loud, and a&lt;br&gt;
date on the calendar for your first application.&lt;/p&gt;

&lt;p&gt;The promotion went to someone else. What I got back was the 11-year-old who loved this stuff, and a 40% raise.&lt;/p&gt;

&lt;p&gt;Six years later, I'm building my own company.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Has your work ever been credited to someone else? What did you do? Tell me in the comments.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>softwareengineering</category>
      <category>discuss</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Three hours on X, and the video that gave Galascribe its direction</title>
      <dc:creator>Galascribe</dc:creator>
      <pubDate>Fri, 30 Oct 2026 03:37:00 +0000</pubDate>
      <link>https://dev.to/galascribe/three-hours-on-x-and-the-video-that-gave-galascribe-its-direction-2jl5</link>
      <guid>https://dev.to/galascribe/three-hours-on-x-and-the-video-that-gave-galascribe-its-direction-2jl5</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://blog.galascribe.com/three-hours-on-x-and-the-video-that-gave-galascribe-its-direction/" rel="noopener noreferrer"&gt;blog.galascribe.com&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; One night in July 2026 I lost three hours to a feed, and Galascribe began as the fix: a slow place for writing, with no feed, built to respect attention. Months in, our pitch had drifted to "articles from your videos". A video by Sandeep Swadia on writing with AI brought me back, and gave us our motto: Sound like no one else. A writing platform should build healthy habits, not chase virality.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It was the last week of July 2026. I had just flown back from India, I was jet-lagged, and at 10 PM I opened X. When I put the phone down it was 1:15 AM.&lt;/p&gt;

&lt;p&gt;The next morning I drove to work on too little sleep. Somewhere on that drive I asked myself a question I couldn't shake: why did I do that? I knew the scrolling was bad for my head. I knew a tired drive is a dangerous one. I did it anyway, for three hours.&lt;/p&gt;

&lt;p&gt;The honest answer is that the product worked as designed. A feed that never ends, ranked to keep you there, paid for by advertisers who want your time. Knowing that doesn't protect you from it, and especially not at midnight with a jet-lagged body clock.&lt;/p&gt;

&lt;p&gt;So I tried to fix it from first principles, at two levels. At the platform level: what would a place for reading look like if it were built to respect attention instead of harvesting it? At the content level: what would people write if the reward were being useful instead of being loud? Galascribe came out of that drive.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I wanted to build
&lt;/h2&gt;

&lt;p&gt;I wanted something slow and organic. A platform that is happy to serve readers less, on purpose, because a limit on quantity forces you to work on quality. Galascribe is bootstrapped from my own pocket, which means there are no investors to please and no ad commitments to honour. That is the only reason the slow version is possible at all.&lt;/p&gt;

&lt;p&gt;Here is what that means in the product today, without dressing it up:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;There is no feed.&lt;/strong&gt; No timeline, no trending list, no recommendations. Readers follow an author and hear from that author. Nothing ranks one writer's work against another's to keep you scrolling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Posts can arrive on a schedule.&lt;/strong&gt; Staggered release lets an author write several posts at once and have them go out on dates they choose, instead of all at once.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;We practise the pace ourselves.&lt;/strong&gt; This blog publishes two posts a week, Sunday and Friday. Not because we can't write more, but because nobody needs more from us than that.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What it does not do yet is judge quality. I have ideas about how to measure it and what to lift up or push down, but I won't claim any of them until they're tested on real writers and proven to work. A platform that says it rewards quality and can't show how is just another marketing line.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I drifted
&lt;/h2&gt;

&lt;p&gt;Building a product pulls you towards whatever is easiest to explain. For a while our pitch was "Articles from your videos, on a website you own." It described one feature well. It was also narrow, and it didn't give anyone much reason to try us. Worse, it had quietly moved me away from why I started. That line is about producing more content faster, with AI doing the work and the person tidying up after it. I set out to do the opposite: to help people's own work, and let AI serve it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The video that brought me back
&lt;/h2&gt;

&lt;p&gt;Then I watched Sandeep Swadia's &lt;a href="https://www.youtube.com/watch?v=-wreCvpBdso" rel="noopener noreferrer"&gt;Everyone Can Spot AI Writing, Here's How To Fix It&lt;/a&gt;. Galascribe already existed; the video didn't start it. What it did was give the project its direction back, and help me put into words what I believe about writers in 2026.&lt;/p&gt;

&lt;p&gt;His point is simple: AI can write everything for you, and that is exactly why everyone sounds the same. In his words, AI gives you an accent. He sets out a five-step check that spells VOICE: is it verified, is it owned (built from your own experience), is it insightful, is it clear, is it engaging. He opens by promising writing that is "clearer, more insightful, and unmistakably yours".&lt;/p&gt;

&lt;p&gt;That phrase stayed with me, and it's where our new line comes from. We changed what Galascribe says about itself to:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Sound like no one else.&lt;/strong&gt; Write clearly. Share insights that are unmistakably yours.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The debt is plain, and I'd rather say so than pretend we got there alone.&lt;/p&gt;

&lt;p&gt;His VOICE steps changed how we work too. This post was written that way: I was interviewed one question at a time about what actually happened, my answers were checked against our own code and records, and every claim about the product that couldn't be verified was cut. Further out, I'd like Galascribe to offer authors a VOICE-style review of their own drafts. That is a plan, not a feature, and it will stay a plan until it's built and tested.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I believe
&lt;/h2&gt;

&lt;p&gt;Most people believe a writing platform should chase engagement: help you go viral overnight, change the world, please everybody.&lt;/p&gt;

&lt;p&gt;I believe it should build healthy habits instead. It should not turn readers into test subjects for attention-hungry feeds, or writers into editors of whatever a model produced. It should be gentle, and it should carry knowledge that is actually worth someone's evening.&lt;/p&gt;

&lt;p&gt;The difference comes down to a few things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Not everything is about money.&lt;/strong&gt; That doesn't mean free. Galascribe has to keep the lights on and feed my family. But I hold to a simple rule: hunger has a limit; ego doesn't. Charge enough to keep going, and be ambitious only where it helps the people using it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ordinary is fine.&lt;/strong&gt; A moderate, simple post that teaches one person one useful thing is a good post. Not every piece has to perform.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Try things anyway.&lt;/strong&gt; I'd rather encourage people to be a little shameless, publish the idea, and see what happens, than wait until it's perfect.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this asks writers to give up reach. Post your links wherever your readers are. We are just not going to build another place that rewards stunts over substance. We are not trying to please every audience either. A handful of readers and writers at first is enough, if a few of them spend one fewer evening the way I spent that one in July.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this leaves us
&lt;/h2&gt;

&lt;p&gt;Sandeep closes his video with a line I keep coming back to: you don't write just to find words, you write to find out what you think. Writing this post, I found out what I think. Galascribe exists so that night in July happens to fewer people, and so the writing they find instead sounds like a person.&lt;/p&gt;

&lt;p&gt;To start a site of your own, the start flow is at &lt;a href="https://app.galascribe.com/" rel="noopener noreferrer"&gt;https://app.galascribe.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>writing</category>
      <category>ai</category>
      <category>productivity</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
