Editing new content from the iPad for this blog poses some challenges.

I started writing this post using my iPad, Working Copy and Textastic¹. The file was initially created within Working Copy’s sandbox, but I fetched content from the Blot Git repo to store the most recent changes locally on my iPad.

As with every app on the iPad, Working Copy runs within its sandbox. When cloning the Blot repo locally, files were placed in the application’s sandbox, which is inaccessible outside the iPad². Ulysses uses external folders, so I can point it to my iCloud Drive, where I stored the cloned repo with Nova. Only Textastic can edit files with Working Copy’s sandbox.

Writing with Textastic and publishing with Working Copy feels geeky compared to a workflow based solely on Ulysses. It is geeky because I have to think about what I’m doing in regard to my local repo being up to date with the remote one. I must remember that after pushing this article on Blot, I’ll have to do a fetch when I go back to editing on the Mac. I’m not certain that I like this dance. Textastic is good, but not as a writing application like Ulysses. The former is more directed to developers, while the latter is for writers.

Make no mistake, this isn’t a review of Working Copy. Read this excellent review from MacStories instead. MacStories likes it because it enables better group collaboration. It sounds overkill for me since I’m alone editing my website. Working Copy can work in conjunction with Textastic. After re-reading their review of Working Copy³, I found out that, in fact, I could have replicated a similar setup to the one on my Mac: using Working Copy to edit the local repo of this blog sitting on iCloud Drive (instead of Working Copy’s sandbox)⁴. In that case, I would use Ulysses to edit files as usual, and Working Copy, you see them as uncommitted changes.

If I don’t redo my setup on the iPad⁵, compared to using Nova on the Mac, I find this to be much less intuitive. Maybe I should focus on using Ulysses everywhere for my writing needs and use the Mac to push content on my Blot blog. It’s not a big deal, and Numeric Citizen I/O is not a place where I’ll publish as often as on, say, Micro.blog. Having to sit in front of the Mac for the final posting isn’t a big deal.

One last thing: Working Copy wouldn’t be needed if my Git usage was limited to GitHub. Blot, on which Numeric Citizen I/O is hosted, uses its Git server, which requires me to use a Git client capable of connecting to it. I didn’t find a way to do this with the official GitHub client.

I’m still undecided about what to do to enable my iPad to edit this blog. My mobile needs are quite low as the pandemic continues, limiting our travel possibilities.

Thinking about text editor apps. Following a recent article from Jason Snell about finding the best markdown editor for the iPad, I started thinking about using Ulysses for all my text editing needs. Is it the best tool for all use cases? Probably not. But it is cross-platform, and for me, it’s a must. As I write this blog post, I’m using Nova text editor on my Mac to start editing, finishing in Ulysses. It depends. I’m unsure how my text editor selection happens when I start writing a new blog post. Maybe I should do the same as Mr. Snell, build a table of much-needed features, and see if Ulysses still fits my needs. On my to-do list, I plan to write a blog post about GIT clients for the iPad. Working Copy is a very popular one and includes a text editor. Jason Snell’s article refers to Textastic too. They compete against Ulysses, but the latter doesn’t do Git stuff. Like many blogs, it may be okay to use a different text editor, depending on the platform. I could use iA Writer on the iPad for this blog and Ulysses for the rest. Or maybe Working Copy would be a better choice because I’ll need to use it to push updates here anyway? As you can see, I’m constantly reflecting on the tools I use or plan to use and my workflow. It’s a never-ending process. Back to Ulysses. For now. Update #1: I’m not alone in rethinking my text editor choices. Chris Hannah, too.

You can leave a comment on each blog post, thanks to Commento, you’re not being tracked.

When I created the Numeric Citizen I/O blog, I thought it would need a way for visitors to be able to leave comments as they see fit. I decided to go the Commento route because of its tight integration with Blot, but also for a more profound reason: privacy protection. According to Commento’s website:

Commento is more than just a comments widget you can embed — it’s a return to the roots of the internet. An internet without the tracking and invasions of privacy. An internet that is simple and lightweight. An internet that is focused on interesting discussions, not ads. A better internet.

There are no ads with Commento, so there is no need to track users. The weight of the script needed to add Commento support is light. Commento is easy to use for end-users and doesn’t require an account to publish a comment. But, if you prefer, you can use your Twitter account, your Google account, your Github account, etc, to identify yourself with the service before posting your comments. The design is nice and simple. Commento is not a free service, but I’m paying $99/year for it. That’s the price that I’m willing to pay so my readers aren’t tracked.

Do you want to try the end-user experience? Please respond to this blog post; you’ll see. Thanks in advance.

Update: 2022-11-15: Since this blog is no longer hosted on Blot.im, comments are handled “automagically” by Craft as a Craft-based document. Update: 2024-04-10: This content is now hosted on Micro.blog. You can reply to this post by using the provided buttons, below.

Testing a web-based blog post publishing tool for posting directly to Blot from a webpage.

I’m currently testing a straightforward blog post publishing tool running on a webpage. The tool is accessible at https://wall.blot.im. I wrote a front matter; I guess Blot will process it as usual. The editor provides a character count, a word count, and a way to export the current blog post or publish it directly on my Blot website. Once published, I guess that I’ll have to do a “pull” from my Git client to sync the newly published content with my local repo clone. Let’s try this. Nope. It won’t work unless I use Dropbox, not Git. Too bad. Returning to normal programming in 3, 2, 1.

I made a few layout changes to my archives page.

Someone on Micro.blog posted something from its Blot website and I noticed he was using an unknown meta tag in the post’s front matter: metadata.icon. He used a tag to add an icon to each of its blog post. I wanted to know how Blot actually used this tag to format the blog post, so I asked the guy. His answer made me look deeper into Blot processing of meta tags. After some readings, I decided to change the content of the archives page to use the “summary” tag after each blog post title. It is super easy to edit Blot templates. In that case, it was a matter of adding a {{summary}} tag like this:

Using Git instead of Dropbox for Blot content syncing provides an unexpected benefit.

As I recently wrote, Blot supports two mechanisms for synchronizing content from my Mac to the web: Dropbox or Git. I chose Git. As I write this, I’m still testing Nova as the Git front-end (I’m a GUI type of guy). One of the great benefits of using Git is the built-in history of commits that is at the core of any Git repo. As shown below, as I push updates to my Blot-based website, I make sure to write a short comment in the commit action to document the commit action. I think this is an important asset in managing a blog and owning its content.

A better view at the GIT panel in Nova:

Micro.blog allows for archiving all content to GitHub. Here is why I did it.

This blog post is about explaining a Micro.blog allowing me to archive all my blog posts, including images and why I do it.

First, you must know that Micro.blog already provides an archiving feature of all blog posts to the Internet web archive. You can find mine here. I think it is important because in our society, the durability of the numerical artifacts we create is far from guaranteed. Saving my blog posts outside of Micro.blog is one way to prevent my content from vanishing if something really bad happens to Micro.blog.

Micro.blog feature to archive my blog posts to a GitHub repo

I wanted to go further, though. This is where Github comes in. First, I needed to create a new repo: numericcitizien-archives. Next, by using the built-in feature of Micro.blog to archive blog posts to the newly created GitHub repo. Enabling it is super simple from the design page settings. Once done and after waiting for about a week, I could see my content from my GitHub account. You can find it here: https://github.com/jfmartin67/numericcitizen-archives.

Now that my Github repo has a copy of my blog content hosted on Micro.blog, I can use a Git client like Nova on the Mac to clone this repo to my local machine. The archive feature of Micro.blog creates a big index file in HTML format that I can then open in Safari. It’s really nice.

Setting up this blog with Blot was pretty straightforward.

It all started as an experiment. But now, it’s not. It’s something permanent¹. In less than a day, everything was set up and running. From the setup of the domain name (with GoDaddy) to having an actual site available for browsing. This is the very short story behind setting up the Numeric Citizen I/O website with Blot.

My interest in Blot came from the desire to have better control over the visual appearance of my microblog, which is hosted on Micro.blog. Micro.blog supports some customization but it’s too demanding as you have to have some knowledge of HTML, CSS and Hugo templates inner working. Another goal was to own my content.

Blot is a nice solution to my objectives: owning the content, easy visual styling, and easy publishing. Blot allows me to keep using my current applications like Craft for initial post writing Ulysses on the Mac, which supports Markdown files for editing. I had to select a GIT client to complete my workflow for publishing blog posts.

Opening my account on Blot was super easy. Before going further with any of the Blot settings, configuring my GIT client was mandatory. Cloning the Blot repo on my machine was quick and easy, too. Any non-fixable issues at this stage would have jeopardized the whole initiative.

Next up: setting up analytics, page structure, support for commenting blog posts, and closing a link format. All of this was dead simple to set up. But I wasn’t done yet. The next step was to select a visual theme. I wasn’t satisfied with the available themes, so I asked for support for help as I knew there were other themes available. After describing what I was looking for, the guy behind Blot agreed to bring back one of the decommissioned themes (for an unknown reason). In fact, it was the previously available default one. This closed the loop. I’m a happy camper now. I like this theme because it gives this blog a “scientific paper” look, and I love it; it aligns with the blog’s purposes.

Selecting a GIT client for the Mac is a bit harder than I thought. When I decided to create this blog using Blot.im, I had to select the synchronization mechanism between my Mac and the Blot.im service. Blot.im offers two choices: Dropbox (easy, seamless, but too invasive and bloated software) or GIT. I decided to use GIT, for a few reasons.

First, GIT is geeky. I like geeky stuff. This blog is about being geeky, so why not! More seriously, using GIT means that I have to select a GIT client on my Mac (and eventually on the iPad, too, for on-the-go publishing). The leanest way to manage content sync could have been to settle for the command line only. It is super easy to install GIT in the command line on the Mac. But, now, that’s too geeky to my taste. I prefer going GUI, being able to preview commits, file content, etc.

Here is a list of GIT clients for the Mac that I more or less tested with my impressions for each.

• GITHUB Desktop Client. I think this one is mandatory as it is the official Github client. Works fine as a GitHub client. Super easy to use but limited in editing functionalities, but I can configure it to open files in Nova¹. But it cannot connect to Blot.im GIT remote repo. Yet, it’s a keeper because of Github. It’s free.
• Microsoft Visual Studio Code. This one is impressive but also overwhelming. Do I need this complexity? Probably not. I don’t like its look and feel either: too Microsoft, not enough Apple-like. It’s still not optimized for my M1-based Mac mini, which is not good! It’s free. I will probably delete it from my machine.
• Tower. This one was mentioned by someone I follow on Micro.blog. It’s not free. I like the look and feel of this app. It’s clean. Works great on macOS Big Sur. But somehow, I find it less intuitive compared to Nova. It’s a fully native application (not Electron-based). Will be deleted.
• Sourcetree. Another GIT client but for Gitlab only (could not find a way to connect to Blot.im GIT repo). Still Intel only, not optimized for M1-based machines. No go. Deleted. Thanks to App Cleaner.
• Atom. It’s still Intel-only, sadly. It looks good, but I cannot connect to Blot.im GIT repo. It only supports Github.
• Nova. This app is well-known in the Mac community. They recently released version 5.0. It looks great: a tad busier and crowded interface and costs more than Tower. It comes with a local web server, so I can preview my Markdown file edits effortlessly. It also supports many file types (HTML, CSS, to name a few). It does support extensions to augment its features which is cool. I installed a few of them (Prettier, for example). Finally, Nova supports connecting to many types of servers (FTP, SFTP, WebDAV, etc.). I feel Nova will serve me better in my blogger workflow in the long run or could be used if I ever want to test a local installation of Hugo. Who knows.

As I write this blog post, I choose to settle on Nova for now. I’m still on the trial period. I have 18 days left. I can still change my mind. Meanwhile, if you have any suggestions, feel free to post a comment at the end of this blog post (not from the main page but by hitting the date & time of the post, which will bring you to the post page where you can comment).

In a future post, I’ll explore GIT clients for the iPad. WorkingCopy seems pretty popular.

I’ve been a user of Micro.blog since 2018. At first, I wasn’t sure I would like the place. Eventually, it grew on me because it is such a quiet place¹, with more engagement from the community members and with much more respect. There is something that I don’t like about Micro.blog, though. It’s the lack of easy control over the visual appearance of my blog.

Micro.blog is based on Hugo, a static site generator. It’s pretty flexible, fast and open-source. My current understanding of Micro.blog is that it doesn’t expose all of Hugo’s controls, only a subset of them. I’m ok with this, as Hugo is not for the faint of heart. Yet, I’m not ok with the look of my microblog. I want to make it more personal, less like a generic website based on a frequently used visual theme. To make changes, I need to know about HTML (I’m kind of okay with this) and CSS (I’m not okay with this!). CSS is the weirdest thing I have ever encountered in my digital life. What a messy “language”². No amount of reading or YouTube videos will make it understandable for me.

Another solution would be to import an already-made Hugo theme in Hugo. The other issue with Micro.blog is that it isn’t easy to import open-source Hugo-based themes. They need to be “ported”. Again, it’s not something I want to mess with. I recently started to think that maybe it was time to have my own microblog hosted somewhere to get complete control of the visual appearance. Installing Hugo on my M1-based Mac mini is simple. Having a publishing pipeline from my machine to the web looks pretty easy, too. It’s only the beginning. Even with great articles like this one, I find it difficult to wrap my head around it.

After much reading, I changed my mind and settled on the “Hyde” theme of Micro.blog. I would lose too much if I were to be alone, and new challenges would certainly arise. I hope for Micro.blog to keep evolving, especially in the area of better customization. I asked its founder to open up its roadmap. I’m anxiously waiting to see what’s next.

Writing about my numeric experience isn’t new for me. When I was an indie iOS developer (2009-2013)¹, almost at the same time I started learning Objective-C, I opened a Blogger site called “buildingiphoneapps.com”². The idea behind this was to share my experience of learning a new language and a new programming platform. I wanted to share my discoveries, my challenges, etc. It was fun while it lasted. This website started my experience of being a blogger. So, today, welcome to Numeric Citizen I/O - a metablog from Numeric Citizen.

Meta definition according to Wikipedia:

Any subject can be said to have a metatheory, a theoretical consideration of its properties, such as its foundations, methods, form and utility, on a higher level of abstraction. In linguistics, grammar is considered as being expressed in a metalanguage, language operating on a higher level to describe properties of the plain language (and not itself).

Meta?

This blog is all about meta-blogging³. What? You might think? In other words, this blog is about the tools, services and workflow I depend on daily to build and maintain my online presence. I think that many people find it interesting to know how things are done behind the scenes. This is the purpose of this blog. From time to time, I’ll post updates when a new tool, application, or service comes into play. I’ll also document workflow changes or retired services. From now on, updates will be published here. While waiting for the next post and to get a sense of my current blogger workflow, consider the following diagram. It doesn’t reflect the presence of this blog yet. Wait for an update very soon.

Why?

But why use a separate website to write about blogging? I’m glad you asked. Here is why. Each of my websites has a specific audience and content type. Think of my websites as different specialized TV channels. Each of them fills a specific role or targets a specific audience. I think it is better for a blog to stay focused on its core subjects. Each website can have its own personality and visual theme to support it. That’s why.

Make sure to visit the About page for more details about this blog. You can leave a comment, too; I would be more than happy to engage in the conversation! To do so, just hit the post’s publishing date to see an individual post and add your comment at the bottom. Thanks.

As a content creator, I’m always looking for new ways, tools and services to improve my workflow to be as efficient as possible. If something no longer fits my needs, I’m not afraid to make changes. The last update to my blogger workflow dates back to last November. Since then, I made quite a few important changes.

What’s in?

First, I added my Synology DS720+ as a central tool to manage my digital assets, mostly pictures used in my publications. I acquired this NAS last year to consolidate my numerical assets, and I cannot overstate how good this product is. The first use was to back up important files and archives later I added the digital assets use by taking advantage of Synology Moments, a photo library service that comes with the product. Read more about my use of Synology NAS here.

Next, an important addition is Craft. I’m still in the early stages of working with Craft, and I plan to write about my observations in the near future. Meanwhile, let’s say Craft is a similar yet quite different beast than Notion. It has a cleaner and really polished design and helps me gather digitals tidbits, write and organize my thoughts. You can have a look at a few micro-interaction examples with Craft on my Vimeo page. I don’t plan to kick out Notion from my workflow yet. Notion is much more powerful than Craft. I think there is a place for both of them in my toolset.

Speaking of Vimeo, I’m back for another year as a paying subscriber. I much prefer Vimeo to YouTube (you know my stance on data privacy protection and Google, right?). I used Vimeo to publish a video about why I’ll never be a YouTuber. I’m also creating a collection of short clips of great micro-interactions with apps. Craft is one of the collections. My Vimeo profile page is here.

To create short animation clips in my publications, I use GIF files. Those are created from video clips and then converted to animated GIFs using the powerful ImgPlay application available on iOS, iPadOs and macOS Big Sur (thanks to the M1-powered Macs!). For me, it’s the best animated GIF creation application out there. Think of ImgPlay as a Final Cut Pro but for animated GIF creation.

Finally, the diagram doesn’t show my use of Apple’s Shortcuts to automate many repetitive tasks. One shortcut is used to add a device frame to any screenshots. Screenshots are prettier this way. Another shortcut saves interesting links into Apple’s Reminders app for future link posts. Finally, another one is used to create an archive of my microblog front page from time to time using Newsy.

What’s out?

Google Analytics is out, thanks to Plausible, a great alternative. I wrote about my switch recently and decided to walk the talk regarding my stance on data privacy protection. While not as powerful as Google Analytics, it does the job quite well for my basic needs. Since closing my Google Analytics, Databox was no longer needed.

A mature workflow

After many updates in the last 18 months, I think my blogger workflow is in an equilibrium and mature state. We never know when a new application or service pops up and can make a difference for me as a content creator looking for efficiency. That being said, I don’t expect much change for the foreseeable future.

It’s been a while since I updated my blogger workflow. The last time was back in September of 2020. It’s time for some tweaks.

The number of services I pay for has increased. Now, I’m paying for IFTTT and Buffer. IFTTT has improved its offerings this year and started to offer a paid tier. I recently added an automation where new posts from my Micro.blog RSS feed will get saved to a Google Sheet document. It makes it much easier to find previous post references when working on my Numeric Citizen Introspection newsletter.

I’m paying for Buffer because of the added features I get in return. I get more channels and better post-management. All of my blog posts are now queued to Buffer. From there, I can choose when my blog post will be reposted. Sometimes, I may elect not to repost some of my work. Another use of Buffer is when an Apple event comes up. I will schedule tweets in advance. On the event day, I can focus on the event itself. It’s working fine for me this way.

The other addition is in fact a return of an old buddy: Reeder 5, the venerable RSS feed reader. I’m still depending on News Explorer (read my review here). I’m using Reeder 5 because of the Read Later feature, where I put all my internet articles that I want to eventually read. It works great, supports tags and runs on all Apple platforms.

Probably on the way out is MarsEdit. It’s not that the app is bad; quite the contrary. What I’m looking for is to consolidate my writing apps. Ulysses is rumoured to introduce support for Micro.blog beginning of next year. If that’s the case, I’ll drop MarsEdit.

In the next few weeks, I’m looking forward to Apple finally approving my submission of this blog for publication on Apple News. They recently updated their review process and asked all content creators to resubmit their articles and answer questionnaires. We’ll see.

Finally, I updated the general look of the diagram to make it easier on the eyes. I hope you’ll like it! Are you a blogger too or a content creator? What is your workflow?

Since the last update to my blogger workflow, Substack has been an important addition. Here is why and how I’m using Substack, a content publishing platform that is gaining traction for writers and bloggers like me.

Why Substack?

As you probably know, I recently started something new: a monthly newsletter about Apple, photography, privacy protection and climate change. I could have done it with Mailchimp or other similar services. Substack is free. For a few months, I’ve been paying attention to a nascent publishing platform named Substack. I do see more and more bloggers and writers publishing on it. One example is M. G. Siegler with 5ish.org.

I’m using Notion to gather my highlights during the month, coming from the usual sources and generated newsletters I get from Mailbrew. When the end of the month arrives, I go to my desk, sit down and do my write-up on my iMac. There is no native iPadOS app for Substack. Yet. This doesn’t bother me too much because it forces me to do it in a stretch. The newsletter is sent in the first week of every month. A link is cross-posted to Micro.blog.

Expect a review of Substack in the coming weeks, but first I need to gain more experience and insights into this service. Stay tuned for that one.

Cleanup required

Some cleanup had to be done too. I decided to remove any references and cross-posting to Reddit as it doesn’t generate traffic at all. Reddit is a special place (a jungle?), and I’m not sure if it fits me. Lastly, I’m still waiting for Apple News to approve my submission of this blog as a publication. It’s been months since I submitted my blog for review. I asked for support on the Publisher portal available on my icloud.com page. My expectations are low. I do hear here and there that Apple has become picky about which publication they allow. My fingers are crossed.

Finally, I wanted to update you about the visitor trend for this blog. The following graph shows sign of a slow and painful recovery following Google’s algorithms changes last November.

A few important additions have occurred since my last update to my blogger workflow. Here is my updated blogger workflow as of 2020-08.

The arrival of the controversial HEY email service has enhanced how I consume information. I recently published my thoughts on HEY. I’m happy to report HEY is now joining other important apps and services like News Explorer and Mailbrew. Who knew emails could become part of my information consumption routine? HEY combined with Mailbrew forms a killer combination.

WordPress application keeps receiving significant updates every few weeks. They are essentially bringing the block editor experience into the mobile app and adding nice touches here and there.

My favourite writing application, Ulysses, received a major update, V20, that brings a dashboard which groups a statistics panel, a text navigator, a comment section, and a media overview, among other things. Ulysses also includes a spell checker on macOS that is still unavailable on iOS but will come later this year. This addition could make me reconsider my use of Grammarly. All the details are available here.

On the subject of Grammarly, with the updated Safari in macOS Big Sur supporting extensions, my hope is to see a version of Grammarly introduced later this year. Still, regarding extensions, the same expectation is for Notion to support Safari.

Another addition, not pictured on the diagram, is the use of Apple’s Shortcuts with Reminders to created to-dos to remind me of bits of informations I want to write about. I’m using new features of Reminders shortcut support in iOS 14 for this. Oops. Works like a charm.

Finally, MarsEdit was updated to version 4.4 which bring full support of the Micro.blog platform for writing and posting directly from the application. I was testing the beta, and it works great.

If you are a blogger and use additional tools that are time savers for you, please let me know in the comment section below. Thanks!

Quite a few things have happened since my previous blogger workflow update in March. Mailbrew is in, Apple News is out, forgot about Reddit and a few surprises. Let’s dig in.

The biggest change is the introduction of Mailbrew

Mailbrew comes in to complement News Explorer as a tool to help me more efficiently consume information that needs my attention. I’m really in love with this service. Please read my Mailbrew review here.

The side effect of the Mailbrew addition is that I’m reconsidering my use of Mailchimp. I’m currently suggesting my newsletter subscribers switch to my new newsletter coming out of Mailbrew, which is much more complete and better looking. It gathers my blog posts from my main blog’s RSS feed and posts coming out of Micro.blog’s RSS feed. I’m closely monitoring the situation. I’ll see how it goes.

My blogger workflow as of 2020-05

Apple’s News for my content distribution

As I write this third workflow update, I’m still waiting for Apple to approve my feed submission, more than three months after my submission. Some people think Apple no longer allows user-generated content. Too bad. I decided to remove the service altogether from my workflow diagram for now. Who news Apple anyway, right?

What about Reddit

Curiously, I forgot to mention that my blog posts are cross-posted to my subreddit named /numericcitizen. I’m using IFTTT for this. For those who consume their content from Reddit, they can subscribe to my subreddit.

Cross-posting from Micro.blog to WordPress

The thing that I like the most about Micro.blog is its simplicity. It is very easy to post new thoughts, comments, etc. Sometimes, I want to put something out there without all the fuss and requirements of WordPress, like tags, SEO edits, feature images, etc.

But, for some of my posts on Micro.blog, I want them to appear on my main blog too. I recently experimented with a few things with IFTTT and a WordPress plugin to automate this task. But in each case, I didn’t like the results. On top of that, the WordPress plugin that I tried has not received an update in more than two years. There are some bugs with my current version of WordPress, which is 5.4.1. For me, it’s a no-go.

I decided to use a manual process with MarsEdit. This venerable macOS application is simple and can post to WordPress and Micro.blog. The latter is currently being added to an upcoming version. So far, it is working fine for me.

Cross-posting with MarsEdit means copy-pasting my text from one place to another and hitting the “post to blog” button. Simple enough.

