Random Access Memory.

Using iPad and for blogging on Github Pages

23 October 2021

TL;DR VS Code + Github Pages is great. iPad hardware is good. iPadOS cripples everything.

My blog’s workflow was previously relied on using VS Code on the computer for editing and committing markdown files to Github, which was not conveniently feasible on the iPad.

Now the VS Code is available as a web, it is possible to merge VS Code and Github workflow together on the iPad.

Content Editing

I can just open, coonect to Github and editing files in my blog’s repository. All of my contents were markdown, so I only need a Markdown Preview Github Styling extension to help me preview the blog content before I push to the repository.

The only drawback of this is, I couldn’t use the local Jekyll to preview the draft contents before pushing to Github. But only markdown preview is enough.

Image Editing

On the computer, I used Pixelmator Pro or GIMP to edit the cover images and export them as WebP. Currently all the program I known as tried was not support exporting my edits to WebP. I’ll keep the list updated here:

  • Pixelmator Pro for iPad - does not support WebP export
  • Pixelmator Photo - does not support WebP export
  • Pixlr - does not support WebP export

Last updated 23/10/2021

So currently my cover images editing workflow will be, editing -> export to jpeg -> convert to WebP on a random online JPG to WebP converter.

Publishing to Github Pages

Since VS Code and Github are own by Microsoft, we can expect the harmony between the two. I accidentally close the Safari tab that contain VS Code and the data is still intact.

The issue is on the iPadOS, which is not designed for the multitasking as I familiar on my computer. It makes adding files to the repository is not as simple as drag-and-drop to the VS Code. I need to upload the file to the destination directory on the VS Code.