feat: refactoring + mermaid support & new-docs

[Neilblaze]

Description

• Added Technical Fork into the metrics section.
• Updated Contributing guide (linked Mermaid Diagram getting-started guide)
• Updated Docs (user_docs), added mermaid diagrams for UML figures & shifted default examples into dropdowns.
• Added support for tap-to-zoom on markdown images using image-zoom docusaurus plugin.
• Refactored Blockquote styling to enhance visibility.

Ref : Slack Discussion / cc: @frank-zsy
○ Partially resolves #11 > Deployed URL 🚀

Before submitting the PR, please take the following into consideration

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. If you don't have an issue, please create one.
• Prefix your PR title with feat: , fix: , chore: , docs:, or refactor:.
• The description should clearly illustrate what problems it solves.
• Ensure that the commit messages follow our guidelines.
• Resolve merge conflicts (if any).
• Make sure that the current branch is upto date with the main branch.

[Neilblaze]

Adding a note that, this & this might create a merge conflict, since I forgot performing cherry picking from the update-vX branch (on my local), so simply ignore it by accepting all incoming changes.

[frank-zsy]

/preview

[github-actions]

🪧The website for this PR is deployed at https://open-digger.cn/pull_20/

[frank-zsy]

Oh, I forgot that in Docusaurus we need to set the base URL properly. Will fix the workflow soon.

[Neilblaze]

Haha, no worries! 😄
@frank-zsy I have a worker that deploys from my local everytime I create PR, and for now, you can access the deployed preview from here!

[frank-zsy]

Haha, no worries! 😄 @frank-zsy I have a worker that deploys from my local everytime I create PR, and for now, you can access the deployed preview from here!

Cool, how do you do this in local env? Do you need to modify the base URL on building?

[Neilblaze]

Cool, how do you do this in local env? Do you need to modify the base URL on building?

@frank-zsy It's a very simple hack — I just wrote a shell script followed by an alias ("buildRun") to trigger a deploy preview on netlify. So essentially every time I perform buildRun on the terminal, it does npm run build & takes the build folder and overrides the previously deployed build file (on my subdomain), and the cool part is that, since the path and domain remains the same, the overriding performed does purge all previously stored cache duing the previous build, so it's fresh everytime!

[Neilblaze]

@frank-zsy made the changes, preview it here 🚀

[Neilblaze]

@frank-zsy PTAL!

[frank-zsy]

@Neilblaze I have made a bit change in the title because the Chinese version should to be translated.

LGTM and thanks for the start.

[Neilblaze]

@frank-zsy Oh my bad, yes, i18n should be the folder where I keep the EN variant and the default docs should have the To be Translated label since the defaultLocale is ZH, thanks for the edit!