Another tiny but really useful addition: Pager for Reddit

A bit like NewsExplorer and Mailbrew, Pager is an application that works for me in the background. The Pager app helps me stay updated with content I care about on Reddit. I should probably write a separate review. The design of this iPadOS application is great. Setting up filters is easy. It’s been a while since the last update; my hope is that this app is still being maintained. It’s a really cool app, and it is free!

An unexpected change of behaviour

As you probably know by now, Apple recently introduced a few new things regarding its iPad product line: iPadOS 13.4 with complete support for mouse and trackpad and the Magic Keyboard. These two simple things are unexpectedly changing my workflow. I happen to work much more often on my iPad than I used to. Second, my usage of Notion diverted my time spent in Ulysses. Notion is not a text processor per se, but it can act as one. I write most of my text in Notion and do the final write-up in Ulysses when I’m done with my research and my ideas are fully written down. Overall, I spend less time in Ulysses, but it’s still an essential application in my workflow.

Final words

I feel my blogger workflow is stabilizing a bit. No major changes are on the horizon, which is a good thing. Now, I’m concentrating on the content.

Initially published a month ago, my blogger workflow received a lot of traction, and since then, I made a few important changes. Today, I want to address how I consume content and which tools I use to support my research.

A significant change was made to how I manage and consume RSS feeds. I recently switched from Reeder to News Explorer (read my review of News Explorer) because of the more powerful features available, as I wrote in my review. Because of this change, first, I no longer need to depend on Feedly for my synchronization service. Second, I can more easily keep track of VIP tweeps or YouTube channels.

A fundamental change is integrating Notion.so to help me as a blogger. I no longer rely on Apple’s Reminders for bookmarking internet stuff I want to blog about. And Notion is so much more powerful than Raindrop.io. Expect a review of Notion in the near future.

Flipboard and Tumblr were also added as new publishing conduits for those who prefer these platforms. As of this writing, I’m still waiting for Apple to approve my submission. Rumours are circulating that Apple no longer accepts user-created content for News. If true, I think it is a missed opportunity for Apple.

Two apps that I use a lot made their apparition on the workflow: Linky and Birdbrain. The former is used to generate visual quotes like the following one. The latter helps me manage the Twitter followers or tweets that I follow.

Other improvements to come

I would like to see better support for Apple’s Shortcuts in Notion.so app and Micro.blog. Another thing that I would like to see is the support of Micro.blog in Linky, which currently only supports Twitter. I asked the developer about it, and he said we were often asked about this. My fingers are crossed.

If you are a blogger like me, you may find it interesting to learn about what tools other bloggers are using. If you are not (yet) a blogger, you’ll see what it takes to start and thrive! As a long-time blogger, I’m happy to share all the details about my workflow with you. You’ll learn about the tools I like to use and the relation between them. Let’s dig in.

Two platforms and a social network

For my blogging needs, I rely on two blogging platforms: WordPress and Micro.blog. They have their own purposes.

My main blog (“Numeric Citizen Blog”) is hosted on WordPress.com. The design is based on the Baskerville 2 WordPress theme¹. As a paying subscriber to the WordPress Business Plan, my readers get an ad-free website.

Recently, I decided to lower the frequency of new posts in order to publish longer ones. For shorter posts, I’m now using exclusively micro.blog (see “The Return of Micro Blogging ?”). I’m quite happy with my choices. WordPress is well known but micro.blog is quite marginal. This platform is simple to use, looks a bit like Twitter but doesn’t have all the noise and there is no advertising. There is a choice of native macOS or iOS clients, too, which is mandatory for me.

As you can see from the workflow diagram below, Twitter is the only social network that I use to reach out to potential readers. Posts from micro.blog and WordPress get cross-posted automatically to Twitter. This is another way of reaching more people, especially with the use of hashtags.

Because of my use of Micro.blog, I rarely publish directly on Twitter these days. I prefer micro.blog for this purpose. With automatic cross-posting to Twitter, I save time and reach both communities with a single post which is nice.

I don’t use Facebook, for well-documented reasons (see “My Final Post On Facebook”). I’m not on Pinterest either, as my blog content doesn’t fit this platform. I used to be on Tumblr a few years ago with many smaller blogs, but I decided to leave this behind (see “Bye Bye Tumblr”). Will I return? It depends. The future of Tumblr is now in the hands of Automattic, the owner of WordPress.com (see “Automattic buys Tumblr from Verizon for reportedly less than $20 million”). I’ll see.

