2022-07-29 08:30

Making YouTubes Videos - Observations & Notes

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 videos creation workflow. I’m using a template for each new video with things to do, research notes, documentation, video script, 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 in order to prevent overheating. On the Mac mini, there is no such thing and 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 rate.
  • 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 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.

View comments Craft Tools YouTube
2022-05-25 08:30

I’m Ready to Move This Website to Craft

Numeric Citizen I/O hosted within Craft document.

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.

View comments Craft Tools
2022-05-17 13:00

Proof of Concept With Craft

I recently published an article about the possible death of Blot.im in the future. It made me think about alternatives. I’m currently in the process of testing Craft and its Share Page feature to migrate from Blot.im to Craft. You can see the work-in-progress website here.

View comments Service Craft Blot Meta
2022-02-15 08:00

On Migrating WordPress Content to Ghost

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
WordPress export with selected content plugin in action
  1. Switch to the WordPress instance running on the Synology NAS
  2. Select Import from the Tools menu
  3. Select the XML file created from the Export step earlier
  4. Set the author for the imported posts
WordPress import plugin in action
  1. Set the Download and import file attachments to bring in images
  2. Click Submit and wait for the process to complete (it takes some time, depending on the number of posts and images to import)
  3. Verify if all posts are listed in the Posts section (check creation date, author, etc.)
  4. Check for Media Library to verify if images are imported
  5. Open a few posts to see if content is correctly formatted
  6. Edit posts with back links or other elements that need to be updated before importing content into Ghost
  7. Edit tags according to the destination website requirements
  8. Edit post slug and post title according to destination website requirements
  9. Export using Ghost Migrator plugin, select the JSON format since ZipArchive module isn’t installed with this version of WordPress and PHP
Ghost Migrator plugin is pretty limited in functionality
  1. Import JSON file created in the previous step
  2. Check for imported posts issues. This is where I hit the wall. Missing photos, content imported as HTML blocs, etc. Not great at all.
Images are missing in imported post
Posts from WordPress are imported in HTML block in Ghost which is not good
  1. 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.


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.

View comments WordPress Ghost Service CMS Data Mobility
2021-12-18 17:00

My Blogger Workflow As of 2021-12

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

My blogger workflow as of 2021-12

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 one of the most important additions this year are Toggl, Timery, and Focused Work to track my time while creating content (consider bookmarking and read 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 with the 14 days trial period where 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 reasons. I quickly found out that many features like custom themes, custom integrations, 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 theme. 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 added to enable Commento integration. Forking such a builtin theme requires staying in sync with the official theme, as Ghost update them from time to time to benefit from all Ghost’s additions. Finally, I paid a visit to 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 need (consider bookmarking and read 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 a Readwise as a source to my weekly newsletter built using Mailbrew.
  • Using Readwise sharing feature to repost quotes on Twitter is handy. I don’t use it too often, though.
Sharing a Readwise highlight
  • 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 create Also on my …” type of blog posts automatically. It didn’t generate much traction and added too much noise in 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 gain 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 things to watch in 2022. Finally, Typefully brings great engagement analytics
Typefully 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 read Migrating My Content From Hey World to Substack). I can say the same thing about my Substack experience. These services, while being 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 doesn’t happen there anyway, even if HEY provide a newsletters dedicated feed, one of the tent pole feature of the mail client.

  • Substack is out as mentioned earlier. The popularity of a platform doesn’t guarantee the popularity of your content.

  • I closed my Telegram account, read more here to know the reasons 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. Too bad because on paper the idea is cool.

  • I’m always thinking about my use of Apple’s Reminders in my workflow. Reminders has improved quite a lot over the years, but occasionally, I think Craft could take over if tables 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 I’ll make a move.

    Things to Improve

  • The addition of 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, the implementation of this feature could be tricky. Where should we be able to tag things actually: In a page’s properties, inline in 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.


  • 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 Craft calendaring feature to prepare a weekly planning which contains 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 for pumping my data out of Notion, I might be done with Notion once and for all. Notion is not shown on my workflow diagram, but it will in an upcoming post about 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 too. 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. It doesn’t help at all. Even if cross-posting is done automatically using WordPress builtin 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, this is hosted on Ghost, with my Friday Notes Series and my 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 visitors 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 that I post on Reddit, to my Twitter channel on Buffer. There is a new calendar view in Buffer which helps see a timeline overview of all future publishing. Buffer isn’t cheap, but I like what it does for me. Cross-posting content do help create traffic and improves engagement.

Well, that was a long one. For an upcoming article, I want to walk you through my reading workflow. I do read a lot of stuff online, and many applications and services are at play 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.

View comments Workflow Tools Craft Blot Toggl Timery WordPress Ghost Readwise Matter Meta
2021-12-02 07:00

Moving From Substack to Ghost — My Experience

Digital nomads. Flavour of the day. Looking for a better digital experience. Every reasons are 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 have a look and see how it is evolving over time. Following those two blog posts, I got back to one of my article about a past experience with Ghost for photo sharing. At the time, it didn’t go well. Furthermore, for unknown or clearly defined reasons, I started using Substack to host my newsletter. So, this time around, I came back to Ghost to look at it has 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 or because Substack is very popular these days.
  • I prefer the way Ghost is handling 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 in Ulysses each new issues would be much easier to put together as Ulysses supports templates., Substack doesn’t. Since the basic structure of my newsletter stays the same each month, using a template makes full of sense.
  • Substack offers some visual customization options, but they are quite limited. On the other hand, Ghost offers themes which helps a lot to 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 something not possible with Substack. Another must-have for me.
  • Stripe integration which I already use for Medium payments if I ever chose to make 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 setup 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 possible only via RSS feeds. As a paying member of IFTTT, I chose the latter.
  • Better RSS feeds support on posts, tags, 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 just 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 while using the 14-days evaluation period, it was clear that I had to.

How Ghost Could Be Improved for Me?

One of the most powerful and useful features of the Ghost editor is the ability to create and re-use content snippets. If you’ve ever used an email client with a concept of saved replies then 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. Export my data from Substack — this took less than 10 minutes to complete. Substack makes this super easy to do.
  2. Import my subscribers list into Ghost’s members list.
  3. Download Xcode from the Mac App Store, launch it for default configuration (required for the next step).
  4. Install Homebrew in order 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 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 falseA 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. Once the import is complete and without error, configure site pages and tags.
  9. Review imported content and set tags according to each post 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 in order to get in touch with me.
  11. Connect my account Ghost 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 reason I switched from Substack to Ghost, right?
  13. Do a test run with a fake article, check RSS feed content generation.
  14. Configure the support and reply-to email addresses.
  15. Setup Plausible analytics and add it to my Ghost website using the customization feature, in the header section.
  16. Update all my IFTTT automations for when a newsletter issue comes out for cross-posting to Twitter via Buffer.
  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 which is not available 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. You can subscribe to my free newsletter by going to the website: https://numericcitizen-introspection.blog.
View comments Ghost Service Substack How-To