MS

Hello, I’m Michael Sliwinski, founder of Nozbe - to-do app for modern teams. I write about productivity, #NoOffice, #iPadOnly and I believe that work is not a place you go to, it’s a thing you do.

Why in any company you should be using version control for anything - how we use Github not only for code, but also for writing!

🏝NoOffice ,📱iPadOnly

At Nozbe among all the apps we use to run our company, we also take advantage of Github’s implementation of Git - the version control system - because when many people work on code, things can quickly fall through the cracks if you’re not using a version control system.

Why in any company you should be using version control for anything - how we use Github not only for code, but also for writing!

I originally posted this on my NoOffice blog

Git in a software company is nothing new, but recently we started using Git for more things - especially for writing content… and now everyone on our team knows how to do it! And thanks to the Working Copy app I can work like this on my iPad Pro, too. Here’s the setup and the inspiration:

How we started working with Git for writing… our main Nozbe page

When we decided to redesign our Nozbe web page a year ago, we wanted not only a faster and more responsive web site, but also a place where many people could quickly edit things and not overwrite each others’ changes… so we went with Hugo which is being published to our servers directly from a Github repository.

This way we get all the benefits of using Git:

We all had to learn Git and Github

The downside of all this was that everyone in our company had to learn how to use Git and Github if they wanted to contribute to our site. And this can get very technical and very tricky. Yes, it was a learning curve in the beginning and we had to write internal manuals for folks so that configuring this locally would be as painless as possible.

I had to also figure out how to configure this on my iPad Pro and thanks to the Working Copy app it was possible - now that’s a real Pro app right here.

We went further with Github… and applied the same principles to our help page

Again, our Nozbe help page needs to be edited frequently to stay up-to-date and we need to be able to do it in many languages. After trying different help page solutions we finally settled on building our own, again using the same technologies we used for our main web site - Hugo and Github.

As everyone on our team has already figured out how to write in Markdown, how to commit and push things to Github… it was pretty straightforward and the team is really happy we went with this approach :-)

Now we’ve also started using Github for drafting texts in our Marketing department! Before we were using Dropbox…

Up until now we used to draft texts and blog posts by putting them in a shared Dropbox folder and it worked fine. Everyone had access and they could use any app they wanted to edit the texts written in Markdown.

But…

It was hard do track changes. To see who’s changed what in each text… and to make sure nobody was working on the same document at the same time…

This unfortunately created some strange habits of creating copies of texts, additional drafts… a mess.

But there’s a solution - and it came from Federico Viticci

Please check out Federico’s article where he gets into details, but apparently, the Working Copy app has this great feature that you can sync an iCloud folder to it and later push it to a remote repository… so this is exactly what I did! And the sync works both ways, so when someone changes a file remotely and I sync the repository in Working Copy, it’ll automatically be visible on my iCloud Drive!

So this is what I did:

Thanks Federico for this tip and thanks Working Copy for being an amazing Github client which is constantly updated to use the latest and greatest iOS APIs.

Git and version control is a way to go!

Yes, you should use Git. And not only in an all remote team like ours, but I think in any team when people are working on different computers and want to get things done together!

I’m so happy that in my team everyone embraced this and now we’re updating our sites and writing texts in the most collaborative way possible.