[Feature] Support for multiple pages from the same repo

[felhag]

Select Topic Area

Product Feedback

Body

Hey,

I use github pages for some of my projects which works really well. One my repositories is creating two artifacts which I want to deploy to two different domains. The only way I can achieve this now is by duplicating my repository. I think it would be a great feature for Github Pages if we can deploy multiple branches to multiples pages. For example:

Note: This feature was already proposed in 2020 with this ticket. @yoannchaudet advised to open an issue in this community, so here we are :)

[codebydant]

This will be really important for monorepos where we have docs folders in different locations in the repository. We will be able to choose each path in the main branch to deploy a readthedocs github page per subproject.

[bethac07]

Another thing this would be really nice for - multilingual sites! Right now, we have content we can publish to different branches for different languages, but can only serve one as a "live" page.

[TheQueenIsDead]

That would require that you merge singular changes to common components across multiple branches. Imagine trying to update your favicon.ico with 25 internationalisations. 25 pull requests.

It would likely be wise to use i18n functionality that is already provided, for example:

• Hugo https://gohugo.io/functions/i18n/
• Vue https://www.npmjs.com/package/vue-i18n
• Angular https://angular.io/guide/i18n-overview

Most frameworks have the ability to do this for you

[bethac07]

Most do, but JupyterBook does not have first-class support for this, at least not yet! This is a good workaround until it does, as long as the number of languages is, as you point out, not huge

[nicfv]

I think it would be a great feature for Github Pages if we can deploy multiple branches to multiples pages.

I like this. It should even be generalized to supporting multiple pages in a single branch. For example if I have my main app in dist/ and documentation in docs/ (in the same branch), I may want to publish the app to example.com and documentation to docs.example.com. I could see this work well as a setting in the Deploy Github Pages action.

[rngadam]

In addition to deploying to different domains, this feature would also helpful if we need to have versions at different stages of development (dev, uat, prod).

[what1s1ove]

Something similar... but native support would be more desirable!
https://github.com/marketplace/actions/deploy-static-app-in-branch-to-gh-pages

[SergeyRoyt]

Found the solution for Github pages with multiple subfolders here
https://github.com/github/docs/discussions/26012#discussioncomment-6203134

Single branch, multiple directories with different websites with URL route navigation between them - good enough for my case

[nicfv]

This is not bad, and definitely works for some implementations, but it's got a few limitations.

1. This forces you to have everything in the same branch, which is one of the issues brought up in this thread.
2. To me this feels more like a single website rather than 3 separate ones. I don't think doing it this way will allow you to assign a custom domain for each of these subdirectories, so you're stuck with this structure: user-name.github.io/repo/<website-name>

Either way, thank you for sharing this solution!

[what1s1ove]

Yeah... the main problem is attaching the domain

[nauderuan]

Broken link?

[TWiStErRob]

@nauderuan not the original but probably along these lines: https://stackoverflow.com/a/41879114/253468, same solution as described by @SergeyRoyt below the link.