{"id":76351,"date":"2019-04-05T10:50:56","date_gmt":"2019-04-05T17:50:56","guid":{"rendered":"https:\/\/cloudblogs.microsoft.com\/opensource\/?p=76351"},"modified":"2025-06-27T09:21:44","modified_gmt":"2025-06-27T16:21:44","slug":"publishing-github-pages-from-azure-pipelines","status":"publish","type":"post","link":"https:\/\/opensource.microsoft.com\/blog\/2019\/04\/05\/publishing-github-pages-from-azure-pipelines\/","title":{"rendered":"Publishing GitHub Pages from Azure Pipelines"},"content":{"rendered":"\n

Do you work on or maintain a project for technical users? A key part of attracting users, especially to an open source project, is publishing great documentation. However, keeping it up to date as your APIs and concepts change can be challenging or just time-consuming.<\/p>\n\n\n\n

A popular way to maintain great docs is to keep them in your project\u2019s repo. Often they\u2019re built from some kind of easy-to-edit source format (like Markdown) and rendered as HTML. Once you\u2019ve built the HTML, where do you publish it? For open source projects on GitHub, a seemingly obvious choice is GitHub Pages<\/a>.<\/p>\n\n\n\n

GitHub Pages will automatically handle building Jekyll content for you. In my case, however, I want to generate my own HTML. First, I\u2019ll show you what I set up in my own GitHub repo. At the end, I\u2019ll walk you through building and publishing your own GitHub Pages using Azure Pipelines.<\/p>\n\n\n\n

What we\u2019ll need<\/h2>\n\n\n\n

We\u2019re going to need:<\/p>\n\n\n\n