-
-
Notifications
You must be signed in to change notification settings - Fork 553
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
Make furo sage standard doc theme #33833
Comments
This comment has been minimized.
This comment has been minimized.
Author: Kwankyu Lee |
Branch: u/klee/33833 |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Dependencies: #34252 |
This comment has been minimized.
This comment has been minimized.
Changed branch from u/klee/33833 to none |
Changed author from Kwankyu Lee to none |
This comment has been minimized.
This comment has been minimized.
Changed commit from |
Changed dependencies from #34252 to none |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:13
It looks like that after these refinements, the new theme may be ready to become standard. How about a sage-devel vote? |
This comment has been minimized.
This comment has been minimized.
Branch: u/klee/make-furo-standard-theme |
Commit: |
comment:16
I don't see this a problem:
and removed it. Last 10 new commits:
|
This comment has been minimized.
This comment has been minimized.
comment:65
Replying to @mkoeppe:
The policy should be mentioned here: https://doc.sagemath.org/html/en/developer/packaging.html#prerequisites-for-new-standard-packages |
comment:66
Then could it be that furo is still the default when we build sage from source? |
comment:67
We'd need to add the Python packages that are needed for building furo from source. But I'm not sure if that solves the problem completely because one of these dependencies is |
comment:68
I'd suggest that we back out the change to "standard" from this ticket and pursue the path to make it a standard normal package on a separate ticket |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:70
Anyway here's the branch with all the dependencies - and it does have the problem that I thought:
(it's trying to download Node.js from the internet, which fails because our installation poisons the https proxy) |
comment:71
An alternative direction would be to install furo from a wheel. We don't have a mechanism for that yet, but it would not be very hard to add. This would avoid the complicated nodeenv business (which is only needed for from-source build of furo). I've opened #34450 for this |
comment:73
Try this |
comment:75
Replying to @kwankyu:
I've added it to the documentation in #34450 |
Changed branch from u/mkoeppe/make-furo-standard-theme to u/klee/make-furo-standard-theme |
comment:78
It works well. Thank Matthias! New commits:
|
Changed reviewer from Matthias Koeppe to Matthias Koeppe, Kwankyu Lee |
comment:79
The branch also passes Volker's test. |
comment:80
Great, thanks for testing! |
Changed branch from u/klee/make-furo-standard-theme to |
In #33601, the furo theme has been introduced for the documentation. The aim of this ticket is to make it the standard theme. Before it happens, the remaining issues need to be fixed:
To support this ticket, the standard Furo package was accepted by the voting done in
along with subsidiary votings in
Other possible improvements:
Depends on #34252
Depends on #34262
Depends on #34265
Depends on #34267
Depends on #34450
CC: @kwankyu @strogdon @haraldschilly @mkoeppe
Component: documentation
Author: Kwankyu Lee, Matthias Koeppe
Branch/Commit:
1f03957
Reviewer: Matthias Koeppe, Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/33833
The text was updated successfully, but these errors were encountered: