Wiki + Readme: MD security and improvements

[ianalexis]

• Standardized MD GitHub Wiki format
• Removed outdated and malicious links.
  • Removed the fake sites from the main README because listing them poses a real risk.
    Search engines like Google can crawl and index these URLs, potentially treating them as legitimate resources. This can lead to accidental promotion of malicious sites. To avoid this, I replaced the list with a simpler CAUTION message and added clearer, more prominent official links and badges.
• Modularized calibrations
• Suggested calibration order added
• Minor bug fixes
• Image improvements and corrections
• Added winget commands
• Completed previous WIPs
• Added new WIPs
• Removed obsolete references

Description

To deprecate #9370 and utilizing the merge from #9383.

[Noisyfox]

Looks good overall. Some small issues need to be fixed.

[Noisyfox]

LGTM, thanks!

[StdVectorBool]

Can someone else confirm if from the wiki clicking on the Pressure Advance guide now opens up the raw.githubcontent link so it doesn't actually render rich text.

[Noisyfox]

Yeah I noticed that too. Also images are broken too.

[ianalexis]

Can someone else confirm if from the wiki clicking on the Pressure Advance guide now opens up the raw.githubcontent link so it doesn't actually render rich text.

Maybe the wiki builder bot?

[Noisyfox]

I think the links in those files have to follow sepcial rules to make it work for github wiki?

[Noisyfox]

https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#relative-links

@ianalexis I think this was the cause

[ianalexis]

https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#relative-links

@ianalexis I think this was the cause

Mm I think I know what to do. Tomorrow will try to put a new pr with it.

[ianalexis]

images are broken too.

Its really strange, in some cases ./images works just fine and others it doesn't.
The best "standard" and updateable way is to reference the link with raw like ![tab-popup](https://github.com/SoftFever/OrcaSlicer/blob/main/doc/images/tab-popup.png?raw=true) so i will change all the broken ones and if that works i will try to standarize everithing like that becouse there are a lot of links like ![image](https://user-images.githubusercontent.com/103989404/215334900-97c75010-4752-45f1-a57c-f0b723a8cb3f.png) that will never update if someone push a new file.

[ianalexis]

@StdVectorBool @Noisyfox check #9858

[Noisyfox]

Its really strange, in some cases ./images works just fine and others it doesn't.

Maybe use /doc/images/xxxxx instead? Since "The path of the link will be relative to the current file." so if you use ./images you must make sure the .md file is at the same dir as the images folder.

[ianalexis]

Its really strange, in some cases ./images works just fine and others it doesn't.

Maybe use /doc/images/xxxxx instead? Since "The path of the link will be relative to the current file." so if you use ./images you must make sure the .md file is at the same dir as the images folder.

Will response it on new PR.

[Noisyfox]

NVM, I'm wrong on this one.

[dewi-ny-je]

I'm happy this got merged.

How should we proceed to improve the wiki further?

1. should I base my comments on the official wiki or a different one, more speedily updated iteration after iteration?
2. where should we discuss it? I'm personally open to a new draft pull, or a dedicated Discord discussion/thread

[ianalexis]

I'm happy this got merged.

How should we proceed to improve the wiki further?

1. should I base my comments on the official wiki or a different one, more speedily updated iteration after iteration?

2. where should we discuss it? I'm personally open to a new draft pull, or a dedicated Discord discussion/thread

I already have new things to do like the:

1. "How to wiki"
2. Full images update
3. Infill Patterns (for this issue Wiki Section for Infill Patterns #9802 ).

For the last one surely i will need help and thats why i was thinking the same.
Draft another PR and maybe make a Discord discussion/thread if you can do it great (im an elder that uses Discord for the basics and never get hoy to create things over there). My discord is titan.boreal

I will make 2 PR now (#9872 and #9873 ), one for discussion and collaboration an another for the things i already done.
If anybody wants to help i always tag user in the commits (so the Commit count for them too) o they can PR my fork and i cherry pick the commits to the one in the PR.