&lt;?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Articles from June 2026 on PowerShell.org - Welcome Automaters!</title><link>https://powershell.org/articles/2026/06/</link><description>Recent content in Articles from June 2026 on PowerShell.org - Welcome Automaters!</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://powershell.org/articles/2026/06/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Write for PowerShell.org</title><link>https://powershell.org/articles/2026-06-23-how-to-write-for-powershell-org/</link><guid>https://powershell.org/articles/2026-06-23-how-to-write-for-powershell-org/</guid><pubDate>Tue, 23 Jun 2026 00:00:00 +0000</pubDate><description>&lt;p&gt;There&amp;rsquo;s a thought that stops a lot of good articles: &lt;em&gt;who am I to write for
PowerShell.org?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s our brains safety net from the (highly unlikely) possibility of getting
denied. Or worse! Accepted! And now we&amp;rsquo;re forever on the hook to be an expert.
But it&amp;rsquo;s not true.&lt;/p&gt;
&lt;p&gt;You don&amp;rsquo;t need to be an &lt;strong&gt;MVP&lt;/strong&gt;. You don&amp;rsquo;t need a &lt;strong&gt;blog&lt;/strong&gt;, a &lt;strong&gt;following&lt;/strong&gt;, or
a &lt;strong&gt;clever opinion&lt;/strong&gt; about the pipeline. You need one thing you figured out that
the documentation didn&amp;rsquo;t explain well. The &lt;code&gt;-Filter&lt;/code&gt; quirk that cost you and
afternoon. The script that finally tamed a chore you&amp;rsquo;d been doing by hand for a
year. If it helped you, it&amp;rsquo;ll help someone else who&amp;rsquo;s about to lose the same
afternoon.&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>There&rsquo;s a thought that stops a lot of good articles:<em>who am I to write for
PowerShell.org?</em></p><p>It&rsquo;s our brains safety net from the (highly unlikely) possibility of getting
denied. Or worse! Accepted! And now we&rsquo;re forever on the hook to be an expert.
But it&rsquo;s not true.</p><p>You don&rsquo;t need to be an<strong>MVP</strong>. You don&rsquo;t need a<strong>blog</strong>, a<strong>following</strong>, or
a<strong>clever opinion</strong> about the pipeline. You need one thing you figured out that
the documentation didn&rsquo;t explain well. The<code>-Filter</code> quirk that cost you and
afternoon. The script that finally tamed a chore you&rsquo;d been doing by hand for a
year. If it helped you, it&rsquo;ll help someone else who&rsquo;s about to lose the same
afternoon.</p><div class="ps-alert ps-alert-important" role="note"><p class="ps-alert-title"><i class="fas fa-bullhorn" aria-hidden="true"/>Important</p><div class="ps-alert-body"><p>And here&rsquo;s the part that should lower your blood pressure:<strong>nothing you submit
goes live unreviewed</strong>.</p></div></div><p>A maintainer reads every submission, helps shape it, and
edits for clarity and formatting before it publishes. You are not flipping a
switch that broadcasts your rough draft to the world. You&rsquo;re starting a
conversation with people who want you to succeed.</p><p>So let&rsquo;s get you published. There are two ways in, so pick the one that matches
how comfortable you are with Git because both land in the same place.</p><h2 id="path-a-the-github-issue-no-git-required" class="ps-heading">Path A: The GitHub issue (no Git required)<a class="ps-heading-anchor" href="#path-a-the-github-issue-no-git-required" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h2><p>If &ldquo;fork the repo&rdquo; already made you tense up, this path is for you. You&rsquo;ll never
touch a command line.</p><p>Open the<a href="https://github.com/PowerShellOrg/PowerShellOrgWebsite/issues/new?template=guest-blog-post.yml">guest blog post
form</a>
and fill it out. The form does the structuring for you. It asks for exactly what
we need and nothing else:</p><ul><li><strong>Article title</strong> and<strong>your name</strong> as you&rsquo;d like it displayed.</li><li><strong>Submission type</strong>, and this is the part people miss: you can choose<em>&ldquo;Pitch
&ndash; I&rsquo;d like feedback before writing.&rdquo;</em> You don&rsquo;t have to show up with a
finished draft. Float the idea first, and a maintainer will tell you if it&rsquo;s a
fit and help you shape the angle before you spend the writing time.</li><li><strong>Description</strong>, one or two sentences. This becomes your SEO blurb and social
card, so it earns its keep.</li><li><strong>Category</strong> and<strong>tags</strong> (more on choosing these well below).</li><li><strong>Article content</strong>, where you paste your full Markdown if you have a draft.
Leave it blank if you&rsquo;re pitching.</li></ul><p>Submit it, and the rest happens in the issue thread. That&rsquo;s the whole path. No
branches, no merge conflicts, no Git vocabulary.</p><h2 id="path-b-the-pull-request-for-the-git-comfortable" class="ps-heading">Path B: The pull request (for the Git-comfortable)<a class="ps-heading-anchor" href="#path-b-the-pull-request-for-the-git-comfortable" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h2><p>If you already live in Git, you can submit the article directly and watch it
flow through the same review.</p><ol><li><p>Fork the repo and create a branch for your article.</p></li><li><p>Add a Markdown file in<code>content/articles/</code> using the date-slug naming
convention:</p><pre tabindex="0"><code>content/articles/YYYY-MM-DD-your-article-slug.md</code></pre></li><li><p>Start it with this front matter:</p><div class="highlight"><div style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><table style="border-spacing:0;padding:0;margin:0;border:0;"><tr><td style="vertical-align:top;padding:0;margin:0;border:0;"><pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 1</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 2</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 3</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 4</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 5</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 6</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 7</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 8</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 9</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">10</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">11</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">12</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">13</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">14</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">15</span></code></pre></td><td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"><pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-markdown" data-lang="markdown"><span style="display:flex;"><span>---</span></span><span style="display:flex;"><span>title: "Your Article Title"</span></span><span style="display:flex;"><span>description: "A 1-2 sentence summary used for SEO, social cards, and the article list."</span></span><span style="display:flex;"><span>author: Your Name</span></span><span style="display:flex;"><span>authors:</span></span><span style="display:flex;"><span><span style="color:#ff7b72">-</span> Your Name</span></span><span style="display:flex;"><span>date: "YYYY-MM-DDT00:00:00+00:00"</span></span><span style="display:flex;"><span>categories:</span></span><span style="display:flex;"><span><span style="color:#ff7b72">-</span> Category Name</span></span><span style="display:flex;"><span>tags:</span></span><span style="display:flex;"><span><span style="color:#ff7b72">-</span> tag1</span></span><span style="display:flex;"><span><span style="color:#ff7b72">-</span> tag2</span></span><span style="display:flex;"><span>---</span></span><span style="display:flex;"><span/></span><span style="display:flex;"><span>Your article in Markdown goes here.</span></span></code></pre></td></tr></table></div></div></li><li><p>Open a pull request with a short description, and we&rsquo;ll review it there.</p></li></ol><div class="ps-alert ps-alert-tip" role="note"><p class="ps-alert-title"><i class="fas fa-lightbulb" aria-hidden="true"/>Let VS Code do the boring part!</p><div class="ps-alert-body"><p>Install the<a href="https://frontmatter.codes/">Front Matter CMS</a> extension, open the
repo, and run<strong>&ldquo;Create content&rdquo;</strong> in the<code>content/articles</code> folder. It
scaffolds the<code>YYYY-MM-DD-slug.md</code> filename and every front-matter field for
you, and it gives you a form for the title, description, category, and tags
instead of a wall of YAML you can typo. It turns the single most error-prone
step into a fill-in-the-blanks. If you only adopt one tool from this article,
make it this one.</p></div></div><h2 id="best-practices-that-get-you-published-faster" class="ps-heading">Best practices that get you published faster<a class="ps-heading-anchor" href="#best-practices-that-get-you-published-faster" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h2><p>None of these are gates. They&rsquo;re the small things that mean a maintainer spends
their time on your ideas instead of your formatting.</p><ul><li><strong>Open by telling readers what they&rsquo;ll walk away with.</strong> A two-sentence intro
that promises a payoff beats a warm-up paragraph every time.</li><li><strong>Write in Markdown, and fence your code with a language hint.</strong> Use<code>```powershell</code> so your samples get syntax highlighting instead of a gray
slab.</li><li><strong>Run your code before you paste it.</strong> A snippet that works on the first try
is the difference between a reader trusting you and a reader closing the tab.</li><li><strong>Keep the title concrete.</strong> &ldquo;Speed up your console with PSReadLine predictive
IntelliSense&rdquo; tells me what I&rsquo;m getting. &ldquo;PowerShell tips&rdquo; tells me nothing.</li></ul><p>That&rsquo;s the bar. It&rsquo;s lower than the one in your head.</p><h2 id="categories-and-tags-are-how-people-find-you" class="ps-heading">Categories and tags are how people find you<a class="ps-heading-anchor" href="#categories-and-tags-are-how-people-find-you" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h2><p>It&rsquo;s tempting to treat these as paperwork and pick whatever&rsquo;s first in the list.
Don&rsquo;t. They&rsquo;re the difference between an article that&rsquo;s read once and one that
keeps getting found.</p><p>Pick the single<strong>category</strong> that fits best. The current set:</p><blockquote><p>Announcements - Books - DevOps - Events - Graph - In Case You Missed It -
News - PowerShell Summit - PowerShell for Admins - PowerShell for Developers -
Scripting Games - Tips and Tricks - Tools - Training - Tutorials</p></blockquote><p>Category is the big bucket. It&rsquo;s how someone browsing &ldquo;PowerShell for Admins&rdquo;
stumbles onto your piece months from now.<strong>Tags</strong> are the specific hooks: the
cmdlets, modules, and concepts your article actually touches (<code>psreadline</code>,<code>regex</code>,<code>azure</code>,<code>pester</code>). Three to five honest, specific tags beat a dozen
vague ones. Tag what&rsquo;s really in the article, not every PowerShell word you can
think of, and your post surfaces next to its actual neighbors.</p><h2 id="claim-your-author-page" class="ps-heading">Claim your author page<a class="ps-heading-anchor" href="#claim-your-author-page" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h2><p>Once you&rsquo;re credited on an article, you can give yourself a real author page at<code>/authors/&lt;your-name&gt;/</code>: an avatar, a tagline, a short bio, and links back to
your own site and socials. Every article you write points back to it. It&rsquo;s a
small, durable corner of the PowerShell community that&rsquo;s<em>yours</em>, and it builds
with each post.</p><p>It&rsquo;s opt-in. Skip it and your byline still works exactly as before. But it takes
about five minutes, so why leave it on the table? You can see an example of mine
at the bottom.</p><p>Your profile is a single file at<code>content/authors/&lt;slug&gt;/_index.md</code>. The one
rule that trips people up: the<code>&lt;slug&gt;</code> has to match your byline exactly
(lowercased, spaces to hyphens), or the page attaches to nothing.</p><p>So let the helper script handle it:</p><div class="code-terminal ps-terminal rounded-xl overflow-hidden shadow-xl my-6"><div class="flex items-center px-4 py-3 border-b border-gray-700"><div class="flex space-x-2 mr-4"><div class="w-3 h-3 rounded-full bg-red-500"/><div class="w-3 h-3 rounded-full bg-yellow-500"/><div class="w-3 h-3 rounded-full bg-green-500"/></div><span class="text-gray-400 text-sm font-mono">PowerShell</span></div><pre class="text-sm leading-relaxed"><code class="language-powershell">./tools/new-author.ps1 "Jane Doe"</code></pre></div><p>That scaffolds<code>content/authors/jane-doe/_index.md</code> with every field commented.
Fill in what you want, delete the rest:</p><div class="highlight"><div style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><table style="border-spacing:0;padding:0;margin:0;border:0;"><tr><td style="vertical-align:top;padding:0;margin:0;border:0;"><pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 1</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 2</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 3</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 4</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 5</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 6</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 7</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 8</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679"> 9</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">10</span><span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#737679">11</span></code></pre></td><td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"><pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-yaml" data-lang="yaml"><span style="display:flex;"><span><span style="color:#ff7b72">---</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#7ee787">title</span>:<span style="color:#6e7681"/><span style="color:#a5d6ff">"Jane Doe"</span><span style="color:#6e7681"/><span style="color:#8b949e;font-style:italic"># required -- keep this as your byline name</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#7ee787">preferred_name</span>:<span style="color:#6e7681"/><span style="color:#a5d6ff">"Jane"</span><span style="color:#6e7681"/><span style="color:#8b949e;font-style:italic"># optional -- changes only how your name displays</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#7ee787">tagline</span>:<span style="color:#6e7681"/><span style="color:#a5d6ff">"Cloud automation, mostly."</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#7ee787">gravatar_hash</span>:<span style="color:#6e7681"/><span style="color:#a5d6ff">"..."</span><span style="color:#6e7681"/><span style="color:#8b949e;font-style:italic"># MD5 of your lowercased email -- keeps your email private</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#7ee787">github</span>:<span style="color:#6e7681"/><span style="color:#a5d6ff">"https://github.com/janedoe"</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#7ee787">website</span>:<span style="color:#6e7681"/><span style="color:#a5d6ff">"https://janedoe.dev"</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#8b949e;font-style:italic"># twitter / mastodon / linkedin / bluesky also supported</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#ff7b72">---</span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/></span></span><span style="display:flex;"><span><span style="color:#6e7681"/><span style="color:#a5d6ff">Your bio in Markdown goes here.</span><span style="color:#6e7681"/></span></span></code></pre></td></tr></table></div></div><p>One thoughtful detail worth calling out: you can set an avatar<strong>without</strong>
putting your email address in a public repo. Store the MD5 hash of your
lowercased email as<code>gravatar_hash</code>, and Gravatar serves your picture while your
email stays private:</p><div class="code-terminal ps-terminal rounded-xl overflow-hidden shadow-xl my-6"><div class="flex items-center px-4 py-3 border-b border-gray-700"><div class="flex space-x-2 mr-4"><div class="w-3 h-3 rounded-full bg-red-500"/><div class="w-3 h-3 rounded-full bg-yellow-500"/><div class="w-3 h-3 rounded-full bg-green-500"/></div><span class="text-gray-400 text-sm font-mono">PowerShell</span></div><pre class="text-sm leading-relaxed"><code class="language-powershell">$email = "jane@example.com"
[System.BitConverter]::ToString(
[System.Security.Cryptography.MD5]::Create().ComputeHash(
[System.Text.Encoding]::UTF8.GetBytes($email.Trim().ToLowerInvariant())
)
).Replace("-", "").ToLowerInvariant()</code></pre></div><p>And if your name ever changes,<code>./tools/new-author.ps1 "Old Name" -To "New Name"</code>
rewrites your byline across every article and adds a redirect so your old
profile URL keeps working. Open a PR with the result.</p><h2 id="your-turn" class="ps-heading">Your turn<a class="ps-heading-anchor" href="#your-turn" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h2><p>The whole point of PowerShell.org is that it&rsquo;s built by the people who use
PowerShell, and that includes you. You don&rsquo;t have to be sure it&rsquo;s good enough.
That&rsquo;s literally what the review is for. Pitch the idea, paste the draft, or
send the PR, and you won&rsquo;t be doing it alone. There&rsquo;s a community on the other
side of that submit button that wants to help you get it across the line.</p><p><a href="https://github.com/PowerShellOrg/PowerShellOrgWebsite/issues/new?template=guest-blog-post.yml">Start here.</a></p>
]]></content:encoded></item></channel></rss>