docs: 📝Update README to improve Markdown linting and structure

[okineadev]

Description

Improved and simplified centering of elements, added exclusion of some rules for markdownlint, allowed to use HTML only where it is really necessary (tags for centering elements) and nowhere else, this will prevent the use of HTML instead of native Markdown, which will positively affect the readability of the code

[patak-dev]

Thanks! It seems we are missing some padding after the logo after the PR

[okineadev]

Thanks! It seems we are missing some padding after the logo after the PR

Fixed in e1e3005 👍

[patak-dev]

The current one with more padding feels more balanced 🤔

[okineadev]

The current one with more padding feels more balanced 🤔

Fixed in 475ea5d

[okineadev]

Done.

[patak-dev]

I'll let others take a look before, to be honest the added markdownlint comments are quite noisy.

[okineadev]

I'll let others take a look before, to be honest the added markdownlint comments are quite noisy.

They do not interfere with anything and do not bite

[okineadev]

A little off topic
I think it would be good to move the name to the logo so that it is easier to recognize the name of the tool:

---

      Vite ⚡

[sapphi-red]

If we want to introduce markdownlint, I think we should add it to the CI, otherwise people that installed it might get a lint error that was edited by people that didn't install it.
But I don't think it's needed for us (at least for me), because I don't have strong preference with code styles of markdown files and I check the code correctness by the preview. I assume it does not support vitepress's syntaxes and the files that can be linted will be quite limited in that case. Also some stylistic rules may conflict with prettier and resolving that might take time more than it's worth.

[okineadev]

If we want to introduce markdownlint, I think we should add it to the CI, otherwise people that installed it might get a lint error that was edited by people that didn't install it.
But I don't think it's needed for us (at least for me), because I don't have strong preference with code styles of markdown files and I check the code correctness by the preview. I assume it does not support vitepress's syntaxes and the files that can be linted will be quite limited in that case. Also some stylistic rules may conflict with prettier and resolving that might take time more than it's worth.

Look, I'm not planning to add CI for linting now, I want it to be at least this way now, I'll look at the vitepres support later

Let this PR stay.

[bluwy]

Tbh I don't really see the point of changing the markup and looking the same anyways. Sorry to be a bit harsh here, but I'd appreciate if the PRs were addressing actual bugs or issues, rather than subjective / own-opinion / styling changes, especially for first time contributions.

[okineadev]

Tbh I don't really see the point of changing the markup and looking the same anyways. Sorry to be a bit harsh here, but I'd appreciate if the PRs were addressing actual bugs or issues, rather than subjective / own-opinion / styling changes, especially for first time contributions.

Well, you suffocated..

[okineadev]

review