[Bug]: Remove gh-pages branch
wuda-io opened this issue · comments
Before submitting...
- I have searched for duplicate or closed issues.
- I have read the CONTRIBUTING document and my issue is following the guidelines.
- I have read the template completely before filling it in.
Context
What is the purpose of a seperate gh-pages branch?
I think it is better to keep the documentation on the main branch.
I would open a PR soon to remove this branch and keep it in main. What do you think?
best regards
Current Behavior
Some Links are cross-refrerenced between the gh-pages branch and the actual main branch.
Expected behavior
When changing the domain the links, stylesheets and javascript should be loaded from the same
server or at least the same branch.
Possible Solutions or Causes
- Remove gh-pages branch and adapt workflows to the same branch.
- (Create seperate Repo for documentation) not preferred
Steps to reproduce
No response
Your Environment
- Version used: 1.2.2
- Browser Name and version: firefox, chrome
- Operating System and version (desktop or mobile): ubuntu
- Additional information you want to tell us:
Ok, I saw at bootstrap that they also have a gh-pages branch.
So I figured it would make sense to compile old versions of the docs too maybe in future.
I think we should keep the gh-pages branch and fix the links instead... i will check this.