![]() 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |