Some cleanup: Readwise is gone. Supporting services are now grouped at the bottom. Corrected a few typos. I made some visual adjustments to make things a little bit cleaner and easier to visualize, especially for website miniatures. I renamed the diagram to reflect the notion of an ecosystem instead of a workflow.

Many additions: each enhanced service with generative AI features is marked as such with a little brain icon. That’s the case for Inoreader, Craft and Grammarly. All my Micro.blog-hosted websites are now indicated. Since adhering to POSSE principles, I added the Fediverse and Bluesky icons and drew the cross-posting arrow lines to them.

A high-resolution version of this diagram is available here.

What is POSSE

The POSSE principle stands for “Publish (on your) Own Site, Syndicate Elsewhere.” It is a content distribution strategy often recommended for writers, bloggers, and publishers. The primary idea is to first publish your content on a platform you control, such as your personal website or blog, and then syndicate or share that content on other platforms like social media, Medium, or different online communities.

Here are some key points about the POSSE principle:

1. Ownership and Control: By publishing on your own site first, you maintain control over your content and ensure it exists in a space you own. This helps protect your work from the risks of platform changes or shutdowns.
2. Centralized Content: Your website becomes the central hub where all your content is stored and can be accessed by your audience.
3. Traffic and SEO: By driving traffic to your own site, you can improve your website’s SEO, increase your audience, and potentially monetize traffic through ads, affiliate links, or direct sales.
4. Syndication: After publishing on your own site, you can share your content with a wider audience by syndicating it to other platforms. This strategy helps reach readers who might not visit your site directly.
5. Preservation: Content publishing on third-party platforms may be subject to their rules and policies. Publishing first on your own site ensures your content is preserved and remains unchanged regardless of policy changes elsewhere.

The POSSE principle is popular among creators who value long-term control over their work and want to build a sustainable and direct relationship with their audience.

It’s been quite a long time since my previous content creator workflow update, more than a year actually, back in November 2023. With 2024 coming to an end, it’s time for a detailed update. First, consider the following overall diagram, then continue reading.

Outlining purposes: Zavala, a free open-source outliner, is nearly perfect for outlining YouTube video production. I don’t do detailed scripting before recording videos, but I like to create the outline. I was using Zavala until the release of Mindnote Next, but this might change. Mindnote is a superbly designed mind-mapping application that also supports the creation of outlines, which are more beautiful than those created in Zavala. One of Zavala’s strengths is that it is free but also easily exports a document into Craft via a simple drag-and-drop. I will see how it goes in 2025.

Presentation purposes: iA Presenter offers a unique approach to presentation creation. I rarely use presentation software outside of my day job, but when I do, it supports me while recording a YouTube video. A recent update to iA Presenter introduced an online presentation sharing feature that works really well and is beautifully implemented. For 2025, I’ll try to take advantage of this. iA Presenter is such a unique take on a very old software category I must keep trying to find a use for it.

Website site analytics: Tinylytics joins Plausible in my toolset. I was happy with Plausible until this year, but the developer of Tinylytics is also the developer of Scribble.pages, a blog hosting service I really like. I decided to subscribe to Tinylytics as a support gesture for all his hard work building simple yet valuable web services.

Web bookmark management: I’m happy to introduce Anybox. Sure, it’s not raindrop.io, but it’s a great native Mac app, also available on the iPad and the iPhone. That’s all I need. My collection has less than four hundred bookmarks, all organized using folders and tags. It’s nothing fancy but practical.

RSS feeds publishing: FeedPress is a simple yet effective way for adding a unified feed in front of all my different websites (Ghost, Micro.blog, Scribbles, Medium). Also, I offer an RSS megafeed that encompasses all my other individual RSS feeds, which can be found here: https://feeds.numericcitizen.me. The added value of using FeedPress is to enable RSS feed analytics, which other publishing platforms like Micro.blog, for example, won’t provide.

Podcasting purposes: Micro.blog is now my podcast hosting service of choice. The feature is built-in and very simple to configure and use. There are two ways for me to share a podcast episode: either use the narrated post feature of Micro.blog or use a traditional workflow, build an audio file using Screenflow, post-process it in Adobe Podcast, and convert it from WAV to MP3 using Permute before uploading the audio file to Micro.blog.

Files-hosting and cloud storage service: Dropshare will upload a file to Backblaze cloud storage, and Short.io will shorten the resulting URL. All my files are shared under the following domain name: https://go.numericcitizen.me, using my custom branding. Here is an example: https://go.numericcitizen.me/PLx2st2Y. This workflow was implemented in 2024 and works well. The only thing is that I don’t use it often enough, and it can compete with CleanShot Cloud, which I use more often when sharing screenshots or short video clips. Those media files are using the following URL: cloud.numericcitizen.me.

Specialized blog hosting: Micro.blog. I created a metablog on Micro.blog using one of the five blogs in my Micro.blog subscription. As you can conclude, I’m increasing my foothold on Micro.blog because it is cheap, effective and unique on the market.

Read-later service: I removed Omnivore because the service is no longer being developed, and I decided to focus on Inoreader instead. It’s not a perfect solution, but it is a cheaper one. I still depend on Readwise to sync text highlights from Inoreader.

Another blog hosting service, Scribbles, was. I’m using it to host short-form posts called Blips or longer ones using the /Now spirit under the following URL: https://blips.numericctizen.me.

One-page website hosting: Numeric Citizen Hub on Micro.blog has replaced my Linktr.ee page. I’m again focusing on Micro.blog for many of my online publishing needs while saving some money along the way. This one-page website is for hosting my visitor card, sort of. Micro.blog offers support for one-page websites, so I’m taking advantage of this.

When saving bookmarks on Miicro.blog, I take advantage of text highlights while reading the article that Micro.blog is keeping from the bookmark. Text highlights are synced to Readwise, too.

Website for my supporters: For prople who wants to show their support for my work, I have built a Ko-fi page that can be reached here: https://ko-fi.com/numericcitizen. It was created for the one dollars a month club initiative from Manuel Moreale. I’m one of his supporter.

Document writing and editing needs: Craft & Ulysses. Both apps are still at the center of my publishing needs. More than ever, I depend on Craft to gather my thoughts and notes, research, and write. Ultimately, content is exported into Ulysses for publishing to either Ghost, Micro.blog or, more recently, Medium.

Behind-the-scenes newcomers: Apple Freeform plays a more prominent role in helping me create diagrams. Freeform is joining Mindnote and Keynote for creating visual content when needed.

These are gone: All my domain name registrations are now entirely moved to Cloudflare, and gone is GoDaddy. Omnivore is being phased out by its developers; it’s gone, too.

Until next time

The continuous evolution of toolsets reflects the dynamic nature of technology and the diverse needs of users. No toolset is flawless, and each comes with its own set of strengths and weaknesses. This notion is evident in your evolving content creator workflow, where you adapt and integrate new tools, illustrating digital tools’ perpetual state of change. For 2025, I don’t expect too much change in my workflows. Don’t forget to visit my complete content creator toolset if you are curious about the individual tools that I’m using.

This document is also available as a Craft shared document.

For those who didn’t know, I maintain a description of all the apps and services that I use on “My Complete Content Creator Toolset And Some More” page.

I spent some time this morning to update my content creator toolset mini website. It was long overdue.

For long-time readers and followers, they know that I own a few websites or publishing places, but a reminder is always welcomed. With so many places to publish to, you might wonder why not use only one big website. Well, I’m glad you asked. You’ll find most of the answers in the following diagram.

As you can see, each place fills a different role. Think of them as publishing channels. I prefer to have many focused places with content directed to a specific crowd over having a single channel full of seemingly unrelated posts. But there is more to it: I love using different tools and services. Each has its strengths and weaknesses and a specific set of features. That’s what drives me the most to use different publishing platforms.

Circumventing Ghost’s limited posts management capabilities.

I recently decided to spend some time editing past articles published on my Numeric Citizen Space website. I first thought that by going to my Ghost admin page, I could quickly browse past published articles by month. I couldn’t be more wrong. In fact, Ghost offers limited post management capabilities, thanks to its limited content browsing capabilities. I cannot go back, say, list articles published early in 2023. I can sort by ascending or descending order, but from there, I have to scroll through a long, dynamically created list of posts. It’s not very effective for a website with 600-plus posts. I had to find a different option to locate a post for an update. This is where Ghost’s content APIs come into play.

The following API request doesn’t do the job (API key voluntarily removed!):

curl -H "Accept-Version: v5.0" "https://numeric-citizen-introspection.ghost.io/ghost/api/content/posts/?key={APIkeygoeshere}&fields=title,url,published_at,updated_at&filter=published_at:>2024-01-01%2Bpublished_at:<2024-02-01" | json_pp

Let me explain what is this API request.

First, I’m going to the request using the macOS command line, hence the curl command. Next, the whole query follows in quotes. I query the content/posts API endpoint. Next, I pass my API key, followed by a field selection (&fields), and next with the filter using the published date between two dates. Finally, I pipe the results in the pretty JSON print macro (is this a macro?) so the output looks like this:

jfm@CraftingMAChine ~ % curl -H "Accept-Version: v5.0" "https://numeric-citizen-introspection.ghost.io/ghost/api/content/posts/?key={API-key-goes-here}&fields=title,id,url,published_at,updated_at&filter=published_at:>2024-01-01%2Bpublished_at:<2024-02-01" | json_pp
	{
	   "meta" : {
	      "pagination" : {
	         "limit" : 15,
	         "next" : null,
	         "page" : 1,
	         "pages" : 1,
	         "prev" : null,
	         "total" : 9
	      }
	   },
	   "posts" : [
	      {
	         "id" : "65b6a09840566000015b0d37",
	         "published_at" : "2024-01-28T13:50:19.000-05:00",
	         "title" : "My Weekly Creative Summary for the Week of 2024/03",
	         "updated_at" : "2024-01-28T13:50:19.000-05:00",
	         "url" : "https://numericcitizen.me/my-weekly-creative-summary-for-the-week-of-2024-03/"
	      },
	      {
	         "id" : "65b6540640566000015b0cf7",
	         "published_at" : "2024-01-28T08:23:26.000-05:00",
	         "title" : "Special Message to Paying Subscribers",
	         "updated_at" : "2024-01-28T08:23:26.000-05:00",
	         "url" : "https://numericcitizen.me/special-message-to-paying-subscribers/"
	      },
	      {
	         "id" : "65b16e25bc7fde0001314ccb",
	         "published_at" : "2024-01-24T15:09:24.000-05:00",
	         "title" : "The Mac Turns 40",
	         "updated_at" : "2024-01-24T15:09:24.000-05:00",
	         "url" : "https://numericcitizen.me/the-mac-turns-40/"
	      },
	      {
	         "id" : "65ad35418532ae000169ddd2",
	         "published_at" : "2024-01-21T10:22:33.000-05:00",
	         "title" : "My Weekly Creative Summary for the Week 2024/02",
	         "updated_at" : "2024-01-21T10:22:33.000-05:00",
	         "url" : "https://numericcitizen.me/my-weekly-creative-summary-for-the-week-2024-02/"
	      },
	   ]
	}

Next, I copy the post ID of one article and paste it my browser for edition using this special URL:

https://numeric-citizen-introspection.ghost.io/ghost/#/editor/post/652e6eedb8a2650001ad9c5b

This URL brings me directly into the Ghost editor, provided that i was already authenticated with my account. That’s pretty much it. It could be much simpler. For this, I miss WordPress.

You can find the Ghost API document right here.

My creative workflow as of 2023-11. You can download an higher resolution here.

This 2023-11 version has a few changes and a cleaner and more focused workflow. Before going into specific details, I wanted to remind readers that I support the " POSSE " idea. You can read one post about it here. This workflow presented reflects this. As a reminder, here is one definition of the POSSE principle according to ChatGPT:

“POSSE” is an acronym that stands for “Publish (on your) Own Site, Syndicate Elsewhere.” It’s a content publishing model that first encourages publishing content on your own website, and then syndicating (or sharing) that content on other platforms or websites. This approach is often recommended in digital marketing and personal branding strategies, as it allows individuals to maintain control over their original content while still benefiting from the audience and engagement found on larger, established platforms. The POSSE model is particularly relevant in the context of blogging, social media, and online content creation.

Welcome AI, welcome ChatGPT, Dall-E, Midjourney

AI is making an official entry in my creative workflow. I wrote a long piece stating my guidelines for using AI in my creative work. You should read those and maybe get some inspiration out of them. The header image of this article was generated using Dall-E.

A new setup to share files easily

Dropshare coupled with Short.io enables me to share files like screenshots or other things. The setup was documented in detail in a previous article on this meta blog. Behind the scene, Dropshare is configured to use Backblaze to store files in a S3 bucket.

Bye bye to my Digital Garden

I came to the conclusion that a digital garden isn’t something for me. I decided to move some portions into my official about page. You can still access the remains of the garden, here.

A fun experience with Tinylytics

I’ve been using Plausible for my analytics needs but a cool guy (the same who’s also working with Manton Reece on Micro.blog hosting service, developed a lightweight version which I decided to support.

The Tinylytics dashboard

Google Sheets is out too

I was using Google Sheets to save links to every post on Micro.blog via an IFTTT automation. I no longer feel the need to key this in place.

Brief

Brief is now part of my workflow because they also took over Mailbrew, both are forming a powerful content consumption enabler duo. Some of my Mailbrew newsletters contain Brief as a source for news, which is heavily using AI for summarization.

This article posted back in 2022, was a glimpse at a great moment of confusion. Following the publication of “Things That Don’t Stick With Me”, the next logical thing to do now is to talk about my seemingly permanent state of confusion with my choices of many digital tools.

In short, the problem is that, in many cases, I use different apps to do the same thing. The worst case to come to my mind is RSS feeds readers. After many years with News Explorer, I tried NetNewsWire, Reeder and Inoreader. Oh, I forgot about ReadKit too. The light at the end of the tunnel is in sight because News Explorer is now out. After discovering and experimenting with Inoreader, I concluded that News Explorer no longer fit my needs. One of them being the text-highlighting capability. That is one less app to use or consider. NetNewsWire simplicity makes the app attractive. Reeder’s design is also attractive. I do use Inoreader with Inoreader web service. I’m not decided yet on the next steps: which one should I keep?

Twitter vs Tweetbot was another example. When I was on Twitter, I constantly switched between those two. The funny thing is that for those still on Twitter, third-party apps for Twitter are all dead. This would have fixed my issue! Now, with Mastodon, it’s worst because of the plethora of available apps. There are too many to list here and the list keeps expanding. Thankfully, I don’t use Mastodon much, but if I did, well, you know the drill by now, right?

On Micro.blog, same issue. I’m constantly moving between the original Micro.blog app and Gluon. Both are great but latter is a bit more complete.

Box and Dropbox used to be examples of my indecision before I went all in with iCloud Drive a few years ago. I still use Google’s Drive for storing Google’s Sheets updated via an IFTTT automation. That, I’m no longer sure about its usefulness.

Clipboard managers were another source of conflicting views. There were three apps in that space: Copied, Pastebot and Unclutter. I’ve settled on the latter because it is so much more than a clipboard manager. Yet, it took me way too long before deciding which one to keep. I don’t use a clipboard manager on the iPhone anymore.

• Here’s another one: Apple’s Notes, Notion or Craft. I use Craft 95% of the time, Notes 4% of the time, and Notion 1% for the rest. Oh, I forgot to mention Tot, a nifty tech editor! What is preventing me from settling on Craft for everything? I use Notion for storing information about a sideline project because Craft is not as good for that type of information.
• For my photo processing and retouching needs: Acorn 7, Pixelmator Pro, Photomator, Adobe Lightroom CC and Lightroom Classic are installed somewhere on my devices. I should probably drop Adobe Suite, but It would be a mess to retrieve all my photos backed up to the Adobe Cloud. I’m being lazy here. I’m really enjoying Photomator on my iPad and iPhone. This application is better designed than Apple’s Photos for photo editing. Photomator is coming soon to the Mac, too, apparently, to make matters worst, I guess. I’m on the waiting list for a TestFlight invite.
• As a computer performance enthusiast, I use utilities like Sensei, iStats Menu, iStatistica Pro, and the open-source project “Stats” available on GitHub. I use iStats Menu on my Mac mini, Stats on my Mac Pro (used for my SDDCbox project) and iStatistica Pro on my MacBook Air. Sensei should probably be dropped.

• Reddit, Apollo, Slide and Comet. There are all Reddit clients. They all offer nice and different things when consuming or interacting with Reddit content. For example, Slide comes with the best widgets, but is lacking active development and isn’t the best at browsing content. Comet isn’t been updated in two years. Apollo runs on Apple Silicon Macs but suffers from some display bugs.
• Password Managers, another story of indecision and laziness: 1Password and Apple’s Password Keychain. I should move from 1Password to Apple’s solution once and for all. Maybe if Apple had a discreet password manager? I’m undecided.
• Tasks managers represent another case of spreading myself all over the place. For personal to-dos, I depend on Apple’s Reminders. For my creative workflow, I depend on Things 3 but there was a time last year when I tried using Craft as a to-do manager. It didn’t go well, and I decided to bring back Things 3 in my workflow. I documented my change of heart in this video. One comforting thought, I know that I’m not alone in my quest for the best tools. This documented case with Things 3 and OmniFocus is a good example.

There is hope

I might sound like a tormented person, but I’m not. I would say that I’m not as focused as I should be. But there is hope because I do make decisions from time to time when things become clear or obvious. Let’s see a few examples.

• On the publishing platforms front, things are improving. Thankfully, this year, I’m focusing. There use to be WordPress, Micro.blog, Substack, Ghost, Blot and Write.as. WordPress is out. Substack is out. Blot is out. I’m down to two publishing platforms: Ghost and Micro.blog. That’s it. Sure, i cross-post some content to Mastodon, Bluesky and Flipboard. But that doesn’t count.
• On the photography side, at some point, there was 500px, Smugmug, Unsplash, Glass, Exposure. 500px is out. I decided to move out of Smugmug by the end of my subscription (next year), so that I can focus on Glass and Exposure.

• I recently dropped Pocket, Matter and Readwise Reader. So, you see, there is hope!
• For bookmarking, at some point, I was using Apple’s Safari Reading List, Pocket, Craft bookmarks, Apple’s Quick Notes, and Mailbrew saved items. I dropped all of these in the last year to focus on Anybox. I couldn’t be happier. Oh, I sometimes use Micro.blog bookmarking feature to archive articles than I can highlight then create a linkpost using these highlights.
• Ever since I got my M1-based Mac mini, I bought a M1 MacBook Air. I constantly use both of them. One thing that I like to do is to use on app on one Mac and another competitive app on the other Mac. For example, on my MacBook Air, I use “Stats” and on my Mac mini, I use iStats Menu.
• iPad Pro vs MacBook Air: because reasons. I love both but in different usage scenarios. I’m fortunate enough to have both.
• My reading workflow was in a state of flux: https://numericcitizen.micro.blog/2022/05/07/my-reading-workflow.html. But, thanks to my decisions to drop traditional read-later services like Matter or Pocket, I’m more focused now in that area.

I should probably update this article occasionally because my digital toolkit is constantly evolving. You probably should keep an eye on my documented toolset that I keep up to date.

This article was previously published on Numeric Citizen Space:

Why It’s So Hard to Make Up My Mind About Digital Tools?

Time for another workflow update (the previous update can be found here). This update probably contains the most profound changes in a long time. My journey with WordPress as a CMS (content management platform) has ended. It started in 2015, after closing my indie developer blog hosted on Google’s Blogger. There are a lot of moving parts. The dust is starting to settle a bit now. Let’s dig in.

As for the diagram, I wanted to make it more focused on digital tools and how they relate to each other, so I removed the devices representation as well as icons of apps that are better documented in my toolset (see down below). I kept the essential making the foundation of my workflow.

Bye Bye WordPress.com

Following the completion of my migration from WordPress to Ghost, I think it’s the right time for an update to my content creator workflow. This WordPress migration forced a reconsideration of many tools that I use to create. This post will highlight most of these changes.

Bye bye Twitter

Up until a few months ago, Twitter was really at the center of my online presence. It’s no longer the case. It’s (nearly) nowhere to be seen (except for searches through Inoreader). With Twitter out from my digital landscape, the following are no longer needed.

• Birdbrain, an iPhone app that allowed me to track who was following or unfollowing me.
• Buffer, a scheduling service to post content on Twitter. It was used to repost past content to stimulate exposure and traction. If I consider the price of the service, I don’t think the return on investment was worth it.
• My @Apple_Observer Twitter account is in read-only mode. My @numericcitizen Twitter account is also in read-only mode but is used in conjunction with Inoreader for searching and scrapping Twitter for specific content using specific keywords.

Changing reading habits

My reading habits are evolving too. Reading is the fuel behind my creative activities.

• Speaking of Inoreader earlier, this content consumption service appeared on my radar and was later adopted. It is replacing News Explorer, an RSS reader. Inoreader allows for much more than reading RSS feeds. Reeder (read my review here) and ReadKit are two RSS readers that I use alternatively to consume my content on Inoreader simply because these two apps offer a native experience on the Mac that Inoreader currently doesn’t offer. I’m still undecided as to which of the two apps I’m going to keep. That’s for another content creator workflow update.
• Gone is Matter and Readwise Reader. Since I’m mostly reading content through RSS feeds, these two services are no longer needed. I keep Readwise highlights subscription, though. It serves as an archiving service of some sort. All text annotations by Inoreader are saved to Readwise.

A more focused publication channel

• Content publishing services were also reconsidered. Medium is out. Spending time there’s no longer viable as readership is stagnant at best. Tumblr is out too. I was cross-posting content there, but it is no longer viable too. Even if it was an automated process, thanks to Micro.blog cross-posting ability and to IFTTT, it doesn’t make sense to maintain Tumblr as this platform is a walking dead.
• Back to the WordPress migration, for obvious reasons, all my WordPress plugins, like Yoast, are no longer needed. Many others were dropped, too, saving me quite a lot on recurring expenses. Yoast was useful when writing a blog post to optimize SEO content but added some friction and probably didn’t make a big difference for my SEO optimization aspirations.

Is my Craft usage fading out?

• My Craft usage is still important, but a few use cases were dropped. I don’t use daily notes to manage my things to do (as explained in this video “Why I’m No Longer Using Craft Daily Notes”). I went back to Things 3 for this. The other use case that was removed from Craft is bookmarks management, as explained in detail in this video “Why I’m Moving My Bookmarks Out of Craft”. Now, I’m depending on the excellent Anybox bookmarks manager, as I explained in this article: “Anybox – My Experience with a Bookmarks Manager”. Switching to Anybox also means I dropped Raindrop.io too. Even as a free service, it was redundant to keep.

Finally, since my tool set is always changing, I created and shared a Craft document where you can have a complete view of the apps and services I depend on to create things and put them out there on the net. You’ll also see tools that are under consideration and the tools that I dropped in the past. Link: https://world.numericcitizen.io/meta-toolset.

The time has come for the return of a more open web. I’m embracing this movement by joining platforms or services that are built on open standards and promoting the open web in general as a byproduct.

Write.as is an instantiation version of the WriteFreely writing platform, available as an open-source project. Think of WriteFreely as the open-source version of WordPress. Anyone can get the source and install their own instance.

In May 2022, I took advantage of five-year special pricing to subscribe to the Write.as platform. Without exactly knowing what would be my use case for it, I decided to support the platform, just like I’ve been supporting Micro.blog since 2018. After a while, I discovered the many facets of this writing ecosystem and found it to be a bit confusing. In this article, I explain all the parts of the open and dedicated blogging platform.

First, let’s see what ChatGPT says about Write.as.

Aaron Taylor is the founder & CEO of Cosmic.org and a team of remote employees who work on the Write.as and Remark.as platforms. He is passionate about creating secure, anonymous spaces where people can express themselves without judgement or censorship. He has worked to create tools and features that make anonymous publishing easier and more secure for users. He is also the creator of the Remark.as platform, which gives users more control over how and when they share their thoughts.

Write.as is a project of a small team led by the founder & CEO, Aaron Taylor, at Cosmic.org. They are a remote team based all over the world, from Portland to Berlin to Mexico City.

Write.as is a platform designed to help people express themselves freely and anonymously. It provides a space for everyone to post their thoughts without worry of judgement or censorship. All posts are public and open to comments, however, the identities of the posters can remain anonymous. The project offers a suite of applications and services to make anonymous publishing easier, more secure, and more secure for users. It also provides a way for people to follow topics, publications, or users, engaging in thoughtful dialogue and idea exchange.

Remark.as is a project that is a part of the Write.as platform. It is designed to help users to have conversations with each other in an anonymous, secure, and censorship-free environment. Remark.as has features like tagging topics and publications, creating polls, and engaging in private forums. It also gives users more control over how and when they share their thoughts. Remark.as also provides users with the ability to create polls, surveys, and other interactive features to encourage public participation.

All in all, Write.as and Remark.as are projects by Aaron Taylor and the team at Cosmic.org that provide users with an anonymous, censorship-free space in which to express themselves freely and engage with others. They are both designed to make anonymous publishing easier, more secure, and to give users more control over how and when they share their thoughts.

Write.as is a simple, privacy-focused writing platform. It allows users to create and publish anonymous blog posts, journal entries, and other types of writing without the need for an account or personal information. The platform also includes a built-in editor and the ability to customize the appearance of your writing with different fonts and themes. Additionally, Write.as supports markdown formatting and has a feature called “focuses” which allows users to group related posts together. The platform is designed for those who value privacy and simplicity.

More seriously, here’s a brief description of each component, starting with an overview.

An Overview of the WriteFreely Ecosystem

The following diagram shows all the parts making up the Write.as service, which is part of the WriteFreely ecosystem.

• The Write.as service is where all the writing experience happens. Since this article isn’t a review, suffices it to say the editor offers a minimalistic and distraction-free environment. Write.as supports adding tags to any blog posts. Cross-posting content in Write.as is available for other platforms like Tumblr, Ghost and Twitter. I connected my account to Ghost but rarely cross-post over there. It’s nice to have, though.
• The writer can attach photos at the end of each post by dragging them on the bottom bar. Photos attachments go to the “snap.as” minimalistic photo sharing add-on, tied to Write.as. All photo attachments are shown in one place, on snap.as. Photo galleries are available, albeit with a one-time fee of 10$. Some features are marked as coming soon, but I suspect they are long in coming. I’m unsure if I would invest in this as I prefer dedicated services like Glass.
• Submit.as is another add-on to Write.as. As the name suggests, it is a way for an author to accept submissions from other writers. No registration is required from the submitter, helping a frictionless experience. This service is not cheap and comes with a 12$ per month minimal fee. It’s not cheap and I don’t know why. Again, integration with other platforms is marked as coming.
• Remark.as is yet another add-on closely tied to Write.as and offers to comment to any of the writer’s blog posts. Commenting is enabled on a per-post basis by adding a special <—discuss—> line anywhere within the post.
• Read.write.as is like a content feed coming from other writers. Content published on Write.as gets published on this feed. It comes from the hosted version of Write.as. According to this website, content is cross-posted to an RSS feed, Mastodon and Twitter, but I fear this has been abandoned as the content is somewhat old.
• The Mail add-on is where you’ll receive comments from other writers. Those comments are grouped in one place and are public.
• Café is a place for discussion, but frankly, I don’t know how posts get promoted there. Those discussions are conversations happening on the Read.write.as section.
• Other add-ons like a post signature is available for a monthly 10$ addition (ouch) and eBooks export is also available for another monthly 10$ (ouch).

Still with me? I know, it’s not simple. Write.as certainly feels like a bunch of add-ons taped together.

Some remarks about the whole thing

• The Write.as experience is minimalistic and needs some polishing. I didn’t see improvements since I’m subscribing to the platform. This annoys me.
• Overall, the Write.as ecosystem feels minimalistic and unfinished. I don’t expect many improvements to come to the platform. Yet, Matt, the founder of Write.as, is active on discuss.write.as discussion forum, so it’s a good sign.
• There’s a Mac app for the Write.freely ecosystem, which should support Write.as but it has been in beta for more than a year. iOS and iPadOS are also available. All apps are available here. I didn’t test these, preferring the web experience.
• All these services are part of a suite called the Musing Studio. It’s more of a branding thing. The site hasn’t been updated for a while.

With this article, I hope I shed some light on this open-source project dedicated to writers and bloggers. Overall, I like Write.as, even with some rough edges or unfinished integration. If I failed to explain something correctly, let me know in the comments!

This article has been published on https://write.as/numericcitizen/ (here).

It’s been a while since I shared details about my blogger creator workflow. From now on, I’m renaming it to “my content creator workflow” as it better reflects the coverage of my work. As you might expect, a lot has changed in a year. Without further due, let’s begin.

• Cleanshot Cloud has been added to my toolset following an update to the Cleanshot application. I think it’s one of the best Mac utilities out there. I even wrote a love letter. The most recent update brings screenshots history which is really nice.

• Raindrop.io is making a small comeback using the free tier for storing non-text bookmarks like things to watch. I didn’t subscribe to the service, and I explain why in this blog post “When War in Ukraine Influences My Application Choices - Numeric Citizen Blog.” I rarely use it, but when needed, it’s there.

• Notion was dormant since I switched to Craft until recently when I started to use it more often in combination with IFTTT. I use it to store information like popular discussions about Craft on Reddit or YouTube videos that I liked. More details in this YouTube video that I made.

• I became a subscriber of write.as as explained in [this article](https://numericcitizen-introspection.blog/friday-notes-63-i-writeas-myself/](https://numericcitizen-introspection.blog/friday-notes-63-i-writeas-myself/). There was a promotion earlier this year for a five-year subscription plan. I decided to make the plunge and give it a try. I’m using Write.as mostly when I’m musing about a very specific subject. The war in Ukraine has been one of those subjects. I like Write.as for its simplicity and its connection to Ghost, albeit without using it for every post.

  My write.as page.

• Matter is becoming more of a nice read-later service. I like it a lot. But then, the long-awaited Readwise Reader is coming into beta and looks like a serious contender. In Early October, I was finally able to try the Readwise Reader application. I like it a lot too, but it offers a quite different experience than Matter. Which one will stick with me is still unclear, though, like many things as I wrote in [this article](numericcitizen.me/2022/07/0…](http://numericcitizen.me/2022/07/03/things-that-dont-stick-with-me/).

• The Reminders app from Apple is removed from my workflow, as I’m trying to focus on fewer tools. Instead, I came back to using Things 3 for my weekly planning instead of relying on Craft’s to-do list and daily notes. What’s better than a task manager to manage… tasks? More details about this change in this YouTube Video “Why I’m No Longer Using Craft for My Daily Notes.”

• Vimeo is out, but YouTube is in for hosting a series of videos about Craft. I could see myself creating videos about other subjects too in the future. At the time of publishing, I made 35 videos so far, I currently have a bit less than 500 subscribers. My goal is to hit the 1000 mark within the first year of producing videos.

• I settled on using a few Apple shortcuts for storing web clips in Craft Inbox. I discovered MarkDownload, a Safari extension for downloading web articles in markdown files that are easy to import in Craft for reading and processing. CraftClip 1.3 is also in there for use on my iPad when I’m browsing the web and want to save an article for further processing and inclusion in Craft. My reading workflow is still in flux, though. I’m thorn between Matter and Readwise Reader. As described in my YouTube video, Craft plays an important role too as explained in this YouTube video “My Reading Workflow Using Craft”

• I closed my Blot.im account and move to Craft for hosting the Numeric Citizen I/O website, representing a 60$ savings that will serve to pay for the Craft Business plan. What if Blot.im disappeared? I asked myself this question recently.

  • A side-effect of moving to Craft for hosting my content is the loss of RSS feed support.
  • Blot.im was based on a GIT repo and for publishing I needed Nova, it has been removed from my workflow too as well as WorkingCopy for the iPad.
  • Commento was disabled and closed on all my blogs after closing my Blot.im account (another 260$ of yearly savings) and when Ghost introduced native comments. I was never or very rarely used by visitors to post comments anyway. What a waste of time and money.

This meta blog is mostly about my content creation workflows. Photography is a big part of it, so I posted an update last week-end about it, after a two-year period.

My last photo processing update is more than two years old. Quite a few things have happened since 2020: many things are in, but many things are out too. I learned to use new services while dropping those that don’t fit my content creation journey. Let’s see what’s in and what’s out.

What’s in

• Glass, the new kid on the block of photo-sharing services, is in, and I like it a lot, as I wrote in “my experience with the service.”
• Exposure is in, and I love it so much that it will replace Smugmug as my official home. The main reason is the possibility of a great mix of images and text forming beautiful posts. All posts published on Exposure are cross-posted to Micro.blog.
• Adobe Spark was renamed to Adobe Express recently. I’m rarely using it, but when I do, I like this creative tool.
• On the hardware side, my iPhone 11 Pro was upgraded to an iPhone 13 Pro back in the fall of 2021, and I wrote in detail in Upgrading From the iPhone 11 Pro to iPhone 13 Pro — the Love Story Continues – Numeric Citizen Blog. In summary, it was a great upgrade for my photography creativity.

What’s out

I guess the following items should be added to my long list of “Things that don’t stick with me” article. Let’s see one by one the ousted service or app.

• My iPhone 13 Pro played a major role during my trip to Italy last summer. Two-thirds of my shots came through my iPhone 13 Pro device, one third with my Nikon D750. The trend is worrisome. Is my Nikon D750 on the way out? Not yet, but… I know it won’t be part of my next trip to South America this coming December.
• 500px is out (it previously replaced Flickr) and eventually was, in turn, replaced by Smugmug. The latter is on the way out too, and will be replaced by Exposure. The process has already started (read my Experience using the service recently published).
• Universe was a one-year experience but was later abandoned. It gave me the unique experience of building a simple website showing my urban exploration photographic work.
• Gurushots, a photo contest community, is out of my digital life. I still have an account but I no longer spend time on this website. It’s a big waste of time as fully documented GuruShots Tips and Tricks Guide — The 2021 Edition — Part I – Numeric Citizen Blog and in GuruShots Tips and Tricks Guide — The 2021 Edition — Part 2 – Numeric Citizen Blog.
• Camera+ is another victim of my workflow constant optimization. It was briefly replaced by the excellent Halide, but again it was dropped in favour of Apple’s stock Camera app. If I had an iPhone 14 Pro, I would probably switch back to Halide as it offers an easy way to turn on and off the 48-megapixels camera mode.
• Also out is my content on Adobe Portfolio (I wrote a small review about the service a while back). While the tied integration with Adobe Lightroom is nice, it wasn’t easy to create a website to my liking, and I eventually dropped the service. Exposure is a photo-sharing service that goes way beyond Adobe Portfolio.
• My use of Adobe Lightroom Classic has significantly decreased since my last workflow update. My go-to photo editing app is Adobe Lightroom (both on iPad or M1 MacBook Air), and Pixelmator Photo on the iPad comes in second. The latter was extensively used during my summer trip to Italy.
• I also stopped using Skylum Aurora HDR & Luminar as my need for HDR is nonexistent (it used to be the case when I was doing urban exploration, which is no longer the case, sadly).
• On the hardware side, I sold my 2017 4K Retina iMac (read “Remembering My Story of Owning The 4K Retina 21.5 inches iMac — 2017-2021 – Numeric Citizen Blog”) and bought an M1 Mac mini shortly after it came out on the market. I wrote a must-read article on how to migrate Adobe Lightroom Classic from one Mac to another. A few months later, I got an M1 MacBook Air. Both of these machines are simply incredibly mighty.

Miscellaneous

I’m still using Unsplash for selecting photos for addition to my content when it makes sense. I contribute from time to time, and that ok. I’m not investing much time in selecting photo content for publication on Unsplash. Sometimes, less is more.

I used to have an Instagram account (The Perfect Imperfctions) and mostly stopped posting on it. Time is a finite resource, and I have to make choices on where I spend my time creating new and meaningful content. One thing is for sure, Instagram is not what it used to be for photography lovers like me.

Concluding words

My photography workflow is constantly changing but maybe not as often as my blogger workflow. It has been more than two years since my last workflow update, and a lot has changed in two years. I don’t see major changes in the future, as I’d like to keep things a bit more stable for now and use my creativity to make good use of my toolset.

The following screenshot was taken from the Plausible Analytics dashboard. It displays the analytics for Numeric Citizen I/O before being shut down for good. Plausible Analytics isn’t supported on Craft website, but since I’m a Craft Business Plan subscriber, I got some analytics. I’ll be able to compare overtime if Craft website is correctly reachable from Google.

In the coming days, this blog will be transitioning to a Craft-based hosting solution. As you probably already know, I’m a big fan of Craft (see my YouTube videos here), and a proof-of-concept was running (see: https://world.numericcitizen.io/meta) for a while, and I’m happy with the results. It’s time to move forward.

Why This Change

As a cost-cutting measure and workflow simplification desire, I’ll cancel my subscription to Blot.im and fully focus on Craft as the hosting solution. Craft, when used with the Business Plan subscription tier, proves to be an effective solution for hosting simple websites like this one.

The consequence of this move is that I’ll no longer rely on GIT and Nova (a great GIT client on macOS) to to my publishing. While I learned a few things related to GIT with Blot.im, I need to move forward with a less time-consuming solution.

What You Need To Know

The way Craft hosting is working, I’ll have to make some changes for the domain name to points to the right place. The actual website under Craft is already hosted behind the following URL: https://world.numericcitizen.io/meta. Links like https://numericcitizen.io should be pointing to the new destination URL. I added a domain forwarding rule in GoDaddy DNS so this should happen automatically.

Please note that, unfortunately, Craft website doesn’t support RSS feeds. So, consider removing your RSS feed subscription from your RSS reader app. I don’t have a way to know how many readers are coming here through the RSS feed. This is sad, and I hope not too many readers will be impacted by this change. Please keep coming and visit my website for new and updated content.

I’m also happy to report that Google well indexes Numeric Citizen I/O under Craft at the time of this writing. You’ll always be able to find this blog. Also, recent content will be marked as such using Craft “Focus” box option coupled with a 🆕 emoji.

Looking Forward

Since publishing content in Craft is super easy and frictionless, expect more updates in the future. The goals of this website stay the same: to share my experience with my content creator tools and services. I hope that you learn something new when you visit my website.

I’ve been making videos since early June of 2022. I wasn’t destined to produce content for YouTube as I’m more of a “written words” type of guy. So far, I have made 18 videos totalling more than two hours and a half of viewing time. Along the way of producing those videos, I learned a lot, and at this point, I feel pretty satisfied with my workflow. Here are my gathered observations and notes about my endeavour.

• Craft is a great application for helping me stay organized and support my video creation workflow. I’m using a template for each new video with things to do, research notes, documentation, video script, and post-process steps are all part of the template. I also maintain a table of past and future videos. I’m very happy with Craft in that respect.
• I did learn a few things about Craft along the way of producing these videos, for example, while preparing the video about explaining the differences between a document and a page in Craft, I learned that dragging a page to the navigation pane on the left portion of Craft main window, the page gets converted to a document.
• As much as I love my M1 MacBook Air, exporting videos using ScreenFlow can take up to an hour. It’s the use case that makes me wish I had a more powerful MacBook Pro.
• At Episode 15, I decided to use an external 1TB SanDisk SSD drive to store all my past and present episodes instead of my MacBook air internal drive. This way, I can plug the drive on my M1 Mac mini when I’m ready to export a finished video. Remember that a MacBook Air has no fan, and after 10 or 15 minutes of intensive use, the Mac will throttle down the CPU to prevent overheating. There is no such thing on the Mac mini; the CPU can run at max power for as long as needed, shortening the video rendering time.

• Having an external drive to store my videos also enabled me to use my Mac mini which uses an Apple Studio Display which brings much more space to work with while doing video editing.

• Doing the video montage on the Apple Studio Display helps a lot and helps me reduce the time it takes to create a new rendering.
• A typical folder containing a recorded episode contains the Screenflow document, the episode header image in full and lower resolution and the resulting .MP4 video file, ready for upload in YouTube Studio.
• Speaking of Screenflow: it’s a great application, but it is afflicted with a few bugs here and there. Updates to fix those are slow in coming. At some point, I contemplated the idea of switching to Final Cut Pro but doing so would still require me to keep Screenflow. So I’m sticking to it. Oh and I don’t like iMovie. Maybe I should look back at LumaFusion? But I don’t want to do production on the iPad.
• With each video, I’m perfecting something in my process or in the final product. My best montage can be found in Craft Doesn’t Need to be Notion and “Learn the Differences Between Documents and Pages.” I’m recording with a 4K Logitech Brio webcam, but I’m planning to use the Opal C1 webcam when the software gets more mature, and bugs are fixed. I’ll update this post after putting it to work and compare it with the Logitech.
• It took me a while to understand how chapters on YouTube work. Publishing from within Screenflow doesn’t export chapter markers (another Screenflow bug?). To get my markers exported, I need to first export them to an .MP4 file, then manually upload them to YouTube. That’s annoying.
• Google, unsurprisingly, offers a comprehensive plethora of analytics. It’s really a rabbit hole for those like me who love numbers. So far, I’m happy with the numbers, except for people retention. Surprisingly, people don’t stick around for a long time at my videos. Is my content that bad? Is this a major trend on YouTube or something that is closely tied to my content? Looking at my comments and likes ratio, these are vastly positive and aren’t indicating a problem with the content and the visual quality of my work. The retention time tends to increase as I produce longer videos.
• It makes a noticeable difference when posting a new video is coupled with a post on Reddit, Circle and Slack, as well as Buffer on Twitter.
• Being active on Reddit, Slack and Circle helps a lot to increase awareness about my videos, and I’m getting many new subscribers each day. On average, I’m getting about three new subscribers per day, which could mean that by the end of my first year of publishing content on YouTube, I could reach close to 1000 subscribers. This looks unrealistic. If I ever get past 500 subscribers, I’ll be happy.
• When I’m referring to one of my blog articles in the episode notes, I do get visitors. YouTube seems a great way to help grow visitor traffic.
• According to my Linktr.ee analytics, I can see positive impacts on visitors and conversion rates.
• Credibility seems to be building over time as I’m posting on a regular basis new content. I’m getting a score of close to a 100% likes ratio, which is a good indication that I’m doing good, but is this sustainable?
• I don’t pay too much attention to time release timing of a new video. YouTube processing into 4K takes forever. I tend to release a new video on the day after it has been uploaded and transcoded by the YouTube back-end.
• Most popular video: “Planning my week ahead using Craft Daily Notes.“ People are looking for productivity hacks, and I should probably do more of these videos in the future.

You can view a behind-the-scenes video here.

In recent days, I’ve been working on a proof-of-concept to replicate Numeric Citizen I/O website currently hosted on Blot.im into Craft. I’m happy to report that the main portion of my work is completed. You can have a look at the end results here (Craft link). Now, the only missing part is the support of custom domains and notifications. The former will help mask the Craft URL behind a more user-friendly URL. The latter will let me know when someone is dropping a comment on the website. For the time being, I’ll update both versions in parallel. Enjoy.

Moving content from one platform to another isn’t easy. And it shouldn’t be that way.

The problem: I want to migrate a few dozens of posts from my Numeric Citizen Blog to my other website, Numeric Citizen Introspection, hosted on Ghost. Easy, right? Think again. The Ghost migrator plugin doesn’t support posts selection; it’s an all or nothing tool. How can I migrate a subset of my posts in that context? By assigning a specific category to each post, I can use the WordPress export tool to export these posts. Next, those posts can then be imported into an empty WordPress instance. From there, I could use the Ghost Migrator plugin. The issue is that I don’t have an empty WordPress instance sitting idle. Using WordPress.com, I cannot install the plugin in a free instance (it’s part of a Business plan, which I subscribe to for my main blog). The solution, was to use my Synology NAS to install an empty WordPress instance locally and proceed from there. Let’s see what the workflow looks like.

1. Turn off post update in the WP to Buffer Pro plugin to prevent flooding your Buffer queue
2. On the source WordPress instance, update posts category that you want to export
3. Install the “Export media with selected content” plugin (which is needed to export images as well as text content)
4. Export content to an XML file with the plugin
5. Install WordPress on Synology NAS with all required dependancies
6. Configure a WordPress website that will be used to host exported content in transit to Ghost
7. Install “Export media with selected content” in Synology WordPress instance (not really required)
8. Install the Ghost Migrator plugin
9. Delete the default post and unneeded page from the WordPress instance, as well as any images from the media library.
10. For each post to export, add the export category of your choice (in my case it was “PhotoLegend”.)
11. Export posts using these options from the WordPress Tools menu

12. Switch to the WordPress instance running on the Synology NAS
13. Select Import from the Tools menu
14. Select the XML file created from the Export step earlier
15. Set the author for the imported posts

16. Set the Download and import file attachments to bring in images
17. Click Submit and wait for the process to complete (it takes some time, depending on the number of posts and images to import)
18. Verify if all posts are listed in the Posts section (check creation date, author, etc.)
19. Check for Media Library to verify if images are imported
20. Open a few posts to see if content is correctly formatted
21. Edit posts with back links or other elements that need to be updated before importing content into Ghost
22. Edit tags according to the destination website requirements
23. Edit post slug and post title according to destination website requirements
24. Export using Ghost Migrator plugin, select the JSON format since ZipArchive module isn’t installed with this version of WordPress and PHP

25. Import JSON file created in the previous step
26. Check for imported posts issues. This is where I hit the wall. Missing photos, content imported as HTML blocs, etc. Not great at all.

27. Turn back on the WP to Buffer Pro Post Update option

This workflow doesn’t meet the goal of migrating WordPress content to Ghost. I ended up deleting the posts on the source WordPress instance and kept a copy of them on my Synology instead. I don’t know what I’ll do eventually with these “archived” posts.

Observations

Some observations are in order. This whole story brought many observations that I think you should consider if you’re attempting something similar.

• The Ghost Migrator plugin is very limited, which make it hard to build an optimal migration workflow.
• Images migration is close to impossible or very unreliable, forcing to use a manual export and import process.
• Image optimization plugins on WordPress could make the migration harder than necessary.
• Website optimization plugins on WordPress could add tags that are probably hindering the migration process.
• Ghost import feature is still a work in progress can there is no way to select which post to import after reading the JSON file.
• Testing the migration with a single post would most likely help identify issues faster, instead of importing all the content on the first try.
• It doesn’t help to convert the WordPress post to use the block editor before exporting the content.
• Migration efforts are time-consuming, making sure the content still has value to your reader is a good idea. I ended up deleting my 23 posts after spending hours of migration efforts. The positive side of this story is that I learned quite a lot.
• Even if I couldn’t use the ZIP file for the Ghost Migrator plugin, I don’t think it would have made a difference in the migration quality. I tried to add ZIP Archive to the PHP installation, but the WordPress installation within my Synology NAS is hard to customize. After spending a few hours trying, I dropped the ball.
• Data portability is really an issue these days. Even with export or import plugins exist, there are other problems that are inherent to each platform or CMS.

One thing that I gained from this experience is that by using WordPress on my Synology NAS, I can export content from my online WordPress to my Synology NAS for archiving purposes. That’s cool. Other than that, the problem of data mobility across content platform is real.

My previous blogger workflow update was in March 2021. Quite many things have happened since then. It’s time for another update. Buckle up because this is a big one, and enjoy the ride!

What’s in

For 2021, I was expecting a year without many changes to my blogger workflow, and yet, I was in for quite a few surprises.

• Probably some of the most important additions this year are Toggl, Timery, and Focused Work to track my time while creating content (consider bookmarking and reading “Why and How I’m Tracking Time With Toggl” if you want to know all the details.) Tracking my time does take some time, but I like the results.
• Hello Ghost (again)! I started experimenting with Ghost during the 14-day trial period, during which all features were available for testing. I started building automation with the Zapier integration. After the trial period ended, the integration with Zapier stopped working for some reason. I quickly found out that many features like custom themes, custom integrations, and commenting support are only available with certain subscription tiers. Commenting on each blog post isn’t available by default unless I’m on the Creator tier and customize one of the provided themes. To use Commento, I needed an API key, as well as a custom theme and a custom integration. And moreover, a custom version of Casper with some script invocation was added to enable Commento integration. Forking such a built-in theme requires staying in sync with the official theme, as Ghost updates them from time to time to benefit from all Ghost’s additions. Finally, I visited Google Search Console to add my Ghost website for better SEO management and optimizations. I became a subscriber at the entry-level tier for $9 per month, but I quickly realized that the $25 was the one I needed (consider bookmarking and reading “Moving From Substack to Ghost–My Experience” for more details.)
• iPadOS 15 introduced support for Safari extensions. Working on the iPad now feels less and less a compromise, as Grammarly support and many other extensions are now available. For people depending on the iPad, it is a much-welcomed addition. Unexpectedly, in 2021, my workflow shifted towards the MacBook Air (read “Coming Out of a Rabbit Hole and Buying Two MacBook Air”).
• Pocket made a comeback in addition to Readwise (consider bookmarking and read “Instapaper vs Pocket — Which Read Later Service Is Better for Me”). Pocket is well-known and doesn’t need much introduction. According to Readwise website: “Readwise makes it easy to revisit and learn from your ebook & article highlights.” Resurfacing previously highlighted text snippets is fun and helps build a lasting memory of past readings. I added Readwise as a source to my weekly newsletter built using Mailbrew.
• Using the Readwise sharing feature to repost quotes on Twitter is handy. I don’t use it too often, though.

• WordPress plugin: I’m using the paid version of “WB to Buffer” for reposting previously published posts to Buffer. With another WordPress plugin named “Feedzy” it imports RSS feeds from Substack and Microblog and creates “Also on my …” type of blog posts automatically. It didn’t generate much traction and added too much noise to my original content feed. This was disabled after a few months when I moved out of Substack.
• I unexpectedly started using Matter when Matter officially became public. Matter seems to have gained some traction over Pocket as the best read-later service. Compared to Pocket, it creates great link posts that can be saved or shared online, just like Readwise and Pocket.
• I became a subscriber of Typefully (typefully.com), a web application for writing threads on Twitter. Some features of Typefully are similar to Buffer’s, like being able to schedule tweets. I use it to write threads to complement some of my articles. The latest example of things to watch in 2022. Finally, Typefully brings great engagement analytics.

What’s out

• My experience with HEY World didn’t last long. I’ve been moving out of HEY World to go to Substack for my Friday Notes* and Photo Legend* Series (consider bookmarking and reading “Migrating My Content From Hey World to Substack”). I can say the same thing about my Substack experience. These services, while attractive, didn’t stick in my workflow.
• HEY is no longer on the workflow diagram. HEY doesn’t really contribute to my blogger workflow. Most of my readings don’t happen there anyway, even if HEY provides newsletters dedicated feed, one of the tent pole features of the mail client.
• As mentioned earlier, Substack is out. The popularity of a platform doesn’t guarantee the popularity of your content.
• I closed my Telegram account. Read more here to learn why. I’m contemplating Signals instead.
• WordPress Plugin: Coblock was disabled to remove overhead in webpage processing. It didn’t make a difference, though.

In progress

• I do spend more time maintaining my digital garden in Craft all year long. You can find a lot of stuff in there.
• I’m still trying to figure out how to use Apple’s Quick Notes feature in iPadOS 15 and macOS Monterey. I may end up having no use for this after all, which is too bad because, on paper, the idea is cool.
• I’m always thinking about using Apple’s Reminders in my workflow. Reminders have improved quite a lot over the years, but occasionally, I think Craft could take over if table support was better (sorting, tagging, etc.). The more things I’ll do with Craft, the more synergy it creates. I’ll watch Craft’s evolution in 2022, and maybe make a move.

Things to improve

• Adding text clipping in Craft would be so helpful. There are shortcuts that work with Craft that do just that, but I don’t find the experience very satisfying.
• Speaking of Apple’s Shortcuts, I do find more use cases for them to speed up a few key tasks, like setting up my work session after logging into my account on macOS.
• Templates in Craft to kickstart the creation of a new article would be very handy. It is expected in 2022, in an upcoming update in 2022 or via an extension.
• As much as I would like to see the addition of tags in Craft, implementing this feature could be tricky. Where should we be able to tag things? In a page’s properties, inline in the page’s content?
• I have to work on my reading workflow and decide what I’m going to do with Pocket, Readwise and Matter. Pocket will probably go as it is entirely covered with Matter.

Miscellaneous

• My usage of ** Craft ** has significantly increased this year. It is becoming my second brain (Fun fact: find out the name of my MacBook Air). Lately, I decided to use the Craft calendaring feature to prepare a weekly plan containing my content creation objectives. As the week progresses, I keep it up-to-date and check items off the list. It’s a satisfying experience, trust me.
• I’m still using Notion to keep my old data and connect Matter to Notion to save my reading highlights automatically. As soon as a Craft extension allows me to pump my data out of Notion, I might be done with Notion once and for all. Notion is not shown on my workflow diagram but will be in an upcoming post covering my reading workflow.
• Twitter Revue: I had a Revue account before Twitter bought them. Now that it is integrated into their platform, I experimented with it (read a sample issue here). I love Twitter Revue, but I have yet to find a unique and useful use case for it. I currently have five subscribers.
• Furthermore, I should consider closing my Flipboard account. I never go there; it’s not what it used to be, and I don’t get any traffic from this platform.
• Google News, where I cross-post my main blog content, could also go down the drain. I don’t get any traction there.
• Finally, Tumblr is another place where I cross-post content. Tumblr has become a ghost town in recent years, and it doesn’t help at all. Even if cross-posting is done automatically using WordPress’ built-in feature, I should consider stopping using this platform.
• In my previous workflow update, I considered moving my Photo Legend Series to Hey, which I did for a short while. Now, it is hosted on Ghost, along with my Friday Notes Series and monthly newsletter. I like consolidating stuff sporadically.
• Since getting a MacBook Air, my iPad Pro usage significantly dropped. The Mac is the power user tool. I cannot be as productive on an iPad.
• I worked a lot on my WordPress blog to improve its score on Google’s PageSpeed Insights, as documented here. Did it make a difference? According to my blog visitor statistics, the answer is no. Here is a strange thing: if I run PageSpeed tests twice in a row, the final score is quite different. Usually, the second try gives much better results. How much trust should I put in these results? Another observation: my score for this blog, a static website, is the worst. Is Blot hosted on a low-end performance tier in the cloud?
• I’ve been using Commento with Blot to add comments support on this blog. I never got a single comment! It’s a high price to pay for a service that nobody takes advantage of. Maybe it will be a better fit with my newsletter website on Ghost? Time will tell.
• IFTTT still plays an important role in my publishing workflow as it works with Buffer to help me control the cross-posting flow. Each day, I spend some time managing the Buffer queue to spread out posts to be published. I also use IFTTT to cross-post anything I post on Reddit to my Twitter channel on Buffer. Buffer has a new calendar view that helps you see a timeline overview of all future publishing. Buffer isn’t cheap, but I like what it does for me. Cross-posting content does help create traffic and improves engagement.

Well, that was a long one. I want to walk you through my reading workflow for an upcoming article. I read a lot of stuff online, and many applications and services are involved here. Reading is the source of my inspiration for most of my work as a content creator. I think there are some interesting things to write about. Stay tuned, and see you in 2022.

Digital nomads. The flavour of the day. Looking for a better digital experience? Every reason is good to move from one place to another in the digital world. It’s about having some fun.

I recently came across this blog post from Greg Morris where he writes: “I look at blog designs like Birchtree.me* and think to myself “I want a blog like that” and then go out and try to build one.”*. I often tell myself the exact same thing. But then, not long after, I came across another blog post , but this time by Andy Nicolaides writing on his blog, The Dent:

“I’ve just gone through yet another blog migration, moving from Micro.Blog to Ghost (again). I was happily posting to Ghost a year or so ago, saw a nice looking blog on Micro.blog and jumped ship. I then sat there, not posting for half a year, before I saw Greg Morris’ updated site over on Ghost and my blog envy kicked off again. Let’s not even mention how incredible Matt Birchler’s Birchtree looks right now!”

Ghost has always been a source of curiosity for me, coming back to it from time to time to look and see how it is evolving. Following those two blog posts, I got back to one of my articles about a past experience with Ghost for photo sharing. At the time, it didn’t go well. Furthermore, I started using Substack to host my newsletter for unknown or clearly defined reasons. So, this time, I returned to Ghost to look at it as an alternative to Substack. Why? After all, I was quite happy with Substack. And yet… If I look at Substack and Ghost, there are many things that made me dubious of my choices.

• I don’t get any subscribers from Substack Discovery because Substack is very popular these days.
• I prefer the way Ghost handles the publishing process and the distinction between having a CMS and a newsletters publishing platform within the same platform.
• Ghost’s API supports text editors like Ulysses, which would help speed up the process of creating newsletter issues. By working directly with Ulysses, each new issue would be much easier to put together, as Ulysses supports templates, while Substack doesn’t. Since the basic structure of my newsletter stays the same each month, using a template makes perfect sense.
• Substack offers some visual customization options, but they are quite limited. On the other hand, Ghost offers themes that help make a more personal-looking website.
• Ghost supports Unsplash, which is a must for me.
• Ghost provides better support for photos than in Substack with photo galleries. This could prove to be useful for my photo legend series, among other use cases.
• Integration of plausible analytics is easy, but it is not possible with Substack. Another must-have for me.
• Stripe integration, which I already use for Medium payments, if I ever choose to add a paid tier to my newsletter.
• Commenting is possible by tweaking the theme and adding some integration code. Yet, I wish there was a better and easier way to add this to a website. In the future, I could try to set up Commento for comments using this procedure. Ghost theme customization is available only on mid-tier and up-paid plans. This feature could replace the thread feature available on Substack.
• Good integration with Buffer via Zapier. IFTTT integration is possible only via RSS feeds. As a paying member of IFTTT, I chose the latter.
• Better RSS feeds support posts, tags, and pages just by adding /RSS to any URL. On top of that, it is possible to customize the webpage referring to a tag by adding a header image and a description, just like here for the Photo Legend Series.
• Selecting a fully featured theme is challenging, as Ghost doesn’t provide an easy way to filter themes by supported features.
• I’ll leave my Substack account active for the Substack Reader feature.
• Easy migration path from Substack to Ghost using this procedure.
• Should I import my content? After a short test run using the 14-day evaluation period, it was clear that I had to.

How Ghost could be improved for me?

One of the Ghost editor’s most powerful and useful features is the ability to create and reuse content snippets. If you’ve ever used an email client with saved replies, this will be immediately intuitive.

• Integration features and custom themes for the entry-level paid plan (access to the API admin token).
• A customizable dashboard.
• A native client on Mac or iPad.

Steps to move from Substack to Ghost

1. I exported my data from Substack, which took less than 10 minutes to complete. Substack makes this super easy.

2. Import my subscribers list into Ghost’s members list.

3. Download Xcode from the Mac App Store and launch it for default configuration (required for the next step).

4. Install Homebrew to be able to install NPM modules later (importing content into Ghost requires Node.js and NPM modules): https://treehouse.github.io/installation-guides/mac/homebrew

5. Install Node.js and NPM: https://treehouse.github.io/installation-guides/mac/node-mac.html

6. Follow this procedure to import articles into Ghost CMS. This is done via the command line.

   `migrate substack numericcitizen-export-2021-11-14-m9k19kr99s/posts.csv –readPosts numericcitizen-export-2021-11-14-m9k19kr99s/posts –url https://numericcitizen.substack.com –useMetaImage –useMetaAuthor –drafts false

   `A lot of my decision to switch depended on the success of this step. If content was successfully imported without too much required tweaks, I would consider this a success and go with the next steps.

7. Import the created zip file (the migrate command generated a 230 MB zip file ready to import). This file was then imported using this procedure.

8. Configure site pages and tags Once the import is complete and without error.

9. Review imported content and set tags according to each post’s content. That step was tedious but was mandatory to recreate the same content structure currently on my Substack website.

10. Configure and write a contact page so that users can click from the bottom portion of my Ghost website to contact me.

11. Connect my Ghost account to my Stripe account just in case, even though my newsletter is free—you never know!

12. Configure Ulysses publishing options to publish content from within the application to Ghost. After all, this was one of the main reasons I switched from Substack to Ghost, right?

13. Do a test run with a fake article and check RSS feed content generation.

14. Configure the support and reply-to email addresses.

15. Set up Plausible analytics and add it to my Ghost website using the customization feature in the header section.

16. Update all my IFTTT automations for cross-posting to Twitter via Buffer when a newsletter issue comes out.

17. For mid-tier paid plans only: Add Twitter Revue new sign-up to Ghost via Zapier (this requires the Admin API token, which is not available in the entry-level paid tier).

18. For mid-tier paid plans only: Add Ghost cross-posting to Buffer via Zapier (this requires the Admin API token unavailable in the entry-level paid tier.)

It took me about a day of work to accomplish all this, from the trigger to the final announcement post on Substack. I’m super happy with the end results.

Yesterday, I put an end to my HEY World experiment. After making the call, I wanted to keep my content and migrate it to Substack. So, I tried the Substack RSS feed import feature, but it wasn’t working. As shown in the following screenshot, the error wasn’t explicit enough to pinpoint the cause of the problem.

I had 23 posts to import, which was not a big deal, but I preferred not to move my content manually. Trying different variations of the URL didn’t help. Substack wouldn’t detect any feeds from HEY World. Here is my solution.

HEY World uses ATOM RSS feed format. I thought Substack couldn’t parse those. The idea was to transform the ATOM RSS feed into something else. After googling for a solution, I remembered about RSSMix (this service is no longer available and FeedPress is way better). This free web service enables merging many feeds into one. I use it to merge all my personal RSS feeds into a single one to build a publishing timeline. It’s pretty cool¹. For my HEY World content migration, I took the ATOM RSS feed with another one and merged the content². The end result is another feed, but this time in XML format. I went to Substack again, and sure enough, the resulting feed could be imported. After the import was completed, all I had to do was delete posts from the second feed content which wasn’t part of HEY World³. Simple as that.

Update #1: 2022-05-22 : Since the publication of this article, I moved (again) my newsletter to Ghost. Update #2: 2024-06-15 : Replace RSSmix with FeedPress as the former is no longer available