<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>publishers &amp;mdash; Micro Matt</title>
    <link>https://micro.baer.works/tag:publishers</link>
    <description>Micro thoughts and mini posts.</description>
    <pubDate>Wed, 29 Apr 2026 00:31:40 +0000</pubDate>
    <image>
      <url>https://i.snap.as/4R3vdrBj.png</url>
      <title>publishers &amp;mdash; Micro Matt</title>
      <link>https://micro.baer.works/tag:publishers</link>
    </image>
    <item>
      <title>Spending time designing an entirely new UI for Write.as / #WriteFreely today,...</title>
      <link>https://micro.baer.works/spending-time-designing-an-entirely-new-ui-for-write-as-writefreely-today?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[Spending time designing an entirely new UI for Write.as / #WriteFreely today, tailored toward power users. After breaking down jobs-to-be-done and building up an interface from scratch, I’ve arrived at… essentially, WordPress or Ghost or any other CMS. So, how do I plan to make this different?&#xA;&#xA;First: two distinct interfaces, “basic” and “advanced.” This CMS-ish UI would be the “advanced” one, activated only when you indicate you need it, such as when starting a publication rather than a personal blog. By default, users would continue getting a minimalist interface that is centered around writing and distribution, rather than advanced content creation and management. My idea here is that we hopefully don’t lose the plot, and Write.as remains useful as a personal writing / blogging platform. But if I’m rethinking things, I’ll probably want to revamp the “basic” UI users will see by default…&#xA;&#xA;#design #publishers&#xA;&#xA;Thoughts? a href=&#34;https://remark.as/p/micro.baer.works/spending-time-designing-an-entirely-new-ui-for-write-as-writefreely-today&#34;Discuss.../a]]&gt;</description>
      <content:encoded><![CDATA[<p>Spending time designing an entirely new UI for Write.as / <a href="https://micro.baer.works/tag:WriteFreely" class="hashtag"><span>#</span><span class="p-category">WriteFreely</span></a> today, tailored toward power users. After breaking down jobs-to-be-done and building up an interface from scratch, I’ve arrived at… essentially, WordPress or Ghost or any other CMS. So, how do I plan to make this different?</p>

<p>First: two distinct interfaces, “basic” and “advanced.” This CMS-ish UI would be the “advanced” one, activated only when you indicate you need it, such as when starting a <em>publication</em> rather than a <em>personal blog</em>. By default, users would continue getting a minimalist interface that is centered around <strong>writing and distribution</strong>, rather than advanced content creation and management. My idea here is that we hopefully don’t lose the plot, and Write.as remains useful as a personal writing / blogging platform. But if I’m rethinking things, I’ll probably want to revamp the “basic” UI users will see by default…</p>

<p><a href="https://micro.baer.works/tag:design" class="hashtag"><span>#</span><span class="p-category">design</span></a> <a href="https://micro.baer.works/tag:publishers" class="hashtag"><span>#</span><span class="p-category">publishers</span></a></p>

<p><em>Thoughts? <a href="https://remark.as/p/micro.baer.works/spending-time-designing-an-entirely-new-ui-for-write-as-writefreely-today">Discuss...</a></em></p>
]]></content:encoded>
      <guid>https://micro.baer.works/spending-time-designing-an-entirely-new-ui-for-write-as-writefreely-today</guid>
      <pubDate>Tue, 20 Apr 2021 20:13:52 +0000</pubDate>
    </item>
  </channel>
</rss>