Repository navigation
Test website: Grouping in navigation bar, relative/absoulte URLs and links to Git Reference and HTML docs #830
Description
Hello.
This is a presentation (and request for comments) of test version of https://git.github.io with 3 separate features:
- link grouping in left navigation bar
- using relative/absolute URLs to git.github.io
- links to "Git Reference" and "Git HTML docs"
Preview site: https://muxajibi4.github.io/git.github.io/
Repo: https://github.com/MuxaJIbI4/git.github.io on branch 'master'
1. Link grouping in navigation bar
see MuxaJIbI4/git.github.io@da0819c
This is done by moving all pages (except /rev_news) to new /links folder and subfolder inside determines page's group (defined using scope in _config.yml). Then in navbar.html we show groups titles followed by that group pages. Ordering of groups determined by array nb-order in _config.yml. This approach allows not assign group to each page inside 'front matter'.
Also pages inside one group can be ordered using 'order:' property inside pages of the group.
Also although some pages are moved into /links/* folders their links are not changed because of permalink: option in _config.yml.
Group titles and ordering, assigning group to pages, changed page titles, names of /links folder and subfolders are given only as an example
2. Using relative/absolute URLs to git.github.io
see MuxaJIbI4/git.github.io@135a957
This removes hard-coded domain name from subpages.
Removed only in some files - didn't touch /_posts and /links.
Also did not change direct links to /images folder in /_posts and /links.
3. Links to "Git Reference" and "Git HTML docs"
see MuxaJIbI4/git.github.io@b010429
There are 2 additional websites on git.github.io that don't have any links to them (you can find out about them only from outside sources):
https://git.github.io/git-reference - Git Reference
https://git.github.io/htmldocs - Git HTML docs
So I decided to add them to Navigation bar and to the Main page.
On test website link don't work since they are external websites, but URL itself should be correct.
Question: Can somebody tell how do these 2 websites are being deployed and not being overwritten by deployment of git.github.io?
Activity
chriscool commentedon Mar 2, 2026
Interesting, but I think the 3 different improvements should be made separately in different PRs as they are quite independent. Thanks!
MuxaJIbI4 commentedon Mar 3, 2026
@chriscool I wanted to get preview out but didn't create PR because didn't want to overstep and it was behind main branch. Also I would wait until
mainbranch become stable after rn-132 and maintainers comment/request changes, so I would need to update/rebase commits in PR.Or is my thinking is wrong and I still should have made PR?
Based of comments for answers below I will create new PR from the current HEAD of
mainbranch.1. Questions about navigation groups.
Mass moving of files into /links/* is the cornerstone, so it's required.
Do you approve following changes?
1.1) New folder names (
links,dev,gsoc,outreachy,applicants) and group titles and ordering ("Git Rev News" > "Git Development" > "GSoC" > "Outreachy" > "Applicants"). Or you could have made changes during merging PR into main?1.2) Splitting Historical-SoC-Outreachy.md into separate files for GSoC and Outreachy because of separate groups?
1.3) Ordering of links in "Rev News" group
2. Questions about relative/absolute URLs.
I could do it separately, except it touches 2 files from /rev_news (different lines) from previous commit. It doesn't matter when merging because conflict can be resolved automatically?
3. Questions about links to Git Reference/HTML docs
This commit need to be done after introducing grouping, otherwise links are sorted by filepath (or title?) in descending order, so it become chaotic.
Do you approve following changes?
3.1) Adding both links to Navigation bar
3.2) Adding both links to Main page.
3.3) Adding group "Resources" to the top.
chriscool commentedon Mar 3, 2026
A number of people could give their opinion, and they might only be interested in doing that about one topic. That's why it's better to have 3 different issues and/or PRs. Also it allows the issues to be addressed one by one at their own pace instead of all at the same time.
Edition 132 is published so mostly over. And anyway you don't need to wait for
masterto become stable. Conflicts in a repo like this one are almost always trivial.MuxaJIbI4 commentedon Mar 3, 2026
created PR #834 for navigation grouping. Other 2 will wait.