[ImgBot] Optimize images

[imgbot]

Beep boop. Your images are optimized!

Your image file size has been reduced by 33% 🎉

Details

File	Before	After	Percent reduction
/.gitbook/assets/16779385.png	88.62kb	26.78kb	69.78%
/.gitbook/assets/image (2).png	24.13kb	10.06kb	58.32%
/.gitbook/assets/54266482.png	207.03kb	102.89kb	50.30%
/.gitbook/assets/54266485.png	166.30kb	83.73kb	49.65%
/.gitbook/assets/54266483.png	118.84kb	60.99kb	48.68%
/.gitbook/assets/54266484.png	259.71kb	134.84kb	48.08%
/.gitbook/assets/39125004.png	3.29kb	1.71kb	47.92%
/.gitbook/assets/54266486.png	49.71kb	26.09kb	47.51%
/.gitbook/assets/16779386.png	16.60kb	9.54kb	42.52%
/.gitbook/assets/54266481.png	377.53kb	225.88kb	40.17%
/.gitbook/assets/39125010.png	38.11kb	22.90kb	39.91%
/.gitbook/assets/51840083.png	383.57kb	243.73kb	36.46%
/.gitbook/assets/image (1).png	18.41kb	13.03kb	29.26%
/.gitbook/assets/image.png	18.41kb	13.03kb	29.26%
/.gitbook/assets/image (3).png	18.41kb	13.03kb	29.26%
/.gitbook/assets/54266480.png	100.81kb	74.05kb	26.54%
/.gitbook/assets/54266487.png	352.92kb	263.81kb	25.25%
/.gitbook/assets/23037808.png	32.07kb	26.35kb	17.85%
/.gitbook/assets/improve the documentation (1).png	114.75kb	95.70kb	16.60%
/.gitbook/assets/improve-the-documentation-1-.png	114.75kb	95.70kb	16.60%
/.gitbook/assets/translation (many pages) (1) (1).png	96.57kb	80.57kb	16.57%
/.gitbook/assets/translation-many-pages-1-.png	96.57kb	80.57kb	16.57%
/.gitbook/assets/translation (many pages).png	94.35kb	78.93kb	16.35%
/.gitbook/assets/translation (many pages) (1).png	94.35kb	78.93kb	16.35%
/.gitbook/assets/translation-many-pages-.png	94.35kb	78.93kb	16.35%
/.gitbook/assets/translation-many-pages- (1).png	94.35kb	78.93kb	16.35%
/.gitbook/assets/build-puffin-writing.png	22.86kb	19.54kb	14.51%
/.gitbook/assets/puffin-2x-2-.png	68.55kb	60.58kb	11.62%
/.gitbook/assets/Puffin@2x (2).png	68.55kb	60.58kb	11.62%
/.gitbook/assets/bullet_blue.gif	0.06kb	0.05kb	10.00%
/.gitbook/assets/23038066.png	29.65kb	28.46kb	4.01%
Total :	3,264.18kb	2,189.89kb	32.91%

---

📝 docs | repo | 🙋🏾 issues | 🏪 marketplace

~Imgbot - Part of Optimole family

[pull-request-quantifier-deprecated]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 0

Change summary by file extension:

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.