![]() ![]() Up until now we used to draft texts and blog posts by putting them in a shared Dropbox folder and it worked fine. 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.Īs 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… We went further with Github… and applied the same principles to our help pageĪgain, 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. 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. 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. And this can get very technical and very tricky. 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. we can write in Markdown and publish as HTML which makes working on texts easy! (Actually, I’m writing this blog post in Markdown to later publish it as HTML, too…).we can add and correct translations easily (our site supports 11 languages!).we can create pull requests (to experiment with different versions of the site).many people can work on the site content at once.This way we get all the benefits of using Git: 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. Here’s the setup and the inspiration: How we started working with Git for writing… our main Nozbe page 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. I originally posted this on my NoOffice blog 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |