Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Shrink Documentation #28376

Open
saraedum opened this issue Aug 21, 2019 · 6 comments
Open

Shrink Documentation #28376

saraedum opened this issue Aug 21, 2019 · 6 comments
Labels
c: build c: documentation p: major / 3 t: enhancement

Comments

@saraedum
Copy link
Member

as a followup to #28374 of sorts: Why are we shipping 900+ MB of documentation (600MB zipped)?

CC: @nthiery @slel @haraldschilly @tobiasdiez

Component: documentation

Issue created by migration from https://trac.sagemath.org/ticket/28376
@saraedum saraedum added this to the sage-8.9 milestone Aug 21, 2019
@saraedum
Copy link
Member Author

comment:1

Some experiments:

  • html-minifier shrinks HTML content to 80%-90%
  • converting SVG that contain base64 PNGs to PNG and using pngquant shrinks 3D plots to 25%
  • zipping regular SVGs shrinks them to about 30% but browsers mostly refuse to display svgz.
  • imagemin with mozjpeg cuts most JPEG sizes in half.

Now, I don't want to turn all of these tools into SPKGs but they could be installed with yarn easily.

@saraedum

This comment has been minimized.

Sign in to view
@saraedum
Copy link
Member Author

comment:3

Note that my numbers above (900MB/600MB) come out of the CI. Locally, things might look a bit different.

@embray
Copy link
Contributor

embray commented Dec 30, 2019

comment:4

Ticket retargeted after milestone closed

@embray embray modified the milestones: sage-8.9, sage-9.1 Dec 30, 2019
@mkoeppe
Copy link
Contributor

mkoeppe commented Apr 14, 2020

comment:5

Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date.

@mkoeppe mkoeppe modified the milestones: sage-9.1, sage-9.2 Apr 14, 2020
@mkoeppe mkoeppe modified the milestones: sage-9.2, sage-9.3 Aug 29, 2020
@mkoeppe
Copy link
Contributor

mkoeppe commented Feb 13, 2021

comment:7

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Feb 13, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 18, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 Apr 7, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Aug 31, 2022
@mkoeppe mkoeppe removed this from the sage-9.8 milestone Jan 29, 2023
@nthiery nthiery mentioned this issue Jan 29, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: build c: documentation p: major / 3 t: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@saraedum @embray @mkoeppe