![]() ![]() The script ( available here) takes text shared to it as input, performs the substitutions and prompts you the share menu, ready to export text to Working Copy. ![]() I wrote a little script for Pythonista, a cool iOS app which provides a full Python IDE and environment. Option 1: the built-in oneīefore exporting from iA Writer to Working Copy or committing on desktop, do a quick Find & Replace right in the text editor. Although those aren’t common actions and editing all the posts can be done in batch by a bash script, they break the Jekyll repo concept and best practises.įor this reason, replacing the domain (e.g. While the above solution works fine, it doesn’t fit in case you have to change your website domain or the baseurl. Both BitBucket and GitHub support large file storage. Then, I made another repo and enabled Git LFS on it. With static files online and publicly accessible, I just have to write their url (e.g.) in the blog post to get a working preview in iA Writer (provided an Internet connection, of course). On desktop many options are available, from Cyberduck to command line, on the go there are the free Documents by Readdle on iOS and ES File Manager on Android. Therefore, I excluded static files from the website repo to be able to put them online without needing to commit and to make the repo much smaller. The downside effect of the above changes is I wasn’t able to preview post images in iA Writer, because the path (starting site.baseurl) couldn’t be rendered as a correct and publicly accessible url. It is available as open-source and you might want to start from it in case you decide to go for Jekyll-Blue. So I’ve build a template using the same CSS code from the blog to preview posts on desktop and mobile without committing and pushing. What’s more, their new feature called templates lets you customise the markdown rendering in Preview mode. I really like iA Writer, it’s well designed and makes you focus on what you type. So I decided to leave move on and leave the built-in Working Copy editor for another one which would have improved my blogging experience. It worked fine but the most important part, the writing experience, was not that great. In part 1 I wrote about my basic workflow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |