-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improvement: relative links #187
Comments
Hi @Hendrikto , good idea! it looks great for me! |
Great :) Work is already ongoing, but it is a bit more effort than I anticipated, as I have to test whether all links still work. |
I am mostly done with the conversion to relative links. As mentioned above, it was more work than anticipated, as I had to review everything. I found several problems with some ports, which I fixed. I need to review the fixed ports, and some other minor things. Here is a progress report: ReviewGeneral
Documentation
Ports
|
Hi Dalton,
What do you think about making links relative?
If you look at the main branch of my fork, you will see that all of the links to the ports etc. are linking to your personal repo, even for forks of Aura Theme. This means that it is harder to develop new ports and work on the repo, because one cannot easily test whether the links work. Also, it makes it harder to fork the project in general.
It would be nice if one could click on the links in the READMEs, and stay within the same project while doing so. I made the links for the Sway port relative, so this already works for that port on the relative links branch. One can click from the main README through to the Sway port README, and then to
aura-theme.conf
, all while staying within the fork.In summary, making links relative would:
The text was updated successfully, but these errors were encountered: