Fix formatting problems

[maltekliemann]

While reading the docs, I noticed some formatting problems and went down the rabbit hole:

• Indentation of Rust code in code blocks is often broken (2 space indents or tabs for indents)
• Markdown indentation isn't always correct, leading to broken enumerations and incorrectly indented text and code blocks
• Inconsistent rust code style

I've also noticed that running prettier on some of the files significantly changes some code, like that following <Message expressions. Is this indented? I have not committed the changes proposed by the auto-formatter.

[sacha-l]

@maltekliemann - Thanks for this! Curious: did you fun a formatting tool to do this? Need to run the PR locally to double check, but looks good to me.

[maltekliemann]

@sacha-l No, unfortunately, this had to be done by hand (except for replacing tabs with spaces). For example, you can't correct the indentation of enumeration items with a formatter - how is the formatter supposed to know where the indentation starts/ends? :)

[sacha-l]

Cool - Yeah ! Unfortunately there is no ideal way to do this and although prettier is sometimes useful, other times it completely messes things up 🥶 🤷🏻

[sacha-l]

So much better this way, thanks again.

[maltekliemann]

Glad I could help! 👍

[sacha-l]

Just resolving merge conflicts.

[sacha-l]

Just resolving merge conflicts.

Update: resolved most merge conflicts with the exception of /v3/tutorials/11-kitties-workshop/b-kitties-frontend/index.mdx . Can you have a look there and also address @nukemandan's request? Thanks.

[maltekliemann]

This should fix the merge conflict. No idea why the CI fails now.

I'll get on replacing the spaces with tabs, and I'll use the option that's not broken by prettier (see above).

[maltekliemann]

So what's going on with #666?

[nuke-web3]

Check links unfortunately fails always due to docer CI auth keys not being available for non-org members 🙄 safe to ignore, but we should check locally for sure if you touched URLs anywhere.

[nuke-web3]

Did a yarn fmt and hand cleaned all files to work at aminimum with this cc @sacha-l please remember to run this in your PRs moving forward ;)

I also ran yarn server:fresh and the yarn checklinks locally - found a broken img too.

[nuke-web3]

ummmm wtf? I did not merge this. Now it's missing things. This automation @sacha-l for develop? should be turned off asap.

[nuke-web3]

https://github.com/substrate-developer-hub/substrate-docs/commits/develop somehow it's right here. 🤷
moving forward @maltekliemann I hope you keep contributing!! 😁

Please do target main and read our contributor guidelines to get a feel for the flow we are (attepting!!) to workout. #4

[maltekliemann]

Thanks! 👍 I'll check out the guide and will try to keep up the contributions as I learn!