#Markdown pro archive
#Markdown pro code

It’s possible to work with the same version of a file between multiple iOS apps now. As a side benefit, relying on GitHub for collaborative editing has resulted in a third layer of backups for my drafts and it’s making me consider GitHub as an internal wiki tool to create nicely formatted Markdown guides for the MacStories team. Working Copy and GitHub have enabled us to be faster and more consistent at proofing each other’s stories with a fantastic set of integrations on iOS.

I wouldn’t be able to switch to any other collaborative Markdown environment now.

#Markdown pro archive

Every week, I archive old GitHub documents from Textastic on iOS, committing changes in Working Copy with GitHub notifications that are delivered to multiple Slack channels at once – no Mac involved. I don’t have to create duplicates or copy files around with extensions. As long as a file can be shared with extensions, we can commit it to our repositories with Working Copy.Ĭhanges made in Textastic (left) are reflected in Working Copy’s repository.Īs with open mode in iA Writer, any change I make in Textastic is saved back into Working Copy thanks to the iOS document provider API. This allows us to save Markdown documents from any text editor, screenshots from an email client or the Photos app 12, and so forth. Working Copy lets you commit (save) files from other iOS apps with a share extension. Working Copy is one of the apps I’ve used the most this year and it played an important role in convincing me GitHub was the right service for us. Working Copy is a power-user GitHub client with Markdown support, app integrations, automation features, and ongoing support from its developer. My favorite GitHub client for iOS is Working Copy by Anders Borum. Fortunately, there are great GitHub clients for iOS with a proper GUI to manage repositories and commits, making the GitHub experience on iOS visually appealing and integrated with iOS apps. Most programmers interact with GitHub from a command line interface (CLI) on desktop computers, which isn’t exactly user-friendly much of the GitHub terminology is already quite obscure, and using the service from a terminal only adds to that complexity. We have a general Club MacStories repository that John and I use to assemble issues of our newsletter every week, and I also have a personal repository where I save drafts I would like others to read in advance. Other members are invited to the repository so they can read each other’s stories and provide feedback.

#Markdown pro code

The same principles that allow programmers to host their code on GitHub can be used for collaborative Markdown writing, which is what we’ve done through several GitHub repositories.Įach MacStories writer has their own private GitHub repository where they can save drafts of articles currently being worked on. At a fundamental level, however, GitHub deals with text and compares differences between versions of the same text file. GitHub is mostly known as a code hosting platform that enables programmers to collaborate on code and keep track of changes in shared projects called repositories. This is how we’ve been collaborating on stories – including my iOS 10 review – throughout 2016 for both MacStories and Club MacStories, and I couldn’t be happier with it. The system we’ve been using over the past year relies on GitHub and has native support for Markdown and iOS. For a while, if we wanted to check out a story someone was working on, we had to exchange files, create duplicates, and then compare differences between two text files with a diff tool on the Mac before sending the annotated version back. Over time, as the MacStories team expanded and multiple writers had to provide feedback on drafts, my stance on not using collaborative rich text services was becoming a hurdle for everyone. I like plain text and John Gruber’s invention so much, we even rebuilt MacStories to accept native Markdown text for every post. Unlike most tech publications, we never collaborate on articles using Word or Google Docs because I don’t want to deal with rich text or HTML code. Markdown and plain text are also easily scriptable, which saves us time when editing stories. We appreciate the portability of plain text and how it enables us to try different text editors for iOS and macOS. Here at MacStories, we like to write in Markdown. Longform Writing and Research with Scrivener 10.Email Management with Airmail and Sanebox 6.