Publishing services

Blogging is cool, but being read is even better! That is why I’m using a few publishing services to reach more people. From time to time, I manually cross-post my most important pieces on Medium. I’m part of the Medium Partner Program, which gets me a few dollars here and there for my content but nothing to pay the bills.

I’m also relying on Google News albeit with fewer expectations to reach out to readers. On top of this, I’m waiting for the approval of Apple’s News service and Flipboard to go live. I don’t expect too much traction from these services, though. I see them as complemental tools to reach audiences where they are. The effort to put them in place is very low, so why not? Think of this as experimental.

Supporting tools

As you may already know, I’m very much invested in the Apple ecosystem. As such, I’m using the Mac, the iPad or the iPhone as a writing or creation tool. To enable this movement between all devices, I rely on multi-platform support for most of my supporting apps. From Ulysses (see “Switching to Ulysses for my Writing Needs”) to Adobe Spark (see “My Review of Adobe Spark Post”), I can use all of these on all my devices. Apple’s iCloud is the syncing service that ties it all up, and it works without an itch².

The journaling app DayOne plays an important role behind the scenes. This is the tool that I use to archive my published content. Very cool stuff. (see “Documenting My Numeric Life”).

A less-known web service called CrowdSignal allows me to create polls and gather feedback for my blog posts. Each blog post can be rated, and the results are accumulated on CrowdSignal. As of this writing, the post’s rating is at 4.5 / 5.0, which is not bad at all! This service, owned by Automattic, is free of charge, which is cool.

WordPress is an open architecture that allows the development of plugins. I use a total of 26 plugins that complement the basic WordPress features. One example is a Buffer plugin, which will put every post on my Buffer queue in order to repost a reminder about content published on my blog to Twitter a few days later. Another plugin is Google Analytics, which provides a dashboard of the visitor’s statistics on my WordPress Admin page, which is very handy. Finally, I’m using a plugin that cross-posts content to Apple’s News Service³.

Quality control

To improve the quality of my posts, I rely on two important tools: Grammarly and Yoast SEO. I pay for these because I think the quality is mandatory. Don’t forget, I’m French-Canadian, so I need help improving my English. Both of these plug-ins are doing a great job. Grammarly is available as a browser plugin, as a standalone application or on the web. I wish I could use it within Ulysses, but plugins are impossible on iOS. Because of that, the final proofing is done on the web, not within Ulysses. Finally.

Yoast is a WordPress plugin and works in the background while editing a new post. It helps me optimize my blog posts for search engines⁴. The following screenshot is Yoast in action while editing this post.

A few words about my blogger routine

Each morning, I spend about 45-60 minutes to work on many things related to being a blogger. It can be reading, searching, designing, testing, writing or publishing. I do spend even more time during the weekends. Overall, five to ten hours per week of hard work. That is a lot, but it is rewarding. This time is on top of what I spend on my other passion: photography.

Miscellaneous notes and room for improvements

Finally, on the workflow diagram, you’ll find all the paying services or applications with a green dollar icon. I spend over $500 annually on this blogging adventure, but I think it is worth it. If you want to encourage me, feel free to give me some tips or become a paying member of my blog⁵. It is less than the cost of a Starbucks coffee. Think about it.

RSS feeds are an important tool in my blogger life. I use them a lot to stay in touch with my sources. But I also enable them on my blogs as I think they facilitate content diffusion and consumption (see “To all content creators: RSS feeds as facilitators, use them!”).

There is one place where I think I’ll change the tools that I use. Look for the yellow box on the diagram. I’m in the process of reconsidering Reeder as my RSS reader and replacing it with something else⁶. I want to get rid of Feedly altogether. Because Google dropped support for Google’s Reader service, I had to migrate to Feedly.

Last words

If you think I could improve something in this workflow, feel free to make any suggestions in the comments section. I would be glad to read from other bloggers.

If you want to know why I do all this, read my “Why This Blog” page. If you have any questions, please use the comments section and don’t be shy about asking! I’ll be more than happy to provide answers.