<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[slate]]></title><description><![CDATA[slate]]></description><link>https://slatecoil.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 19:18:51 GMT</lastBuildDate><atom:link href="https://slatecoil.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[The WordPress sitemap that suddenly looks broken in Chrome]]></title><description><![CDATA[Since 17 November 2026, when Chrome 158 began rolling out to most users, Chrome no longer applies XSLT stylesheets. WordPress core and Yoast used one to…]]></description><link>https://slatecoil.hashnode.dev/the-wordpress-sitemap-that-suddenly-looks-broken-in-chrome</link><guid isPermaLink="true">https://slatecoil.hashnode.dev/the-wordpress-sitemap-that-suddenly-looks-broken-in-chrome</guid><category><![CDATA[WordPress]]></category><category><![CDATA[SEO]]></category><dc:creator><![CDATA[Slate]]></dc:creator><pubDate>Fri, 20 Nov 2026 10:26:18 GMT</pubDate><content:encoded><![CDATA[<p>Since 17 November 2026, when Chrome 158 began rolling out to most users, Chrome no longer applies XSLT stylesheets. WordPress core and Yoast used one to render the XML sitemap as a readable table, so the same URL now shows a wall of raw XML. The file is byte for byte what it was yesterday.</p>
<h2>Why this matters for a small business site</h2>
<p>The danger is a well-meaning fix. A site owner or freelancer sees raw markup, assumes the sitemap broke, and deletes or regenerates it, or swaps SEO plugins. None of that is needed. Google reads sitemaps under the sitemaps protocol, meaning the URL list, and the stylesheet hint was only ever for browsers. Chrome's own figures put XSLT at about 0.02% of page loads, and Chrome 176 (17 August 2027) ends even the enterprise exception.</p>
<p>The ecosystem is adapting: Yoast 28.9, released 18 November, removes the stylesheet from its XML sitemaps, and WordPress 7.2, due 8 December, is planned to do the same for the core sitemap.</p>
<ol>
<li>Open Search Console, go to Indexing, then Sitemaps, and confirm the status and the last read date.</li>
<li>Update Yoast to 28.9 and confirm WordPress 7.1.5 is installed.</li>
<li>Add a plain HTML sitemap page if visitors need a browsable list of pages.</li>
</ol>
<p><a href="https://www.slate.co.il/en/news/2026-11-20-chrome-sitemap-raw-xml">Read the full story on Slate</a></p>
]]></content:encoded></item><item><title><![CDATA[Before You Upgrade for Gemini 4 Neon, Run This One Test]]></title><description><![CDATA[Google released Gemini 4 Neon on 18 November 2026, and it sits behind a paywall: in the Gemini app only Google AI Pro and Ultra subscribers can select it…]]></description><link>https://slatecoil.hashnode.dev/before-you-upgrade-for-gemini-4-neon-run-this-one-test</link><guid isPermaLink="true">https://slatecoil.hashnode.dev/before-you-upgrade-for-gemini-4-neon-run-this-one-test</guid><category><![CDATA[AI]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Slate]]></dc:creator><pubDate>Thu, 19 Nov 2026 07:24:05 GMT</pubDate><content:encoded><![CDATA[<p>Google released Gemini 4 Neon on 18 November 2026, and it sits behind a paywall: in the Gemini app only Google AI Pro and Ultra subscribers can select it. In Israel AI Pro costs ₪74.90 a month; AI Plus, at ₪19, gets the lighter Hydrogen model instead, and free accounts get Hydrogen through automatic model selection.</p>
<h2>Why paperwork is the right test</h2>
<p>Google's own examples for Neon are office chores: explaining a spike on a utility bill, comparing vendor prices before a purchase, and cross-checking receipts to negotiate a refund. That makes it easy to judge on your own data rather than on benchmark claims.</p>
<p>Two numbers frame the decision. Pro holds 1 million tokens of context, against 128,000 on Plus and 32,000 on the free tier, so long statements and bundles of invoices only fit at the top. And Google gives no daily cap for Neon: Pro gets four times the standard usage limit, refreshing every five hours up to a weekly ceiling.</p>
<h2>The test</h2>
<ol>
<li>Take three months of business card charges in one file and remove card numbers and customer names.</li>
<li>Ask Neon to list recurring subscriptions and every charge that rose month over month.</li>
<li>Verify three of its answers by hand.</li>
<li>Upgrade only if it was right and saved real time; the model reads receipts, but your invoices still belong in a proper invoicing system.</li>
</ol>
<p><a href="https://www.slate.co.il/en/news/2026-11-19-gemini-4-neon-pro">Read the full story on Slate</a></p>
]]></content:encoded></item><item><title><![CDATA[Record Once, Update Forever: Google Vids Opens Personal Avatars to Free Accounts]]></title><description><![CDATA[On 17 November 2026 Google opened personal avatars in Google Vids to every personal Google account, free of charge. A personal avatar is an AI presenter…]]></description><link>https://slatecoil.hashnode.dev/record-once-update-forever-google-vids-opens-personal-avatars-to-free-accounts</link><guid isPermaLink="true">https://slatecoil.hashnode.dev/record-once-update-forever-google-vids-opens-personal-avatars-to-free-accounts</guid><category><![CDATA[AI]]></category><category><![CDATA[marketing]]></category><dc:creator><![CDATA[Slate]]></dc:creator><pubDate>Wed, 18 Nov 2026 07:26:28 GMT</pubDate><content:encoded><![CDATA[<p>On 17 November 2026 Google opened personal avatars in Google Vids to every personal Google account, free of charge. A personal avatar is an AI presenter built from your own face and voice. You record once on a phone, type a script, and Vids produces a clip of you saying it. Until now it was limited to Google AI Pro, AI Ultra and Workspace business plans.</p>
<h2>Why a small business might care</h2>
<p>The win is not a polished brand film. It is the short explainer that breaks every time something changes: a pricing page walkthrough, a booking how-to, a reply to the question every customer asks. Re-recording those usually means a camera, lights and a free hour. With an avatar, a changed price is a changed sentence in the script.</p>
<p>The catch is reach. Personal avatars work in English only for now and are unavailable in the EEA, Switzerland and the UK. Google has not published a clear monthly quota for free accounts; its help table shows six AI avatar generations for personal accounts while still listing personal avatars under paid plans. Every clip carries an invisible SynthID watermark, so viewers see no AI label unless you add one.</p>
<p>Recording takes a few minutes: choose Personal avatar in Vids, scan the QR code, and follow the prompts in a quiet, evenly lit room. Only the account owner may record, and only from age 18.</p>
<h2>A short plan</h2>
<ol>
<li>Secure the Google account with two-step verification first, since it now holds a copy of your face and voice.</li>
<li>Pick one English video that goes stale often and write a 30 to 60 second script.</li>
<li>Generate it, watch it end to end, and correct any wrong figure before publishing.</li>
</ol>
<p><a href="https://www.slate.co.il/en/news/2026-11-18-google-vids-personal-avatar-free">Read the full story on Slate</a></p>
]]></content:encoded></item><item><title><![CDATA[Sharing a Gemini Notebook site shares the whole notebook]]></title><description><![CDATA[On 16 November 2026 Google added site generation to Gemini Notebook. You upload sources to a notebook, type "make me a site" in its chat with a short…]]></description><link>https://slatecoil.hashnode.dev/sharing-a-gemini-notebook-site-shares-the-whole-notebook</link><guid isPermaLink="true">https://slatecoil.hashnode.dev/sharing-a-gemini-notebook-site-shares-the-whole-notebook</guid><category><![CDATA[AI]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Slate]]></dc:creator><pubDate>Tue, 17 Nov 2026 07:25:27 GMT</pubDate><content:encoded><![CDATA[<p>On 16 November 2026 Google added site generation to Gemini Notebook. You upload sources to a notebook, type "make me a site" in its chat with a short description, and get back an interactive page: a sales dashboard, a project tracker, a timeline. It is live on the web worldwide for users aged 18 and over, free Gmail accounts included, and the mobile app gets it later.</p>
<h2>What it changes for a business owner</h2>
<p>Most small businesses share numbers as a spreadsheet attachment or a screenshot, and the person on the other end then asks for a different cut. A filterable page removes that round trip. A contractor can give a client a page showing which stages are done. A freelancer can show how hours split across projects in a month.</p>
<p>The free tier allows 100 notebooks with up to 50 sources each, under a usage quota that refreshes every five hours up to a weekly cap. Google AI Pro raises that to 500 notebooks and 300 sources. Google does not say how many sites fit in the quota.</p>
<p>The catch sits in the sharing model. According to Google's help page, sharing a site by link means sharing the notebook itself, and viewers get access to the whole notebook. Whatever else lives in it, such as the raw export with customer names or prices quoted to someone else, travels with the link. Deleting the site or turning off sharing breaks links already sent, and sharing requires a consumer Google account.</p>
<h2>Before you send a link</h2>
<ol>
<li>Build client-facing sites in a fresh notebook that holds only the file the client may see.</li>
<li>Review the notebook's source list right before sharing and remove anything private.</li>
<li>Check every figure on the page against the original file, since the site displays mistakes as neatly as facts.</li>
<li>Keep the authoritative income and expense numbers in your bookkeeping system and use the site only to present them.</li>
</ol>
<p><a href="https://www.slate.co.il/en/news/2026-11-17-gemini-notebook-interactive-sites">Read the full story on Slate</a></p>
]]></content:encoded></item><item><title><![CDATA[Your CSS Has a Left-and-Right Problem]]></title><description><![CDATA[If your app ever needs Hebrew or Arabic, every margin-left in your CSS is a bug you have not met yet. RTL is not a translation problem. The entire page…]]></description><link>https://slatecoil.hashnode.dev/your-css-has-a-left-and-right-problem</link><guid isPermaLink="true">https://slatecoil.hashnode.dev/your-css-has-a-left-and-right-problem</guid><dc:creator><![CDATA[Slate]]></dc:creator><pubDate>Fri, 31 Jul 2026 07:58:17 GMT</pubDate><content:encoded><![CDATA[<p>If your app ever needs Hebrew or Arabic, every margin-left in your CSS is a bug you have not met yet. RTL is not a translation problem. The entire page mirrors: navigation sits on the other side, tables read the other way, form labels swap edges, and the "back" chevron points the wrong direction.</p>
<p>The old answer was a second stylesheet full of overrides: [dir="rtl"] .card { margin-right: 16px; margin-left: 0; }. Every new component doubles the work, and the override file rots the moment someone forgets it exists. The better answer has been in every browser for years: CSS logical properties.</p>
<p>Instead of naming a physical edge, you name the edge relative to text direction. margin-inline-start replaces margin-left. padding-inline replaces the left-right padding pair. inset-inline-end replaces right for absolutely positioned elements. border-inline-start replaces border-left. text-align: start replaces text-align: left. In LTR they resolve to the left side, in RTL to the right side, with zero extra code.</p>
<p>Flexbox and grid are already logical: flex-start, justify-content, grid columns all follow direction on their own. So a layout built on flex, grid, and logical properties flips completely when you set dir="rtl" on the html element. One attribute, whole app mirrored.</p>
<p>Some things deliberately do not flip, and knowing the list saves debugging time. Transforms and box-shadow offsets stay physical. Icons need judgment: a "next" chevron should mirror, a company logo should not, a clock icon should not. Keyboard arrow-key handling stays physical too, because the user's physical keyboard did not mirror. For these cases a scoped [dir="rtl"] override is correct, as the exception rather than the system.</p>
<p>The hard part is not learning the properties, it is enforcement. One margin-left merged into a shared component breaks a layout that only a user in the other direction will ever see, so your LTR-speaking team never notices. Ban physical inline properties in review or with a stylelint rule (stylelint-use-logical), and treat any left or right in a diff as a question to answer, not a default to accept.</p>
<p>We build <a href="https://www.slate.co.il/">Slate</a> this way: an invoicing app for Israeli businesses, Hebrew RTL first with an English LTR fallback. The whole interface flips by switching one dir attribute per language, and there is no direction-specific stylesheet anywhere in the codebase. If your product has any chance of shipping in an RTL language, start with logical properties on day one. Retrofitting them later means touching every component you own.</p>
]]></content:encoded></item></channel></rss>